Prompts
Service-blueprint drafter
draft a service blueprint linking user actions to front-stage and back-stage support
ResearchDigitalCLARA
Output: Markdown service blueprint with stages, customer actions, front-stage, back-stage, and support processes.
Paste into a CLARA-enabled chat
CLARA will confirm the route, ask for anything she still needs in one batched question, and show you the draft before filing.
Use CLARA's `service-blueprint-drafter` for <programme name>.What CLARA will ask you for
- Programme name — your programme's name (e.g. SKYPROTECT).
- Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or
Programme-wideif it spans tracks. - Journey — page reference under
Knowledge Base/{{track}}/Journeys/*. - Inputs — CLARA will search the programme's Confluence space for journey map for the same scope; persona for the journey; system context — systems, tools, and back-stage teams involved. You can also paste fresh material if it's not in Confluence yet.
Where the output lands
Knowledge Base/{{track}}/Service blueprints/{{journey-scope}} inside your programme's Confluence space.
Tips
- Service blueprints expose the cost of design choices the journey map doesn't show. A "simpler" front-stage often means more back-stage work, not less.
- The handoffs section is where the most surprising findings tend to surface. A back-stage handover that goes through three teams is a place where things break.
- Pair the output with a Napkin AI diagram so the layers are visually distinct.
Where this fits in the chain
Use after
These prompts produce outputs you can paste as inputs here.