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

Accountability Without Blame

/in , , , , /by

Accountability has a reputation problem.

For a lot of people, being held accountable feels like being set up to be blamed. So, they hedge commitments, qualify timelines, and avoid owning outcomes they’re not certain they can control.

The result is a team that’s busy, well-intentioned, and too often vague about who is responsible for what.

That’s not an accountability problem. It’s a safety problem.

When people experience accountability as punitive, they learn to protect themselves from it. They underpromise. They blame circumstances. They point to dependencies. None of this is laziness. It’s rational behavior in response to the environment they’re in.

I worked at a large consulting firm where accountability and blame were synonymous. During a performance review, I told one of our staff consultants that the partner wanted him to share more of his ideas. He said he didn’t know that was ‘allowed’. He had seen too many staff consultants blamed for ‘not following the plan’ when they tried to add a different way of thinking to a project or plan. The message was don’t add anything to the process. Just do what you’re told. The project managers thought they were creating accountability. What they were really doing was creating an atmosphere of fear.

Real accountability is built on clarity, not pressure.

It starts with commitments specific enough to be meaningful. Not “we’ll make progress on this” but “we’ll have a decision by the 15th.” Vague commitments can’t be held — they can only be argued about.

It also requires that when something goes wrong, the first question is “what do we need to do differently?” rather than “whose fault is this?” These may sound a bit similar. But they produce completely different conversations.

The leader’s role

The tone of accountability on a team usually traces back to how the leader handles their own misses. When a leader acknowledges openly that something didn’t go as planned — without deflection — they give everyone else permission to do the same. I’ve seen this happen in real time in executive teams. The power of acknowledgement was the productive conversation it created.

That modeling is quiet and powerful. It signals that honesty about what’s not working is valued more than the appearance of having everything under control.

How does your team handle accountability when things don’t go to plan? Reply and let me know.

E.Onderick-Harvey@NextBridgeConsulting.com

cracked concrete wall showing past stresses

The Organizational Scar Tissue Problem

/in , , , , , /by

Every organization carries history.

Hopefully a lot of it is good, sometimes a lot of it is bad. The restructuring that blindsided people. The leader who played favorites. The initiative that consumed enormous energy and went nowhere.

New leaders don’t always know the details. But they feel the effects every day.

Scar tissue is invisible on an org chart but visible everywhere else.

It shows up in the room that goes quiet when a new idea surfaces. In the team that nods enthusiastically and then does nothing differently. In the manager who learned that raising concerns leads nowhere good.

It’s not resistance. It’s memory.

The mistake most leaders make

They treat skepticism as a communication problem. More emails, more town halls, more slides. But scar tissue isn’t a communication problem. It’s a trust problem. And trust isn’t built by talking. It’s built by doing, consistently, in ways people can actually feel.

What actually helps

Name it. Acknowledging that history exists — “I know there have been changes here that didn’t go the way people hoped” — signals that you’re paying attention to something real.

Let actions outpace promises. Make small, visible commitments and keep them. Repeatedly. Until the pattern becomes undeniable.

Give it more time than you think you have. Trust rebuilds on its own timeline, not the leader’s.

An organization’s history doesn’t disappear when new leadership arrives. However, it can be rewritten by what happens next.

The leaders who understand that earn something more valuable than compliance. They earn commitment.

What’s the history on your team that’s still shaping how people show up today? Reply and let me know.

  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.

What Signals Are You Sending?

/in , , , , , , /by

Culture doesn’t come from a slide deck

Your organization doesn’t learn culture from a slide deck. It learns it by watching what the leadership team actually does: how you disagree, how you decide, and whether your actions match your words.

The culture of the senior team is the culture of the organization, whether it intends to be or not.

When a leadership team debates openly and decides with clarity, that behavior tends to show up in the teams below. When a leadership team is siloed, territorial, or conflict-avoidant, those patterns replicate too — often without anyone consciously choosing to model them.

The behaviors of a senior team travel downward fast.

Three things that are watched closely

How you handle disagreement. When two senior leaders have a conflict, does it get worked out directly? Or does it go underground and show up as friction between their teams? People learn what to do with conflict by watching what the people above them do with it.

Whether decisions stick. When directions get quietly reversed or different parts of the organization operate as if different decisions were made, people lose confidence that anyone is actually steering.

How you talk about each other. The way leaders refer to their peers — in meetings, in passing, in how they explain decisions — sets the tone for how the whole organization talks about itself. Respect at the senior level is contagious. So is the opposite.

The question worth sitting with

If your team were to describe the leadership team’s dynamics to a new hire, what would they say? Not the official answer. The real one.

That description is your culture. And it starts at the top.

What’s one behavior you’ve seen ripple from a leadership team through an entire organization? Reply and let me know.   E.Onderick-Harvey@NextBridgeConsulting.com

AI isn’t your change problem.

/in , , /by

Your Change Leadership is.

Most AI transformation efforts will fail.

It’s been true for transformations for decades. This one will be no different. Not because the technology isn’t ready. Because the organizations implementing it aren’t.

Leaders who couldn’t build change-ready teams before AI aren’t suddenly going to succeed at it under more pressure, more urgency, and more competing priorities.

The harder truth is that most organizations were already confusing activity with change leadership long before AI entered the conversation. Launching initiatives, building roadmaps, communicating milestones — those things create the appearance of transformation without building the underlying capacity to sustain it. AI adoption has simply made that gap impossible to ignore. 

When the pace of change required outstrips an organization’s ability to absorb it, people don’t innovate. They comply, wait it out, or leave.

Build Muscle Memory

What I’ve watched work — consistently, across three decades — isn’t faster implementation. It’s leaders who build change into the muscle memory of their teams through everyday behavior. Not through transformation programs, but through the questions they ask in one-on-ones, how they respond when something fails, and whether their teams feel safe enough to say “this isn’t working” before it becomes a crisis.

That capacity doesn’t get built by an AI initiative. It gets built by you, daily, in the way you lead.

How can you increase your change capacity?

Ask your team one question — “What’s one thing AI is supposed to be changing for us that hasn’t actually changed yet, and why?” Listen for the real answer, not the safe one. Then ask yourself whether your organization is building genuine change capacity or just keeping pace with announcements.

Those are very different things — and right now, most organizations are doing the latter and calling it transformation.

Is your team underperforming? Or is it underwater?

/in , , , , /by

Overcommitment isn’t a performance problem.

It’s a leadership one.

 

Execution problems are almost always misread.

You see slippage and then reach for familiar responses: tighten accountability, have more frequent check-ins, set seemingly clearer deadlines.

Those aren’t wrong, exactly. But they’re treating the symptom. What I see happening most frequently right now isn’t a discipline issue. It’s that your team is drowning.

Teams aren’t failing to execute because they don’t care or don’t know how. They’re failing because the volume of what’s been declared important has exceeded the organization’s actual capacity to pursue any of it well.

Progress gets spread too thinly.

New priorities layer on top of old ones. Legacy work never fully comes off the table. The result isn’t dramatic — no single project collapses — but progress gets spread so thinly across so many efforts that none of them build real momentum. I’ve talked about this with mid-level leaders in development programs and workshops. I’ve heard about it in coaching sessions with leaders. Dilution of effort is a harder problem to see than failure, which is exactly why it persists.

The instinct to add more oversight misses this entirely.

You can’t concentrate effort by increasing pressure on a system that’s already overextended. The only move that actually works is reducing the load — deliberately, visibly, with the willingness to say out loud that something that once mattered now matters less.

Here are two steps you can take immediately

  • Cut one active initiative, not because it’s unimportant but because capacity is finite and concentration is a choice.
  • Then define what success looks like for your top priority over the next 60 days — one owner, one visible measure, nothing ambiguous.

Execution isn’t always a discipline problem. It’s often a design problem. How can you fix the design?