From blueprint to bot: Designing resilient AI-powered services
Summary
This case study shares how service design helped us make that shift by:
1. Helping front-line staff see AI as a collaborator
2. Preparing customers for a new kind of interaction at different stages of their customer journey by involving sales and customer service agents
3. A data driven approach to aligning internal processes, systems and workflows
Key Insights
-
•
82% of companies worldwide are using or exploring AI due to competitive and investor pressure.
-
•
AI failures are unpredictable because AI models hallucinate, so designing for resilience is essential.
-
•
C-suite leaders often expect flawless, scalable AI impact but must see AI rollout as a learning pilot.
-
•
Service design can untangle organizational complexity by aligning strategy, orchestration, and implementation layers.
-
•
Orchestration teams translate high-level AI strategy into actionable workflows to anticipate downstream effects.
-
•
Product teams must design fallback mechanisms for predictable failures and iterate based on real-world AI errors.
-
•
Involving frontline staff as co-creators reduces AI anxiety and improves AI adoption and fallback design.
-
•
Continuous feedback loops across organizational layers enable timely learning and more resilient AI services.
-
•
Framing AI deployment as an experiment or pilot aligns stakeholders to expect failures and focus on learning.
-
•
Performance metrics should go beyond containment rates to reflect customer experience and resilience over time.
Notable Quotes
"With AI, we don’t want to save a few minutes here and there. We want something that has a large impact and can scale really fast."
"AI models hallucinate when they fail, they fail unpredictably."
"Every feature release with AI is really an experiment, not a finished feature."
"If you only design for the ideal experience, you might panic and hire back human help when things don’t go as planned."
"Service designers can help the organization untangle complexity across layers so they collaborate effectively."
"Frontline staff should feel ownership, not fear, around AI implementation."
"Involving frontline staff as co-creators helps ensure AI is a collaborator rather than a threat."
"We must build our service vision not just for the ideal, but for how to handle things when they go wrong."
"It’s important to establish feedback loops so each organizational layer learns from the others continuously."
"Framing AI introduction as a pilot helps stakeholders understand it’s a learning experience to build resilience."
Or choose a question:
More Videos
"Design thinking is the scientific method for the 21st century."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"The most powerful word in the design ops vocabulary is no."
Rachel Posman John Calhoun"Ask Me Anything" with Rachel Posman and John Calhoun, Authors of the Upcoming Rosenfeld Book, The Design Conductors
September 25, 2024
"The official time zone of this conference is Pacific time."
Bria AlexanderOpening Remarks
June 10, 2021
"Designers embedded alongside technical teams can spot unseen issues in the spaces between operational silos."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"I am the shock absorber for everything that’s happening so my boss can focus on bigger priorities."
Lisa GirondaOpener: Chief of Staff–An unexpected journey
January 8, 2024
"The lack of consistency between healthcare IT systems causes critical information delays and interrupted care."
Lais de Almeida Maria IzquierdoDesigning Data Services
December 4, 2024
"Craft is not just about a beautiful final object, but a facilitative anchor that enables productive teamwork across departments."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Alert fatigue is real; users can't be burdened with constant security decisions or they'll ignore them."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"In enterprise, we’re moving from systems of record, to systems of engagement, to systems of assets where context drives experience."
Greg PetroffEverything is About to Change: Software as Material
June 8, 2016
