Four Phases That Turn Strategy Into a Working Plan

A four phase strategy development process moves from diagnosis to execution in a structured sequence: define the problem, analyse the landscape, build the strategic response, and operationalise it into a plan with owners and timelines. Done properly, it stops teams from jumping to tactics before they understand what they are actually trying to solve.

Most strategy failures are not failures of intelligence or ambition. They are failures of sequence. Teams skip the hard diagnostic work, land on a solution that feels right, and then spend months wondering why the numbers are not moving. A phased process forces the discipline that instinct alone rarely delivers.

Why Most Strategy Processes Break Down Before They Start

I have sat in a lot of strategy kick-off meetings over the years. The pattern is almost always the same. Someone senior frames the problem in about ninety seconds, the team nods, and then everyone moves straight to brainstorming solutions. By the end of the session there is a whiteboard covered in ideas, a loose sense of direction, and no shared understanding of what problem is actually being solved.

The first time I ran a full agency strategy session, I was handed the whiteboard pen with almost no warning. The founder had to leave for a client meeting and literally passed it to me mid-sentence. My internal reaction was not confidence. It was something closer to controlled panic. But that moment taught me something useful: the quality of a strategy session is determined almost entirely by the quality of the questions, not the quality of the ideas. If you cannot frame the problem precisely, no amount of creative thinking will save you.

That lesson has shaped how I approach strategy development ever since. The four phase process described here is not a theoretical framework. It is the structure I have returned to across agency turnarounds, new business pitches, go-to-market planning, and growth strategy work across more than thirty industries. It works because it enforces sequence, and sequence is what most teams are missing.

If you are working through broader go-to-market and growth challenges, the Go-To-Market and Growth Strategy hub covers the wider strategic landscape in depth.

Phase 1: Define the Problem With Precision

The first phase is diagnostic. Its purpose is to establish a shared, precise understanding of what the business is actually trying to solve. This sounds obvious. In practice, it is where the majority of strategy processes go wrong.

There is a meaningful difference between a brief that says “we need to grow revenue” and one that says “we need to grow revenue from our enterprise segment by 20% over the next twelve months without increasing headcount, because our SMB base is at capacity and our current CAC makes it unprofitable to scale downmarket.” The second brief produces a completely different strategic response. It narrows the solution space in ways that are genuinely useful.

The diagnostic phase should answer four questions with specificity. What is the business problem, not the marketing problem? What does success look like, and how will it be measured? What constraints are non-negotiable? And what do we know versus what are we assuming? That last question is the most important one, and the most frequently skipped.

When I was turning around a loss-making agency, the presenting problem was “we are not winning enough new business.” The real problem, once we dug into the numbers, was that we were winning the wrong new business at the wrong margins. The pipeline was fine. The qualification criteria and pricing model were broken. A strategy built on the presenting problem would have made things worse. The diagnostic phase exists to close that gap between symptom and cause.

The output of Phase 1 is a written problem statement, agreed by all key stakeholders, that defines the challenge with enough precision to make the next phase productive. If you cannot write that statement in two or three sentences, you are not ready to move on.

Phase 2: Analyse the Landscape Honestly

Phase 2 is where the team builds a rigorous picture of the environment the strategy will operate in. This includes the competitive landscape, customer behaviour and needs, market dynamics, internal capabilities and constraints, and any structural factors that will shape what is possible.

The temptation in this phase is to conduct analysis that confirms the direction the team already wants to go. I have seen it happen in every type of organisation, from startups to large enterprise marketing departments. The deck gets built to support the conclusion, not to test it. That is not analysis. It is rationalisation dressed up as research.

Good landscape analysis looks for tensions and contradictions, not just supporting evidence. What do customers say they want versus what the data shows they actually do? Where is the competitive positioning genuinely differentiated versus where is it a claim every competitor makes? What internal capabilities are genuinely strong versus what is assumed to be strong because it has always been that way?

Forrester’s work on intelligent growth models is worth reading in this context. The argument that growth strategy requires a structured understanding of where you are playing, not just where you want to play, is one that holds across sectors and company sizes. The landscape phase is where that structured understanding gets built.

BCG’s research on the relationship between brand strategy and go-to-market execution makes a related point about alignment. The most common failure mode in landscape analysis is not a lack of data. It is a lack of shared interpretation. Different functions look at the same market and reach different conclusions, and no one forces the synthesis. The output of Phase 2 should be a shared view of the landscape, including the tensions and trade-offs it surfaces, not just a collection of slides from different teams.

The specific output here is a landscape summary that identifies the two or three most significant strategic implications of the analysis. Not everything the research found. The things that will actually shape the strategy.

Phase 3: Build the Strategic Response

This is the phase most people think of when they think about strategy. It is where the team makes choices about positioning, priorities, and approach. It is also the phase where the most common mistake happens: trying to do too much.

A strategy that does not make trade-offs is not a strategy. It is a list of aspirations. I have reviewed hundreds of strategy documents over the years, and the ones that fail in execution almost always share the same characteristic: they contain no clear statement of what the business will not do. Without that, resource allocation becomes impossible, because every initiative looks equally valid.

The strategic response phase should produce three things. A clear positioning statement that defines where the business will compete and how it will win. A set of strategic priorities, ideally no more than three, that reflect the choices made in light of the landscape analysis. And a rationale that connects those priorities directly back to the problem statement from Phase 1. If the strategic response does not address the problem defined in Phase 1, something has gone wrong in the process.

BCG’s framework for go-to-market strategy in complex launch environments is instructive here, even outside the biopharma context it was written for. The emphasis on sequencing decisions, on being explicit about the order in which strategic choices are made, is directly applicable to any strategy development process. You cannot make a good channel decision before you have made a positioning decision. You cannot make a good messaging decision before you have defined the audience. Sequence matters.

One practical discipline I have found useful in this phase is what I call the “so what” test. For every strategic choice on the table, the team has to answer: so what does this mean for what we actually do? If the answer is vague, the choice is not specific enough to be strategic. It is still conceptual, and it needs another round of sharpening before it can drive action.

The output of Phase 3 is a strategic brief: a document of no more than two pages that states the positioning, the priorities, and the rationale. If it cannot be said in two pages, it is not clear enough yet.

Phase 4: Operationalise Into a Plan That Can Be Executed

Phase 4 is where strategy becomes work. It is the translation of strategic direction into specific initiatives, owned by specific people, resourced appropriately, with timelines that are realistic rather than aspirational. It is also, in my experience, where more strategies fail than in any of the previous three phases combined.

The gap between a good strategy and a working plan is not a creative gap. It is an operational one. Teams that are strong at strategic thinking are often weak at the granular discipline of operationalisation, because it requires a different kind of rigour. You have to be willing to say: this initiative will take this long, cost this much, require these capabilities, and if we do not have those capabilities, we need to either build them, buy them, or remove the initiative from the plan.

Vidyard’s research on why go-to-market execution feels harder than it used to points to something real: the operational complexity of getting strategy into market has increased, not decreased, as the number of channels and touchpoints has grown. That complexity makes rigorous operationalisation more important, not less. A plan that is vague about ownership and resourcing will not survive contact with that complexity.

When I grew an agency from twenty to a hundred people, the single biggest operational challenge was not hiring or winning clients. It was making sure that the strategic direction was actually reflected in what people were doing day to day. That required a planning process that connected the strategy to team-level objectives, to individual roles, and to the metrics being tracked week to week. Without that chain, strategy stays at the top of the organisation and never reaches the work.

The operationalisation phase should produce a plan with four components. A prioritised initiative list, with each initiative connected to a specific strategic priority from Phase 3. An ownership model, where every initiative has a named lead. A resourcing view, including budget, headcount, and any capability gaps that need to be addressed. And a measurement framework that defines how progress will be tracked against the problem statement from Phase 1.

That last component is worth dwelling on. The measurement framework should be built from the problem statement, not from whatever metrics are easiest to track. I have seen too many plans where the KPIs bear almost no relationship to the strategic objectives, because someone defaulted to the metrics already in the dashboard. That is not measurement. It is comfort.

How the Four Phases Work Together

The value of a phased process is not in the phases themselves. It is in the outputs each phase produces and the way those outputs constrain and inform what comes next. The problem statement from Phase 1 shapes what analysis is worth doing in Phase 2. The landscape synthesis from Phase 2 shapes the strategic choices available in Phase 3. The strategic brief from Phase 3 defines what should and should not be in the operational plan in Phase 4.

That chain of dependency is what gives the process its integrity. Break it at any point, and you get the kind of strategy that looks coherent in a deck but falls apart in practice. Teams that skip Phase 1 and go straight to analysis end up analysing the wrong things. Teams that skip Phase 2 and go straight to strategy end up making choices without understanding the environment. Teams that skip Phase 3 and go straight to planning end up with a list of activities that are not connected to any clear direction.

The process also needs to be iterative, not linear. Phase 2 analysis will sometimes reveal that the problem statement in Phase 1 was wrong, or incomplete. Phase 3 work will sometimes surface constraints that require going back to Phase 2 for additional analysis. That is not failure. That is the process working as intended. The phases provide structure, not a rigid sequence that cannot accommodate new information.

Forrester’s analysis of go-to-market struggles in complex sectors identifies a recurring pattern: organisations that treat strategy development as a linear, one-time exercise tend to produce strategies that are outdated by the time they are executed. Building iteration into the process, with explicit checkpoints where earlier outputs can be revisited in light of new information, is what separates a working strategy process from a strategy theatre exercise.

Tools like Hotjar can support the landscape analysis phase by surfacing behavioural data about how customers actually interact with products and content, as opposed to how teams assume they do. The distinction between observed behaviour and assumed behaviour is one of the most productive tensions in any strategy process.

Common Failure Modes Across the Four Phases

After running this process across multiple agencies and client engagements, the failure modes are predictable enough to be worth naming explicitly.

In Phase 1, the most common failure is a problem statement that is too broad to be useful. “Grow the business” is not a problem statement. Neither is “improve brand awareness.” A useful problem statement names a specific gap between current and desired state, with enough context to make the cause of that gap at least partially visible.

In Phase 2, the most common failure is confirmation bias in the analysis. The team selects data that supports the conclusion they already favour and ignores or discounts data that challenges it. The antidote is to assign someone the explicit role of devil’s advocate, with a mandate to find the evidence that contradicts the emerging view.

In Phase 3, the most common failure is a strategic response that is too broad to drive clear choices. This usually happens when there is political pressure to include everyone’s priorities, and no one has the authority or willingness to make the trade-offs explicit. The result is a strategy that tries to be everything to everyone and ends up being nothing to anyone.

In Phase 4, the most common failure is a plan that is under-resourced relative to its ambitions. Teams agree on the strategic priorities in Phase 3, and then discover in Phase 4 that they do not have the budget, headcount, or capabilities to execute them. The right response is to go back and revise the priorities. The common response is to keep the priorities and hope the resourcing problem resolves itself. It never does.

Vidyard’s research on go-to-market team performance points to a related issue: the gap between strategic intent and operational capacity is one of the most significant drags on GTM effectiveness. Closing that gap requires the kind of honest resourcing conversation that Phase 4 is designed to force.

If you want to go deeper on the broader strategic context that this process sits within, the Go-To-Market and Growth Strategy hub covers positioning, market entry, and growth planning across a range of strategic challenges.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions