Skip to content

PPP User Personas ​

Status: Awaiting product owner confirmation — see #4461

These are draft personas. Matt to confirm, correct, or add before this document is considered final. Questions for Matt are listed at the bottom of each profile.

These personas give the whole team a shared language. Instead of saying "a user", we can say "Dr Sarah (FY2 trainee)" or "Mr James (Consultant)". Every user journey, bug report, and feature spec should reference one of these personas.


P1 — Dr Sarah · FY2 Foundation Doctor ​

FieldDetail
RoleFoundation Year 2 doctor
Career stageJunior — 2nd year post-graduation, completing Foundation Programme
CountryUnited Kingdom
SubscriptionPPP Full Platform
Dashboard/ppp-dashboard
GoalComplete the Foundation Programme ePortfolio requirements, pass ARCP, and build evidence for specialty applications
Success looks likeAll WPBAs, reflections, and CPD activities logged; ARCP signed off; strong personal portfolio ready for specialty application
Pain pointsToo many tools to maintain (paper, Horus, separate CPD tracker); hard to find evidence when preparing for ARCP at short notice; supervisors are hard to pin down for signatures

Typical workflows ​

  • Logging a workplace-based assessment (DOPS, mini-CEX, CBD) immediately after a procedure
  • Uploading a reflection after a clinical incident or significant event
  • Preparing an ARCP portfolio with supervisor sign-off
  • Tracking CPD hours against Foundation Curriculum domains

P2 — Dr Priya · Specialty Registrar (ST5 Surgical) ​

FieldDetail
RoleSpecialty Registrar — ST5 (Higher Surgical Training)
Career stageMid-training — 5 years post-foundation, pursuing surgical subspecialty
CountryUnited Kingdom (some users: Australia)
SubscriptionPPP Full Platform
Dashboard/ppp-dashboard
GoalBuild a high-quality surgical logbook for CESR / FRCS; demonstrate operative exposure across required procedure categories; prepare for Penultimate Year Assessment (PYA)
Success looks likeLogbook shows required case numbers in all procedure categories; trainer feedback is positive; PYA/ARCP passed; ready for CCT application
Pain pointsLogging complex multi-step procedures is slow during busy theatre lists; hard to prove case mix spread across specialties; supervisors based across different hospitals

Typical workflows ​

  • Adding a surgical case to the logbook from theatre (procedure, grade, supervision level, notes)
  • Attaching a supervisor assessment to a specific logbook entry
  • Running a procedure count report by category for ARCP evidence
  • Preparing a Case-Based Discussion with logbook-linked evidence

P3 — Mr James · Consultant ​

FieldDetail
RoleNHS Consultant Surgeon (established specialist)
Career stagePost-CCT — 10+ years in practice
CountryUnited Kingdom
SubscriptionCPD Home
Dashboard/cpd-dashboard
GoalComplete annual GMC revalidation requirements; log CPD activities; collect multi-source feedback; submit appraisal documentation
Success looks like50 CPD credits logged per year; MSF and patient survey complete; appraisal submitted on time; no revalidation flags
Pain pointsCPD logging feels administrative and disconnected from real learning; MSF collection is awkward; appraisal paperwork is time-consuming

Typical workflows ​

  • Adding a CPD activity (conference, audit, journal club) with supporting evidence
  • Requesting multi-source feedback from colleagues
  • Generating an annual CPD summary for appraisal
  • Uploading the completed appraisal form and linking CPD evidence

P4 — Dr Amira · GP ​

FieldDetail
RoleGP Partner
Career stageEstablished — 8 years post-CCT
CountryUnited Kingdom
SubscriptionCPD Home
Dashboard/cpd-dashboard
GoalStay compliant with RCGP revalidation; log CPD activities efficiently; maintain evidence for annual appraisal without it consuming clinical time
Success looks likeAll CPD requirements met; appraisal prepared in <2 hours; no last-minute scramble; clean revalidation record
Pain pointsCPD logging is a chore squeezed into evenings; difficult to remember what counts as CPD; appraisal submissions feel bureaucratic

Typical workflows ​

  • Quickly logging a CPD activity from a mobile device between consultations
  • Tagging activities by RCGP curriculum area
  • Running a year-end CPD report for appraisal submission
  • Reviewing the CPD plan and identifying gaps before the appraisal date

P5 — Claire · Hospital Admin (Team Manager) ​

FieldDetail
RoleMedical Education Manager / Postgraduate Training Coordinator
Career stageNon-clinical administrator, 5+ years in medical education management
CountryUnited Kingdom
SubscriptionHospital Admin (institutional account)
Dashboard/hospital-admin
GoalOversee the training portfolios of 20–30 junior doctors; monitor ARCP readiness; flag trainees who are at risk of failing their assessment
Success looks likeAll trainees are engaged with their portfolios; no surprises at ARCP; TPD has clean evidence for every trainee; no compliance gaps
Pain pointsNo visibility into which trainees are behind; chasing trainees for updates is manual; no easy way to compare across cohorts or flag early warning signs

Typical workflows ​

  • Viewing a dashboard of all trainees and their portfolio completion status
  • Identifying trainees who have not logged any activity in 30+ days
  • Exporting a cohort report ahead of an ARCP panel meeting
  • Messaging a trainee in-app to prompt them to complete outstanding tasks

Questions for Matt (product owner) ​

These personas are drafted from the team's understanding of PPP users. Matt to review and confirm before #4461 is closed:

  1. Are these 5 personas the right ones? Are there important user types missing?
  2. Naming — Do any personas need renaming to match how the team talks about users internally?
  3. Missing personas — Should we add: international users (AUS/NZ trainees), nurses, allied health professionals, private sector consultants?
  4. P1 vs P2 — Is the Foundation/Registrar distinction meaningful enough to keep as separate personas, or should they merge into a single "trainee" persona?
  5. P5 scope — Is Hospital Admin used by training programme directors (TPDs) as well as admin staff? Should we split these?
  6. Country scope — Several personas are UK-only. Should Australian usage patterns be reflected in P2 (or a new persona)?

How to use these personas ​

When writing an issue, user story, or test scenario:

As P2 (Dr Priya, ST5 Registrar), I want to log a DOPS from theatre
so that I can build my operative logbook evidence for PYA.

When triaging a bug or feature request, ask: "Which persona does this affect most?"

When prioritising work, consider: "Which persona has the highest urgency for this feature?"


Referenced by: #4460 — PPP story map and user journeys

Internal documentation — org members only