Case study
Product management changes when mistakes actually matter
What clinically safe triage taught me about evidence, translation, and disciplined product judgment
In some products, a weak decision means inconvenience. In clinically safe triage, it can mean much more than that. This piece reflects on how that context changes product practice.
A lot of product culture is built around speed and confidence. In clinically safe triage work, those instincts are still relevant, but they are not enough.
When decisions sit near care pathways, evidence thresholds rise — and performative confidence becomes a liability.
When decisions sit near care pathways, the burden of reasoning changes. You still make product decisions, but evidence thresholds rise and assumptions must be explicit.
Working with clinicians and analysts reshaped what product expertise looked like. It became less performative and more relational: combining domain perspectives into decisions that were practical, safe, and accountable.
Data mattered, but only when tied to the right questions and interpreted with discipline. A metric without framing can create confidence without clarity.
The primary care clinical triage review work involved show-and-tells, workshops, governance artefacts, and sustained relationship-building. Much of the meaningful progress was translational: aligning language and assumptions across expertise boundaries.
Important product work here was often infrastructural rather than flashy: backlog clarity, workflow refinement, risk framing, and better conditions for decision quality.
This changed how I build now. It helps explain why I care about disciplined reasoning in SOPHIA, and governance/interpretability in Restormel, and why shallow move-fast rhetoric feels increasingly unhelpful.