Skip to content
Ben P edited this page Sep 18, 2018 · 4 revisions

Transition Information and UX research Resources

Links in this doc are restricted. Reach out to @michaelccata for access.

Origin story

OPM was the target of a data breach between 2014 and March 2015. As a result, OPM’s Federal Investigative Service (FIS) became NBIB, National Background Investigation Bureau. A memo was issued that gave DoD (specifically DISA) responsibility to build and maintain all new NBIB IT systems. However, OPM is still responsible for existing NBIB systems. In early 2016, OPM’s CIO shop began discussions with TTS to use the Agile BPA to re-design e-QIP. DISA and PAC stakeholders were involved with the project from its inception. Mid-2016, OPM signed a tripartite IAA with TTS (and FAS AAS) to help find a great vendor to help them rebuild the applicant-facing portion of e-QIP, now known as eApp. TTS’s IAA for eApp is with OPM because NBIB didn’t yet exist when the project began, but DISA assumed product ownership for this effort in FY17. September 2017, DISA signed a second IAA with TTS to help determine the path forward to replace the agency-side portion of e-QIP that federal agency representatives use to track their personnel and contractors through the background investigation process.

Project Summary

Maps

  • Initial 2017 Mapping of some process journeys after talking with those users and visiting several Army/DOD processing facilities. (pdf)
  • eApp Customer Journey Map (pdf) (sketch)
  • eApp Customer Communication Opportunities (pdf)

Interviews & Insights

2107 Initial Research

  • Interviews with current eQIP agency users and their themes and pain points. (mural)

Summer 2018 Research

  • UX Research Update (slides)
  • Collected Insights from Agency users (mural)
  • Collected Insights from Applicant users (mural)

Content Review

  • eApp content reviewed/rewritten - includes rewritten questions that would require a policy change to implement (doc)
  • List of questions, their help text and error text. Contains highlights and comments on things that seemed weird (spreadsheet )

Usability Testing Resources

Testing Notes In the past we’ve done a mix of usertesting.com and in person or video usability testing (roughly 5-7 users a sprint). Occasionally this has included people who use screenreaders but we have not done a large push to research this audience. Users and devices have not been part of research segmentation in the past, but its recommended that in the future there is very intentional and segment by device, usability, technical competency, contractor vs. federal hire, pc vs mac, etc.

Feedback collection options

Pilot Feedback

Continual Qualitative Collection

  • Rate this form/open answer feedback form
  • A version of this form could always be attached on final page in eApp after an applicant submits their form for continued qualitative data collection and usability testers