Insights — Ghizzone Performance Solutions

01 Insights & Articles

GPS thinking on leadership development

Feedback & Communication

The Manager Effectiveness Gap Nobody Talks About

Manager Effectiveness · Nick Ghizzone · 7 min read · August 2026

Most mid-market companies can identify their best individual contributors. Very few can tell you which of those people will thrive as managers.

Here's a story I've seen play out at nearly every company I've worked with.

Jordan is the best engineer on the team. She’s a technical expert; she solves the problems nobody else can crack; she’s the one everyone goes to with questions. When the team lead leaves, the decision feels obvious. Jordan gets the promotion, a title bump, and a raise.

Six months later, things look different. Jordan is working 60-hour weeks because she's still writing code at night. Two people on her team have stopped speaking up in meetings. One is interviewing elsewhere. Jordan's own engagement has cratered, and she's quietly wondering if she made a mistake.

Nobody did anything wrong here, exactly. The company rewarded excellent performance. Jordan accepted a well-earned opportunity. But the organization made a bet without any real data, and it lost twice: it gained a struggling manager and lost its best engineer.

That's the manager effectiveness gap. It's the space between "great at the work" and "great at leading people who do the work." And in my experience, it's one of the most expensive blind spots in mid-market organizations.

Different job, different skills

We promote people into management for what they've done. Then we ask them to succeed at something they've never done.

The research here is sobering. Gallup's work on manager selection found that companies pick the candidate with the right talent for the manager role only about one time in five. A well-known study of sales organizations by Benson, Li, and Shue found that top sales performers were the most likely to be promoted, and then tended to perform worse as managers. The Peter Principle isn't just a punchline. It shows up in the data.

The reason is simple: the skills that make someone a star individual contributor are often different from, and sometimes opposite to, the skills that make an effective manager.

What made them a great IC —> What the manager role requires

Solving problems personally —> Helping others solve problems

Deep expertise in one domain —> Enough context across many domains

Recognition for individual output —> Satisfaction from the team's output

Control over their own work —> Influence over work they don't do

Speed and independence —> Patience, coaching, and delegation

Being the go-to expert —> Making others the go-to experts

When a new manager falls back on what made them successful before, things go sideways. They jump in to fix problems instead of coaching. They hold onto the interesting work. They measure their value by their personal output, while their team's growth stalls.

None of this means your best ICs can't become great managers. Many do. It means performance in the current role is a weak predictor of success in a different role. To make a better bet, you need different data.

Why mid-market companies feel it most

Large enterprises have their own problems, but they usually have some infrastructure for this: formal HiPo programs, leadership assessment centers, a 9-box talent review, and an L&D team to run a new-manager curriculum.

Mid-market organizations, roughly 500 to 5,000 employees, are in a tougher spot. They're big enough that management quality makes or breaks results, but often lean enough that there's no dedicated system for picking and preparing managers. In practice, that looks like this:

Promotions happen reactively. Someone leaves, and the role gets filled by whoever's performing best right now.
"Readiness" is a gut call. Decisions rest on a senior leader's impression, which often means rewarding visibility and confidence over leadership capability.
Onboarding is a title change. New managers get a new org chart and maybe a compliance training. Then they're expected to figure it out.
The bench is thin. With fewer people at each level, one bad promotion hits a bigger share of the organization.

Where it becomes a retention problem

Gallup has estimated that managers account for at least 70% of the variance in team engagement. When you put the wrong person in the role, or the right person without support, the cost compounds:

You risk losing the star. A struggling new manager often burns out or leaves. Many can't step back into their old role without feeling demoted.
You risk losing the team. People leave managers, not companies, is a cliché because it's so often true. Disengagement spreads quietly, then all at once.
You lose the pipeline. When a team watches management chew someone up, your next generation of high performers decides they don't want the job.

By the time turnover shows up in the exit data, the gap has already been open for months.

Closing the gap: Assess, Align, Advance

The good news is that this gap is predictable, which means it's preventable. At GPS, we approach it in three stages.

1. Assess: get real data before the promotion

Development plans built on guesswork don't work, and neither do promotions. Before someone steps into a manager role, look past their output and at the capabilities the job actually requires.

Use validated assessments. Tools like the Hogan HPI and HDS show how someone is likely to lead day to day, and how they may derail under pressure. The HDS is especially useful here. Many "derailers" (perfectionism, a need to be the expert, avoiding conflict) are invisible in an IC role and become obvious the moment someone manages people.
Look for early signals. Does this person already help teammates get unstuck? Do peers seek them out for advice, not just answers? Do they share credit? Do they handle disagreement well?
Ask the person directly. Some of your best contributors don't want to manage. They're doing it because it's the only path to more pay and status. That's worth knowing before the promotion, not after.

2. Align: match people to the right path

Once you have the data, use it to make a real decision, not just a yes or no.

Build a dual career track. Give senior individual contributors a path to growth, compensation, and influence that doesn't require managing people. This alone solves a surprising share of the problem.
Create low-risk trial runs. Let emerging leaders lead a project, mentor a new hire, or run a team meeting. Watch how they do and ask what they learned.
Be transparent about the gap. A promotion conversation can include "here's where you're ready, and here's what we'll build together." That's a far better start than silence.

3. Advance: support new managers through the transition

The first 90 days in a management role set patterns that can last for years. Don't leave them to chance.

Give them a real foundation. New managers need practical skills fast: running a meaningful one-on-one, delegating, giving SBI feedback, and adapting their style to each person. Leadership models like situational leadership are built for exactly this.
Pair them with a coach or mentor. An outside perspective helps a new manager work through the identity shift from "doer" to "leader" without feeling like they're failing in public.
Measure and adjust. A self-assessment at 30 days, and a live 360 around six months, tells you and the manager where they stand, while there's still time to course-correct.

The bottom line

Your best individual contributors are among your most valuable assets. Promoting them into management without data or support doesn't reward them. It puts them, their teams, and your retention numbers at risk.

Closing the manager effectiveness gap doesn't require an enterprise-sized L&D budget. It requires a shift in mindset: treat the move into management as a new job that deserves real assessment, a deliberate decision, and real support.

Every manager deserves the chance to grow into the role, not just the expectation that they'll figure it out alone.

———————————————————————————————————————————————————————————————————————————————————————————————————————————-

Where do your managers stand today? The GPS Manager Effectiveness Self-Assessment is a quick way to find out, covering communication, coaching, execution, and self-awareness. For a deeper look, Ghizzone Performance Solutions offers assessment-driven manager readiness, executive coaching, and custom leadership programs for mid-market organizations. Reach out at nick@ghizzoneperformancesolutions.com.

Feedback & Communication

Why Most Feedback Conversations Fail Before They Start

Feedback & Communication · Nick Ghizzone · 5 min read · August 2026

The problem isn't the words managers choose. It's the threat response they trigger before a single word is spoken.

Picture a message that lands in your inbox at 4:45 on a Thursday: "Can you grab 15 minutes with me tomorrow morning?" No agenda. No context.

Most of us know exactly what happens next. Your stomach drops. You replay the last three meetings you were in. By the time you walk into that room Friday morning, you've already rehearsed your defense.

Now flip it. You're the manager who sent that message. You spent the evening choosing your words carefully. You planned to open with something positive. You were going to be fair, balanced, even kind.

It didn't matter. The conversation was lost before you said hello.

In more than 20 years of leadership development work, I've watched thoughtful, well-intentioned managers struggle with feedback over and over. We tend to treat it as a script problem: find the right phrasing and the conversation will go well. But the real problem sits upstream of the words. It's biological.

Your brain treats feedback like a threat

The human brain is wired to scan constantly for danger. The amygdala, a small structure deep in the brain, acts as an early-warning system. It flags potential threats and triggers a stress response before the thinking part of the brain has fully weighed in.

That system evolved to keep us alive around predators. It hasn't caught up to the modern workplace. It reacts to social threats (a loss of status, a sense of unfairness, being judged) using much of the same machinery it uses for physical ones.

When that alarm goes off, a few predictable things happen:

Stress hormones rise. Heart rate goes up and attention narrows onto the perceived threat.
The prefrontal cortex takes a back seat. That's the region responsible for reasoning, perspective-taking, and problem-solving. It's exactly what we need for a productive feedback conversation.
Defensiveness takes over. People fight (argue, justify), flee (shut down, nod along), or freeze. None of these lead to learning.

Neuroscientist and leadership researcher David Rock captured this in his SCARF model. It names five social domains the brain monitors for threat or reward: Look back at that Thursday afternoon message. It hits almost every domain at once: no certainty, an implied status threat, and no control over the outcome. The employee's threat system is fully activated before the manager says a word.

SCARF Domain → What the brain is asking → How feedback threatens it

Status → Where do I stand relative to others? → "You're being evaluated" feels like a demotion.

Certainty → Can I predict what happens next? → A vague, no-agenda meeting invites worst-case thinking.

Autonomy → Do I have control? → Being told what to fix removes a sense of choice.

Relatedness → Is this person on my side? → Feedback can feel like the manager switched teams.

Fairness → Is this just? → Generalizations and secondhand claims feel unfair.

This is why the old "feedback sandwich" rarely works. People quickly learn that the compliment is a setup, so the praise itself becomes a threat signal. You can't phrase your way out of a biological alarm. You have to avoid setting it off in the first place.

How SBI addresses the root cause

The Situation-Behavior-Impact (SBI) model, developed by the Center for Creative Leadership, is often taught as a simple formula. That undersells it. Its real power is that each part of the structure lowers a specific threat signal.

Situation: anchor it in a specific moment. "In yesterday's client call with Meridian..." tells the brain exactly what this is about, and what it isn't. That restores certainty. It also keeps the conversation about one event, not the person's entire track record, which protects status.

Behavior: describe what you observed, not what you concluded. "You interrupted the client twice while she was explaining her concerns" is observable. "You were dismissive" is a judgment about character. Observable behavior is hard to dispute and feels fair. Judgments invite a defense.

Impact: explain what it caused. "She stopped sharing details, and we left without the information we needed for the proposal." Impact turns feedback from a verdict into shared information. It signals, "I'm telling you this because it matters to our work," which protects relatedness.

Then comes the step most managers skip: ask, don't tell. "What was going on for you in that moment?" or "How do you see it?" Handing the conversation back restores autonomy. It also gives you information you probably didn't have.

Here's the difference between a threat-triggering approach and an SBI approach:

—————————————————————————————————————————————————————————————————————————————————————————————

Threat-triggering version: "You need to be more of a team player."

SBI version: "In Tuesday's sprint planning, when Maria asked for help with the API work, you said you were too busy. She ended up missing the deadline. Can we talk about that?"

Threat-triggering version: "Your reports are sloppy."

SBI version "The Q3 forecast you sent Friday had three formula errors in the regional tab. Finance caught them before the board deck went out, but it cost them half a day. What would help you catch those before sending?"

The second version of each is longer. It's also far more likely to be heard, because the listener's brain stays out of threat mode long enough to actually process it.

Win the conversation before it starts

SBI handles what you say. But the threat response often fires before the conversation begins, so the setup matters just as much.

Kill the mystery meeting. Give context when you schedule: "I'd like 15 minutes to talk through how the Meridian call went. Nothing to worry about, I just want to compare notes."
Make feedback normal. When feedback only shows up when something is wrong, every feedback conversation is a threat. Share observations often, including positive SBI feedback. "In the Meridian call, you summarized the client's three concerns back to her before responding. She visibly relaxed, and we got a yes on the timeline."
Go in curious, not certain. You're sharing one observation, not delivering a verdict. Be genuinely open to learning something that changes your view.
Check your own threat response. Managers get anxious about feedback too, and that anxiety leaks into tone and body language. If you're activated, wait until you're not.
Plan it in writing. Jot down the Situation, Behavior, and Impact before the conversation. If you can't name a specific behavior, you're not ready to give the feedback yet.

The bottom line

Feedback is one of the most powerful development tools a manager has. It's also one of the most misused, not because managers don't care, but because nobody taught them how the brain on the other side of the table works.

When you understand the threat response, SBI stops being a script. It becomes a way of keeping the other person's thinking brain online long enough to actually grow.

Want a head start? The GPS SBI Feedback Planner walks you through preparing a feedback conversation step by step. For teams that want to build these skills together, Ghizzone Performance Solutions offers hands-on SBI feedback workshops and manager coaching for mid-market organizations. Reach out at nick@ghizzoneperformancesolutions.com.