|
| 1 | +--- |
| 2 | +title: "Call it a thing" |
| 3 | +description: "Investigating onboarding" |
| 4 | +date: 2025-04-21 |
| 5 | +tags: |
| 6 | +- alpha |
| 7 | +- prototyping |
| 8 | +--- |
| 9 | + |
| 10 | +## Intro or scene setting |
| 11 | + |
| 12 | +The personalised prevention platform (PPP) team have moved into an alpha phase! |
| 13 | + |
| 14 | +<figure> |
| 15 | + <blockquote class="govuk-inset-text govuk-!-margin-left-0 govuk-!-padding-left-6" cite="https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works"> |
| 16 | + <p>Alpha is where you try out different solutions to the problems you learnt about during discovery.</p> |
| 17 | + </blockquote> |
| 18 | + <figcaption>From the <a href="https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works">GOV.UK Service Manual</a></figcaption> |
| 19 | +</figure> |
| 20 | + |
| 21 | +Towards this end, we’ve completed our first round of prototyping and user research, an exploration into ideas around ‘onboarding’. |
| 22 | + |
| 23 | +To be clear, in alpha we’re building prototypes to explore further and test our hypotheses. Some elements of these prototypes may make it past alpha, and some are deliberate provocations as opposed to attempts at solutions. |
| 24 | + |
| 25 | +## What we did |
| 26 | + |
| 27 | +The things we aimed to explore were: |
| 28 | + |
| 29 | +- users’ understanding of the proposition |
| 30 | +- assumptions about consent and data sharing across the system |
| 31 | +- the need for information and guidance balanced against service finding |
| 32 | +- how to supply information and guidance as one element of a continuous transaction |
| 33 | +- system generated priorities versus a user’s priorities |
| 34 | +- barriers — the things that get in the way of making lifestyle changes |
| 35 | +- preferences — the things that make services more appealing |
| 36 | +- what sort of services might be returned after onboarding |
| 37 | + |
| 38 | +We did this by creating a mock journey that represented only the initial stages of our (WIP) service blueprint: |
| 39 | + |
| 40 | +- entry points |
| 41 | +- starting to interact with a PPP |
| 42 | +- confirming and giving information |
| 43 | + |
| 44 | +We also made the following assumptions: |
| 45 | + |
| 46 | +- our chosen scenario starts as a high height-to-waist ratio |
| 47 | +- users are already registered with NHS login |
| 48 | +- the platform has access to user information held with ‘the NHS’ |
| 49 | + |
| 50 | +<figure class="govuk-!-margin-top-7"> |
| 51 | + <img src="prototype-flow.png" alt="Diagram depicting the prototype user journey using sequential screen grabs from left to right." style="width: 92vw; max-width: 960px;"> |
| 52 | + <figcaption>The whole prototype journey from left to right, from calculator result to a ‘finding services’ loading screen.</figcaption> |
| 53 | +</figure> |
| 54 | + |
| 55 | +Our prototypes are built in code (html, css, and javascript only when needed) in order to give users hi(gh?)-fidelity and ‘real feeling’ stuff [omg rewrite]. Working in code means we can iterate and edit extremely quickly. Each prototype gets a few rounds of crit from the whole team. Er, maybe this is a waste of space. |
| 56 | + |
| 57 | +We ran 6 interview sessions with people from our initial target [audience?population?er?] |
| 58 | + |
| 59 | +## Exploring with users / how it went / or something |
| 60 | + |
| 61 | +As an example entry point we used results from the <a href="https://www.nhs.uk/health-assessment-tools/calculate-your-waist-to-height-ratio">calculate your waist to height ratio</a> tool. This represented one potential route (amongst many) into the platform. |
| 62 | + |
| 63 | +GRAB |
| 64 | + |
| 65 | +Any findings? |
| 66 | + |
| 67 | +--- |
0 commit comments