The Strategy That Never Left the Room

A leadership team meeting at a conference table, one leader reviewing a weekly calendar on a laptop while taking notes

You walk out of the quarterly leadership meeting with three priorities clear in your head. You could recite them to anyone who asked. Then you get back to your desk, open your task list, and go back to assigning the same work you were assigning last week.

Nobody decided to disconnect the two. It just happens. The meeting produces clarity for the person in the room. It produces nothing for the eight or twelve people who report to that person, because the only artifact that made it out of the meeting is what's in your head, and your head isn't a deliverable.

So the team keeps working on what they were already working on. Most of it is probably fine. Some of it quietly isn't. A project that made sense two quarters ago is still running on its own momentum, with no one checking whether it still connects to anything the company is actually trying to do this quarter. You find out it's drifted when someone above you asks why resources are going there, and you don't have a clean answer. Or you find out when someone on your team asks, almost offhand, "wait, why are we doing this again?" and you realize you're reconstructing the logic in real time instead of stating it.

That question, "why are we doing this," is the tell. It's not just a communication gap, it's a decision-rights gap: no one ever decided who's allowed to keep a project running without checking it against this quarter's priorities, so nothing forces the check until it's too late to do quietly. If you're building the answer on the spot, the connection between company direction and team work was never written down. It lived in your head, and heads are unreliable distribution systems. DDI's October trust research shows how much rides on that distribution. Only 31% of leaders trust senior leadership, and the number falls to 21% among individual contributors, the people carrying out the decisions. Leaders who do trust senior leadership are 5.9 times more likely to say its decisions translate into action. Meanwhile, Betterworks' 2026 survey found that 59.6% of business leaders see priorities change at least quarterly, but only 36.8% say formal goals change that quickly. The priorities move, the written goals don't, and your head is the only place the two get reconciled. The same ambiguity resurfaces every few weeks, in slightly different words, and you pay the Escalation Tax each time: re-explaining the logic from scratch because there's nothing to point to.

Here's the shift. Instead of carrying the connection in your head, put it on one page. Company priorities at the top: the two or three that actually matter this quarter, not the eleven from the strategy deck. Your team's current initiatives in the middle. A line between each initiative and the priority it serves, or just as useful, the honest acknowledgment that a line doesn't exist yet.

That third category is where the real work happens. Some of what your team is doing will map cleanly. Some will map indirectly, a few steps removed but still defensible. And some won't map at all. That's not an indictment, it's information.

Work with no visible connection to current priorities falls into one of three places: it gets paused, it gets reframed so the connection is real instead of assumed, or it gets explicitly named as necessary-but-not-strategic: maintenance, compliance, the stuff that has to happen even though it won't show up in a priorities deck. Naming it that way is itself useful. It stops you from quietly treating housekeeping work as if it were strategic work, and it stops your team from wondering why something that feels secondary keeps getting top billing.

Once the page exists, it's not a strategy presentation. It's a 15-minute conversation with two questions: what on this page surprises you, and what should we be doing that isn't here. You're not briefing the team. You're checking the map against what they actually see from where they sit, which is often a more accurate vantage point than yours.

Before that conversation, the pattern repeats every few weeks: someone asks why, you reconstruct the logic live, the clarity lasts until the next ambiguous assignment. After it, the question mostly stops getting asked, because the answer is already sitting on a page people have seen. The three weeks of ambient "wait, why are we doing this" gets replaced by one direct conversation, once a quarter, that actually resolves it.

What would your team say surprised them if you put this page in front of them tomorrow?

If the honest answer is "I don't know, I've never built the page," start smaller than a two-week commitment. The Executive Escalation Assessment is a free, under-12-minute diagnostic that shows you where the Escalation Tax is actually costing your team, before you build anything. From there, the Lead Better Sprint is where the Strategic Cascade gets built: a two-week sprint for managers, and the Strategic Cascade is one of five tools you build inside it, the one that turns "they should just know what matters" into something you can actually hand someone and ask about.

Where Are Decisions Getting Stuck on Your Team?

The Executive Escalation Assessment shows where decisions route back up to you and what it costs, in under 12 minutes.

Lead Better in 2026 – Without Carrying the Whole Team on Your Back Find out how →

Close Welcome Bar
Scroll to Top