A strategy you can decide by

"Should we do this?" In growing companies this question comes up every day, in Slack, in the hallway, over coffee. Should the team bring a big customer’s request forward, build a new integration, switch cloud providers or tidy up first? And almost always it ends up with the same person, the founder, because that is the only place where the whole picture lives.

As long as the team is small, that works. With every new person, though, that one desk becomes a bottleneck. Decisions wait, teams work with the handbrake on or pull in different directions, and in the end work gets redone because it missed the actual direction. This bottleneck has little to do with technology. It arises because the strategy exists only in one person’s head, or on a slide nobody can decide by. A good strategy solves exactly that, which makes it one of the most effective tools for speed a company has.

Vision, mission, strategy, sorted

The terms are often mixed up, yet each answers its own question. The vision says where the journey should go: the big picture of the world you want to help shape. The mission says why you exist and what you contribute to it. The strategy says what you actually do to get there, and just as important, what you deliberately do not do. Tactics, finally, are what is on the plan this week.

Vision and mission change rarely, and that is a good thing, because they provide a footing. The strategy, on the other hand, may and should adapt when the market, the team or the funding changes. Tactics change all the time. Keep the levels apart and you also know what is being discussed: whether someone is questioning the direction or just the next step.

Strategy means choosing

A strategy is not a statement of intent but a series of decisions. Strategy is doing, and it is just as much saying no. A strategy that allows every customer request, every market and every technology decides nothing, and therefore helps nobody decide either. Only its boundaries make it useful, because they let a team see whether an idea fits or not.

Whether a sentence is a real decision is shown by the reversal test. If the opposite is a sensible option that another company could just as well choose, you have made a choice. If the opposite is absurd, the sentence is a platitude. "We deliver quality" fails, because nobody has ever deliberately chosen poor quality. "Our standard product over special requests" passes, because there are companies that do very well on special requests. The same goes for the fundamental questions worth answering early, such as how you are funded, whether you work with a permanent team or with freelancers, and how close you are to the customer. Every honest answer rules paths out, and that is the point.

Strategies interlock

As a company grows, further strategies appear next to the company strategy: for finance, product, sales, technology. They are not separate worlds but closely linked, and overlooking that builds in contradictions. Suppose the finance strategy calls for strict cost control and quick profitability. Then the product strategy will focus on a few features with a clear revenue contribution. And that reaches all the way into technology: instead of building new platforms, it pays to make the existing cloud environment more efficient, use managed services and allocate costs visibly.

It works the other way round too. If the product strategy bets on fast innovation and many new features, development needs more budget, and the technology has to be built to ship often and safely. Both directions are legitimate. It only becomes a problem when finance, product and technology strategy point in different directions because each was made on its own. Then teams work against each other, although everyone believes they are doing the right thing.

A simple test brings this to light: put the core sentences of the individual strategies side by side. If the product strategy says "speed over cost" and the finance strategy says "cost over speed", you have found the conflict before it breaks out in day-to-day work. Then the company strategy decides which sentence applies, and the other one is adjusted.

Communicate, including what you rejected

A strategy only works once the people who decide every day know it. That sounds obvious, but it often fails because only the result is shared, not the way there. A team that only knows what applies has to ask with every new case. A team that also knows why it applies can place the new case itself. This is exactly where speed comes from: decisions move to where the knowledge about the specific case lives, instead of waiting in a queue.

Just as important is to be open about the options you rejected. Why did you decide against the second market, against your own hardware, against the enterprise business? If you do not write that down, you will have the same discussion again every few months, as soon as someone new joins the team or the mood shifts. What works well is to record the strategy and important decisions in writing, briefly and in a place everyone knows. A document that people can read in peace and point to carries further than any presentation.

In practice that means one page in a fixed place everyone knows, for example in the wiki and linked in the team channel. Bring it up more often than feels right, because when you can no longer stand hearing a sentence yourself, it is only just arriving in the team. And use it in everyday work: with every bigger decision, ask which sentence of the strategy you are deciding by. Ask that question regularly and the document becomes a tool, and new colleagues learn the strategy not from a presentation but from the decisions they take part in.

Exercise: your strategy is in your last decisions

You do not have to invent a strategy at a retreat. Usually it is already there, just unspoken, in the decisions you made over the past weeks. For this exercise you need an hour and your inbox, Slack or your calendar.

First you collect, for about a quarter of an hour. Write down the last ten "Should we …?" questions that landed on your desk: a customer’s special request, the new integration, the tool someone wanted to introduce, the role you decided not to advertise after all.

Then you give reasons, a good twenty minutes. For each question, note how you decided and above all why, in a single sentence. After the third or fourth answer the reasons start to repeat, and exactly those repetitions are your strategy.

After that you condense, another twenty minutes. Sum up the reasons in three to five sentences. The form "A over B" works well, because it forces a choice between two things that are both good, and that is exactly where a team needs orientation. Add one or two sentences about what you do not do.

An app for employees who want to see
their finances in one place.

Simplicity over breadth of features.
Loyal users over fast growth.
Our product over custom requests.

No investment advice, no loans.

The test follows the week after. Give the page to someone on the team, together with two or three questions that are currently open. If they reach the same decision as you, the strategy holds. Where they do not, a sentence is missing, or you decided by something that is written nowhere, and that is exactly what belongs on the page.

AI is a great companion for this exercise, but only in the second step. You are best off writing the first draft with pen and paper. Writing by hand forces you to decide on every word and quickly shows where your own thinking is still fuzzy, whereas a language model likes to produce smooth, general sentences that sound clever and still fail the reversal test. Once your page exists, AI helps all the more with refining it: have it put every sentence through the reversal test, look for contradictions between the sentences, turn vague wording into the form "A over B", or play a new colleague who is supposed to decide an open question with your page. How to build a structure in which strategy and governance are not only documented with AI but used effectively in everyday work is described in our article Compliance that answers in everyday work. And if you want to build that for your company, get in touch.

This works particularly well with a sparring partner who is not part of the company. Someone from outside does not know your internal assumptions, so they ask the naive questions nobody inside asks any more, and they have no stake in how the decision turns out. That can be a business friend in a similar situation, a founder from your own network, or a mentor. And if you are looking for someone to take on that role and think through the technical side along the way, we are happy to be your sparring partner.

Measure what triggers a decision

Every strategic decision is a bet that something will change. To make it verifiable, each sentence of the strategy gets a metric, and for that metric a simple rule applies: it is only good if a change forces or enables a decision. Everything else is a vanity metric, a number that points nicely upwards in the report and still makes nobody do anything differently.

The test is a single question: what would we do differently if this number rose or fell by a fifth tomorrow? For an app’s number of downloads, the honest answer is usually: nothing. It goes up with every ad campaign but does not tell you whether the app delivers on its promise. It is different with the share of users still active after 30 days. If it falls, something is wrong with the product and the team has to act. If it rises clearly, the chosen path holds and you can put more into it.

For the metric to actually lead to a decision, you set it up as a corridor rather than a single number. The corridor has a target, a risk threshold and an opportunity threshold, and a decision is attached to each threshold in advance. For the finance app and its sentence "simplicity over breadth of features", it looks like this:

Simplicity over breadth of features

Metric: active after 30 days
Target: 50 %

below 35 % → pause new features,
             simplify onboarding
above 60 % → invest in marketing

The trick is that the decisions are settled before the number moves. If the value slips below the threshold, nobody debates whether that is bad; the team does what was agreed, without waiting for management. That way measurability pays into speed as well. How to set up such corridors properly is described in detail in our article Getting KPIs right. And how to derive concrete goals for individual teams and periods from the strategy, for instance with OKRs, is the subject of an article of its own.

What this means for you

A strategy is not measured by the beauty of its slides, but by how many decisions can be made without you, and made well. That takes clear levels from vision to tactics, deliberate choices including what you do not do, sub-strategies that point in the same direction, and open communication that also explains the paths you rejected. Then the strategy becomes a tool for speed, instead of a document taken out once a year. If you want to sharpen your strategy, or finally write it down so the team can decide by it, we are happy to do that together.