Service blueprint checklist: before, during, and after the workshop
This checklist covers the full service blueprinting process from preparation through post-workshop action planning. Use it to ensure you have the right research inputs, the right people in the room, and a concrete plan for acting on findings. Each phase builds on the previous one — skipping preparation steps leads to a blueprint based on assumptions rather than evidence.
Before blueprinting
- Service scenario selected: one customer type, one channel, one process with clear start and end
- Customer research available: journey map, interview data, or support ticket analysis showing frontstage pain points
- Employee interviews completed (5-10 across departments involved in delivering the service)
- Existing process documentation collected: SOPs, system architecture diagrams, escalation flows
- Cross-functional workshop team assembled (6-12 people representing all involved departments)
- Frontline employees included — people who do the work, not just managers who describe it
- Workshop logistics set: room or virtual space, blueprint template on whiteboard or Miro, time blocked (4-8 hours)
- Stakeholder support secured for acting on findings
During the blueprinting workshop
- Customer actions mapped across the top row from research data, left to right in sequence
- Line of interaction drawn — boundary between customer and frontstage employee
- Frontstage employee actions added for each customer action
- Line of visibility drawn — boundary between what the customer sees and what is hidden
- Backstage employee actions mapped for each frontstage interaction
- Line of internal interaction drawn — boundary between employees and support systems
- Support processes and systems documented for each backstage action
- Physical evidence added above customer actions (receipts, screens, emails, signage)
- Fail points marked with [F]: what fails, how often, why, and what the customer experiences
- Wait points marked with [W]: where the customer waits, how long, and what happens backstage during the wait
- All handoffs between roles or systems identified and annotated with risk level
After blueprinting
- Blueprint validated with 2-3 frontline employees not present in the workshop
- Corrections from validation incorporated into the blueprint
- Final blueprint designed in a clean, shareable format
- Top 5 fail points summarized with root causes and recommended fixes
- Each priority improvement assigned to an owner with a timeline
- Blueprint distributed to all stakeholders and posted in shared workspace
- Blueprint referenced in upcoming sprint planning, process improvement, or service redesign
- Review cadence established: update after major process changes, system migrations, or new research
- Blueprint dated clearly so viewers know when it was last validated