USDS / CMS / Current work
Make provider-data complexity usable.
Research, interaction design, and implementation review within a small team building the National Provider Directory.
- My role
- Digital Services Expert (Design)
- Context
- US Digital Service, on detail at CMS
- Scope
- Design and research within a small team
- Status
- Ongoing
The operating problem
The data depends on people and responsibilities.
A provider directory depends on people maintaining information, understanding responsibility, and working across organizational boundaries. Technical completeness alone does not make those workflows usable.
Providers and delegates need to understand what they can do, which information they are responsible for, and how a task connects with the wider service.
My contribution
Carry evidence through delivery.
I connect research questions with interaction design, coded prototypes, acceptance criteria, and implementation review. The aim is to make assumptions testable and keep the user’s workflow visible throughout delivery.
The work is part of a multidisciplinary team. My design and research contribution sits alongside product, engineering, and agency responsibilities.
Choices in the work
Three connected decisions.
Examine responsibility and handoffs
Consider how providers and delegates maintain information, including permissions and transitions between people.
Make uncertainty testable
Use prototypes to make assumptions concrete and identify what needs to be learned from people doing the work.
Review the implemented experience
Connect design intent with acceptance criteria and implementation review so the delivered behavior can be examined.
Evidence and limits
An ongoing practice story.
The National Provider Directory is public, and the work is ongoing. This account describes responsibility and approach rather than claiming a measured production outcome.
Research findings, prototype results, and production outcomes answer different questions. Internal artifacts and specific findings are excluded from this account until approved for publication.
Reflection
Keep the workflow in view.
Design intent has to survive the transition from research to requirements to implementation. Connecting those stages creates opportunities to question assumptions and improve the next decision.
Discuss this work: rob@robfay.com