The Product Success Blueprint

Every product that's ever quietly failed on us had passed somebody's definition of success first - the board loved the business case, or the users loved the prototype, or the operations team loved how neatly it fitted their process. The pattern took us years and a respectable amount of scar tissue to see clearly: products don't fail because nobody loved them, they fail because only some of the people who had to love them did. Out of that pattern came the simplest drawing we use, and the one we now refuse to start builds without.

Three circles. The business's goals - what the organisation needs this product to earn, save or enable. The operators' needs - what the people who run, staff and maintain the thing require for it to be workable on a wet Tuesday. The end users' desire - what the customer actually wants enough to change their behaviour for. Product success lives in one place only, which is where all three overlap, and the whole discipline of the blueprint is refusing to pretend the centre is bigger than it is.

The three near-misses, and what they cost

The reason the drawing earns its keep is what the pairwise overlaps predict - each two-circle zone is a specific, recognisable failure with a specific bill attached, and most struggling products are living in one of them.

• Business + users, without operators: the product customers enjoy and the organisation can't sustain. It demos beautifully and burns out the team running it - support drowns, content rots, the 'temporary' manual workaround becomes a job description. This one fails slowly and expensively, because the pain lands on staff before it lands on the dashboard.
• Business + operators, without users: the efficient ghost town. Clean processes, tidy integrations, a launch party - and adoption numbers that need increasingly creative framing, because nobody asked whether customers wanted it enough to switch. This is the most common enterprise failure, and the easiest to spot in advance if anyone looks.
• Users + operators, without business: the beloved hobby. Everyone enjoys it, it runs smoothly, and it can't explain itself at budget time - so it survives exactly until its executive sponsor changes jobs. Fine for a community project; fatal for a product that needs investment to grow.

Most struggling products aren't outside the circles. They're in the wrong overlap.

Finding the centre, honestly

The blueprint's method is to research each circle separately, on its own evidence, before looking for the overlap - because the moment you research them together, the loudest circle (usually the business, since it's paying) starts answering for the other two. The business circle gets pinned down to numbers: not 'digital leadership' but the revenue, cost or risk figure this product must move, signed by whoever owns that figure. The operator circle gets mapped by watching the actual work - the queues, the workarounds, the systems already fighting for the same people's attention. The user circle gets tested against behaviour rather than opinion, because people are polite in interviews and honest in funnels.

Then, and only then, the overlap conversation happens - and it's a filtering exercise, not a brainstorm. Every candidate feature, journey and scope decision gets asked three questions: which business number does this move, who operates it and have they agreed, and what evidence says users want this enough to act. Anything that can't answer all three lives outside the centre, and outside the centre is where scope goes to become regret.

Design for the smallest true centre

The counsel of the blueprint that teams resist most is that the centre is small, and that this is good news. The first version of a product should sit entirely inside it - the modest scope that all three circles genuinely endorse - rather than sprawling into the overlaps on the promise that the missing circle will come around later. It almost never comes around later; what actually happens is that the centre-dwelling parts of the product carry the rest, and everyone learns to avoid the wings.

Shipping the small true centre first does something else valuable: it generates evidence that redraws the circles. Real usage tells you what users actually desire (as opposed to what they said), real operations tell you what the workload actually is, and real numbers tell the business what the product can actually earn - so the centre grows outward on proof, release by release, which is the only direction of growth that compounds instead of diluting.

The blueprint at precinct scale

The V&A Waterfront is the clearest example we have of the drawing doing real work, because the three circles there belong to three groups who rarely sit in the same meeting. The brand carries the precinct's commercial goals. The visitors are the millions of people who arrive for a day out and have no interest whatsoever in anyone's systems. The tenants are the businesses trading inside the precinct - roughly 3,000 relationships across 800 stores and businesses, spanning hotels, retail, commercial and more - who live with whatever gets built every single day.

Put a digital transformation roadmap next to those three circles and the near-misses become obvious before anyone has spent anything. The visitor-facing app the brand would love and no tenant can keep current is business and users without operators. The tenant portal that satisfies the brand and the operations team while visitors never touch it is the efficient ghost town. Plenty of good ideas were plotted somewhere in the wings, and the question was never whether they were good - it was which work sat in the centre, where all three circles genuinely agreed, and would therefore return the most for being built first.

What survived that filter was not the most visible thing on the list. It was the tenant relationship layer: reframing tenant value away from lease economics into something that could actually be measured, then building the Tenant Value Index to score it and a CX framework to run it across the whole lifecycle from onboarding to exit. It sits in the centre because it answers all three circles at once - the brand gets a commercial measure it can act on, the tenants get a relationship that is managed deliberately rather than at renewal time, and the visitor experience improves as a consequence of a better-run precinct rather than as a promise. The build is written up in the case study.

That's the blueprint - three circles, three honest research streams, three questions at every scope decision, and the discipline to build in the middle. Draw it on a whiteboard at your next roadmap argument and plot where each contested feature actually lives; in our experience the drawing ends the argument faster than any deck, because everyone can see the wings for what they are. The centre is where products succeed. Everything else is just proximity.