Why this matters
Most organisations do not understand the system they operate in. They rely on intuition, dashboards, inherited assumptions, and linear planning in environments that are anything but linear. Product decisions are then made around visible symptoms rather than the deeper structures driving behaviour.
The result is predictable: misaligned incentives, hidden constraints, unintended consequences, and features that solve local problems while creating wider system friction.
My work exists to fix this. I bring structure to ambiguous product problems, reveal the real drivers of system behaviour, and help teams design products, models, and decision-support tools that support clearer thinking and improved decision making.
Every system is perfectly designed to get the results it gets
Deming
What I do
I help organisations turn complex operating environments into better product decisions.
That means helping teams: understand the system — identify the constraints, dependencies, behaviours, incentives, and risk points shaping real-world outcomes.
Model dynamic behaviour — use simulations, scenarios, decision models, and prototypes to test assumptions before committing to a product direction.
Design for confident action — create software and workflows that support judgement, prioritisation, planning, and operational control.
It is not "data-driven" product management in the shallow sense of reporting what has already happened.
It is structural clarity: understanding how the system works so product teams can decide what to build, what not to build, where to intervene, and how to design software that supports confident action.
You cannot optimise a system by optimising its parts
Ackoff
How I think or why I think like I do
My product approach is shaped by an unusual combination of History, Computer Science, Business, and Logistics.
History gave me evidence-led thinking and a long view of how systems change. Computer Science gave me technical structure, modelling, and software reasoning. Business added strategy, operating models, and commercial value. Logistics grounded all of it in real-world operational pressure.
That mix is central to how I work as a product manager: connecting operational reality, technical possibility, commercial priorities, and the wider system around the product.
It is a capital mistake to theorise before one has data
Sherlock Holmes Conan Doyle