Ask a leadership team to articulate your strategy in one sentence and watch what actually happens in the room. Not a value statement. Not the line from the intranet homepage. The real thing: what you are trying to achieve, where you will compete, and why a customer picks you over the next best option.
Most teams cannot do it. Worse, the ones who think they can rarely agree with each other once you ask them one at a time, in separate rooms, with no chance to compare notes first.
Why You Can't Articulate Your Strategy in a Single Sentence
David Collis and Michael Rukstad ran into this problem directly while advising a financial services firm that could not settle its own priorities. Their research, published in Harvard Business Review in April 2008 under the title "Can You Say What Your Strategy Is?", made a blunt claim: if you cannot state your strategy in thirty five words or fewer, your organisation does not actually have one, regardless of how thick the strategy deck sitting in the shared drive happens to be.
Thirty five words sounds like an arbitrary constraint until you try to hit it. It forces three decisions that most leadership teams have discussed around but never actually settled out loud: the objective, which is what you are trying to achieve and by when; the scope, which is where you will compete and, harder still, where you have deliberately chosen not to; and the advantage, which is the specific and honest reason a customer chooses you over the alternative sitting next to you on the shortlist.
Drop any one of the three and the sentence collapses into a slogan. Add a fourth idea and it turns into a paragraph nobody can repeat back to you a week later, which defeats the entire point of having a strategy statement rather than a strategy document.
Collis and Rukstad illustrate this with a brokerage firm that had quadrupled its market share over two decades. Ask any of its thousands of advisers to state the strategy, and the answer came back consistent: grow the adviser network to a stated target within a stated number of years, by offering trusted, face to face financial advice to conservative individual investors who prefer to delegate their financial decisions rather than manage them directly. Objective, scope, and advantage, in one breath, said the same way by people who had never compared notes with each other. That consistency is the actual test. It is not whether the statement sounds impressive. It is whether two people who have never spoken to each other produce the same answer.
- Objective: A single, time bound target that every person in the room would state the same way. A number and a date, not an ambition.
- Scope: Where you compete: which customers, which markets, which products. The harder half is naming what you have deliberately chosen to walk away from.
- Advantage: The specific, honest reason a customer chooses you over the next best option. If the sentence could describe two competitors equally well, it is not an advantage.
Most leadership teams get the objective roughly right, because a number and a date are hard to argue with once someone writes them down. Scope is where the disagreement starts, because scope means telling a senior person in the room that something they care about is not, in fact, the plan. Advantage is where most teams fail outright, because it requires admitting the real reason customers choose you, which is rarely the reason the marketing slide claims.
This Is an Alignment Problem, Not a Wording Problem
The instinct, once a team notices it cannot agree, is to fix the language. Bring in a copywriter. Run another offsite. Draft version six of the strategy statement and hope the right combination of words finally sticks. That treats a structural gap as if it were a vocabulary gap, and it is why the exercise so often gets repeated every eighteen months without ever actually resolving.
In the Leadership Capability Architecture I use with clients, this sits squarely inside the Alignment System, the first of five Structural Pillars an organisation's leadership infrastructure gets scored against. A vague strategy statement is not a communications failure. It is a diagnostic signal that the team has not yet made the underlying decision, and no amount of rewriting the sentence fixes a decision that has not been made.
I have sat in enough of these rooms to recognise the pattern immediately: five capable, senior people, five confident answers, and no two of them describing the same business. Nobody is lying. Each of them is describing the strategy as they privately understand it, which is exactly the problem. Private understanding does not scale past the room they are sitting in.
This matters more than a wording exercise deserves to, because a leadership team that cannot articulate your strategy in one sentence cannot delegate the decisions that sit underneath it either. Every judgement call further down the organisation, on pricing, on which deal to chase, on which feature actually ships next quarter, has to travel back up the chain for a decision the strategy statement should already have made on everyone's behalf. That is not a leadership team functioning as a system. That is a bottleneck wearing a leadership team's job titles.
Why 'We're Aligned' Is Usually Wrong
Almost every leadership team I meet describes itself as aligned before we run this exercise. They believe it. That belief is the actual obstacle, because a team that assumes agreement never tests for it, and untested agreement is just five private opinions sharing a boardroom.
This is the illusion of consensus at work: everyone nodded at the same strategy slide in the same meeting, so everyone assumes they took the same meaning away from it. They did not. A word like growth means something different to a finance director than it does to the head of sales, and neither of them finds out how differently until a real decision, a pricing call, a hiring freeze, a deal that falls outside the plan, forces the gap into the open. By then it has already cost time, and usually a working relationship or two.
What the Gap Actually Costs
The cost rarely shows up as a single dramatic failure. It shows up as friction that everyone below the leadership team learns to live with, because naming it feels like a bigger fight than working around it. A regional lead quietly pursues a segment the strategy never intended to serve, because nobody ever told them clearly enough not to. A product team ships a feature that makes sense on its own terms but pulls the release plan away from the stated advantage, because the advantage was never stated precisely enough to test the decision against.
None of this looks like a strategy problem from inside the business. It looks like a coordination problem, a prioritisation problem, occasionally a personality clash between two directors who keep disagreeing about the same account for reasons neither of them can quite name. Most of the time, the actual cause sits one level up: the leadership team never converged on the thirty five words, so nobody below them has anything precise enough to check their own decisions against.
There is a hiring cost too, and it is easy to miss because it never appears on a balance sheet as a single line. Every leader you promote or bring in from outside inherits whichever version of the strategy the person who interviewed them happened to believe. Multiply that across a handful of hires a year, over a few years, and you have built a leadership bench that was never actually aligned in the first place. Fixing that later, once the team is bigger and the informal versions have hardened into habit, costs considerably more than fifteen minutes and an uncomfortable meeting.
A 35-Word Test for Your Own Leadership Team
This is deliberately simple to run, and that is the point. Complexity is usually how a team avoids finding out that it disagrees.
- Write it alone: Give every member of the leadership team fifteen minutes, no discussion, to write their own thirty five word version covering objective, scope, and advantage.
- Compare in the room, unattributed: Read every version aloud without saying who wrote it. Do not edit the wording yet. Just notice where the versions genuinely disagree on substance, not where they simply use different words for the same idea.
- Name the real disagreement: Almost every gap traces back to scope (what you have not actually agreed to stop doing) or advantage (the honest reason customers choose you, rather than the flattering one). Name the specific unmade decision, not the wording around it.
- Resolve the decision before the sentence: Settle the underlying choice first, as a team, out loud. The thirty five words that follow should take minutes to agree once the actual decision is made rather than avoided.
Do this before your next planning cycle, not after it. A strategy statement that everyone can repeat, unprompted and in the same terms, is the cheapest alignment check available to any leadership team. It costs an afternoon. The alternative, discovering the gap mid way through a difficult quarter, costs considerably more than that.
A strategy statement is not a marketing artefact. It is the shortest possible proof that a leadership team has actually decided something, together, out loud.
If your own team could not produce a matching version just now, treat that as useful evidence rather than a failure. It tells you precisely which part of your leadership infrastructure needs attention first, and it is far cheaper to find that out in a fifteen minute exercise than six months into a strategy that three of your directors were quietly executing differently.
This is exactly what a proper diagnostic is for. My Free Leadership Diagnostic scores your organisation against all five Structural Pillars, including the Alignment System this article sits inside, and produces a personalised Architecture Brief so you are working from evidence about where the gap actually sits rather than a guess based on which director complained most recently. The same underlying model sits behind CapabilityAI, which is where clients keep testing their own answers against the framework between formal engagements.