Templates › Persona and scenario catalogue
Persona and scenario catalogue
Template id: scenario-catalogue
Responsible skill: copilot-adoption:scenario-discovery.
Use this catalogue to record the personas in scope and the role-based scenarios each will use. Every fact the organisation must supply is marked [To confirm: ...]; replace the marker when the fact is confirmed, and never fill it with a guess. Example rows are fictional and are there to be replaced or deleted. Every published scenario has a verification step and an owner.
1. Catalogue details
| Field | Entry |
|---|---|
| Audience in scope | [To confirm: organisation, business unit or wave] |
| Catalogue owner | [To confirm: name and role] |
| Approved Copilot experiences by persona confirmed by IT | [To confirm: date and reference] |
| Next review date | [To confirm: date] |
2. Personas
Personas are defined by ways of working, never by seniority or personal characteristics.
| Persona | Roles included | How they work (location, devices, session length) | Main frustrations | Business owner |
|---|---|---|---|---|
| Fictional example: Desk | Finance analysts, HR advisers | Office or home, laptop, long sessions | Month-end reporting, policy queries | Head of Finance Operations |
| Fictional example: Frontline | Site supervisors | On site, shared tablet, short sessions between tasks | Handover notes, finding procedures | Operations Director |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
3. Scenario scoring
Score each criterion 1 to 3. Prioritise scenarios scoring 10 or more with Verifiability and Data safety both at least 2. Data safety of 1 means a security and privacy review before publication.
| Ref | Persona | Scenario | Source | Frequency | Value | Verifiability | Data safety | Total | Priority |
|---|---|---|---|---|---|---|---|---|---|
| Fictional example: S1 | Frontline | Turn rough shift notes into a structured handover | Discovery | 3 | 3 | 3 | 3 | 12 | Starting set |
| [To confirm] | [To confirm] | [To confirm] | Discovery / Champion Challenge / Workshop | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
4. Scenario entries
Copy this block for each priority scenario.
Scenario reference and title
| Field | Entry |
|---|---|
| Persona | [To confirm] |
| Source | [To confirm: discovery, or Champion Challenge or workshop reference, contributor by role] |
| Task in the user's words | [To confirm] |
| Input the user provides | [To confirm: content they already handle; no special category data] |
| Copilot experience used | [To confirm: as confirmed by IT for this persona] |
| Prompt pattern | Goal: [To confirm]. Context: [To confirm]. Source material: [To confirm]. Format: [To confirm]. Check: [To confirm] |
| What good output looks like | [To confirm] |
| Verification step | [To confirm: how the user checks the output before using it] |
| Content relied on and its condition | [To confirm: owner and whether it is current] |
| Baseline and expected change | [To confirm: agreed with the business owner] |
| Tested by a real user | [To confirm: date and role] |
| Scenario owner | [To confirm] |
| Review date | [To confirm] |
Fictional example prompt pattern: "Goal: produce a handover note for the next shift. Context: I am a site supervisor. Source material: my notes below. Format: three headings - safety, open jobs, people. Check: I will compare every open job against the job board before sending."
5. Backlog and referrals
| Ref | Scenario | Reason not yet prioritised | Referred to opportunity intake? | Owner |
|---|---|---|---|---|
| [To confirm] | [To confirm] | [To confirm] | Yes / No | [To confirm] |
6. Champion contributions
Prompt libraries, departmental playbooks and workshop outputs from the champion-challenge-catalogue pass the same scoring, real-user test and verification step before they join the catalogue.
| Ref | Challenge or workshop reference | Contribution | Contributor (role) | Review outcome | Added as scenario refs |
|---|---|---|---|---|---|
| Fictional example: K1 | Fictional example: C1 | Prompt patterns for the weekly team report | Team coordinator | Accepted after test | Fictional example: S7 |
| [To confirm] | [To confirm] | [To confirm] | [To confirm] | Accepted / Revise / Not added | [To confirm] |
Credit: Template from CopilotForge by Simon Foote (https://github.com/SimonFoote-greensparx/CopilotForge), licensed under CC BY 4.0. Keep this credit when you share or adapt the template; in your own completed document you may keep it as a footer or remove it.