One structure for every blueprint.
The classic service blueprint, lines included. Each lane takes one kind of card.
- Inputs
- What a phase needs to start.
- Human actor
- Who acts, what they decide, what it does to their role.
- Frontstage UX
- The screen they see.
- Agent proposals
- What an agent puts up for a person to confirm.
- Agent autonomous
- Work that runs in the background, with an audit log.
- Systems and data
- What gets read or written.
- Outputs
- What the phase hands on.
Time runs left to right. Dashed lines separate the lanes.
The solid line marks where agent work leaves the screen. Where you put a card against it is a design choice, so the editor makes you choose.
One decision per card.
A human card names the impact on the role. An agent card sets how much it may do alone. The editor warns when too many roles get deskilled.
- ElevateThe role gains judgment work.
- AugmentThe role keeps the decision, with better input.
- ReplaceThe role no longer does this step.
- DeskillThe role keeps the step and loses the judgment.
- AutonomousActs and logs. Nobody confirms.
- Propose and confirmDrafts. A person confirms.
- GatedWaits for a go from a named role.
Hard to get wrong.
- Cards stay in their lane. Drag sideways to change the phase.
- Handoffs appear on their own when an output chip matches the next phase's input.
- Filter by pain theme. Cards that miss it dim.
- Add a phase anywhere. Connections stay valid.
- Undo, redo, autosave.
- A copilot drafts the first version from one paragraph about the service.
