Structured brief for preparing permanent secretary demos. Fill in each section as information arrives from Leanne, Tina, and the team.
Rolling individual sessions with permanent secretaries. Emma arranging one-by-one. Coordinate with Alonzo's pitch deck — avoid duplicate artefacts.
For each target department: who is the permanent secretary, what are their priorities, what citizen services do they run, and what's the "so what" that will make them care?
5 persona/user journey briefs from Leanne. Each needs: department focus, persona type, situation context, nightmare scenario (today), and agent solution (future). These drive the handout content and prototype data.
What goes wrong for this citizen today? How many forms, calls, departments, weeks does it take?
How does the agent handle this? What's different? How long does it take? What's the citizen experience?
TBC
TBC
TBC
TBC
TBC
TBC
TBC
TBC
For each new service needed in the demo, what artefacts must be authored? Map from the data requirements spreadsheet. This table will be populated once scenarios are confirmed.
| Service | Dept | Manifest | Policy | State Model | Consent | Instructions |
|---|---|---|---|---|---|---|
| Apply Universal Credit | DWP | ✓ | ✓ | ✓ | ✓ | ✓ |
| Check State Pension | DWP | ✓ | ✓ | ✓ | ✓ | ✓ |
| Renew Driving Licence | DVLA | ✓ | ✓ | ✓ | ✓ | ✓ |
Physical handouts, not screen presentations. This is the proven approach. Each department gets a tailored set. Coordinate with Alonzo's pitch deck to avoid duplication.
Department-specific nightmare scenario. Real numbers: how many forms, how many departments, how many weeks. Make the pain tangible. Include cost figures (X envelopes + X stamps = Y cost).
Screenshots of the citizen-dept prototype showing the journey. Annotated: what the agent does at each step, what data it uses, what the citizen sees. Before/after contrast.
The legibility requirements: which artefacts your department needs to publish (manifest, policy, state model, consent). What exists today vs what's needed. Gap analysis from the studio.
Interactive examples made static: processing costs saved, call centre volume reduction, faster outcomes for citizens. Department-specific numbers where possible.
The two-act structure: "this is what citizens get" then "this is what we need from you." The handout walks through this — the conversation follows the same arc.
Open with the nightmare scenario. Make it personal, specific to this department. "Sarah just lost her husband. Here's what she has to do right now, across your department and four others."
Walk through the handout screenshots. "Here's what Sarah sees instead. One conversation. The agent handles the complexity." Point out: consent, transparency, audit trail.
"Here's what happened under the hood." Show the evidence trail, the artefact structure, the gap analysis. "Your department's services need these artefacts to be legible to agents."
Hard numbers. Processing costs, call volumes, citizen time saved. "This isn't just better for citizens — it's cheaper for you."
"Here's specifically what we need from your department. These are the artefacts. This is the work. Here's how we help you get there." Leave the handout. Follow up in a week.
What does "this went well" look like for each meeting?
Things to resolve before building.