You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/posts/personalised-prevention-platform/2025/04/2025-04-21-alpha.md
+58-16Lines changed: 58 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,50 +18,92 @@ The personalised prevention platform (PPP) team have moved into an alpha phase!
18
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
19
</figure>
20
20
21
-
Towards this end, we’ve completed our first round of prototyping and user research, an exploration into ideas around ‘onboarding’.
21
+
We’ve completed our first round of prototyping and user research, an exploration into ideas around ‘onboarding’.
22
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.
23
+
We’re building prototypes to explore further and test our hypotheses.
24
+
25
+
Some parts of these prototypes could make it into a real product, and some elements are designed purely to provoke conversation in research sessions.
24
26
25
27
## What we did
26
28
27
-
The things we aimed to explore were:
29
+
We aimed to explore users’:
28
30
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
31
+
- understanding of what our potential proposition might be
32
+
- assumptions about consent and sharing their information across services
33
+
- needs for information and guidance balanced against service finding, and how to supply it within an ongoing transaction
34
+
- personal priorities versus what we (the system) are telling them
34
35
- barriers — the things that get in the way of making lifestyle changes
35
36
- preferences — the things that make services more appealing
36
-
-what sort of services might be returned after onboarding
37
+
-expectations of what that might be returned as results after going through the process
37
38
38
-
We did this by creating a mock journey that represented only the initial stages of our (WIP) service blueprint:
39
+
To help us explore these topics, we built a mock journey that represented just the initial stages a potential journey:
39
40
40
41
- entry points
41
42
- starting to interact with a PPP
42
43
- confirming and giving information
43
44
44
45
We also made the following assumptions:
45
46
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’
47
+
- our scenario starts as a high height-to-waist ratio
48
+
- users are already registered and logged in
49
49
50
50
<figureclass="govuk-!-margin-top-7">
51
51
<imgsrc="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>
52
+
<figcaption>The prototype journey from left to right, from calculator result to a ‘finding services’ loading screen.</figcaption>
53
53
</figure>
54
54
55
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
56
57
57
We ran 6 interview sessions with people from our initial target [audience?population?er?]
58
58
59
-
## Exploring with users / how it went / or something
59
+
## Exploring the prototype with users
60
+
61
+
### Entry point into the platform
62
+
63
+
As an example entry point we’ve used results from the <ahref="https://www.nhs.uk/health-assessment-tools/calculate-your-waist-to-height-ratio">calculate your waist to height ratio</a> tool. This represents one potential route (amongst many) into the platform.
64
+
65
+
GRAB
66
+
67
+
Any findings?
68
+
69
+
---
70
+
71
+
### Starting
72
+
73
+
After using the call to action, the user then hits a fairly traditional start page pattern. It’s a bit personalised in that it offers examples that make sense for a journey coming from the waist to height ratio results.
74
+
75
+
GRAB
76
+
77
+
Any findings?
78
+
79
+
---
60
80
61
-
As an example entry point we used results from the <ahref="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.
81
+
We then show a login spinner and a 2 second redirect. We do this to reinforce the illusion that the user has, at some unspecified point, already logged in. This allows us to avoid protracted discussion along the lines of ‘how could it know that?’ in the sessions.
62
82
63
83
GRAB
64
84
65
85
Any findings?
66
86
67
87
---
88
+
89
+
### Information and guidance versus finding services
90
+
91
+
The next part of the prototype is aimed at gaining insights and prompting discussion about the _relative_ value of information and guidance.
92
+
93
+
We do this by asking a simple question: do you want know more about the benefits of reducing your waist size and getting to a healthier weight?
94
+
95
+
We’re offering to ‘send you some guidance’, and giving the user the option of saying yes or no.
96
+
97
+
GRAB 1, 2, 3
98
+
99
+
Any findings?
100
+
101
+
---
102
+
103
+
### Consent
104
+
105
+
Using a fairly realistic barrier, we explore users’ assumptions and expectations about consent and data sharing across the system. Our page presents a forced consent to use a basic set of details in the platform.
0 commit comments