Summary
Moving beyond the service blueprint or user journey map, this case study explores some of the more non-traditional outputs and outcomes driven by service design, particularly through the lens of creating long-term transformational change. Stefanie will overview a variety of recipes for achieving transformative outcomes at three levels within government agencies: the product/service experience, program-wide or platform initiatives, and fundamental agency technology operations. The challenges for each layer are unique, but also offer different opportunities for where service designers can achieve sustainable, real impact. We’ll explore specific examples achieved by a breadth of designers, product managers, and engineers working within government before exploring how this model might be replicated across other partner government agencies to achieve our vision of making more government services become as simple, effective, and accessible as possible.
Key Insights
-
•
Transformation design extends beyond service experience to include programmatic and technical infrastructure layers within government.
-
•
Nava’s dual mission combines running a healthy business with advancing structural change in public services.
-
•
Building better foundations, not just facades, ensures transformational change that outlasts specific projects.
-
•
Injecting agile iteration into government teams helps shift bureaucratic waterfall mindsets prevalent due to procurement rules.
-
•
Programs like the Biden-Harris financial life experience improve access to benefits via plain language and shared principles, influencing future policy forms like income verification.
-
•
Embedding designers on technical teams, such as the VA sandbox project, accelerates application deployment by creating smoother development and incident response workflows.
-
•
At the agency technology and operations layer, designers streamline huge processes like CMS cloud instance onboarding, cutting provisioning time from months to 48 hours.
-
•
Designers tackle administrative burdens by mapping procurement workflows, identifying policy bottlenecks, and proposing changes to prevent burnout of crucial single-role employees.
-
•
Human-centered design helps unify communication, branding, and adoption of shared enterprise services, increasing operational resilience and flexibility.
-
•
Challenges grow deeper into technical infrastructure layers due to unfamiliarity with design value, but proven track records and interagency knowledge sharing help gain buy-in.
Notable Quotes
"Build better foundations, not better facades."
"Service design may start with the product or service experience but can influence policy and infrastructure too."
"Programs that support many product teams act like well-crafted APIs, building once and used by many."
"As much as 140 billion dollars in government benefits goes unclaimed each year partly due to income verification hurdles."
"Giving technical teams a sandbox environment led to apps being built and released in a fraction of the usual time."
"Onboarding originally took months but was reduced to 48 hours through iterative design and automation."
"Contracting officers face severe consequences for deviating from policy, including life in prison, increasing operational risk."
"Designers embedded in these layers can shift enterprise-wide offerings to align with human needs and reduce administrative burden."
"What is done at one agency often becomes the playbook for success at others."
"A human-centered approach is intrinsic to Nava’s DNA and factored into procurement and project planning from the start."
Or choose a question:
More Videos
"I wish I could tell my 22-year-old self what to stop doing and what to embrace to be a better designer."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Playing politics in UX leadership is about maximizing relationships ethically to advance your agenda, not about being underhanded."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Digital is a system, not a project. It’s there all the time and you have to keep iterating on it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Transportation must evolve to be more sustainable and accessible for all."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Design your processes around learning, have blameless post mortems and celebrate failures especially."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Never be afraid to get into good trouble; start by asking why."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"If you don’t bring stakeholders into the research journey, they won’t believe or use the data."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"Randomization is magic — it evenly distributes confounds so the only difference affecting results is your change."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
