> Source: https://brendanlevin.com/insights/how-to-communicate-strategy-to-your-team/
> Most strategy presentations do not change behavior because the strategy lives in a slide, not in the weekly rhythm. Here is how to fix that with one sentence, two or three numbers, and a repeating cadence.

For founders, owners, and operators

# How to Communicate Strategy So Your Team Actually Follows It

By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.

Strategy fails to land when it lives in a slide deck nobody reopens. **State the one outcome your team is organised around this year in a single sentence, attach two or three numbers that prove it moved, and repeat it at every weekly meeting.** That repetition is what makes direction real. See also [how to set that direction](/insights/how-do-i-set-direction-for-my-team/).

Key takeaways

-   One sentence, two or three numbers: that is the whole strategy your team can actually act on.
-   Repetition inside your weekly rhythm does more than any all-hands presentation.
-   If your team cannot state the direction without prompting, it has not been communicated yet.
-   Visible, written direction removes the founder as the person who holds strategy in their head.

## Why the all-hands presentation does not change behavior

A presentation is an event. Behavior change is a habit. When you run an all-hands and share a strategy deck, you get a room full of people who nod, maybe ask a question, then go back to the work that was already in front of them. The deck gets filed. The slide gets forgotten. Three weeks later, people are making priority calls the same way they always did.

The root problem is not communication skill. It is not the quality of the deck. The strategy stays in the founder's head because no structure exists to carry it into the week-to-week work. Every time a priority question comes up, the team does one of two things: they route it back to the founder, or they guess. Both are a sign that direction has not been installed in the business, only announced at it.

If you want to know whether your strategy has actually landed, try this test: stop five people on your team individually and ask each one to tell you the single most important outcome the business is working toward this year. If you get five different answers, or five vague ones, the strategy is still in your head, not theirs.

## The format that actually works: one sentence, two or three numbers

Strategy does not need to be a framework or a four-page document. It needs to be a sentence your team can repeat without looking it up. Something like: 'This year we are moving from twenty accounts to thirty-five, with average revenue per account above $28,000 and gross margin above 62 percent.' That is it. One outcome. Three numbers that tell you whether you got there.

The numbers matter as much as the sentence. Without them, 'grow the business' or 'move upmarket' is not a direction, it is a vibe. Two or three specific numbers give every person in the business a way to test whether a decision they are about to make moves the needle or wastes time. That is what turns a strategy into something a team can actually use.

If you are not sure how to construct that sentence, [setting direction for your team](/insights/how-do-i-set-direction-for-my-team/) walks through the process of getting from a broad ambition to a named, measurable outcome.

## What a strategy communication cadence actually looks like

One articulation of strategy does nothing. Repeated articulation inside a standing rhythm is what changes behavior. The mechanism is simple: every weekly team meeting opens with the direction sentence and the current position on each of the two or three numbers. Not a full review. Thirty seconds. 'Here is where we are relative to where we said we would be. Here is the one thing most likely to close that gap this week.' That is it.

This is what [an operating rhythm](/insights/how-to-build-an-operating-rhythm/) does for strategy. It takes direction out of the slide deck and into a recurring structure that every person in the business experiences every week. After six to eight repetitions, your team stops needing to be reminded. They start using the direction to make their own calls.

## The visibility test: can your team see the strategy without asking you?

If the direction sentence and the three numbers exist only in your head, or only in a document you send out once a quarter, your team cannot use them without coming back to you. That makes you the strategy, and every priority question becomes your problem to answer.

Fix this with a single visible artifact. A shared doc. A pinned Slack message. A printed sheet on the wall in your team's main workspace. One place where anyone on the team can look up the direction and the current numbers without asking. This is not a dashboard project. It takes twenty minutes to create and five minutes a week to update. The point is not sophistication, it is visibility.

This is one of the core moves inside [a founder operating system](/insights/what-is-a-founder-operating-system/): take the things that live in the founder's head and put them somewhere the business can hold them.

## How strategy communication and decision rights connect

Clear direction reduces the number of decisions that escalate to you, but it does not eliminate them unless you pair it with clear decision rights. Even if your team knows the direction, they will still come back to you when they are not sure whether a decision is theirs to make.

The practical fix is a written threshold. For example: any spend under $2,000 that falls inside the current quarter's priorities is the owning person's call. They act and tell you after. Above $2,000, or outside current priorities, they flag it before moving. That kind of written, specific threshold, shared with the whole team, removes a large category of escalations. [Setting decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) covers how to build that structure across your team.

Direction and decision rights work together. Direction tells your team what matters. Decision rights tell them how much they can do about it without coming back to you. Without both, you are still the operating system.

## The comparison: what changes behavior versus what does not

Most founders have tried at least one of the approaches in the left column. The pattern is consistent: a one-time event moves the room but not the work.

Approach

What it produces

What it misses

**Annual all-hands with strategy deck**

Shared awareness for a few days

No repeating structure to reinforce it

**Emailed strategy document**

A record the team can search

Nobody reads it after week one

**Verbal reminders from the founder**

Alignment when you are present

Routing back to you when you are not

**One sentence plus two to three numbers in a weekly rhythm**

Direction your team can act on without asking

Nothing, this is the one that works

Strategy travels further when it fits on one page. The Momentum Engine opens with building that page with you, the Operating Compass your team can repeat back without you in the room.

[See the Momentum Engine](/momentum-engine)

## Common questions

How often should I repeat the strategy to my team?

Every week, at the start of your standing team meeting. Thirty seconds: state the direction sentence, share the current position on your two or three numbers, name the one thing most likely to move the gap this week. After six to eight weeks of this, your team begins to use the direction to make their own calls without prompting.

What if my team already knows the strategy but still makes misaligned decisions?

Knowing the strategy and being able to act on it are different things. If your team can recite the direction but still escalates priority calls to you, the gap is usually decision rights, not communication. They know where you are going but not how much they are allowed to do to get there. Write down a specific threshold for each role and share it openly.

How long should a strategy statement be?

One sentence. If it takes a paragraph, it is still a vision, not a direction. Test it by asking whether someone new could use it to decide between two competing priorities on their first week. If they cannot, it is too vague or too long.

My team is small. Do I still need a formal communication structure?

A small team needs it more, not less. With eight to fifteen people, informal alignment feels easy until it breaks, and when it breaks it usually surfaces as conflict or duplicated work rather than a visible structure problem. A weekly standing meeting with a named direction and a visible numbers update takes less time than the conversations it prevents.

Can I just pin the strategy in Slack instead of running a weekly meeting?

You can pin it in Slack and should, but it does not replace the weekly rhythm. A pinned message is a reference. A recurring meeting is where the direction gets connected to this week's actual work. Both serve a function. Neither alone is enough.

What is the link between strategy communication and owner dependency?

When strategy lives in the founder's head rather than in a named, visible, repeated format, every priority call defaults back to the founder by design. The team is not being difficult. There is no structure to hold the direction without you. Installing that structure is one of the core moves in removing [owner dependency](/insights/what-is-owner-dependency/) from a founder-led business.

Related: [how do i set direction for my team](/insights/how-do-i-set-direction-for-my-team/) · [what is a founder operating system](/insights/what-is-a-founder-operating-system/) · [how to build an operating rhythm](/insights/how-to-build-an-operating-rhythm/) · [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [how to scale past the founder](/insights/how-to-scale-past-the-founder/) · [what is owner dependency](/insights/what-is-owner-dependency/) · [more insights](/insights).
