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?

That meeting is costing you more than you think.

/in , , , /by

Your presence in certain meetings isn’t helping. It’s editing.

 

As a senior leader, what is your impact on meetings?

You’ve probably done the work of cutting low-value meetings from your calendars. Have you ever looked at what your presence in certain meetings is costing the people around you?

When a Director or VP or someone even more senior shows up to a working session or team meeting, the room changes.

The meeting becomes a performance

Debate narrows. Decisions that were forming get pushed aside. Most people in the room are managing up instead of solving the problem. Instead of a working session, and the real conversation happens afterward in the hallway.

I’ve seen this happen in so many meetings I’ve been in. It’s not about intent — most leaders attend these meetings because they care about the work. It’s about effect. Presence at the wrong stage of a decision doesn’t improve the outcome. It can shortcut the thinking that makes good outcomes possible. 

On a project years ago, the team I was leading had gotten into a rhythm and were making real progress. Then my boss came in the room. She asked questions we’d decided upon weeks ago, added ideas she saw as helpful but lacked context. My team shifted almost immediately to make her happy, rather than make the right decision. It then took us multiple meetings to get back on track.

The practical fix isn’t to become less engaged.

It’s to be more deliberate about what kind of engagement a given moment actually needs — input, oversight, or a decision. Those are three different roles, and showing up the same way to all three is where the cost accumulates.

Two actions worth taking this week

  • Audit the recurring meetings on your calendar and identify which ones you attend out of habit rather than necessity.
  • Then pick one working session where your team is developing a recommendation and don’t attend — let them bring you the output instead. Notice what’s different about what they bring you.

Consensus is killing your decisions

/in , , /by

The more people you include, the less likely you are to actually decide anything.

The more uncertain things get, the more leaders do the one thing that guarantees a bad outcome: they add more people to the decision.

A decision that belongs to everyone belongs to no one.

And in a climate where ambiguity is the norm rather than the exception, that diffusion has become one of the most common, and least-discussed, reasons important decisions keep circling without landing. It’s not that leaders lack information. It’s that no one has been clearly handed the call. Too often, I see assumptions made at the end of meetings or discussions about who owns the decision. Everyone walks out believing it belongs to someone else.

Strong organizations don’t eliminate ambiguity. They prevent ambiguity from becoming drift. That means distinguishing between gathering input and making the decision — and being ruthless about when the first activity needs to stop so the second one can happen.

Two moves worth making now:

  • Map your most important live decisions against three roles — who recommends, who decides, who gets informed. If those aren’t distinct, that’s your problem.
  • Then pick one decision that has been in circulation too long and cut the number of people involved.

Speed isn’t the enemy of good judgment. Too many people in the process is.

If No One’s Challenging You, You Have a Problem

/in , , , , /by

Why your team has stopped asking why

You walk the team through a reasonable plan. And when you finish there are a no significant questions. No real pushback. Mostly nods.

If this was you, you may have walked out feeling good. “We have a good plan. We’re aligned. We’re moving.”

You’re not aligned. They’re being careful. And that’s costing you more than you know

There’s a new kind of silence in the room right now.

People are worried about their jobs. The economy is uncertain, layoffs are in the news, “AI is coming for our jobs.” The unspoken calculus on a lot of teams has shifted. Questioning a decision used to feel like contributing, like trying to make it better. Right now, for a lot of people, it feels like a risk.

So they go quiet. They execute. They keep their heads down and wait to see how things shake out.

What looks like alignment is actually self-protection — and you can’t afford to mistake one for the other.

Silence isn’t consensus. It’s a symptom.

When people are genuinely aligned, they still push back. They question to try to make it better.

When they’re disengaged or afraid, the questions stop. If you’re not paying enough attention, this could look like trust. It’s not the same thing.

What to do about it:

Be real about what’s happening. If people are anxious, pretending they’re not doesn’t help. Acknowledging it — “I know there’s a lot of uncertainty out there right now” — gives people permission to relax slightly and re-engage.

Ask one-on-one. “Do you feel like your input actually changes anything?” “Are you concerned about what I’ll think of you if you push back?” are questions people won’t answer honestly in a group. Ask them privately. Then be quiet.

Let pushback land. The next time someone challenges a decision, resist defending it immediately. Say “that’s worth thinking about” — and mean it. People who are scared are watching closely to see what happens when someone speaks up.

Make it visible when input changes something. “Based on what a few of you flagged, we’re adjusting the approach.” That sentence rebuilds trust faster than almost anything else — especially right now.

The cost of silence will catch up with the team — in poor decisions nobody flagged, in resignations that felt sudden but weren’t, in execution that’s technically fine and quietly mediocre.

The good news: it’s recoverable. But only if you notice it first — and create enough safety that people believe speaking up is worth it again.

Have you successfully turned a silent team around? I’d love to hear about it.