Walk into any company over a hundred people and ask three engineers what the top strategic priority is. You'll get three confident, mutually contradictory answers. Then ask each of them how the ticket they're working on right now connects to that priority. The room gets quieter. This is not a communication failure. The strategy was communicated, in slides, in emails, in town halls, with a pull-quote from the CEO. It was communicated until everyone could repeat the words. What was never built was the structural link between those words and the work in front of them on Monday morning.
Most companies treat strategy as leadership's property. They announce it at all-hands. They cascade it through OKRs. They post it in Confluence and pin it in the team channel. They then spend the next quarter puzzled that teams keep making local decisions which, summed up, point somewhere else entirely.
Three levels of strategic awareness
Strategy actually has three layers of saturation in an organisation, and they are not interchangeable.
Visibility is the shallowest. The team has seen the strategy and can describe the top objectives. Most companies get to here within a quarter of any planning offsite. It feels like progress because the room is nodding.
Understanding is harder. The team understands why the strategy is what it is — the trade-offs, the bets, the customer segments deliberately left on the table, the assumptions that would make leadership change their mind. Fewer companies get here, because it requires leadership to publish the reasoning, not just the conclusion.
Connection is the only level that changes behaviour. Every team member can see how their specific work this week traces to a strategic objective, and which objectives have nothing of theirs attached. Almost no company gets to this level structurally. They rely on managers to do the translation in 1:1s, which means the translation is as good as the manager, and degrades the further down the chart you go.
When a developer can see that the feature they're scoping connects directly to the company's goal of reducing churn, they make different scope decisions. They cut the bells. They invite the customer success lead into the design review. When they can't see the link, they optimise for the ticket — closing it cleanly, on time, in a way that earns them a thumbs-up in standup and accomplishes nothing at the level above.
Why cascading isn't the answer
The instinctive fix is to cascade harder. Better OKR software. A more disciplined planning process. A quarterly all-hands with a clearer narrative. Cascade produces three problems that no amount of discipline solves.
First, by the time an objective has been broken into three nested levels — company to function to team to individual — the original intent is often unrecognisable. The phrase "reduce churn" becomes "improve onboarding NPS" becomes "ship six tutorial videos by Q3." The tutorial videos may or may not reduce churn. Nobody downstream is in a position to know.
Second, cascade requires perfect translation at each level. One manager who doesn't really understand the strategy — who treats the planning exercise as a paperwork task — corrupts everything below them. Cascade has no error correction.
Third, cascade creates the connection on paper but not in the work. The OKR document says the team's project supports objective X. The actual Jira board, where the team spends its days, has no mention of objective X anywhere. The connection exists in a quarterly document that nobody opens between planning sessions.
Cascade is a description of the connection. What changes behaviour is a system that embeds it.
Four practices that actually move the needle
A handful of practices reliably move organisations from visibility to connection.
Put goals and work in the same system. When a task is created adjacent to the goal it serves, the connection is structural rather than documentary. Nobody has to remember to maintain it. When the goal changes, the work attached to it is immediately visible as needing review.
Expose goal context at the task level. Every task should display, by default, which objective it contributes to and what the current health of that objective is. Not in a separate report. In the place the work is being done. The reason this matters is that scope and trade-off decisions happen at the task level, by the person doing the work, often without consulting anyone.
Replace strategy announcements with strategy conversations. Ask each team a simple question once a month: which of your current work items connects to our top objectives, and which connects to none? The exercise reveals misalignment faster than any survey and turns strategy into something teams actively interrogate rather than passively receive.
Make trade-offs explicit and visible. The most useful artefact leadership can publish isn't a goal list — it's the logic behind it. The customer segments deliberately not pursued. The capabilities consciously not built this year. When teams understand the trade-offs, they can apply the logic to new situations without escalating every decision upward.
The Vindaris view
Strategy visibility is treated as a communications problem because the tools companies use force it to be one. Goals live in one system, work in another, headcount in a third, and the link between them lives in a deck nobody updates. The only way to fix this is to put strategy and the work that's supposed to prove it in the same surface, where every contributor can see the line from their task to the bet it serves. At that point, visibility stops being something leadership broadcasts and becomes something the system makes obvious. Connection isn't a slide. It's an artefact, and either the system produces it or it doesn't exist.