Skip to content

Commit af4f62f

Browse files
authored
publish-pathway-reflections-post (#446)
1 parent 7ff0e52 commit af4f62f

2 files changed

Lines changed: 76 additions & 0 deletions

File tree

  • app/breast-screening-pathway/2026/03/reflections-on-forecasting-and-planning-discovery
Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
---
2+
title: Reflections on forecasting and planning discovery
3+
description: What worked well and what we would do differently to help future discovery teams
4+
date: 2026-03-31
5+
author: Veronika Jermolina
6+
opengraphImage:
7+
src: /breast-screening-pathway/2026/03/breast-screening-in-mobile-vans/retro.png
8+
alt: Some of the retro comments
9+
tags:
10+
- discovery
11+
- retro
12+
---
13+
14+
We started building the new breast screening service by focusing on participants attending appointments, having mammograms and receiving results. We had no understanding of the parts of the service that preceded what we started building.
15+
16+
To address this gap, in December 2025 we formed a discovery team to understand how breast screening offices (BSOs) forecast demand and plan capacity. The team consisted of a selection of people in different roles already working on breast screening.
17+
18+
We ran a retrospective in February 2026 to reflect on what worked well and what we would do differently to help future discovery teams.
19+
20+
## What went well
21+
22+
### Policy and digital working together
23+
24+
Policy is a set of rules that shapes key parts of the service, from how participants are selected for screening to what data is collected. Historically, the national policy team, responsible for policy, and the digital team, responsible for IT implementation, worked separately, with limited trust between them.
25+
26+
A significant outcome of this discovery was that the two teams started working more closely together, building shared understanding for the first time.
27+
28+
### Self-organising to visit breast screening offices
29+
30+
To ensure we included a wide range of BSOs in the discovery, we needed to visit geographically dispersed locations in a short time. The team did this by organising itself into small multi-disciplinary groups of up to 3 people with clear responsibilities: leading the visit, note taking and observing.
31+
32+
Because we are based across the country, this reduced travel time and costs. It allowed people with different job roles to learn directly from frontline users and meant the team was learning together.
33+
34+
Self-organising in this way helped us form new working relationships quickly, learn different working styles and support each other.
35+
36+
### Building a shared understanding of the problem space
37+
38+
We took detailed notes of the BSO visits and then worked through those in synthesis sessions. This helped us build a shared understanding across all the BSOs without each team member visiting every location.
39+
40+
We created a clear picture of [how BSOs approach planning](../what-bsos-told-us-about-forecasting-and-planning/), where current systems fall short and where the new delivery team could focus their efforts.
41+
42+
## What we’d do differently
43+
44+
### Adapt and share as you learn
45+
46+
Forecasting and planning within BSOs is a complex area. In hindsight, our scope may have been too ambitious as we were trying to do 2 things:
47+
48+
* give the delivery team a clear focus
49+
50+
* understand the full complexity of forecasting from the perspectives of BSOs, commissioners, policy and quality assurance
51+
52+
Building in clear reflection points about our scope, our roles and what we were learning would have helped us adapt and welcome feedback that could have helped us see things sooner.
53+
54+
### Do less, with more impact
55+
56+
The discovery produced more than the new team could immediately use. Only a fraction of the work was timely for them (the findings around creating clinics and setting up appointments).
57+
58+
Building in pauses to reflect would have allowed us to recognise that we had enough high-level understanding and redirect effort to the more granular questions.
59+
60+
### Design the ending and the transition
61+
62+
As the new delivery team was forming towards the end of the discovery, we felt pulled in several directions:
63+
64+
* supporting the new team
65+
66+
* giving answers to our stakeholders and sponsors
67+
68+
* synthesising a large amount of research
69+
70+
We should have considered the different audience needs earlier and designed the end of the discovery as a transition to the delivery team.
71+
72+
### Closing thoughts
73+
74+
Sometimes the most important discovery outcomes are the ones you don't anticipate.
75+
76+
We hope this hindsight helps other teams and their sponsors run better discoveries and leave room for the unexpected.
96.1 KB
Loading

0 commit comments

Comments
 (0)