Taking a critical, legacy system and reimagining it beyond "feature parity" to create a tool that met Asylum Officer's needs and made a serious mark on a years-long backlog. Our goal: to enable Asylum Officers to focus on the most crucial aspect of their job: the Asylum interview. Our software will take care of everything else.
Overview
Users: Asylum Officers (Primary), Asylum Operations and Support Staff, Asylum Seekers
Employer: Pivotal Labs
Client: USCIS Asylum (DHS)
Role: Lead Designer
Team: Don Ruzek (Client Designer), Nick Tomaszewski (Lead Product Manager), Nicholas Leake (Client Product Manager), Eliza Aierstuck (Tech Lead), Thomas Baird (Client Tech Lead)
High-level outcomes:
In approximately two years, we rebuilt and launched a new, modern software solution to the 8 asylum offices across the U.S. The Global Asylum project saved $10MM annually for the USCIS Asylum program and reduced the security check processing time by 92% (from 24 hours to 2 hours) by decommissioning the mainframe system, as well as reducing manual data entry by 60%.
There was also a 98% reduction in the time to process work order requests for a key immigration form, 80% reduction in the time to process Asylum Pre-Screening Officer cases, and 356% increase in production deployments.
Our project was awarded a Director's Cornerstone award.
User-centered outcomes
-
Reduced manual data entry by 60%. We integrated with USCIS' Person Centric Query Service (PCQS) to pull data directly into the file for both the APSO and Affirmative case types, which helped to ensure consistent data during handoffs between government agencies.
-
Improved transparency of in-progress case status with the state machine. By aligning the status of the cases in the code with that of the asylum process, we were able to convey much more specifically where a file was located in the process. This enabled visibility into the backlog.
-
Improved transparency of case histories with the Case Log, where we built an audit trail that included data and documents and allowed asylum operations a clearer picture into the actions taken by the adjudication staff. It also allowed staff to find documents quicker with an asylee's file.
-
Case status visibility for asylees. We exposed endpoints to share file status with asylees that created visibility on where they were at in the process.
-
Improved "clock" for a case's timeline. At one point in the process an asylee could be scheduled for a biometric appointment (that is, fingerprinting) and for the asylum interview itself. Both events stopped their "clock," which counted the time until they could get authorization to work in the United States. If the asylee missed both their biometric appointment and their asylum interview, their work authorization clock would be effectively "double" stopped. We advocated for a system where the clock would restart when they completed their biometrics, rather than the asylum interview, enabling the asylee to meet the work requirement quicker. This process change demonstrates how we on the technology side can influence the policy side in favor of our users.
Process
This was a long project, and followed every stage of design and development from discovery to rollout. Throughout, however, some aspects of our process remained, and were crucial to our success. They include:
-
Weekly user interviews. Whether discovery "ride-alongs" to gain new domain knowledge, in-depth contextual deep-dives into a particular part of the process, or simple usability tests, we made it a core team practice to speak to users every single week. Over the course of the project, I was able to meet and get feedback from nearly every single member of the Asylum organization, from officers all the way to data-entry.
-
Client pairing. Part of the mission in Pivotal Labs' projects was a teaching model, in which our clients would provide us functional "pairs" for each member of the "balanced team" — design, product, and engineering — and would join us in our office to
-
Balanced team collaboration and improvement. No member worked or made a decision in a silo, and we checked in twice weekly as a team to ensure we were all aligned on what we were building and why; at the beginning of the week, during Iteration Planning meetings, and at the end of the week, during retros. In this way, we were committed to continuous improvement and self-reflection, both for the product we were building and the team we were a part of.
Over the course of this project, I was able to:
-
Plan and lead weeklong onsite Contextual Inquiry research projects
-
Lead Discovery design thinking activities with clients and stakeholders
-
Work from inclusive principles, learn accessibility best practices, and ensure the entire app conforms to WCAG 2.1/Section 508.
-
Manage stakeholder alignment and present work to upper leadership within USCIS
-
Incrementally improve an app from its smallest MVP to a robust application spanning four case types and hundreds of users
-
Get really, really, really good at forms
-
Build and implement a design system from scratch
-
Pair with engineers on front-end code and even commit front-end code by myself to make the application more responsive
Selected Screens
Video
Our colleague and primary stakeholder on the client side gave a talk at Pivotal's Spring One conference about this project, and the processes that enabled its success. You can watch this here.