When Your Leadership Team Is in Different Movies
Ask a leadership team what's happening in the business and you'll get five different answers.
Not five different opinions about what to do. Five different reads on what's actually going on. One person thinks the core problem is operational. Another thinks it's a market shift. A third thinks the team needs to be restructured. The CEO thinks the strategy is right but the execution is slow. The head of sales thinks the strategy is wrong.
Everyone is describing the same company. Nobody is in the same movie.
Leadership team alignment problems are more common than teams admit, and more costly than they realize. The misalignment doesn't just slow down decision-making. It means that every meeting is partly a negotiation about what's true before anyone can start discussing what to do. That negotiation is usually invisible, which makes it worse.
Why Leadership Teams Can't Agree on What's Happening
Each person on a leadership team sees the business from a different vantage point. The CFO sees it through the numbers. The head of sales sees it through the pipeline and the competitive conversations happening in the market. The COO sees it through operations and capacity. The CEO sees it through all of these, imperfectly filtered through what each person chooses to surface.
These different vantage points are a feature of having a leadership team. The problem is that they tend to produce different conclusions about what's fundamentally happening, and teams rarely surface that disagreement directly.
Instead, the disagreement shows up in the way decisions are made. Why does every strategic conversation stall? Why does the same debate keep recurring? Why does alignment in a meeting dissolve by the time anyone tries to act on it? Often, it's because the team is trying to decide what to do before they've agreed on what kind of moment they're in.
The Difference a Named Moment Makes
Working backward from a shared reference point is more productive than building a shared view from scratch.
Consider what happens when a leadership team tries to diagnose a situation from open discussion. One person describes the symptoms they're seeing. Another person interprets those symptoms differently. A third person introduces additional context that reframes the first two. An hour later, the team has more information and less clarity.
Now consider what happens when someone says: "I think we're in a Starbucks 2006 moment: the model is still working, but the decisions we've been making to scale it are quietly eroding the thing that made it work."
That statement does something different. It's not an open invitation to share observations. It's a hypothesis with a specific shape. The team can evaluate it directly: does this fit? What's different about our situation? Where does the analogy break down? The debate becomes convergent rather than divergent. You're narrowing toward a shared read rather than expanding outward into everyone's individual perspective.
This is what a named moment provides: not a definitive answer, but a focal point for a more efficient conversation.
What the Name Enables
Once a team agrees, even provisionally, on what kind of moment they're in, several things become possible that weren't before.
Decisions get easier to frame. A grow-or-hold moment implies certain decisions and defers others. A forced-transition moment implies a different set. When the team knows what kind of moment they're in, they can evaluate options against that frame rather than against each person's implicit model of the situation.
Disagreement becomes more productive. When someone pushes back on a decision in a grow-or-hold moment, the disagreement now has a precise address. "I don't think we're in a grow-or-hold moment. I think we're in a model-straining moment, and the expansion risk is different." That's a useful argument. It's specific. It can be resolved with evidence. Generic disagreement about strategy rarely can.
The team can hold the frame over time. Meetings happen. Personnel changes. Memory fades. A named moment, one that the team has explicitly agreed on, provides continuity. New information can be evaluated against the frame: does this change what kind of moment we're in, or does it fit the existing read?
The Alignment Problem Is a Diagnosis Problem
Most leadership alignment work focuses on process: better meeting structures, clearer decision rights, more explicit communication norms. These are useful. But they address the symptom rather than the cause.
The underlying cause, in many cases, is that the team hasn't agreed on what's happening. They've agreed on the numbers. They've agreed on the priorities. They haven't agreed on the nature of the moment, which means the priorities are being evaluated against different implicit contexts.
Naming the moment is a diagnostic act. It forces a specific, shared answer to the question the team is usually circling without landing: what kind of moment is this, exactly?
When a team can answer that question, when they can say with some confidence "we're in a grow-or-hold moment" or "we're in a forced transition," the alignment that felt impossible from the inside becomes much more achievable. Not because everyone now agrees on everything, but because everyone is now disagreeing about the same thing.
That's the productive version of leadership team conflict. It requires a shared reference point to get there.
If you're not sure what kind of moment your business is in, or you suspect your team has different answers, that's what MyCompanyMoment is built to help with.
Frequently Asked Questions
What does leadership team misalignment actually look like in practice?
It rarely looks like open conflict. More often, it looks like meetings that keep revisiting the same decisions, strategic initiatives that lose momentum after launch, or a pattern where everyone agrees in the room and nobody acts consistently afterward. The misalignment is usually invisible because each person assumes the others share their read on the situation. They don't surface the disagreement because they don't realize there is one.
Why doesn't better communication fix leadership team misalignment?
Better communication helps when people disagree about what to do. It doesn't help when people have different reads on what's happening — because the communication is operating on the wrong level. You can be exceptionally clear and direct with each other and still be in different movies about the nature of the situation. The fix isn't more communication; it's a shared diagnosis of what kind of moment the business is in.
How do you use a named moment in a leadership team meeting?
Present it as a hypothesis, not a verdict. "I think we're in a grow-or-hold moment — here's what that means and here's why I think it fits." Then invite the team to evaluate it: does this fit our situation? Where does it break down? What would be different if we were in a different kind of moment? That framing makes the conversation convergent rather than open-ended. The team is evaluating a specific claim rather than assembling a picture from individual perspectives.
What if the team disagrees about which moment we're in?
That disagreement is productive — it's exactly the kind of argument a named moment is designed to surface. "I don't think we're in a grow-or-hold moment; I think we're in a model-straining moment" is a specific, resolvable disagreement. You can look at evidence, refine the framing, and converge. Generic disagreement about strategy — "I think we have a growth problem" versus "I think we have an execution problem" — is much harder to resolve because the two claims don't have a common reference point.
How is this different from a SWOT analysis or a strategic planning process?
A SWOT analysis produces a list of factors. A strategic planning process produces a set of priorities. Neither produces a shared diagnosis of what kind of moment the business is in — which is the thing that makes the priorities meaningful. A named moment gives the team a frame for evaluating options, not just a catalog of information. The difference shows up in execution: a team that agrees on the moment evaluates every subsequent decision against that frame, which keeps alignment from dissolving between meetings.
Can one person on the team use this approach even if the rest of the team isn't familiar with it?
Yes. You don't need everyone to have read the same framework. You need one person to introduce a named hypothesis into the conversation: "I've been thinking about our situation and it reminds me of Starbucks in 2006 — a model that's still growing but showing strain at the edges. Here's why I think that fits." The hypothesis does the work. The team responds to the specific claim, not to the framework behind it.