Product decisions where customer trust, markets and resilience meet.

Why The Product Desk exists

Most product advice is clean because it is written after the mess has been removed. Real product work is not clean. The customer need is only one input. There are regulatory obligations, operational constraints, platform dependencies, technical risk, market deadlines, finite engineering capacity and stakeholders who are all rational from where they sit.

The difficult part is not knowing that trade-offs exist. It is making them visible early enough, clearly enough and honestly enough for the organisation to choose with its eyes open.

The Product Desk is a record of that work: practical essays on prioritisation, estimation, stakeholder decisions, discovery, roadmaps, metrics and resilient delivery.

The perspective behind the writing

I have spent more than two decades across banking and capital markets, including product leadership for a high-volume retail trading platform. That means working where customer experience, market operations, regulation, reliability and commercial outcomes intersect.

The examples are grounded in complex platform environments, but the underlying questions travel well: What are we really choosing? What becomes harder if we say yes? Which assumptions are carrying the decision? What risk are we quietly accepting? What evidence would change our mind?

Principles from the desk

• Decisions before deliverables. A backlog records choices; it should never replace them.
• Consequences before scores. A prioritisation score is useful only when it exposes what the organisation is accepting or deferring.
• Uncertainty should be visible. Confidence increases when assumptions are stated, not when ranges are hidden.
• Resilience is customer value. Reliability, controls and operational health are product outcomes, even when customers cannot see the work.
• Trust is a product capability. Stakeholders do not need every request accepted. They need the decision process to be intelligible and consistent.

What you will receive

One focused essay each Sunday. Usually five minutes. Always centred on a real product problem and written to be useful in your next planning, prioritisation or stakeholder conversation.

No recycled framework diagrams. No generic Agile advice. No theory without a scar attached.