Learning is the north star: service design for adaptive capacity
Summary
Service design isn’t just about designing services –it’s about shaping the conditions for services to evolve. At its best, it’s a systems-oriented practice that helps people make sense of complexity, appreciate interdependencies, and act decisively amid uncertainty. This session explores how service design builds adaptive capacity across teams, programs, and enterprises through three case studies: a strategy sprint that helped a cross-functional team navigate shifting learner expectations and identify small, feasible next moves; a “learn by doing” initiative in healthcare that combined qualitative research, ecosystem mapping, and narrative sensemaking to link policy decisions with lived experience; and an enterprise-wide collaboration effort that aligned diverse stakeholders around quality and population health goals while strengthening informal networks and emergent coordination. Across these examples, service design functions less as an orchestrating function and more as a catalyst for organizational learning, highlighting a shift from engineering fixed plans to enabling ongoing adaptation, where performance emerges from systems capable of sensing, interpreting, and responding together.
Key Insights
-
•
Organizations often fall into single-loop learning, trying harder rather than smarter, like Wiley Coyote repeating failed experiments without real reflection.
-
•
Complex adaptive systems, common in service design, defy traditional planning and KPI measurement due to their unpredictable, non-linear nature.
-
•
The Cynefin framework helps distinguish clear, complicated, complex, and chaotic systems, with complexity requiring emergent, reflective practices rather than fixed recipes.
-
•
Learning in complex systems is not merely acquiring knowledge but a shift in understanding that changes future actions, emphasizing adaptation.
-
•
Adaptive capacity is the ability of people, teams, or systems to sense change, learn from it, and respond effectively amidst uncertainty.
-
•
Service design techniques can build adaptive capacity at multiple scales—from small teams to enterprise-wide initiatives—by fostering sense-making and collaboration.
-
•
Traditional KPIs can create perverse incentives in complexity, favoring short-term fixes over long-term learning and experimentation.
-
•
Measuring learning involves tracking narrative changes, velocity of shared understanding, integration of new tools, participation diversity, and inquiry shifts rather than counting outputs.
-
•
Learning should be embedded as a daily practice through low-risk probes, experiments, and intentional curiosity rather than formal, large-scale pilots.
-
•
To cultivate a learning organization, model adaptive behavior yourself to become a magnet for like-minded collaborators, rather than trying to evangelize broadly from the outset.
Notable Quotes
"Wiley Coyote is the master of iteration but he never really gets much closer to his goal because he fails to learn."
"Iteration without reflection is not learning."
"Performance is about how effectively we translate experience into new understanding and turn that into wiser action."
"Complex systems are not chaos but non-deterministic due to interdependencies and autonomy within the system."
"In complex domains, best practice is past practice; what worked yesterday may not work today."
"Adaptive capacity is a fractal pattern visible at individual, team, organization, and societal levels."
"Our work as service designers is to help people see their own complex system more clearly, learn from conditions, and take the next right steps."
"Momentum over milestones. Track what's moving, not just what's finished."
"Make yourself the magnet. Be the person who models adaptive learning so others want to join."
"What would change if learning itself was not just a KPI but your North star metric?"
Or choose a question:
More Videos
"We have never played together before and never rehearsed, yet we pulled off a great rendition spontaneously."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"If your topic is already tackled exceptionally by a prior book, go deeper or wait until the market shifts."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Creating evergreen documents enables asynchronous influence — it’s not about being in the room all the time, it’s about having your voice heard."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Less than a third of respondents feel like they work somewhere with a clear investment in customer-driven decision making."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"If you can’t see a human in a video, how do you know the entire conversation wasn’t fabricated?"
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Designers have a hard time interpreting econometrics-driven quantitative research without bridging approaches."
Joshua NobleCasual Inference
October 6, 2023
"Empathy doesn’t come from reading a report—you don’t get close to users by just reading data."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We'll have a centralized Slack channel for all discussion to come together as one community."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"We often say don’t make me think. When that’s not possible, reuse and recycle those learnings."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023