Conversations worth having.

Frameworks get a team to the edge of a decision. What happens after that — under pressure, with incomplete information — is where product leadership actually shows up.

For product teams and leadership offsites. A concrete way to recognise when a framework has stopped being useful and judgment needs to take over.

Regulation, legacy systems and risk appetite aren't obstacles to product leadership — they're the medium it operates in. Leading well here looks different from leading in an unconstrained startup.

For product leaders in regulated or enterprise environments. A framing for translating organisational constraint into product advantage instead of treating it as friction.

The interface is the smallest part of what a customer is trusting when they use a financial product. The real product is the system behind the screen.

For product and engineering teams in fintech. A mental model for evaluating financial product decisions by the infrastructure they depend on, not just the UI.

You don't need to be an engineer to make good fintech product decisions, but you do need a working model of ledgers, rails and settlement — most PMs are never taught one.

For product managers moving into fintech. A practical starting map of the infrastructure concepts that change how you'd scope a financial product.

AI compresses the cost of producing artefacts — specs, prototypes, analysis. It does not compress the cost of being wrong, which is where product judgment still lives.

For product organisations adopting ai workflows. A clear line between what AI should change about a PM's workflow and what it shouldn't touch.

The transition from managing a backlog to carrying responsibility for direction isn't a promotion in scope — it's a change in the kind of problem you're solving.

For senior pms stepping into leadership. A way to recognise which habits from the IC era need to be unlearned first.

Getting to a strategy that actually constrains decisions, not just describes ambition.

Untangling what the system actually does versus what the product docs claim it does, and where that gap creates risk.

Diagnosing where an operating model is creating bottlenecks disguised as process.

Working out whether the problem is structure, incentives, or unclear ownership.

Getting from research activity to a prioritisation call someone will actually stand behind.

Separating genuine leverage from busywork that just moved faster.