Map. Clarify. Plan. The three-phase method behind our Strategy work.

Map. Reading the landscape honestly.

The Map phase is the part of the work that does not look like much in a slide deck and decides almost everything that follows. The job is to read the business landscape with enough honesty that the plan we build later does not rest on a fiction. That means three things in our practice, and the order matters.

First, we read the external picture. Market dynamics, competitor moves, regulatory shifts, the customer behaviour that has changed in the last eighteen months. The teams we work with usually have a view here already, and our job is partly to confirm what they know and partly to surface what has changed since the last strategy refresh. When the picture in the room and the picture in the market have drifted apart, that is the first finding worth naming.

Second, we read the operating constraints. What the organisation can actually do, given its current capabilities, its debt, its dependencies, and the realistic capacity of its leadership bench. In our exchanges with executive teams, the Map phase is where the gap between ambition and operating reality usually becomes visible for the first time. The strategy that ignores that gap tends to fail in execution. The strategy that names the gap and builds the plan around it tends to hold.

Third, and most important, we read the appetite for change. Inside the executive team, who genuinely wants the work and who would prefer that the status quo hold for another year. The appetite reading is the hardest to do in a deck and the most determinant of whether the plan that follows will be acted on or filed. We do this through one-on-one conversations with each member of the executive team, on the record but in confidence, and we surface the pattern in the Clarify phase without attributing the views to individuals.

Clarify. Reducing ten ambitions to three priorities.

The Clarify phase is the part of the method that produces the most discomfort and the most value. The job is to reduce a long list of ambitions, projects, and aspirations to a small number of priorities that the organisation can actually deliver in the relevant horizon. In our experience, the right number sits between two and four. More than that and the plan becomes a wish list. Fewer and the plan loses optionality.

What makes Clarify work is the explicit documentation of trade-offs. Every priority that makes the list does so at the cost of another priority that does not. The teams we advise often hold ten parallel ambitions in their heads, each one privately weighted, with no shared view across the executive team of which one wins when they conflict. The Clarify phase puts those conflicts on the table. We tend to run this as a structured session, with each member of the executive team voting privately on which priorities they would defend, and then a facilitated conversation where the pattern is shared and the trade-offs are named.

The output of the Clarify phase is a short document, usually two to four pages, that states what the priorities are, what was traded off, and the explicit conditions under which the trade-offs would be revisited. The clients we work with who keep that document accessible to their leadership team tend to stay close to their plan. The clients who file it after the steering committee tend to drift back to the long list within a quarter.

Plan. Sequencing the work into phases.

The Plan phase translates the priorities into a sequence of work, with named owners and a funding model that supports the sequence. The plan is the working document the leadership team will use to run the next twelve to twenty-four months, and the discipline that shapes it is sequencing rather than ambition.

Sequencing matters because most strategy plans we have seen are written as if everything will happen in parallel. In practice, capacity is finite, dependencies are real, and trying to do everything at once usually means doing none of it well. The job in the Plan phase is to ask, for each priority, what has to happen first, what depends on what, and which workstreams will compete for the same expert capacity. The teams that do this work explicitly tend to ship. The teams that skip it tend to discover the dependencies the hard way, in the middle of the year, when something they assumed was independent turns out to need something else that has not been started.

Named owners is the second discipline. Every workstream in the plan carries the name of a person inside the organisation who is accountable for it, with the authority to make decisions inside that workstream and the explicit support of the executive sponsor. We have walked into engagements where the plan looked clean but no one in the room could answer the question of who owned which workstream past launch. That is the conversation that turns a plan into work.

The funding model is the third discipline and the one that gets the least attention in strategy decks. Where the budget comes from, what gets reallocated to free it, what the conditions are for releasing the next phase of funding. In our experience, the plans that are funded explicitly tend to be delivered. The plans that are written with an implicit assumption that funding will appear tend to stall in the first quarter.

The deliverable is a working document, not a deck.

The discipline that runs through all three phases is that what the client takes away is not a slide deck. It is a working document that the leadership team co-edits during the engagement, returns to in quarterly reviews, and uses to make decisions on real questions during the year. The deck is for the steering committee, the working document is for the work, and the two have different audiences and different purposes.

In our exchanges with clients who have lived through traditional strategy engagements, the most common complaint is that the deliverable read beautifully and then sat on a shelf. The shift to a working document changes that. The document is shorter, less polished, more iterative. It carries the trade-offs explicitly. It names owners. It contains the questions that have not yet been answered, rather than hiding them behind confident prose. The leadership team can pick it up six months in and use it to debate a real decision, because the document was built for that purpose.

A plan is not the document you present to the board. It is the document you reach for on a Wednesday morning when an unexpected decision has landed on your desk and you need to know what the leadership team already agreed.

How this method connects to the rest of B One.

Strategy is one of our four Consulting pillars, and it tends to feed the other three. The plan that comes out of the Clarify and Plan phases will usually name initiatives that flow into Transformation and Organisation, into Performance and Value, or into AI-Augmented Enterprise. In many of the engagements we run, the strategy partner who led the Map. Clarify. Plan. work stays close to the delivery that follows, ensuring the plan does not drift in execution and the executive team does not lose visibility on the trade-offs they agreed.

The plan also frequently feeds the build side of our firm. When a strategic priority requires a system, a platform, or an AI capability, our Tech Factory in Bali picks up the engineering, with the strategy partner remaining on the file to hold the design intent. That continuity between strategy and build is one of the operating choices we have made deliberately, and clients tend to remark on it because the alternative, with a strategic plan handed over to an unfamiliar engineering team, rarely produces what was intended.

If your leadership team is approaching a strategy refresh, or has lived through one that did not produce the change you wanted, the conversation we usually open with is short. What is the genuine appetite for change inside your executive team. What trade-offs have you been quietly avoiding. What would a plan that you actually used on a Wednesday morning look like. The answers to those three questions tend to shape what the engagement looks like and how long it should run.