A strategy people follow does one thing: it tells them what to do and, more often, what to stop doing. The dictionary sense of the word is the easy part. To write, per Merriam-Webster, is to set down in writing or to compose. Setting down a strategy takes an afternoon. Getting a team to follow it is a different problem, and it is solved by how the document is built, not how long it is.
The gap between the two shows up in a simple test. Ask three people on the team what the strategy is. If you get three different answers, or three polite recitations of the mission statement, the document failed. A working strategy produces the same answer from all three, and each of them can name one thing they will do differently this month because of it. This connects to our earlier piece, A Founder's Framework for Competitor Analysis That Produces Decisions.
What does a working strategy actually look like?
It answers four questions in plain language. Where are we playing? How do we win there? What capabilities do we need? What will we not do? If a section in the document does not answer one of those, it is context, not strategy, and it belongs in an appendix or the trash.
The last question carries most of the weight. A strategy that only lists priorities is a wish list. The commitments that cost something, like dropping a product line, declining a market, or refusing a partnership, are what make the rest of the document believable. Our analysis of why strategy documents die is blunt: they describe ambition without describing trade-offs, so nobody has to change behavior to comply with them.
Length is a signal in the wrong direction. A strategy that takes forty slides usually hides the decisions inside the narrative. One to two pages forces the choices into the open. If a trade-off does not fit on one page, it probably has not been made yet.
Why do most strategy documents fail in practice?
They are written for the wrong reader. Founders write for investors or boards, so the document persuades rather than directs. Persuasion and direction are different jobs. A board deck can say "we will win through superior product velocity" and everyone nods. An operator reading that has no idea whether it means ship faster, cut support load, or kill the roadmap's long tail.
The second failure is abstraction. Words like "customer-centric" or "operational excellence" cannot be followed or violated. A test: if nobody could ever be caught doing the opposite of a sentence, that sentence is not part of the strategy. "We will not build for enterprise buyers before 500 paying customers" can be violated. That is what makes it a decision.
The third failure is silence about sequence. Teams can follow two or three commitments. They cannot follow nine. If everything is priority one, the document delegates the real prioritization back to whoever is busiest that week, which is how strategy drifts into habit.
How do you write it so people can act on it?
- Start with the no list. Write down what the company will not do for the next two to four quarters. This is the hardest list to make and the most valuable one on paper. If this step is easy, the strategy is not specific enough yet.
- Name the bet. One or two sentences on where the company wins and why it wins there. Not five reasons. The ones you would defend with budget, not adjectives.
- Translate each commitment into a behavior change. For every priority, write what a team member does differently on Monday. If you cannot fill that in, the priority is decoration.
- Cut the document until it fits on two pages. Move supporting analysis to an appendix. The two pages are the strategy; the appendix is the evidence.
- Read it aloud to someone outside the leadership team. Ask them what they would stop doing. Their answer is the document's real content. If they cannot answer, revise before circulating anything.
This is information, not a formula with guaranteed results. A two-page document written badly is worse than a forty-slide deck written honestly, because a short document pretends the trade-offs are settled when they are not. The length discipline only works if the decisions underneath it are real.
What this means for a small team
In a company under roughly fifty people, the strategy document competes with the founder's own behavior for authority. If the document says the company will not chase enterprise deals and the founder takes a call with a Fortune 500 procurement team the same week, the document loses. Every time. People follow what leadership does under pressure, not what it publishes in calm weather.
So the writing task is smaller than it looks. The document is a contract with yourself as much as with the team. Write the commitments you are willing to be held to when a competitor moves, a big prospect appears, or a board member pushes. A strategy you would not follow under pressure is not a strategy; it is a mood board.
Revisit it on a fixed cadence, quarterly at most. Change it when the market changes, not when a quarter disappoints. A strategy rewritten after every bad quarter is not a strategy either. It is a scoreboard.
Where focus and follow-through connect
The discipline of writing what you will not do is the same discipline that makes a founder's focus system work day to day. The document and the calendar have to agree. When they do, follow-through stops depending on reminders, because the trade-offs are already visible in how people spend their weeks.
The same logic applies when choosing where to compete. A market entry plan that names one beachhead is easier to follow than one that lists three attractive segments, for the simple reason that a team can only point its effort in one direction at a time. Narrow commitments are not a limitation of small companies. They are the mechanism that makes any strategy followable. Readers following this should also see Market Entry Strategy: How to Pick the Beachhead You Can Actually Win.
Writing it down matters here in the literal sense. The word has carried the meaning of making a permanent record for a very long time; the first known use of "write" in English predates the twelfth century, per Merriam-Webster's etymology notes. A strategy that lives only in a founder's head cannot be followed, because it changes every time the founder remembers a new detail. The permanent record is what makes disagreement possible, and disagreement is how a team sharpens a strategy instead of quietly ignoring it.
The takeaway
Write the strategy as decisions, not aspirations. Keep it to two pages. Make every commitment specific enough that someone could violate it, and check that the leadership's own behavior matches what is on the page. Then treat the document as a living contract: revisit it on a schedule, change it for real reasons, and let the team argue with it. A strategy people follow is one they can quote, question, and act on without a meeting.
