|
| 1 | +--- |
| 2 | +title: "Whose application is it anyway?" |
| 3 | +subtitle: "Building products for everyone in the UK health and care system" |
| 4 | +author: |
| 5 | + - "[Chris Beeley](mailto:[email protected])" |
| 6 | +date: 2025-12-04 |
| 7 | +date-format: "D MMMM YYYY" |
| 8 | +format: |
| 9 | + revealjs: |
| 10 | + theme: [default, ../su_presentation.scss] |
| 11 | + transition: none |
| 12 | + chalkboard: |
| 13 | + buttons: false |
| 14 | + preview-links: auto |
| 15 | + slide-number: false |
| 16 | + auto-animate: true |
| 17 | + footer: | |
| 18 | + Learn more about [The Strategy Unit](https://www.strategyunitwm.nhs.uk/) |
| 19 | +--- |
| 20 | + |
| 21 | +## Introduction |
| 22 | + |
| 23 | +* I want to tell a story |
| 24 | +* It's about ending up in the middle of two things- data science and digital |
| 25 | +* I naively launched in the wrong direction and have beeen redirecting since |
| 26 | +* I'm not an expert in anything I talk about today- if you're doing something big ask an expert |
| 27 | + |
| 28 | +## The story |
| 29 | + |
| 30 | +* I lead a team that built a demand and capacity model for the New Hospital Programme |
| 31 | +* It's a simulation model that predicts demand for acute care in c. 2041 |
| 32 | +* There's a huge amount of analytical work on and around the model |
| 33 | +* We have produced lots of whizzy reports and dashboards to assist with parameter setting and results interpretation |
| 34 | + |
| 35 | +## The problem |
| 36 | + |
| 37 | +* We did everything we were supposed to and people were happy with the model. But there were issues |
| 38 | +* User feedback and prioritisation of developments were ad-hoc |
| 39 | +* Programmes of work were siloed |
| 40 | +* The needs of different bugfixes and improvements were considered in isolation |
| 41 | +* The connection between different deliverables was poorly understood |
| 42 | + |
| 43 | +## Where next? |
| 44 | + |
| 45 | +* I wanted somebody to work across all of the different streams of work |
| 46 | +* They would consider the work programme as a whole and help to prioritise |
| 47 | +* We started to think, **really think** of individuals interacting with our model, inside and outside the unit, as users |
| 48 | + |
| 49 | +## Another story |
| 50 | + |
| 51 | +* This is someone else's story |
| 52 | +* It has a real resonance with an age old problem in analytics- nobody uses our dashboards! |
| 53 | +* The results that the intervention produced were profound but come from a world I knew nothing about two years ago |
| 54 | + |
| 55 | +## The solution - product |
| 56 | + |
| 57 | +](what_is_product_management.png) |
| 58 | + |
| 59 | +## What is product? |
| 60 | + |
| 61 | +* Pro*ject* management is all about delivering a thing |
| 62 | +* You can be agile and iterate on the thing |
| 63 | +* You can do waterfall and spec a thing and then do it |
| 64 | +* Pro*duct* management is about *Why* and *What* |
| 65 | + |
| 66 | +## Back to the other person's story |
| 67 | + |
| 68 | +* They introduced the disciplines of product into their team building PowerBI stuff |
| 69 | +* Specifically: |
| 70 | + * Product management; Product design; Developer; User researcher; Delivery manager |
| 71 | +* Excellent results on engagement with outputs was immediate |
| 72 | + |
| 73 | +## Next steps |
| 74 | + |
| 75 | +* Staff found their roles were too broad |
| 76 | +* It was challenging from a skills and workload point of view |
| 77 | +* Root and branch change of job roles and JDs with the willing participation of all staff |
| 78 | + |
| 79 | +## End result |
| 80 | + |
| 81 | +* Their work is transformed- roughly a third of the staff are involved in: |
| 82 | + * Product management |
| 83 | + * Design |
| 84 | + * User research |
| 85 | +* And they could do more given time and resources- this work is not "one and done" |
| 86 | + |
| 87 | +## Back to my story |
| 88 | + |
| 89 | +* We've been working on adding product roles for the last year |
| 90 | +* Two full time roles (and me chipping in) |
| 91 | +* Many things have worked really well |
| 92 | +* Some things we are still working on |
| 93 | + |
| 94 | +## Product versus delivery |
| 95 | + |
| 96 | +* Separating the *why* from the *how* |
| 97 | +* It's a really specific and clear example of "Involve us at the start" |
| 98 | +* People work better with clear roles and clear responsibilities |
| 99 | +* Build a group of people who know why and a group who know how |
| 100 | + |
| 101 | +## Agile |
| 102 | + |
| 103 | +* Customers talk waterfall but behave agile |
| 104 | +* Agility is a mindset, a mode of practice |
| 105 | +* Being agile is all about being able to review and make decisions frequently |
| 106 | +* But it isn't about changing what you're doing all the time |
| 107 | +* Good code and good teams are ready to change direction- whether they change or not |
| 108 | + |
| 109 | +## Money for old rope |
| 110 | + |
| 111 | +* This is old news to digital people |
| 112 | +* Data science and analytics are expanding |
| 113 | +* We're reinventing the wheel |
| 114 | +* But these methods are being looked at by other teams |
| 115 | + * And I think we really do need to reinvent the wheel |
| 116 | + |
| 117 | +## Data science and analytics is entering its Max Power stage |
| 118 | + |
| 119 | + |
| 120 | + |
| 121 | +## Tying threads |
| 122 | + |
| 123 | +* We need to listen and learn from agile and product colleagues in digital |
| 124 | +* But I also think we need to make these methods our own |
| 125 | +* Let's do it together 🙂 |
| 126 | + |
| 127 | + |
| 128 | + |
0 commit comments