From Strategic Focus to Commercial Results

Over decades of working with and inside product companies, we keep seeing the same thing. Somewhere inside the organisation, usually in a team, sometimes in a market, occasionally in a single leader who has figured something out, there is something that genuinely works. A way of reading customers that drives real decisions. A product team that ships things the market actually wants. A commercial team that wins on value rather than price. Pockets of real customer-centricity, operating well, delivering results.

What we rarely see is those pockets connected. The insight that lives in one team does not reach the product roadmap. The customer knowledge that exists in the field does not shape the portfolio. The focus that one part of the organisation has found gets diluted when it hits the planning cycle. We have seen what happens when these pockets are finally joined up, when the focus, the systems, and the execution start pulling in the same direction. The compound effect is significant. We have also seen what it costs when they are not, though that part is perhaps obvious.

That pattern, brilliant in parts and disconnected in practice, is what Single-Minded is written to address. Not as a management philosophy. As an argument about what it actually takes to build a business where customer obsession is not isolated in pockets but runs as the operating principle through everything. It challenges the management logic that puts internal power above external value — and it does so deliberately.

The argument moves from strategic focus all the way through to commercial results. Not as separate disciplines. As one connected system.

Why single-mindedness matters

The word in the title is deliberate. Single-mindedness is not simplicity for its own sake. It is the discipline of knowing what you are organising around and not letting anything compete with that answer. The customer. Not as a declared value. As a mechanism that drives every meeting, every budget decision, every portfolio call.

Most product companies already believe they are customer-focused. The word appears in the vision statement. Customer satisfaction is measured, reported, and reviewed. And yet the business continues to be designed from the inside out: around what it can build, what it has historically sold, what the organisation knows how to do. The pockets of genuine customer-centricity exist (we see them in almost every company we work with) but they operate in isolation. Customer focus as a declared intention is not the same as customer obsession as a connected operating principle.

Inside-out drift happens through good decisions, not bad ones. Decisions that are internally rational, defensible at the board level, optimised for what the business already knows. The drift is invisible until it compounds into something that shows up in the numbers. We have written about this mechanism in What Is Outside-In Strategy, and it is worth understanding before reading the book, because the book builds from there.

Single-Minded is built on the conviction that connecting those pockets, aligning the focus, the systems, and the execution around a single organising principle, is both achievable and compounding. The organisations that manage it do not look dramatically different from the outside. They are just consistently better at knowing where to play, building what the market will pay for, and executing in a way that actually reaches the customer.

"Customer focus as a function is not the same as customer obsession as an operating principle. The gap between those two things is where growth stalls."

From strategic focus to commercial results: the argument in full

The book is organised around three stages. They are not a methodology. They are not a framework to install. They are a logic: a way of thinking about what a business needs to get right, in the right order, to move from strategic intent to commercial results without losing the thread between them.

THINK is the work of choosing where to compete. This sounds obvious. It rarely is. Most organisations answer the question of where to play by looking inward, at historical strengths, existing capabilities, markets where they already have a foothold. Single-Minded insists on something harder: beginning with external signals, reading where genuine customer need is forming, and identifying the spaces where the organisation has a real right to win rather than just a historical presence. The Where to Play, How to Win discipline is the practical expression of this thinking. Two questions that need separate answers, grounded in evidence from outside the organisation, before resources move. Most execution failures start here, not in how the strategy was implemented, but in the fact that the wrong choice was made about where to compete.

Once the focus is clear, DESIGN is the work of building systems that can actually move with it. Most commercial organisations are designed for control, for predictability, for defensibility, for protecting what already works. That design logic made sense in markets that moved slowly. In markets that move fast, it creates exactly the kind of structural lag that lets more adaptable competitors close the gap. Single-Minded argues for designing around adaptability instead: feedback loops that bring customer reality into decisions before it is too late to act on it, cross-functional structures that respond to signals from the market rather than optimising departmental boundaries, experimentation systems that treat learning as a commercial capability rather than an R&D function.

And then IMPLEMENT, where the system is tested. Execution does not fail when strategy is wrong. It fails when the organisation underneath the strategy was never redesigned to carry it. The metrics still reward internal efficiency. The incentives still protect the existing portfolio. The decisions still escalate to where they take too long to matter. Single-Minded treats implementation as a design discipline, something built deliberately into how the organisation operates, not assumed to follow from good intentions and clear communication. The mechanisms behind execution failure, and what it takes to close the gap between strategic intent and commercial result, are explored in detail in Why Strategy Fails in Execution.

THINK, DESIGN, IMPLEMENT. Not phases. Not a project plan. A continuous operating logic that keeps strategic focus, system design, and execution integrated and that compounds in value the longer it runs.

Evolution, not transformation

One word appears consistently in how organisations talk about this kind of change. Transformation. We avoid it deliberately.

Transformation implies a start and an end, a period of upheaval followed by a new stable state. It implies the organisation can be taken apart and rebuilt, and that once rebuilt it will stay that way. The evidence from decades of transformation programmes is that this is not how organisations change. The disruption is real. The new stable state rarely arrives. The energy invested in the transformation is energy not invested in serving customers.

The Single-Minded argument is for evolution instead. Gradual, continuous movement toward a version of the business that is more genuinely organised around customer truth, without losing the operational capability that keeps the current business running. This is not a softer version of the same ambition. It is a more honest account of how durable commercial change actually works.

Most companies do not fail because they lack ambition. They fail because they spread that ambition across too many fronts and win on none of them.

The organisations that sustain this do not do so because they run bigger programmes. They do so because they stopped treating change as an event and built it into the rhythm of how they work: how they read the market, how they allocate resources, how they decide what to build and what to stop.

The only question that matters

Single-Minded is not a book for organisations that are comfortable with where they are. It is for leadership teams who can see the gap between what their strategy promises and what their organisation actually delivers, and want a clear-eyed account of why that gap exists and what closing it genuinely requires.

The book makes the case. The operational layer beneath it, the commercial architecture, the portfolio mechanisms, the implementation tools we use in client work, is where the argument becomes practice. The commercial agenda is the practical framework for translating the book's strategic logic into sequenced commercial decisions. If the argument resonates, that is where the conversation usually begins.

Read more about the book and request a copy at experienceunleashed.com/single-minded.

Key takeaways

Single-Minded is built on a single conviction: that the customer is not a department or a metric, but the organising principle that every business decision should be built around. Not as a value, but as a mechanism.

The most common strategic failure in mid-sized product companies is not bad strategy. It is strategy spread too thin: too many segments, too many portfolio positions, too many initiatives pursued without enough focus to win on any of them.

Inside-out thinking is invisible from the inside. It feels like discipline because it is built around what the business can measure and control, which is almost always what already exists rather than what the market needs next.

The THINK–DESIGN–IMPLEMENT system is not a sequence of phases. It is a continuous operating logic that keeps strategic focus, system design, and execution integrated rather than treating each as a separate workstream.

Single-Minded argues for evolution rather than transformation: continuous, deliberate movement toward a business organised around customer truth, without the disruption of wholesale reinvention.

FAQ

What is Single-Minded about?

Single-Minded argues that the customer should be the organising principle of the entire business. Not a department, not a declared value, but the logic that drives every strategic choice, every system design, and every implementation decision. The book provides a three-stage system (THINK, DESIGN, IMPLEMENT) for making that logic operational inside a real organisation, from strategic focus all the way through to commercial results.

Who is the book for?

It is written for senior leaders in mid-sized product companies (CEOs, CPOs, CMOs) who can see the gap between their strategic intent and what their organisation actually delivers, and want to close it. It is particularly relevant for leadership teams whose organisations have grown by doing more rather than by doing fewer things with greater intensity.

What makes Single-Minded different from other business design books?

Most books in this territory either diagnose the problem at a structural level or provide tactical frameworks. Single-Minded does both, but its distinctive contribution is the argument about evolution over transformation: that durable commercial change happens gradually and continuously, not through periodic reinvention. It also treats execution as a design discipline, not a communication challenge.

What is the THINK–DESIGN–IMPLEMENT framework?

It is the three-stage system the book is organised around. THINK is the work of choosing where to play and why it matters to customers. DESIGN is the work of building systems that can move with the market rather than against it. IMPLEMENT is the work of ensuring the organisation underneath the strategy is designed to carry it forward, through metrics, incentives, and decision-making that reward customer reality rather than internal convenience. The three stages run continuously rather than sequentially.

How does Single-Minded connect to Experience Unleashed's consulting work?

The book provides the logic that underpins how we work with product companies. The commercial agenda, portfolio management, and implementation mechanisms we use in practice are the operational layer that sits beneath the book's framework: the specific tools for making outside-in strategy real inside organisations with existing portfolios, existing customers, and existing operational constraints.