Merge pull request #216 from NHSDigital/ppp-post-fixes

Post NHSUK frontend tidy up for personalised prevention posts

Author: Demotive

app/posts/personalised-prevention-platform/2025/03/2025-03-20-discovery-summary.md

@@ -19,11 +19,13 @@ Can we help people to proactively manage their health, rather than relying on a
 
 ## Our problem statement
 
-<blockquote class="govuk-inset-text govuk-!-margin-left-0">
-  <p>Many people are at risk of developing - or already have - one or more health conditions.</p>
-  <p>People often don’t know where or how to access the services that could best help them manage or improve their health. Healthcare professionals can also struggle to find services to recommend.</p>
-  <p>We also often don’t know how well services are meeting people’s needs. That means if people do find and use a service, we don’t have a way to help them stay motivated to keep using that service, or to help them find alternatives if the service doesn't work.</p>
-</blockquote>
+> [!NOTE]
+> Many people are at risk of developing - or already have - one or more health conditions.
+>
+> People often don’t know where or how to access the services that could best help them manage or improve their health. Healthcare professionals can also struggle to find services to recommend.
+>
+> We also often don’t know how well services are meeting people’s needs. That means if people do find and use a service, we don’t have a way to help them stay motivated to keep using that service, or to help them find alternatives if the service doesn't work.
+
 
 Our current problem statement has evolved over the course of discovery as we learned more about the problem we were trying to understand. It may change as we learn more in the alpha.
 
@@ -113,7 +115,13 @@ To this end we explored:
 -	potential sources of structured information about users and services, and applicable standards
 -	broad concepts of how a platform might recommend the most appropriate preventative services to users
 
-![A thumbnail view of our mapping document used to explore the problem space.](prevention-platform-discovery.png "We mapped the problem space using broad stages of the user journey that could be experienced by people deciding (or being prompted) to act, choosing, then using a preventative service.")
+{% from "nhsuk/components/images/macro.njk" import image as nhsukImage %}
+{{ nhsukImage({
+  classes: "app-media--full-width",
+  src: "prevention-platform-discovery.png",
+  alt: "A thumbnail view of our mapping document used to explore the problem space.",
+  caption: "We mapped the problem space using broad stages of the user journey that could be experienced by people deciding (or being prompted) to act, choosing, then using a preventative service."
+}) }}
 
 [Download a PDF of the discovery map (103kb)](prevention-platform-discovery.pdf)
 

app/posts/personalised-prevention-platform/2025/04/2025-04-11-onboarding-users.md

@@ -9,15 +9,15 @@ tags:
 
 The personalised prevention platform (PPP) team has moved into an alpha phase.
 
-<figure>
-    <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">
-      <p>Alpha is where you try out different solutions to the problems you learnt about during discovery.</p>
-      <p>Spend alpha building prototypes and testing different ideas. And do not be afraid to challenge the way things are done at the moment: alpha is a chance to explore new approaches.</p>
-      <p>You do not have to prototype the user’s entire wider journey.</p>
-      <p>You might not even want to prototype all of the transaction or element you’re working on: often it makes sense just to focus on the areas you think will be most challenging. This lets you do the minimum you need to test your riskiest assumptions.</p>
-    </blockquote>
-    <figcaption>From the <a href="https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works">GOV.UK Service Manual</a></figcaption>
-</figure>
+> Alpha is where you try out different solutions to the problems you learnt about during discovery.
+>
+> Spend alpha building prototypes and testing different ideas. And do not be afraid to challenge the way things are done at the moment: alpha is a chance to explore new approaches.
+>
+> You do not have to prototype the user’s entire wider journey.
+>
+> You might not even want to prototype all of the transaction or element you’re working on: often it makes sense just to focus on the areas you think will be most challenging. This lets you do the minimum you need to test your riskiest assumptions.
+>
+> -- From the [GOV.UK Service Manual](https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works)
 
 Amongst other things we’re building html prototypes to explore and test our hypotheses, and have just completed our first round, concerned with ‘onboarding’.
 
@@ -42,10 +42,13 @@ We also made the following assumptions:
 - our scenario starts from an NHS.UK calculator
 - users are already somehow digitally registered ‘with the NHS’
 
-<figure class="govuk-!-margin-top-7">
-  <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;">
-  <figcaption>The prototype journey from left to right, from calculator result to a ‘finding services’ loading screen.</figcaption>
-</figure>
+{% from "nhsuk/components/images/macro.njk" import image as nhsukImage %}
+{{ nhsukImage({
+  classes: "app-media--full-width",
+  src: "prototype-flow.png",
+  alt: "Diagram depicting the prototype user journey using sequential screen grabs from left to right.",
+  caption: "The prototype journey from left to right, from calculator result to a ‘finding services’ loading screen."
+}) }}
 
 We ran 6 sessions with people who live in deprived areas of England (within the top 20 areas on the Index of Multiple Deprivation), and have more than one of the following health risk factors:
 

app/posts/personalised-prevention-platform/2025/08/2025-08-29-name.md

@@ -0,0 +1,63 @@
+---
+title: "Recommendations to users"
+description: "Presented with useful and relevant options, do people feel encouraged to take up activities?"
+date: 2025-08-29
+tags:
+- prototyping
+---
+
+
+Hello! We’ve undergone a mild rebrand. We are now known as the Weight Management team, under Personalised Prevention Services.
+
+Prior to this we were the Personalised Prevention Platform (PPP). A lot of our underlying thinking still stands. Thus:
+
+* Our thin steel thread is an end-to-end prevention journey for weight management.
+* We want people feeling supported to make healthier choices that stick.
+
+Our [previous post](/personalised-prevention-platform/2025/04/onboarding-users/) talked about how we've been exploring how we introduce our service to users, and find out a bit about them, through an “onboarding” process.
+
+In this post I’m going to talk about the next stage: recommending next steps.
+
+## Why we did what we did
+
+Our target group of users [is er, dammit]
+
+Everyone in our user research has been aware that they could be doing more to maintain their health.
+
+However people are unaware of the range of places they could get help from – from self-directed apps to in-person programmes to regular community events.
+
+Our [proposition / reckon etc] is that by presenting useful and relevant options irrespective of funding bodies(?) people can be encouraged to take up [activities].
+
+We also [reckon] that if we can find a way to follow up and check in with people, we increase their chances of success
+
+## What we did and how we did it
+
+Service listing and filtering story (2 or 3 iterations?)
+- understanding of the zoom in and out
+- seeing what people made of the offering
+IMAGE - iterations L to R
+
+Service display story (2 or 3 iterations?)
+- From blocking to allowing
+- Information and jazz hands - imagery and logos etc
+- The right level of info - what's pragmatic and possible vs the ultimate ideal
+IMAGE - iterations L to R
+
+Opting into checking in
+- People want robot seals
+IMAGE - iterations L to R
+
+(Act III - resolution) What we learnt
+
+Since discovery[LINKY], we've proved that recommending a blend of national and local services has real value to people.
+"National" and "local" is a false organisational distinction - people are interested in Active 10 and they are also interested in the local Parkrun or free online workouts. Where the thing “comes from” is largely irrelevant.
+We genuinely had people ask if things were real, and then make notes to look them up afterwards.
+We cannot reliably get a user to commit to a recommendation in the moment
+- enough info at granular level to make that decision
+- the nature of deciding to do a thing may well mean stewing on it for a bit
+- blocking the user's journey towards an outcome in order to get a declaration of intent is simply an interaction antipattern - it's only us that needs this, not the user
+
+(Epilogue) What we’re doing next
+
+- Latest work is around "the very first check in"
+- Jumping the gap between presenting the options and figuring out if something's being done