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
"You need well-defined frameworks and guardrails for experimentation success to prevent chaos across teams."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Customers rarely ask us to fix inconsistencies directly; we must watch activation rates and confusion instead."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Sometimes clarity trumps consistency depending on the context or specific use case in the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"Key Experience Indicators gave us rigor to bring into engineering conversations to make design less vague or fluffy."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"It’s really hard to make changes to these systems because it’s risk-ridden and a major undertaking."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Some people prefer their beliefs to data even in academia, which may surprise you."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"If you signed up for a cohort, please make sure you’re in your private cohort channel to meet and discuss with your group."
Bria AlexanderOpening Remarks
June 9, 2021
"Many product teams have never come face to face with their revenue numbers before."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"Design is about cultural imagination, not just problem solving."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024