She reads the weekly summary. The leadership team has been aligned on the year's three big bets for two months. The strategy doc says so. Every leader can recite the bets. The board has been briefed.
She opens the calendars. Three weeks of leadership team time. She tags every meeting against the three big bets.
The bets account for thirty-one percent of the time.
She looks closer. Sales has been working on a different priority — a quota push that emerged when a competitor moved. Marketing has been working on a brand refresh nobody put in the strategy doc. Operations has been working on tools nobody finished implementing. Delivery has been working on the customers who actually called this week.
None of it is wrong. All of it is happening. None of it is moving in the same direction.
The leadership team is not in disagreement. They are in agreement that no longer travels.
She notices the sales leader who stopped bringing the harder strategic question to the leadership team somewhere in the spring.
She notices the marketing function that is building for the brand it wishes it had, instead of the customers it has.
She notices the operations work that is completing a tool implementation nobody is using anymore.
She notices the delivery team that is quietly carrying the customers nobody else is paying attention to.
She did not choose this. None of the leaders chose it. Each function adjusted to the small urgent thing in its own week and stopped checking against the bets that were supposed to be the year.
This is what misaligned growth looks like before anyone calls it that.
For most operators, the pattern becomes visible only after a quarter has been spent producing results that, in aggregate, do not move the year's priorities. The early signal is not a missed number. It is a slow drift in what each function actually does on a Tuesday, away from what the leadership team agreed in January. What follows is what the pattern actually is, where the translation breaks, why aligned teams drift faster than you would expect, and what it looks like to re-align without re-running the strategy offsite.
What Misaligned Growth Actually Is
You sit with the calendars open. You sit with the strategy doc open. You compare.
The doc says the year is about three bets. The calendars say the year is about something else.
Misaligned growth is the gap between where a leadership team has agreed the business is going and where the daily work of each function is actually moving it.
It is not strategic disagreement. Strategic disagreement is loud. It surfaces in leadership meetings. It produces debate. It can be resolved.
Misaligned growth is the quiet version. The leadership team agrees. They agreed in January. They will agree again at the next QBR. They have not disagreed in any meeting. And yet, function by function, week by week, each leader is making local decisions that drift away from the shared bet.
The shape of the pattern
A leadership team agrees on three bets at the start of the year. Each leader walks out of the offsite and translates the bets into what their function will work on. The sales leader translates them into pipeline targets. The marketing leader into campaigns. The ops leader into systems. The delivery leader into account commitments.
Each translation is faithful in the room.
Between the room and the work, the translations diverge. The sales leader's translation runs into a competitor move, and the function adapts. The marketing leader's translation runs into a brand audit, and the function adapts. The ops leader's translation runs into a tool replacement that takes longer than expected, and the function adapts.
Each adaptation is local and reasonable. None of them returns to the room to re-check against the original bet.
After six weeks of local adaptations, the four functions are no longer doing the work the bets implied. The bets are still on the wall.
Why it is not the same as strategy drift
Strategy drift is when the leadership team decides to change direction. The strategy on the wall in March is not the same as the strategy on the wall in January, and everyone knows it.
Misaligned growth is when the strategy on the wall has not changed and the work has. Nobody is hiding this. Nobody is lying. The leaders genuinely intend to be working on the bets. Their teams are genuinely intending to support them. The drift is happening below the level at which the strategy gets discussed.
The fix to strategy drift is to make the change explicit. The fix to misaligned growth is harder, because there is nothing to make explicit. There is only a slow re-checking of where each function actually is, against where everyone agreed it would be.
How It Shows Up Before You See It
The leadership team has a Monday meeting. The dashboards are green. The numbers are on plan. Everyone reports forward motion.
In a Wednesday one-on-one, your CRO mentions a competitor move that has been taking up bandwidth. You ask her if it is worth a strategy adjustment. She says no, she has got it. The conversation moves on.
The pattern shows up first in the texture of the conversations, not in the metrics.
The leader who stops bringing the harder question
There is one leader on the team who used to surface the structural tension at every leadership meeting. We agreed on Bet A, but I am seeing my function pulled toward B. How do we want to handle that.
Six months later, that leader does not bring up the tension anymore. She brings forward-motion updates. She reports green. She is moving fast.
She did not stop noticing the tension. She stopped surfacing it. Somewhere in the spring, she decided that the tension was hers to manage rather than the team's to resolve.
When you find this leader, you have found a sensor. She is reading misalignment in real time and absorbing it at the function level. The cost of her absorbing it is that the team no longer hears about it.
The function building for the wishful brand
Marketing is building campaigns that target the customer the company wishes it had — the larger account, the more strategic buyer, the customer at the next stage of company maturity. The campaigns are well-crafted.
Sales is closing the customer the company actually has — the smaller account, the tactical buyer, the customer at the current stage. The campaigns are not generating these leads. Sales is generating them through other channels.
Marketing's work is real work. Sales's work is real work. The two functions are pointed at different customers. Neither function is wrong inside its own frame. The frames are different.
The operations work nobody is using
Operations finished implementing the new tool last quarter. The tool was the right answer to the question of how to scale.
The team has not adopted the tool. They have continued using the old tool. The migration meetings are quietly being skipped. Operations is following up. The team is polite. The tool is sitting there.
The operations function is operating against an assumption — that the team will adopt — that the team has stopped reinforcing. Operations has not noticed yet because the adoption signal is being absorbed by the team's politeness.
The reconstruction tax at the leadership level
The Tuesday leadership meeting opens. The first ten minutes are spent on a question that was supposedly settled at the QBR. Are we still prioritizing Bet A. I thought we agreed at the offsite that this was the year. Did we.
Then twenty minutes of pulling threads, comparing recollections, eventually settling on a working version that may or may not match what the strategy doc says.
Multiply by the number of leadership meetings per quarter. That is the reconstruction tax at the leadership level. It is paid in the most expensive currency the company has — the time of the leadership team — and it is the receipt for misalignment the strategy doc is not catching.
The leadership team is not in disagreement. They are in agreement that no longer travels.
Agreement That No Longer Travels
The leadership team agreed on the bets in January. The agreement was real. Each leader walked out believing the team was aligned.
In May, the agreement is still in the strategy doc. The work has diverged.
The agreement no longer travels.
Translation entropy
An agreement is made in language. The language has to be translated by each function into specific work. The translation is the moment the agreement leaves the room.
The translation is not free. Each function has to interpret the agreement in light of its own constraints — its team, its tools, its customer touchpoints, its market signals. The translation is faithful to the agreement in the room and adapted to the constraints outside the room.
When the constraints change — and they always do — the translation gets re-adapted. Each re-adaptation is small. Each one is locally rational. None of them returns to the original room.
After enough re-adaptations, the function is working from a translation of a translation of the original agreement. The original agreement is no longer in the loop. The strategy doc on the wall is a record of a translation that no longer matches any of the active work.
This is translation entropy. Agreements decay in the direction of local adaptation unless something actively re-checks them.
The cost of not re-checking
Re-checking against the original agreement feels like overhead. The leaders are busy. The agreements seem clear. Surfacing the tension feels like adding work nobody asked for.
The cost of re-checking is small and immediate. The cost of not re-checking is large and delayed. A quarter of misaligned work costs the same as a quarter of aligned work, but only one of them moves the year's bets.
By the time the misalignment is visible in the numbers, it is two or three quarters too late to recover the year.
Where the Translation Breaks
The leadership team can name the bets. The function teams cannot, all of them, name the work that supports the bets. The break is not at the top. The break is somewhere below.
The translation breaks in specific places. Naming them is the first step in seeing the pattern.
Between the offsite and the Monday plan
Five leaders leave the strategy offsite. They have agreed on the bets. They go back to their functions. Each one has a leadership meeting on Monday to roll out the implications.
In each function's Monday meeting, the bets get translated into the function's work. The translation is led by the leader who was in the room. The function team members were not in the room.
The function teams now have a version of the bets filtered through their leader's interpretation. The leaders' interpretations diverge slightly because each one heard the same words through a different functional lens.
By the time the team is doing the work, the work is one translation removed from the room. By the time the team adapts to a market signal, the work is two translations removed.
In the function's weekly planning
Each Monday, each function plans the week. The plan starts from the function's queue — open opportunities, in-flight campaigns, current implementations, customer commitments.
The bets show up in the plan as background, not as foreground. The foreground is what is in the queue. The background is what the function is supposed to be moving toward.
When the foreground is heavy, the background gets quietly deprioritized. Not removed. Just postponed. Each postponement is small. The aggregate is the misalignment.
In the absence of cross-function check
Sales plans its week. Marketing plans its week. Operations plans its week. Delivery plans its week.
The four plans are not laid against each other. There is no Monday meeting where the four functions check whether their weeks are pointing the same direction. The check happens, if at all, at the next leadership meeting, against the dashboard, two weeks later.
By then, the divergence has compounded. The four leaders look at the dashboard, see that the numbers are on plan, and conclude that the functions are aligned. The numbers are reporting the same thing each function was doing inside its own frame. They are not reporting the alignment between the frames.
Why Aligned Teams Drift Faster Than You Would Expect
A leadership team that meets weekly, reviews dashboards, holds QBRs, and runs annual planning will tell you they are aligned. They will tell you their team is in the most aligned state it has ever been in.
They are not lying. They are also not catching what is drifting.
Surface alignment hides functional drift
Surface alignment is what shows up in the meeting. The bets are named. The numbers are reported. The leaders agree.
Functional drift is what shows up between the meetings. It is what each function adapts to in its own week. It does not show up in the meeting because the meeting is not the place where functional drift is visible.
The meeting is the place where surface alignment gets renewed. Functional drift continues underneath the renewal.
The faster the cycle of renewal — the more leadership meetings, the more dashboards, the more QBRs — the more confident the team feels that they are aligned. Confidence is not the same as alignment. The cycle of renewal can mask drift by giving the team a recurring opportunity to feel aligned without actually checking what each function is doing.
High performance compounds the gap
The functions that drift fastest are usually the highest-performing ones. They have the most operational competence. They are the most willing to adapt locally to market signals. They are the most able to absorb tension at the function level.
These are virtues. They are also what produces functional drift fastest. The function adapts, performs, and absorbs. The leader reports green. The team feels successful. The drift accumulates inside the success.
The leadership team that mistakes function-level performance for cross-function alignment is the team most exposed to misaligned growth.
Confidence is not the same as alignment. The cycle of renewal can mask the drift.
What Re-Alignment Actually Looks Like
The leadership team holds a special meeting. They re-affirm the bets. The functions go back to work. Six weeks later, the calendars look the same as before the meeting.
The methodology was not wrong. The methodology cannot fix the problem.
Not a strategy offsite
Misaligned growth is not a strategy problem. It is a translation problem. The bets are fine. The agreement is fine. The translation between the agreement and the daily work is what has decayed.
Another offsite produces another agreement. The agreement decays the same way the last one did, because the offsite is the moment of highest alignment and lowest translation pressure. The translations begin again the moment the leaders walk out of the room.
The functional calendar check
A different exercise. Once a month, each leader brings two weeks of their function's calendar to the leadership meeting. The four calendars are laid against the bets.
The question is not whether the calendars are full. The question is what percentage of the calendar is moving the bets, and where the rest of the time is going.
The exercise is uncomfortable. The percentages are usually lower than the leaders thought. The conversation that follows is the conversation the team was not having — the conversation about where the actual work is, not where the strategy says it should be.
From there, re-alignment is small and specific. Not a new strategy. A re-decision about what each function will move toward this month, given what the calendars actually show.
The shared dashboard the team did not have
Many leadership teams have a dashboard. Few of them have a dashboard that shows the cross-function alignment.
The dashboard the team usually has shows function-level metrics — pipeline by stage, campaigns by channel, customer satisfaction by segment. Each metric reports inside a function's frame.
The dashboard the team rarely has is the one that shows where the four functions are pointed in the same direction and where they are not. It is harder to build because it requires shared definitions across functions. It is harder to maintain because the definitions decay too.
When this dashboard exists, the leadership team can see misalignment in real time rather than at the QBR. When it does not exist, the team has to reconstruct alignment from individual function reports, and the reconstruction is exactly the place where misalignment hides.
What this is not
It is not micromanagement. The leaders do not need to manage the functions' weeks. They need to see the aggregate.
It is not a strategy change. The strategy is usually fine. The translation is what needs the attention.
It is not a one-time fix. Translation entropy is constant. The re-checking has to be constant too.
When You Notice It in Your Own Work
The reader test for this pattern is concrete.
Open your calendar for the last three weeks. Tag every block of leadership time against the bets you committed to at the start of the year. Be honest. If the block does not actually move a bet, do not tag it.
What percentage of your leadership time is moving the bets.
If the answer is more than half, the team is in a state most teams envy. If the answer is less than a third, the team is in misaligned growth and the strategy doc is not catching it.
The question is not whether the pattern is real. The pattern is real on every leadership team that has held its agreements for more than a quarter. The question is whether the team is willing to look at the calendar honestly, against the bets, and have the conversation that follows.
This is what I have come to watch for. Not the strategy disagreement. The agreement that no longer travels.
Not the strategy disagreement. The agreement that no longer travels.
This is what I have come to watch for. Not the strategy disagreement. The agreement that no longer travels. If you want to look at where it is showing up in your own work, I run Clarity Sessions — forty-five minutes, one named pattern, one concrete next step with ownership.
Book a Clarity Session →