Every product leader has a philosophy, whether or not they have written it down. Mine comes from founding two companies, scaling a hospitality SaaS platform to 300+ venues and a £2.7 million pre-money valuation, and working inside businesses large enough that a bad decision takes a year to surface. Here it is, in the order it matters.
KEY TAKEAWAYS
Anyone can lengthen a roadmap. The scarce skill is removing things and being able to explain why, to a founder who wants the feature and a customer who asked for it. Almost every struggling product I am brought into is not missing a feature. It is carrying twelve that dilute the one that works.
Practically this means every planning session should end with a documented list of what we are explicitly not doing this quarter, alongside what we are. An unwritten no becomes a yes within a month.
In a room with a founder, an engineer and a salesperson, the loudest opinion usually wins. The correct tiebreaker is not seniority, it is evidence, and the strongest evidence is what customers do rather than what they say they would do.
Survey interest is weak. A paid deposit is strong. A user completing a task twice in a week without prompting is strong. When I set an evidence bar at the start of an engagement, it removes most of the political heat from prioritisation later, because the argument moves from taste to data.
Dashboards with forty numbers exist to avoid accountability. A product function needs one metric it is currently trying to move, a named person who owns it, and a review rhythm that is boring and consistent.
The metric changes by stage. Pre-fit it is almost always activation or retention. Post-fit it moves to expansion or efficiency. What must not happen is optimising a growth metric while the retention curve is still sliding, which is the most expensive mistake in early-stage product.
Any product organisation that goes a month without a team member watching a real person use the product is running blind, no matter how good the analytics are. I hold this as a hard rule because it is the cheapest possible insurance against building confidently in the wrong direction.
With AI tooling this is easier than it has ever been. You can put a working version, not a mock-up, in front of someone within days. The bottleneck has moved from production to judgement, which raises the value of talking to people rather than lowering it.
Teams are rarely slow because people are lazy. They are slow because decisions have no owner, scope is unbounded, or the environment makes shipping frightening. Fix those three and pace follows without anybody being asked to work harder.
The specific interventions are unglamorous: a written decision log, a hard limit on work in progress, deploys that happen daily, and a scope that fits inside a fortnight. Most of the speed founders want from a product leader comes from these rather than from any framework.
Product process can be taught in a quarter. Judgement about what matters cannot. When I help founders hire, the interview loop tests whether a candidate can defend a decision they got wrong, explain a trade-off they made under pressure, and describe what they chose not to build.
Certifications and framework fluency predict very little. The best signal is a candidate who talks about customers unprompted and about process only when asked.
A fractional or interim product leader who becomes permanently necessary has failed at the job. Every engagement I run is built around a handover: documented strategy, an operating cadence the team can run alone, a hiring brief and an interview scorecard.
That is also the strongest commercial argument for this way of working. You are buying senior judgement for a period, plus the capability to carry on without it, rather than a dependency.
Wocal, 2020 to 2025, taught me most of it the expensive way: founder and Chief Product Officer, a hospitality SaaS platform grown to over 300 venues and a £2.7 million pre-money valuation. Co-Ride, since November 2025, is where I test whether the framework still holds when I am the one under pressure. Just Eat, Sage and Echo-U supplied the scale and commercial context that early-stage work does not.
The structured version of all of this is The Crossley Method, which sets out the seven stages from Discover to Scale with the decision to kill or continue made explicit at each one.
THE FRAMEWORK
The ability to decide what not to build and defend it, to set an evidence bar the team actually uses, and to leave behind a product function that runs without them. Framework fluency is a distant secondary consideration.
Against one metric that matches the stage, using behavioural evidence rather than stated intent, with an explicit written list of what is being declined in the same period.
Every week, without exception. A month without someone on the team watching a real user is enough time to build the wrong thing with complete confidence.
Optimising acquisition while retention is still falling. It produces impressive charts for two quarters and then a stall, usually just after the team has been hired against those numbers.
EXPLORE NEXT
Every stage from first idea to first revenue, mapped end to end.
Board-level product advice, audits and investor due diligence.
Read moreUK-specific costs, day rates, contracts and how engagements run.
Read moreCost, commitment and stage-fit compared side by side.
Read moreFull-time cover for a gap, a turnaround or a funding round.
Read moreProduct leadership on retainer for pre-seed and seed teams.
Read moreStrategy, roadmap and operating model that survive contact with reality.
Read more