Core concepts (Good Services)
These are the minimal shared definitions used by this skill.
Service, steps, tasks
- Service: something that helps someone to do something. The user's goal defines the service boundary — it can cross multiple organisations and channels, but to the user it feels like one continuous journey.
- Steps: the major parts of the service that give users visibility and control at important decision points (for example: “choose a plan”, “prove identity”, “confirm details”).
- Tasks: the individual actions a user (or staff/system) performs to complete a step (for example: “upload a document”, “enter address”, “review confirmation email”).
Design implication: don't optimise a single touchpoint at the expense of the end-to-end outcome. A “great” step inside a broken service is still a broken service.
Channels are part of the service
Assume services are multi-channel unless proven otherwise:
- Digital (web/app)
- Phone
- Post/email
- In-person (appointments, retail, reception)
- Physical artefacts (letters, cards, forms, devices)
A “digital service” often still depends on physical and human steps. Treat these as first-class parts of the design.
Frontstage vs backstage (service blueprint)
A simple way to think about operational design:
- User actions: what the user does
- Frontstage: what users see (interfaces, staff interactions, messages)
- Backstage: what staff/systems do that users don't see (verification, routing, casework)
- Support processes: upstream/downstream systems and policies (databases, payment rails, legal requirements, staffing)
If your blueprint fails backstage, the user experience fails regardless of how polished the UI is.
Naming principle: prefer verbs
Users search for actions and outcomes. Organisations often name services with internal nouns (programmes, departments, acronyms).
Heuristic:
- Good service name: “get help with court fees”, “change my address”, “cancel my subscription”
- Risky service name: “Fee Remission”, “CRM Portal”, “SORN”
“Good” is three-way
A service is “good” when it is:
- Good for users: helps them achieve outcomes safely and without unnecessary effort
- Good for the providing organisation: sustainable to run (cost, risk, capacity) and aligned with goals
- Good for society: does not create avoidable harm (exclusion, environmental damage, perverse incentives)
Use this triad when choosing measures and prioritising improvements.