To realign an executive team, you need to rebuild agreement on three specific things in a specific order: what the strategy means in practice, who owns which decisions, and how the team will handle it the next time they disagree. Skip the order and, in my experience, the realignment doesn't hold, because a team meeting to discuss ownership without first agreeing on strategy just relocates the disagreement rather than resolving it.
By the time a CEO tells me the team has lost alignment, it has usually been true for months. The good news is that realignment is a specific, sequenced piece of work. The bad news is that the sequence is the part people skip, because it feels like work already done. If you are not yet sure the diagnosis is right, start with seven signs an executive team is not aligned, then come back.
Why do executive teams lose alignment in the first place?
It rarely happens through open conflict, which is why it is so easy to miss until it is embedded. Far more often alignment erodes one small unresolved disagreement at a time, until eight months later nobody can explain when it happened but everyone can feel it. A strategy gets agreed at an offsite, then interpreted five ways by five functions over the following quarter, and nobody surfaces the gap until the interpretations have produced conflicting execution on the ground.
I get called in at a recognisable moment. A CEO tells me the executive team used to move well together and now every decision feels like wading through mud, but nobody can point to an incident that explains it. That is the tell. Alignment that broke over one event usually gets fixed by addressing that event. Alignment that wore away without a nameable cause needs the full sequence, because the drift happened across strategy, ownership and unresolved disagreement all at once. The structural reasons it happens as a company grows are in why leadership teams lose alignment as companies scale.
How do you realign an executive team, step by step?
Three agreements, in this order: what the strategy means in practice, who owns which decisions, and how the team will handle its next disagreement. The order matters because each step depends on the one before it. A team that argues about ownership before it agrees what the strategy means is only moving the disagreement into new role boundaries. The table sets out each agreement with an owner, a suggested time box and a test that it has held. The time boxes are my working suggestions from how this work tends to run, not benchmarks, so adjust them to your team.
| Order | The agreement | Who owns it | Suggested time box | What you have at the end | How you test it held |
|---|---|---|---|---|---|
| 1 | What the strategy means as weekly decisions in each function | The CEO convenes; each executive writes their own answer before the session | One working session, then a week to finish the written versions | A one-page statement of what we will and will not do, with each function's translation side by side | Ask someone two layers below an executive to state the strategy and compare it with the page |
| 2 | Who decides what, with overlaps and orphans closed | The CEO assigns; the team challenges overlaps in the room | One session, then a written decision-rights map within a week | A written map of the recurring decision types and their single decider | Within 30 days, list every decision that was reopened or escalated, and trace each to a gap in the map |
| 3 | How the team disagrees, decides and escalates | The whole team agrees it; the CEO enforces it first | About 90 minutes, then used on the next real disagreement | A one-page protocol: who has final say, the escalation path, the time limit | The next real disagreement is closed by the protocol within the time limit, not parked |
Notice what the table leaves out: no values exercise, no personality profile, no trust fall. Those can be useful, but none of them is the repair. The repair is three written agreements that change how decisions get made on Monday.
Step one: Rebuild agreement on what the strategy means
This is the step everyone wants to skip, because it feels done already, and challenging that assumption in the room can feel slightly confrontational. It has not been done, not in the way that matters. Agreeing a strategy statement at an offsite and agreeing what it means for each function's weekly decisions are two different things, and the gap between them is where alignment first leaks. Realignment starts by putting the strategy back on the table and asking each executive, in plain terms and in writing, what it means for their function specifically. A polite nod around the table is not evidence of shared understanding.
What surfaces is uncomfortable and useful: three different, incompatible readings of the same priority, each reasonable from inside one function, each pulling the business a little differently. Naming that gap in the room is not a failure of the earlier strategy work. It is the actual work of realignment, and jumping to fixing symptoms is the most common reason realignment attempts do not hold.
I say the discomfort deliberately, because pretending it away is one of the ways these attempts fail. Executives do not enjoy discovering, in front of their peers, that they have been executing a different version of the strategy for two quarters. The instinct is to smooth it over and move to solutions. Resist it. A reconciliation nobody fully believes in does not survive the first hard week.
Step two: Rebuild ownership, not just understanding
Once the team agrees what the strategy means, and I mean agrees, the next gap is almost always ownership. Misaligned teams tend to have overlapping authority in some areas and orphaned decisions in others, gaps nobody designed that accumulate as the business grows and roles shift. Realignment means naming, in writing, who owns each major decision category, closing the overlaps and the orphaned gaps at the same time. Leaving either one recreates the drift that caused the problem. The mechanics of who decides what are covered in how to improve executive team decision making.
Four moves that sit under the three agreements
- Surface: Put the strategy back on the table and ask each leader, individually, what it means for their function. Expect real gaps to appear.
- Reconcile: Resolve the competing readings openly in the room, instead of letting the most senior voice win by default.
- Reassign: Close ownership gaps and overlaps in writing, so decision rights match the reconciled strategy and not old assumptions.
- Rehearse: Agree in advance how the team will handle its next real disagreement, so misalignment does not rebuild the same way.
This step meets the most resistance, because naming an overlap can feel like an accusation, as though it means someone has been overstepping. It usually does not. Overlaps and gaps build up as businesses grow and reorganise, without anyone deciding that two functions should both feel responsible for one decision, or that no one should. Naming it is not blame. It makes visible what has been true for a while so the team can fix it deliberately.
Step three: Agree the disagreement protocol before you need it
The step that makes realignment last is agreeing in advance how the team will handle its next real disagreement. Most misalignment does not come from one catastrophic decision. It comes from a hundred small ones with no clean way to resolve them, each leaving a residue of tension that compounds. A team that has agreed how disagreement is resolved, who has final say and what the escalation path is, stops accumulating that residue, because each disagreement gets closed instead of parked.
Keep the protocol short enough to remember. Who decides when the team cannot agree. How long a disagreement may stay open. What the person who loses is expected to do afterwards. The last one matters most: a team that can disagree in the room and commit together outside it is a team whose alignment survives pressure. If the pattern at the seams between strong executives is your problem, why strong executive teams still fail at the seams goes deeper.
What does the evidence say about the gap between strategy and results?
Two sources help here, and I use both for the mechanism and not as a prediction for your company. The first is Harvard Business Review, 2005. Michael Mankins and Richard Steele reported a survey, run in the autumn of 2004 with the Economist Intelligence Unit, of senior executives at 197 companies worldwide with sales above $500 million. Their research suggested companies on average deliver only 63% of the financial performance their strategies promise. They attribute the gap to a combination of factors, including poorly formulated plans, misapplied resources, breakdowns in communication and limited accountability for results. The survey is two decades old and measures financial forecasts, not alignment as such, but the last two causes are exactly the ones this sequence targets.
The second is McKinsey's 2025 article on the scale-up conundrum. It names the top team as the final and arguably most important factor in getting a growing company through the change from founder-led to industrialised growth, and it says one of the decisions is whether, and when, to bring in executives experienced in scaling, because the skills needed to lead a start-up and to be a senior executive of a company ready to list are very different. It warns that procrastinating on that call can undo or prevent good work on every other factor. I read that as support for treating the executive team as a designed system, not a group of capable individuals, which is the argument I make in building executive teams that perform.
Why realign an executive team together, not individually?
A natural instinct when a team has drifted is to coach each executive individually: communication, self-awareness, willingness to collaborate. That work has value, but it does not fix alignment on its own, because alignment is not a property any individual holds. It is a property of the relationships and agreements between them. You can improve every person and still have a misaligned team, because the gap was never inside one person. It was in the space between them, in the unreconciled readings of the strategy and the unclear ownership that individual coaching does not reach.
So realignment is done in the room, together, not as five parallel conversations between each leader and a coach or the CEO. The reconciliation has to happen visibly, with everyone present to hear where the readings diverged and to watch the ownership gaps close. Alignment negotiated behind closed doors and then announced tends to unravel at the first real disagreement. There is a trust cost, too. When realignment happens through side conversations, each executive sees only their piece and has to take it on faith that everyone else agreed to the same thing. That faith erodes the first time two functions execute differently again. Doing it together removes the need for faith, because everyone heard the same commitments made out loud.
What does a realignment look like in practice?
Here is an illustrative scenario, invented for this article and not a client. Suppose a software company of about 250 people has six executives and a stated priority of moving upmarket. In the first session each executive writes, separately, what that priority means for their function this quarter. Sales writes about larger deals. Product writes about enterprise features. Customer success writes about retaining the mid-market base that pays the bills. Finance writes about holding margin. Nothing in the answers is wrong. Together they describe three different companies.
The team spends the session choosing: which segment gets the next engineering quarter, and what each function will stop doing to make room. In the second session it writes the decision-rights map and finds that pricing exceptions have two owners and renewal terms have none. In the third it agrees that a decision stays open for no more than a week, that the CEO decides when the owner and the challenger cannot agree, and that the person overruled commits publicly. Six weeks later the test is simple: how many decisions were reopened, and which line in the map explains each one.
- Name the drift honestly before fixing anything: Say specifically where readings of the strategy diverged. Vague acknowledgement that things have not been quite right gives the team nothing concrete to fix.
- Reconcile strategy before touching structure: Fixing ownership before agreeing what the strategy means just relocates the disagreement into a new set of role boundaries.
- Put ownership changes in writing: Verbal agreement about who owns what fades within weeks. A written, referenceable decision-rights map survives the next disagreement.
- Rehearse the next disagreement, do not just resolve the last one: A team that only fixes what went wrong will drift again on the next thing that goes wrong differently. Agree the protocol, not just the fix.
How long does it take, and how do you know it has held?
The three working sessions can happen in a few weeks. Whether the realignment holds is a separate question, and the answer arrives over the following quarter. I look for three signals at thirty, sixty and ninety days. At thirty days, decisions are being reopened less often, and each reopening traces to a gap in the map that gets fixed. At sixty days, people two layers down can state the strategy in words close to the one-page version. At ninety days, a real disagreement has been closed by the protocol, including one that cost somebody a position they wanted. I read those signals as a stage the team has reached, not a score, which is the idea behind what a team health arc is.
If those signals are not appearing, the usual cause is that the CEO has not honoured the map. The first override after publishing teaches the team more than the document does. That pattern is the same one I describe for founders who stay in every decision in how founders stop being the bottleneck as they scale. If the structure is the issue and you want it designed with you, that is the work inside the Architecture Accelerator, and team coaching covers the working sessions. The free Leadership Capability Diagnostic is a sensible first step, and the CapabilityAI page explains how to map which decisions currently depend on too few people.
What is the difference between a reconciled team and a realigned one?
A reconciled team feels better after the session. A realigned team decides the same way on Monday with nobody in the room. You do not realign an executive team by getting everyone back together for a retreat and reminding them that they are on the same side. You realign it by reconciling what the strategy means, closing the ownership gaps that let readings diverge, and agreeing how the next disagreement will be settled before it happens. Skip any of the three and the alignment you rebuild will drift again, usually within a couple of quarters, for the same structural reasons it drifted the first time.