Nobody Killed the Initiative. It Just Faded.

/in , , , , , , /by

Execution Fade Isn’t a Project Management Problem — It’s a Leadership One

But it started so well…

Most strategic initiatives launch well — clear rationale, visible leadership backing, a kickoff. Then, somewhere around month three to six, the attention quietly moves on.

Steering committee meetings get skipped. Updates get shorter. The thing that was going to change how the organization operates becomes one more line item.

This rarely looks like outright failure.

More often it’s one of three quieter outcomes: the work limps across the finish line, delivered by a team that stopped believing leadership cared about its success.

Or the scope shrinks to match whatever resources are left. Nobody formally decides that or owns it.

Or the bar gets lowered, the team declares victory, and everyone quietly knows what actually happened.

Each version is survivable enough that no one has to name it which is exactly why the pattern repeats.

 

Execution Fade is a leadership team problem, not a project management one. And it has real cost. The sunk budget and resource costs. The project team’s sense that their time was wasted. Another opportunity lost or challenge left partially unaddressed.

 

Two important fixes for Execution Fade.

  • Put the initiative on the standing leadership team agenda and check it against the original intent, not just activity.
  • Make one leadership team member (not the program lead) fully accountable for each initiative. Tie their goals and their incentives to it. Ownership at the program level gets you coordination; ownership at the leadership level gets you commitment.

The launch is the easy part. Sustained attention has to be managed on purpose. Like anything that’s important, it doesn’t happen on its own.

When conflict goes underground

/in , , , , /by

When The Team Doesn’t Disagree In Meetings, There’s a Problem

Two Failure Modes

There are two failure modes when it comes to conflict in leadership teams.

The first is obvious: escalating conflict, openly adversarial peer relationships, meetings that generate more heat than resolution. Most people recognize this as a problem.

The second is more subtle, more common, and often more damaging. Genuine disagreement exists but gets managed rather than resolved. They are discussed openly in hallway conversations but not in the room, separate meetings occur, and functional decisions quietly diverge from what the team appeared to agree on. The goal in the room is to preserve relationships rather than surface real concerns.

This mode produces meetings that look healthy. Calm. Collegial. Efficient. The dysfunction only becomes visible later. I saw this pattern clearly when I worked in a financial services company. Meetings were consistently polite, conflict was rare, and the moment each session ended, executives quietly lined up to get on the president’s calendar to say what they hadn’t said in the room.

Recognizing It

The pattern I look for isn’t whether the team argues. It’s whether what gets raised in the room is the real conversation or a version that’s safe enough to say out loud:

  • Members describe the real conversation as something that happened after the meeting, not during it.
  • The CEO is routinely surprised by concerns raised one-on-one that never surfaced in the room.
  • When disagreement does appear, it resolves quickly, not because the issue was worked through, but because someone backed down to preserve the peace.

The Damage It Does

Conflict that has gone underground is self-perpetuating because its consequences are seldom traceable back to the conflict itself. The feedback loop that would allow the team to learn is broken at exactly the point where the cause was managed out of sight.

Too often, people comply with the decision rather than commit because they don’t feel heard or to avoid any more difficult conversations on the topic. This leads to the deterioration of the relationships among those involved.

Sometimes the team doesn’t learn the cost of compliance, or never recognized the true source of the problem. Post-mortems may blame failure on execution gaps, unclear ownership, insufficient resourcing. What doesn’t surface is that the real disagreement was never resolved.

 

The team that fights openly and well will eventually recognize the true nature of the conflict. A team that manages conflict quietly keeps attributing the consequences to other causes and never reaches the source.

The Fix

The goal isn’t more confrontational meetings. It’s making the room safe enough for real concerns to surface — and building the team’s capacity to work through disagreement without the relationship cost that currently makes avoidance feel like the better option.

 

Profiled. Workshopped. Still Stuck.

/in , , , , /by

Personality profiles don’t explain why you’re not executing

We’ve all experienced personality profiles as part of our leadership team experiences. DISC, Myers-Briggs,Insights Discovery, an enneagram workshop, They can tell you who’s a driver, who’s a stabilizer, who needs more processing time before a decision. They are great for breaking the ice and breaking down interpersonal issues.

What they usually can’t tell you is the complete story about why the team is stuck.

That’s not a flaw in tools. They were built to describe individual style, not to diagnose how a team functions as a leadership system.

Knowing that someone is a driver doesn’t tell you whether the team has a working process for converting decisions into action. Or whether authority and accountability line up. Or where alignment quietly breaks down between the meeting room and the next quarter.

Those are systemic questions, and they require a systemic answer — one built from how the team actually behaves under real conditions not personality preferences in isolation.

Style and system aren’t in competition. But they answer different questions, and treating a systemic problem with a style-based tool is one of the more common reasons executive team work fails to produce lasting change.

If a team already knows its personality types and is still stuck, that’s often the clearest sign the next layer of the problem is systemic, not stylistic.

Our research-based Executive Team Assessment analyzes the team systemically across 8 dimensions. If your team is stuck, let’s chat.

The Combined Leadership Team

/in , , , , , , , /by

Last to integrate. Most expensive to ignore.

Merged on Paper. Not in the Room.

We’ve all heard stories of the teams, that years after the acquisition is done, introduce each other by their previous company’s name. “I’m from Citi” “I’m from Chase.” I know I’ve experienced it post merger.

Integration plans after a merger are usually thorough on systems, processes, and org charts. They are almost never thorough on whether the combined leadership team can actually operate as one team.

The Combined Team Gap

The gap between a truly combined team and two factions that are working together, tends to begin to surface three to six months after the deal closes. The initial goodwill has worn off and real decisions like budget tradeoffs, aligning conflicting priorities, and decisions about whose process becomes the standard need to be made. The leadership groups need to function as a single unit rather than two groups sharing a company name.

A few things tend to be true of combined teams that are struggling, even when the org chart looks clean:

  • Decisions quietly default to “our side” and “their side” rather than a shared standard, even months after the deal closed.
  • Trust that took years to build on each legacy team has to be rebuilt from zero across the combined group, and nothing in the integration plan accounts for that timeline.
  • Disagreements that would have been resolved directly within one legacy team get escalated instead, because the norms for how this new team handles conflict haven’t been established yet.

None of this shows up in an integration checklist.

It shows up in how the combined team actually makes decisions together, resolves conflict, has honest conversations, and tackles tough issues. How do you identify it? With a systemic read of the new team rather than an assumption that good people will sort it out.

The cost of leaving this question unasked isn’t a single bad quarter.

It’s a leadership team that never fully integrates, well after the systems did. And the longer that gap persists, the more the organization learns to work around the team rather than through it — building informal workarounds, duplicate processes, and shadow coordination structures that quietly drain capacity and compound the original cost of the deal.

How much has an unintegrated leadership team cost your merger or acquisition?

E.Onderick-Harvey@NextBridgeConsulting.com

arrow cubes pointing in the wrong direction

The Quiet Cost of Almost-Alignment

/in , , , , , , /by

The most expensive misalignment usuall starts with a nod

The most expensive misalignment on an executive team rarely starts with a disagreement. It starts with a “nod” — physically or verbally — and everyone assuming it meant the same thing.

Nobody flags it. Everyone assumes they’re aligned. They’re not quite aligned. They’re almost aligned. And almost is expensive.

Almost-alignment hides behind professionalism.

Execution isn’t the problem. People go back to their teams, interpret the decision through their own lens, and move. It’s only weeks later that the gap becomes visible: when priorities conflict, resources pull in different directions, or the message sounds different depending on who delivered it.

I know I’ve experienced this time and time again. After a contentious conversation about what we should do next, only then do we realize that we aren’t all trying to achieve the same goal. Our understanding of the decision is different.

By then, the cost is already real.

It usually starts with a meeting that ended too cleanly.

Genuinely good decisions involve tradeoffs that different functions feel differently about. When a leadership team reaches consensus too quickly, it’s worth asking whether the hard part was actually worked through — or just skipped.

The most dangerous executive meetings are the ones where everyone nodded and nobody pushed.

What real alignment looks like

Everyone understands what was decided, why, what was traded off, and what they’re each responsible for next. They can walk out and tell their teams the same story — not the same words, but the same story.

That’s a higher bar than most leadership teams hold themselves to. It’s also the one that matters.

A simple test

After your next significant decision, ask each member of your leadership team independently: “What did we decide, and what does that mean for your priorities over the next 90 days?”

The gaps in those answers are your alignment gaps — and they’re worth closing before they close themselves in ways you won’t like.