For Service Design and Service Delivery Leads
Use this route when service change requires interpretation quality, stakeholder legitimacy, and accountable follow-through. Service leaders often need to balance human experience, operational constraints, and decision cadence.
What goes wrong when this is skipped
When service redesign starts without boundary and authority clarity, teams act quickly but cannot explain trade-offs later. That increases implementation churn and stakeholder resistance.
Typical triggers
- Service changes affect multiple stakeholder groups.
- Existing feedback loops surface issues but not actionable direction.
- Teams need a defensible path from listening to service adjustment.
- Delivery units require clear ownership and review cadence.
Start here
Start with the orientation to set boundaries and next-step posture before delivery. If you are still learning the method, begin with Studio.
- Start with the orientation when authority, governance, policy risk, or shared delivery is active.
- Use Studio or Inquiry when one bounded setup is enough.
- Begin with Studio if you are still learning the method.
- Need scoped support? Talk with us.