To get leadership decisions to the rest of the team, treat sharing as part of the decision itself: write down what was decided, why and what changes, have each leader explain it to their team in person with what it means for them, and then check whether people can explain it back. A decision nobody knows about hasn't really been made.
Why don't employees know about leadership decisions?
Because leaders assume a decision they talked through in the room has already been communicated. It lives in the notes and a few heads. This is about that decision reaching the people who do the work, not about OKRs. Without a step to share what it means for each team, most people never hear it, or hear a distorted version.
Takeaways
- Doing the work and then pushing it forward to the organization is the step most often missed.
- A decision isn't made until the people who act on it know it.
- Cascade in layers: what was decided, why, and what changes for each team.
- Check understanding instead of assuming it.
A go-to-market consultant I talked with recently was blunt about how often this goes wrong. In her experience it's 100 percent of the time, and it's everyone. Doing the work and then pushing it forward to the organization is the step that's so often missed.
I believe her. Most of us have been on both sides of it.
How decisions get stuck
The pattern is familiar. Leaders spend weeks working through a strategy, a new priority or a change in direction. They debate it, refine it and agree. It feels finished.
Then they go back to their teams and say little or nothing about it. Maybe a line in a meeting. Maybe an email. They assume it's spread because they've been living with it for weeks.
Meanwhile, the people doing the work keep doing what they were doing before.
Why it matters so much
A decision only changes results when the people who act on it know about it and understand it. Until then, the strategy exists in a slide deck and a few heads.
Worse, partial communication creates confusion. Some people heard one version, others heard another, and some heard nothing. Work starts pulling in different directions.
Build the cascade into the decision
Make sharing a required step, not an afterthought:
- Write a short summary. What was decided, why, and what changes. One page.
- Each leader shares it live. With their own team, in person or on a call.
- Add the team-specific part. What does this mean for us, specifically?
- Invite questions. And answer them straight, including "we haven't figured that out yet."
- Follow up in writing. So people can refer back.
Repeat more than feels necessary
Leaders get tired of a message long before the team has absorbed it. That's normal. Repeat the key points in team meetings, one-on-ones and updates for weeks. If you're bored of saying it, people are probably just starting to hear it.
Check, don't assume
A week or two later, ask a few people at different levels to explain the decision and what it means for their work. If the answers differ widely, or nothing has changed, it hasn't landed. Go back and fill the gap.
Signs decisions aren't cascading
- People two levels down learn about priorities from customers or rumors.
- Teams keep working on projects leadership already decided to stop.
- Every manager explains the same decision differently.
- All-hands questions show people never heard about a major change.
What to do this week
Pick the most important decision leadership made in the last month. Ask five people, at different levels, to explain it in one sentence and say what it means for their work. Write down what they say. If the answers vary or come back blank, write the one-page summary now, and have every manager share it with their team before the end of next week.
A worked example
Say leadership decides to focus next year on mid-size customers and stop chasing very small accounts. In the version that fails, the decision appears as one slide at an all-hands. Six weeks later, sales is still prospecting small accounts and marketing is still running campaigns for them. In the version that works, every manager walks their team through what changes for them: sales gets a new target list, marketing pauses two campaigns, support updates its priorities. A week later, managers check that people can explain it.
Common mistakes
- Relying on one email. Most people won't read it closely.
- Skipping the "why." People resist changes they don't understand.
- Stopping too early. Repeat it until people can explain it back.
One thing to remember
A decision isn't finished when leadership agrees. It's finished when the people doing the work can explain it, act on it and tell you what changed.
Keep the follow-through from slipping
A lot of decisions die in the follow-through: the reminders, the check-ins, the updates that need to happen after the meeting. Those are exactly the tasks that slip when everyone's busy.
Ants runs AI agents that handle that kind of follow-through — the work that never gets done after a decision.
Ready to put a colony on the work slipping through the cracks? Ants builds, runs and maintains AI agents for follow-ups, renewals, invoices and deadlines. Nothing for your team to babysit. Book a Colony Call.
Questions people ask
How do you cascade decisions through an organization?
Write a short summary of what was decided, why and what changes. Have each leader share it with their team in person, adding what it means for that team specifically. Give people a chance to ask questions. Then check a week later whether people can explain the decision and are acting on it.
Why don't employees know about leadership decisions?
Because leaders often assume that discussing something in a leadership meeting means it's been communicated. The decision lives in the meeting notes and a few heads. Without a deliberate step to share it, with context for each team, most of the organization never hears it or hears a distorted version.
What's the best way to communicate a change to a team?
Explain what's changing, why, what stays the same and what each person needs to do differently. Share it live where possible, then follow up in writing. Invite questions. Repeat the message more than feels necessary, since people rarely absorb a change the first time they hear it.
How can I tell if a decision has been understood?
Ask. A week or two after sharing, ask a few people at different levels to explain the decision and what it means for their work. Watch whether behavior has changed. If answers differ widely, or nothing has changed, the decision hasn't really landed yet.