Not in a performance review. Not in a team meeting with twelve people watching. One-on-one, with the person on her team she trusted most to be straight with her. She picked him specifically because she knew he’d tell her the truth — if she made it safe enough to do it.

She sat down, put her phone face-down on the table, and asked: “What’s one thing I could do differently that would make it easier for you to do your best work?”

Then she stopped talking.

The silence lasted about fifteen seconds. It felt like a month.

He looked at her, then at the table, then back at her. “Honestly?” he said. “You make decisions before you have all the information, and by the time the rest of us find out, it’s too late to push back.”

Her first instinct was to explain. To walk him through the pressures she was navigating, the timeline she was working against, the context he didn’t have.

She didn’t. She said: “Thank you. I’m going to sit with that.” And she wrote it down.

Two weeks later she came back. “I’ve been thinking about what you said. I’m going to start bringing the team in earlier on decisions that affect your work. I can’t promise it will always change the outcome, but you’ll know what’s coming before it lands on you.”

The next conversation was more honest than that one. And the one after that was more honest still.

That’s the whole playbook. Ask deliberately. Receive without defending. Act visibly. Repeat.

It sounds simple. Most leaders never do it — not because they don’t care, but because nobody ever taught them how. And because asking for honest feedback requires a specific kind of courage that doesn’t come naturally to people who are used to being the one with the answers.

The leaders who build this practice don’t just get better feedback. The difference shows up everywhere:

• Problems surface before they compound.

• Blind spots shrink.

• People bring their best thinking, not just their best effort.

• Retention improves.

• Trust — the kind we talked about last week — deepens with every loop completed.

Last week, we built the foundation — what trust costs when it’s absent, how it gets built or destroyed in small moments, and what you can start doing differently today. This week is about what you do once you have it: how to ask for honest feedback deliberately, how to receive it without flinching, and how to make it a practice that keeps getting more valuable the longer you sustain it.

★ The question that changes everything

The most powerful question a leader can ask:

“What’s one thing I could do differently that would make it easier for you to do your best work?”

Ask. Receive. Act. — not a one-time conversation. A practice.

Most leaders overcomplicate this. They wait for the annual review cycle. They commission a 360. They design a survey. All of those have their place. None of them replace the simple, direct, human conversation.

The question works because it’s about what you can do differently — which signals that you believe change is possible and that you’re willing to own your part in it. It’s not a performance assessment of them. It’s an accountability statement from you.

How to ask it well:

• Ask it one-on-one — never in a group where social pressure flattens honest answers

• Give it its own time — not as an afterthought at the end of a packed agenda

• Sit down, ask the question, put your phone face-down, and stop talking

• Let the silence do its work — the employee is deciding whether to trust you. Give them the time to get there.

If the question catches them off guard — and it often will — say so:

“I know this might be catching you off guard. If you’d prefer to think about it and get back to me, that’s completely fine.”

That invitation signals genuine intent. But if they take time to think about it, follow up. Don’t let it become an escape hatch. Make it clear — kindly but directly — that you’re still expecting to hear from them.

How to receive what comes back

This is the harder half. Asking takes thirty seconds. Receiving — without explaining, without qualifying, without getting defensive — that’s where most leaders lose it.

“The instinct to explain is the enemy of honest feedback. The moment you start justifying, you’ve taught them the answer you actually wanted.”

When the answer comes — whatever it is — receive it well:

• Don’t explain. Don’t qualify. Don’t pivot to your own perspective.

• Say thank you — genuinely, specifically — even if you disagree. Especially if you disagree.

• Remember what we talked about last week: feedback is a gift. Now it’s directed at you. Thank them for it.

• Write it down in front of them — it signals that what they said mattered enough to capture.

• Sit with it before you react to it. Not every piece of feedback requires immediate action — but every piece deserves genuine consideration.

Bonus Note: This works in your personal relationships too. Go ahead, try it with your teenager or significant other and watch the shocked look on their face when you don’t try to “explain” and simply say “Thank you. I appreciate you telling me that.”

The hard truth

Most leaders don’t ask because they’re afraid of what they’ll hear. That fear is worth sitting with — because it’s exactly the fear your employees feel every time you ask them to tell you something uncomfortable. The leaders who push through it aren’t fearless. They’ve just decided that knowing the truth is worth the discomfort of hearing it.

What you do after is what builds the trust

We covered the mechanics of building trust last week. But it’s worth being specific about how the ask-and-respond cycle fits into that framework — because this is where trust either compounds or collapses.

Here’s what the ledger looks like specifically around feedback conversations:

↑ Builds trust

• Someone shares honest feedback, and you say thank you — and mean it

• You follow up two weeks later: “I’ve been thinking about what you said. Here’s what I’m doing differently.”

• The person who told you something hard is treated with the same respect afterward as before

• Others see that speaking up changed something — and start doing it too

↓ Destroys trust

• You ask for honest input and then explain why the concern is wrong

• The feedback disappears with no acknowledgment and no follow-up

• The person who spoke up is subtly sidelined in the next meeting

• The only feedback that gets acted on confirms what you already believed

Two weeks after the conversation, come back. Tell them what you’re doing differently — or why you’re not. Either way, close the loop. That follow-through is where trust either gets built or gets burned. And it’s the single most important thing that determines whether the next conversation is more honest than the last one.

The trust account — every follow-through is a deposit. Every broken promise is a withdrawal.

What changes when you get this right

The return on this practice doesn’t show up in a single conversation. It accumulates — in the culture around you, in the team’s behavior, in the quality of the work. Here’s what actually changes:

• Problems surface earlier. When people trust that you can hear hard things, they stop waiting until something is broken to tell you. You find out about friction while it’s still fixable — not after it’s compounded into a resignation or a client complaint.

• Blind spots shrink. Every leader has them. The ones who ask for feedback — from their team, their peers, their own manager — get a view of themselves that no amount of self-reflection can replicate. You start to see how your behavior lands, not just how you intend it.

• People bring their best thinking, not just their best effort. There’s a difference between a team that executes what they’re told and a team that brings their thinking to the table. When people feel genuinely heard, they invest differently. They flag risks. They bring ideas. They act like they have a stake in the outcome — because they do.

• Credibility goes up, not down. Most leaders fear that asking for feedback will make them look uncertain. The opposite is true. A leader who actively seeks honest input and visibly acts on it signals confidence and self-awareness. That’s not weakness. That’s the kind of leader people choose to follow.

• Retention improves. People don’t leave jobs where they feel genuinely heard. They leave jobs where they feel invisible. A leader who asks for their input — and does something with it — is sending a signal that their perspective matters. That signal is worth more than most compensation conversations.

• Team members give each other honest and direct feedback. When people watch a leader model openness to hearing hard things, the behavior spreads laterally. If the person at the top can ask for honest feedback and receive it gracefully, it becomes safe to do it here. The leader never has to orchestrate it — it happens on its own.

• You become someone worth working for. The leaders who ask for honest feedback and actually use it become the managers people want to work for — the ones who show up in reference calls as someone who made people genuinely better. That’s a legacy built one uncomfortable conversation at a time.

Next week we turn the lens inward — because you can’t pour from an empty cup. We’ll talk about what it actually means for a leader to stay functional enough to show up for their people, and why self-care for leaders has nothing to do with bubble baths. Subscribe so you don’t miss it.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Subscribe now

Share Helping Others Succeed

Solid performance numbers. No drama. Nobody was complaining — at least not to him. He’d built what he thought was a pretty open culture. He didn’t micromanage. He was approachable. His door was open.

Then his best employee resigned.

Not for more money. Not for a bigger title. She’d been recruited, yes, but that wasn’t why she said yes. In the exit interview, she was diplomatic about it — she talked about a great opportunity, a chance to stretch. But when her skip-level manager pressed a little, the real answer came out: she didn’t feel like her voice mattered here. She’d raised concerns about a process that was slowing her team down — twice. Both times they’d been acknowledged and then quietly dropped. She’d stopped raising them. Then she’d stopped caring.

Then she started taking recruiter calls.

He didn’t find out until she was already gone.

He thought he had an open culture. What he actually had was a team that had learned, quietly and without drama, that certain things weren’t worth saying out loud.

This story is playing out in organizations across the country right now — more than most leaders realize. According to Gallup, only 23% of U.S. employees strongly agree that they trust the leadership of their organization. Less than one in four. And only 31% believe their immediate supervisor has created an open and trusting work environment (Gallup, State of the Global Workplace, 2024).

Those numbers should give every leader pause. Because the manager in this story almost certainly would have told you his team trusted him. Most leaders would. The gap between how leaders perceive their own trustworthiness and how their employees actually experience it is one of the most consistent findings in workplace research — and one of the most costly.

Last week, we talked about the feedback nobody’s giving — the honest, specific, timely conversations that most leaders either soften into uselessness or avoid altogether. This week, we go upstream to the reason those conversations are so hard to have in the first place: trust. Specifically, what it costs when it’s absent, how to know whether you have a problem, and what you can start doing about it today.

What low trust is actually costing you

Most leaders don’t think of trust as a business problem. They think of it as a culture thing — important, yes, but soft. Hard to measure. Not something that shows up on a P&L.

That’s exactly why it’s so expensive.

In The Speed of Trust (2006), Stephen M.R. Covey made an argument that has only become more relevant with time: trust is not a social virtue — it is an economic driver. It affects two measurable outcomes: speed and cost. When trust goes down, speed goes down and cost goes up — what Covey called the “Low-Trust Tax.” When trust goes up, speed increases and costs decrease — the “High-Trust Dividend.” A Watson Wyatt human capital study cited in Covey’s work found that high-trust organizations outperformed low-trust organizations by 286% in total return to shareholders. That’s not a rounding error. That’s the difference between organizations that thrive and organizations that grind.

The economics of trust — when trust goes up, speed increases, and cost decreases

The Gallup data makes the stakes concrete. In 2024, employee engagement hit an 11-year low of 30% — and 29% of employees cited a lack of clear, honest, or consistent communication from leaders as a primary driver (Gallup, 2025). That’s not a benefits problem or a compensation problem. That’s a trust problem.

Gallup · State of the Global Workplace, 2024

Low trust doesn’t announce itself. It shows up as a resignation you didn’t see coming. A client problem that had been festering for months before anyone told you. A decision made on incomplete information because nobody flagged the risk they all saw. A meeting where everyone agrees — and then nothing changes because nobody actually bought in.

Here’s what a low-trust environment is costing you in language that belongs on a budget line:

• Your best people leave first. High performers have options. When they stop believing their voice matters, they start listening to recruiters. The employees who stay in a low-trust environment are often the ones who can’t afford to leave — which tells you something about the team you’re building over time.

• Problems compound in silence. Small problems get raised early in high-trust environments — when they’re still cheap to fix. In low-trust environments, people manage around problems rather than surfacing them. By the time the issue reaches you, it’s bigger, more expensive, and harder to solve. You’re not just paying to fix the problem. You’re paying for every week it sat unreported.

• Your feedback is filtered before it reaches you. Every layer of the organization is doing an unconscious calculation: is it safe to tell this person the truth? In a low-trust environment, the answer is usually no. What reaches you has been softened, edited, and shaped around what people think you want to hear. You’re making decisions on incomplete information — and you don’t know it.

• Engagement erodes quietly. Gallup’s research shows that 40% of U.S. employees would rather switch departments than report to a manager with different values, and 35% say they would put less effort into helping a project leader they don’t trust succeed. When trust is absent, differences become reasons to disengage. When trust is present, those same differences become manageable — even productive.

• You’re always the last to know. The manager in the opening scenario didn’t find out his best employee was disengaged until she handed in her notice. That’s the default outcome in a low-trust environment — where the information that would help you most is exactly the information people have learned not to share.

The moment we’re in

Gallup’s research makes the opportunity equally clear. When leaders communicate clearly, lead change, and inspire confidence in the future, 95% of employees say they fully trust their leaders (Gallup). That gap — between 23% and 95% — isn’t a talent gap. It’s a behavior gap. And behavior can be changed.

The timing matters too. As trust in government, media, and public institutions continues to erode, employees are increasingly turning toward their immediate leaders as their primary source of stability and reliable information. Gallup found that 34% of employed individuals say they are most influenced by a manager, colleague, or organizational leader — almost as many as those influenced by a family member (Gallup, 2025). The leader who earns that trust is stepping into a vacuum nothing else is filling right now.

Your employees are not looking for you to solve the world’s problems. They’re looking for one thing: a leader they can trust to tell them the truth, hear their concerns, and make decisions with their best interests genuinely in mind. In a world where that feels increasingly rare, the leaders who deliver it stand out in ways that directly affect performance, retention, and the quality of work their teams produce.

How to know if you have a trust problem

Most leaders with a trust problem don’t know they have one. The environment feels fine from where they sit — because the people who could tell them otherwise have already stopped trying.

The Gallup data is instructive here: only 27% of employees say their manager keeps them informed about what’s happening in the organization (Gallup, 2024). Most managers would rate themselves far higher on that same measure. That gap — between how leaders see themselves and how their people experience them — is exactly where trust problems live.

The signs of a low-trust environment are often misread as something else. Quiet teams get labeled “low energy.” Lack of pushback gets read as alignment. High turnover gets blamed on the job market. People going through the motions gets called an engagement problem. All of those can be trust problems wearing a different label.

Instead of asking whether your team trusts you — a question nobody will answer honestly in a low-trust environment — ask yourself these:

• “When did someone last tell me something I didn’t want to hear — unsolicited?”

• “When problems surface, do they come to me early or late?”

• “Do people agree in meetings and then behave differently afterward?”

• “Has anyone pushed back on a decision I made in the last month? If not — why not?”

• “If my best employee got a recruiter call today, what would they do with it?”

If those questions make you uncomfortable, sit with that. Discomfort is data.

The hard truth

A team that never disagrees with you isn’t a high-performing team. It’s a team that has learned it isn’t safe to disagree. Those are not the same thing — and only one of them will tell you the truth when you need it most.

What you can start doing differently today

Trust isn’t built in a team-building exercise or an all-hands meeting. It’s built in the smallest moments — the ones that feel insignificant at the time and turn out to be everything.

Covey’s research identified 13 specific behaviors that high-trust leaders exhibit consistently. They’re learnable. They’re not personality traits. Here’s where to start:

• Receive hard information without reacting. When someone brings you a problem, a concern, or feedback you didn’t ask for, say thank you. Not defensively. Not with an explanation of why the concern is misplaced. Thank you — and mean it. That response, or the absence of it, gets noticed. Gets remembered. Gets shared. It sets the temperature for every conversation that follows.

• Follow through visibly. When someone raises something, close the loop. Even if the answer is “I looked into this and we’re not going to change it — here’s why.” The follow-through signals that the conversation mattered. The absence of it teaches people that raising concerns is a waste of time. One missed follow-up is forgettable. A pattern of them is a trust withdrawal — and those compound.

• Make honesty visibly safe. Don’t just tolerate honest feedback — actively reward it. Thank the person who flagged a problem early. Cite the input that changed a decision. Make it clear, in front of the team, that the people who tell hard truths are assets, not problems. When the team sees that honesty has a payoff, the calculus shifts.

• Check the temperature deliberately. Don’t assume everything is fine because nothing is blowing up. Ask. Regularly. A genuine question in a one-on-one: “What’s getting in your way that I might not be seeing?” Don’t wait for the engagement survey to surface what a conversation could have caught six months earlier.

• Own your part. When you get it wrong — when you react too quickly, miss a follow-up, or make a decision without enough input — say so. Explicitly. “I should have handled that differently” is one of the most trust-building sentences you can say. It signals that accountability goes both directions — which is the only version that actually works.

The research backs this up. Gallup found that when leaders communicate clearly, lead change, and inspire confidence, employee trust reaches 95%. The gap between where most leaders are and where they could be isn’t a talent gap. It’s a behavior gap. And it closes one interaction at a time.

Building trust is not a project. It doesn’t have a launch date or a completion certificate. It’s a daily decision to show up in a way that makes honesty feel safe — repeated consistently, in the small moments that don’t feel like they matter.

But they do. They’re the whole thing.

Next week we get practical — what it actually looks like to ask for honest feedback, how to handle the silence that follows, and what to do when the answer surprises you. Subscribe so you don’t miss it.

Every employee wants to feel valued, respected, and heard. Those words mean nothing in a low-trust environment — because nobody believes them. Trust is what turns the intention into the reality. It’s not a soft skill. It’s the operating system. And without it, nothing else your leadership depends on works the way you think it does.

Helping Others Succeed is written for leaders, managers, and entrepreneurs who are done with corporate speak and ready to do the actual work of developing their people. The perspective comes from 30+ years of leadership in organizational performance across six industries — and from every seat at the table.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Subscribe now

Her direct report — a capable, well-liked member of the team — had been dropping the ball on client follow-through. Not dramatically. No single incident that demanded immediate action. Just a pattern: emails that went unanswered a day too long, commitments made in meetings that didn’t get logged anywhere, a client who’d mentioned feeling “a little out of the loop.”

So she finally sat down with him. She told him he was doing a great job overall. She mentioned that communication was something the whole team was working on. She said she wanted to make sure everyone was “staying aligned on client expectations.” She asked if there was anything he needed from her. He said no, things were good. She said great, keep it up.

He left the meeting feeling fine. She left feeling like she’d handled it.

Six weeks later, the client escalated.

This story is not unusual. I’ve watched some version of it play out in organizations across every industry I’ve worked in. A leader sees a problem. They work up the nerve to address it. They sit down with the employee — and then talk around it so thoroughly, so carefully, so considerately, that the employee has no idea a problem was even raised.

That’s not feedback. That’s a leader making themselves feel better while leaving their employee completely in the dark.

Last week we talked about what happens when you hand training to a subject matter expert without understanding how learning actually works. This week we go to the other side of that equation: what happens when a leader understands that development is their job — but still can’t deliver the one thing their employees need most.

The cost of silence — what delayed and softened feedback actually produces over time

We’ve been taught to soften the wrong thing

Somewhere along the way, leaders were trained to wrap feedback in so many layers of caution that the actual message gets lost. “Constructive criticism.” “Developmental feedback.” “Growth opportunity.” The labels are designed to make the conversation feel safer — for the leader. They do almost nothing for the employee who needs to know, clearly and specifically, what isn’t working and why it matters.

The instinct to soften isn’t wrong. Delivery matters. Tone matters. Timing matters. But there’s a point where softening becomes obscuring — where the leader is so focused on not making the employee feel bad that they fail to give the employee the information they actually need.

“Feedback wrapped in so many qualifiers that the message disappears isn’t kind. It’s a missed opportunity wearing the costume of a conversation.”

Think about what that employee deserved in that opening scenario. Not flattery. Not vague references to team-wide communication norms. A direct, specific, timely description of the pattern her manager had observed — and an honest conversation about what needed to change. What she got instead was a leader who felt better and an employee who stayed stuck.

Feedback is a gift. All of it.

In their book Where’s the Gift?, Nigel and Michael-John Bristow make an argument that sounds simple until you sit with it: all feedback has the power to help us reach our goals, regardless of how it’s delivered. Not just the positive feedback. Not just the feedback delivered skillfully and kindly. All of it. Criticism. Correction. The uncomfortable observation you’ve been sitting on for three weeks.

Their research goes further. The ability to capitalize on feedback — in all its forms — will do more to drive success than IQ, education, or natural talent. And the most dangerous feedback of all? No feedback. Silence. The conversation that never happened because the leader couldn’t find the right moment, the right words, the right way to say it without anyone feeling bad.

The Bristows frame feedback as a gift because that’s exactly what it is from the employee’s perspective: information they can use. Information that tells them where they stand, what’s working, what isn’t, and what to do differently. A leader who withholds that information — out of discomfort, avoidance, or an excess of caution — isn’t protecting their employee. They’re keeping them in the dark.

And employees who are kept in the dark don’t grow. They don’t correct course. They don’t improve. They just keep doing what they’re doing, assuming things are fine, until one day they’re not — and they had no idea it was coming.

The truth about “no news is good news”

Most leaders believe they give more feedback than they actually do. In survey after survey, leaders rate themselves significantly higher on feedback frequency than their direct reports rate them. The gap isn’t small. It’s consistent. And it points to something important: what feels like feedback to the leader often doesn’t register as feedback to the employee.

A comment in a team meeting isn’t feedback. An offhand remark at the end of a one-on-one isn’t feedback. A vague suggestion to “work on your executive presence” isn’t feedback. These things may feel like feedback to the leader who said them. To the employee, they’re noise.

The hard truth

If your feedback process consists primarily of annual reviews and occasional one-on-ones, you are not developing your people. You are documenting them. The employee who gets a surprise in their annual review — a ‘this has been a concern all year’ moment — was failed by their leader twelve months before that conversation happened.

What feedback actually looks like

Here’s a test. Which of these is feedback?

“You need to work on your communication with clients.”

“In Tuesday’s project update, the client asked about the revised timeline and you said you’d follow up. It’s now Thursday, and that follow-up hasn’t gone out. Here’s what I need you to do differently.”

The first one is a wish. The second one is feedback.

The first gives the employee nothing to act on. They know communication is the issue — but what kind? With whom? In which situations? What specifically should they do differently? The observation is real, but the information is useless.

The second gives the employee something concrete: a specific moment, a specific gap, and a clear performance expectation. That’s what feedback is supposed to do. Not make someone feel bad. Not make the leader feel like they’ve handled something. Give the employee information they can actually act on — and make clear what the standard is.

The same test applies to positive feedback. Which of these is feedback?

“Great job on that presentation.”

“The way you handled the pushback from the CFO in Thursday’s meeting — staying calm, acknowledging his concern before responding, then bringing the data — that’s exactly the kind of executive presence that builds credibility in that room. Do more of that.”

“Great job” is a pat on the back. The second statement is something far more valuable: a precise instruction. It tells the employee exactly what they did, why it worked, and that they should repeat it. Without that specificity, the employee who did something right has no idea what to replicate. They got lucky once and they don’t know why.

The feedback spectrum — vague vs. specific, corrective and positive

The other half of the conversation

Most leaders think of feedback as something you give when something goes wrong. That’s half the job — and not the more important half.

Specific, timely positive feedback is one of the most powerful and underused development tools available to a leader. It doesn’t just make people feel good. It tells them precisely what behaviors to repeat, anchors their confidence in real evidence, and signals that their leader is paying close enough attention to notice the good stuff — not just the gaps.

“You get more of what you focus on.”

There’s a reason this works. Behavior that gets noticed and named gets repeated. Behavior that only receives attention when it fails creates a different dynamic entirely — one where people are focused on avoiding mistakes rather than replicating success. The leaders who get this right aren’t just catching people doing things wrong. They’re catching people doing things right — and naming it out loud, specifically, in the moment. That habit does something corrective feedback alone never can: it builds the kind of confidence and clarity that makes people better even when you’re not in the room.

Think about the ratio of feedback you give. If every piece of feedback you’ve delivered in the last month was corrective, your employees know exactly what you’re unhappy about. They have no idea what you want more of. That’s not development. That’s a correction loop. And correction loops produce exactly what you’d expect: more of what you’re correcting for, and less of what you actually want. You get more of what you focus on — and right now, you’re only focused on what’s going wrong.

The Bristows are right that all feedback is a gift. But the gift of specific positive feedback is one most leaders are leaving unwrapped on the shelf.

Feedback is a daily habit, not a scheduled event

The leaders who do this well aren’t having harder conversations. They’re having more of them — and earlier. They don’t wait for the annual review to note that something is off. They don’t wait for the client to escalate. They catch the pattern at two weeks instead of six, and they say something specific enough to be useful.

They also don’t wait for the review to tell someone they did something well. They say it the same week. Sometimes the same day.

That habit — brief, timely, specific, honest, in both directions — is one of the highest-leverage things a leader can do. It costs nothing. It requires no program, no template, no HR approval. It requires the willingness to pay attention and then say, out loud, what you actually observed.

That’s the feedback conversation most leaders never have. And that’s exactly what their employees are missing.

Giving honest feedback — corrective and positive — is only half of the job. Next week we look at the half most leaders never attempt: actively asking for feedback themselves, and building the kind of trust that makes people willing to tell them the truth. Subscribe so you don’t miss it.

Every employee wants to feel valued, respected, and heard. A leader who gives honest, specific, timely feedback — in both directions — is doing all three at once. Telling people that their work matters enough to pay attention to. That they’re capable enough to handle the truth. That their growth is worth the conversation. That’s not a hard conversation. That’s the job.

Helping Others Succeed is written for leaders, managers, and entrepreneurs who are done with corporate speak and ready to do the actual work of developing their people. The perspective comes from 30+ years of organizational performance leadership across six industries — and from every seat at the table.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Subscribe now

That assumption is costing you more than you think. And here’s the part that stings: you made the decision specifically to save money and time. In most cases, it saves neither.

The productivity you expected to see after the training? Still missing. The skill gap you were trying to close? Still open. The time your best technical expert spent building slides instead of doing the work you actually needed her to do? Gone. And if the training didn’t land — which it probably didn’t — someone will eventually have to do it again. Now you’ve paid twice, lost the productivity twice, and the gap is still there.

What you just described isn’t training. It’s a meeting with a learning objective stapled to the front of it.

And meetings don’t change behavior.

The most expensive assumption in leadership

Here’s the version of this I’ve watched play out more times than I can count: a leader identifies a skill gap. They find the most knowledgeable person on the team — the technical expert who does the thing best, who’s been doing it longest, who could talk about it in their sleep. They hand them a project: build the training. Three weeks later, everyone sits through a two-hour session. Slides are covered. Questions are answered. Completion is logged.

Six weeks after that? Nothing has changed.

The SME Trap - what leaders assume happens vs what actually happens.

The SME Trap — what leaders assume happens vs. what actually happens

The leader is frustrated. The subject matter expert is confused. And the employees who sat through it have already forgotten 70% of what they heard — because that’s exactly what the research on human memory says will happen without reinforcement. We covered the forgetting curve in Week 3. This is what it looks like in practice.

The problem isn’t that the content was wrong. The problem is that knowing something and being able to teach it are two completely different skills — and most leaders never think to ask whether their technical expert has both.

A note before we go further: this isn’t about your L&D team or dedicated training professionals — they’re built for exactly this. This is about what happens when the job gets handed to your best technical expert because it seems faster and cheaper. That’s the decision this article is about.

The expert trap

Here’s what happens when you hand training to your best technical expert: they build it the way an expert thinks, not the way a learner needs to receive it.

Subject matter experts forget what it felt like not to know things. The steps that took them years to internalize feel obvious now, so they skip them. The context that makes the content make sense — the prerequisite knowledge a new learner doesn’t have — goes unaddressed because they can’t remember needing it. They front-load information because from where they sit, all of it feels equally important. They build a slide deck that is essentially documentation of everything they know, organized for maximum completeness rather than maximum learning.

The result is training that is thorough, accurate, and largely ineffective.

“Your best subject matter expert is often your worst trainer — not because they don’t care, but because they know too much.”

Researchers call this the curse of knowledge — the cognitive bias that makes it genuinely difficult to reconstruct what it felt like not to understand something you now understand deeply. It affects everyone. It’s not a character flaw. It’s a feature of expertise. And it is exactly why subject matter expertise and teaching ability are not the same credential.

What good training actually requires

In Week 3, we talked about the three things that make learning stick: doing, practicing with oversight, and getting real-time feedback. Those three things aren’t nice-to-haves. They’re the mechanism. Without all three present, information goes in and the forgetting curve takes it back out.

Effective training is built around that mechanism. It sequences content based on what the learner needs to know first, not what the expert considers most important. It creates opportunities for practice — real attempts at the skill in realistic conditions — not just passive absorption of information. And it builds in a feedback loop so that when someone tries something and gets it wrong, there’s someone present to say: here’s what I saw, here’s what I’d try differently.

A slide deck does none of those things.

A slide deck is a presentation tool. It delivers information. It does not create the conditions for practice. It does not build in a feedback loop. It cannot observe what a learner does with the content after they walk out of the room.

What the shortcut actually costs

The reason leaders hand training to a subject matter expert is cost and speed. The logic is understandable. But the math changes when you account for what that decision actually costs — none of which shows up as a line item:

• Your technical expert’s time. Every hour she spends building slides is an hour she’s not doing the job you actually need her doing. That time has a real dollar value — and you’re spending it on a product that probably won’t work.

• Every employee who sits through training that doesn’t change anything. Multiply one hour of ineffective training by the number of people in the room, and you’ve already spent more than you saved — in salary alone, before you count the lost productivity.

• The performance gap that stays open. The mistakes keep happening. The rework keeps piling up. Your senior people keep fielding the same questions. The gap you spent money to close is still there.

• The rebuild. When the first attempt fails, someone eventually has to do it again. Now you’ve paid twice, lost the time twice, and the frustration has compounded on both sides.

The “cheaper” option has a way of becoming the more expensive one. It just hides the cost better.

The hidden cost iceberg — the vendor cost you avoided vs. what you actually paid

What to do instead

This isn’t an argument for always bringing in an outside vendor. If you have dedicated training professionals on staff, use them — that’s exactly what they’re there for. For organizations without that resource, your subject matter expert can still play a valuable role — but as a content contributor, not the designer and deliverer.

For high-stakes skills where performance really matters, invest in someone who understands how adults learn. Have them partner with your technical expert to get the content right, then design the learning experience around the three things that actually make skills stick: practice, oversight, and real-time feedback.

For lower-stakes content, use your technical expert — but give them guardrails. Have them structure content around what people need to do, not just what they need to know. Build in practice. Build in a feedback loops. Define success as behavior change, not completion.

And in every case — stop measuring whether people showed up and sat through it.

The training effectiveness gap — what leaders measure vs. what actually matters

You’ve now got three weeks of context for why this matters. Week 3 told you how adults actually learn. Week 4 told you what happens when leaders solve problems instead of developing people. This week connects both: when you hand training to your best technical expert without understanding how learning works, you’re not skipping the expensive option. You’re choosing the more expensive one — you just don’t see the invoice until later.

Every employee wants to feel valued, respected, and heard. A leader who invests in development that actually works — not just fast, not just cheap — is making that signal louder than any plaque or performance review ever could.

Helping Others Succeed is written for leaders, managers, and entrepreneurs who are done with corporate speak and ready to do the actual work of developing their people. The perspective comes from 30+ years of organizational performance leadership across six industries — and from every seat at the table.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Problems got solved.

Work kept moving.

Her calendar was a disaster, but she wore it like a badge. That’s just what it looks like when you care, she told herself.

What she didn’t see was what was happening on the other side of those conversations. Her team had stopped trying to figure things out before they came to her. Why would they? She was faster. She was better at it. And she never seemed to mind. Over eighteen months, she had built a team of highly capable people who had learned, in the most efficient way possible, not to use their capabilities.

Three of her best people left in two years. Each one said something similar in their exit interview: they didn’t feel challenged. They felt like they were just waiting for instructions.

She was devastated. She had no idea she was the cause.

Over the past three weeks, we’ve covered the leadership mindset, how to diagnose performance problems at the root, and how adults actually learn. This week it all comes together in the thing that makes or breaks whether any of it sticks: whether you’re managing your people or genuinely developing them.

Managing and developing are not the same thing. Most managers know this. Very few do anything differently as a result. And almost none of them realize what the gap between the two is actually costing them.

The Core Difference: Directing vs. Coaching

When you direct someone, you’re solving the immediate problem. You answer the question, make the call, remove the obstacle. Things keep moving. This feels productive because it is — in the short term.

But every time you solve a problem your employee could have worked through themselves, you’ve made a trade: efficiency today for capability tomorrow.

When you coach someone, you’re building future capacity. You ask questions instead of giving answers. You let them try, watch what happens, and debrief the result. It takes longer in the moment. It pays back compounding interest over time.

The simplest version of this in practice: when an employee comes to you and asks, “What do you want me to do here?” — resist the reflex to answer. Instead, ask: “What would you recommend?” Then listen. Not to grade their answer, but to understand how they’re thinking. If their recommendation is solid, say so specifically — that reinforces the behavior you want to see more of. If it needs work, ask a follow-up question rather than correcting outright: “What do you think would happen if you tried that?” You’re not withholding the answer. You’re building the judgment that eventually means they don’t need to ask you at all.

What the Research Actually Shows

The science behind it

In the 1960s, psychologist Martin Seligman discovered something uncomfortable about how living things respond to repeated helplessness. When outcomes consistently fall outside their control — when their attempts don’t matter because someone always intervenes — they stop attempting. Even when the situation changes and they actually could influence the outcome, they don’t try. He called it learned helplessness.

In a management context, learned helplessness doesn’t look like a clinical condition. It looks like a team that brings you every problem and waits. Not because they’re incapable — they’re often highly capable people. But because experience has taught them that you’re the one with the answers, that their attempts are inefficient compared to yours, and that the fastest path to resolution runs through you.

You didn’t intend to build that dynamic. You built it anyway. One answered question at a time.

What This Is Actually Costing You

Most managers who live in problem-solving mode believe they don’t have time to develop people. What they’re actually describing is the direct consequence of not developing people. The two things are the same problem wearing different clothes.

Think about what it costs in a single day. An employee hits a decision point and can’t move forward without your input. They send a message, or stop by your desk, or put something in a queue. Then they wait. While they wait, their momentum stalls. If you’re in a meeting, that wait gets longer. Multiply that across a team of eight or ten people, each waiting for their turn in your queue, and you have an organization that runs at the speed of one person’s availability.

That’s not a people problem. That’s an architecture problem — and you built it.

The financial case is just as stark. Time spent waiting is money spent waiting. A mid-level employee earning $70,000 a year costs roughly $35 an hour in salary alone. Every hour your team spends in a holding pattern waiting for your answer is a direct expense — one that doesn’t show up on any budget line but compounds daily across every person on your team. And that’s before you account for the frustration, the disengagement, and the eventual turnover that follows when capable people realize they’ve stopped growing.

Development Doesn’t Require a Budget or a Program

Here’s what stops most managers from making the shift: they think development requires a formal program. A course. A budget approval. A conversation with HR. It doesn’t.

Development is a daily behavior. It happens in the five minutes after a meeting when you say, “Tell me what you think went well and what could have gone better” — instead of moving straight to the next thing. It happens when you give someone a problem slightly outside their current skill level and stay close enough to coach rather than rescue. It happens when you ask in your one-on-one, “What do you want to be better at by the end of this quarter?” and then actually structure their next few months around the answer.

None of that costs money. None of it requires a program. All of it requires the same thing: a decision to stop being the answer and start being the guide.

The managers who make this shift don’t suddenly have more time. What they have is a team that needs less of it. That’s not a coincidence. That’s the return on investment.

One Thing to Do This Week

The next time someone comes to you with a problem they could reasonably work through themselves — resist. Ask what they would recommend. Let them think out loud. Add what they missed. Then watch what happens the next time they hit the same kind of decision point.

It won’t be perfect the first time. That’s not the goal. The goal is to start reversing the pattern — to give your team one experience of figuring something out with your support rather than your answer. That single shift, repeated consistently, is what turns a team that waits into a team that moves.

Month 2 starts next week with something most leaders get badly wrong — and it costs them more than they’ll ever see on a budget line. Subscribe so you don’t miss it.

Subscribe now

Helping Others Succeed is written for leaders, managers, and entrepreneurs who are ready to do the actual work of developing their people. The perspective comes from 30+ years of organizational performance & leadership across six industries — and from every seat at the table.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Share

Last week we looked at what needs to happen before you put someone on a performance plan. This week we go upstream even further — to what needs to happen before you design or approve any development investment at all.

Here’s what most leaders assume when training fails: the content wasn’t good enough, or the employees weren’t engaged, or the platform was the wrong one. So they try a different vendor, a different delivery method, a different time of year. And they get the same result.

That’s because the problem isn’t what was taught. It’s that the entire process was missing the three things that make learning actually stick. And until those three things are present, it doesn’t matter how good the content is or how much you spend on it.

Why Your Brain Throws Away Most of What It Hears

In the 1880s, a German psychologist named Hermann Ebbinghaus mapped out what he called the “forgetting curve” — the rate at which new information disappears from memory without reinforcement. His finding was stark: without any follow-up, people forget roughly 70% of what they’ve learned within 24 hours. By the end of the week, most of it is gone.

That research is over a century old. It has been replicated dozens of times across different contexts and populations. And organizations continue to design training as if it doesn’t exist — loading employees into a room or a platform, having them sit through content, and calling it done.

The forgetting curve isn’t a character flaw. It’s how human memory works. New information that isn’t connected to action, practice, or meaningful experience doesn’t get encoded as durable knowledge. It gets processed, briefly held, and then released. Which means that expensive training program isn’t just failing to develop skills — it’s disappearing almost entirely within days of completion.

So what actually stops the forgetting? Three things, in sequence: doing, practicing, and getting feedback. Skip any one of them and the learning loop breaks.

Step One: Adults Learn by Doing, Not by Watching

The single most important thing to understand about adult learning is this: information delivered passively does not become skill. Reading about how to execute a lean changeover, watching a video about it, or completing a module on it — none of that is learning. That’s exposure. Learning happens when the employee actually attempts the skill in a real or realistic context.

This isn’t a preference. It’s how adult cognition works. The brain encodes new capabilities through action, not reception. A floor supervisor who completes a module on lean changeover procedures has not learned to execute a lean changeover. A supervisor who attempts one — with a knowledgeable person present — has taken the first step toward actually developing that skill.

“Telling someone how to do something is not developing them. It’s the beginning of the process, not the end of it.”

This is where the $50,000 training scenario breaks down first. Supervisors watched, listened, and answered quiz questions. Nobody asked them to actually do anything with what they’d learned. The information went in, the forgetting curve did its work, and six weeks later nothing had changed.

Step Two: Practicing — With Someone Paying Attention

Here’s where most training investments fall apart. Delivering information and calling it done is the equivalent of showing someone a map and assuming they now know how to navigate. The map is useful. But until someone actually attempts the route — with all the uncertainty that comes with it — the map hasn’t produced any capability.

Practice means attempting the skill in a real or realistic context, with someone present who knows what good looks like. That last part is critical. Practice without oversight isn’t development — it’s repetition. And repetition encodes whatever the employee is already doing, whether it’s right or wrong. The value of practiced attempts comes entirely from what happens next.

Sometimes an employee will attempt something and get it exactly right. That matters just as much as getting it wrong — because without feedback, they often don’t know why it worked, which means they can’t reliably repeat it. Practice, in both directions, creates the raw material for learning. Feedback is what turns that raw material into durable skill.

Step Three: Feedback That Actually Develops

Feedback is the mechanism that makes practice productive. But most leaders give feedback in a way that accidentally short-circuits the learning it’s supposed to create.

The instinct is to lead with your own observation: here’s what I saw, here’s what I’d change. That’s not wrong, but it skips the most valuable step — asking the employee what they think first. Start instead with: “Tell me what you think went well and what could have gone better.” Then listen.

This does three things the standard feedback approach doesn’t. It develops the employee’s ability to self-assess, which is the skill that eventually makes them less dependent on you for direction. It signals that you trust their judgment enough to hear it. And it frequently surfaces insights you wouldn’t have raised yourself. Only after the employee has reflected do you add what they didn’t catch — reinforcing what worked, adjusting what didn’t, and connecting both directly to the attempt they just made.

Feedback is most effective when it’s immediate and specific — close enough to the actual attempt that the employee can still feel the decision points they hit in real time. A general observation about performance trends isn’t feedback for learning. It’s a summary. What develops skill is a conversation that happens right after the attempt, tied directly to what just occurred.

The Hard Truth

The reason your training didn’t move the needle isn’t the content or the instructor. It’s that the learning loop was never completed. Employees received information but never practiced. And without practice, there were no attempts to observe, no results to reinforce, and nothing specific to give feedback on.

A process with no practice loop and no feedback isn’t training.

It’s an expensive presentation.

What the Complete Learning Loop Looks Like

The fix isn’t a better platform or more engaging content. It’s adding the two missing pieces. Before your team completes any training — online or otherwise — build in a plan for what happens after. How will employees apply what they learned? When will they attempt it? Who will observe and give feedback?

None of this requires a formal program or a dedicated training budget. It requires a leader who pays enough attention to say, shortly after an employee attempts something new: “Tell me what you think went well and what could have gone better.” Then add what they missed. That conversation — brief, specific, and timely — is worth more than any module ever completed in isolation.

An employee who is given the chance to try, allowed to practice with someone who is paying attention, and given honest feedback on both is receiving something rare and genuinely valuable.

Every employee wants to feel valued, respected, and heard — and consistent, intentional development is one of the clearest signals you can send that you mean it.

If this resonated with you, subscribe and share it with a leader who needs to hear it. And if something I said landed wrong — I genuinely want to know. Hit reply.

Next week we bring the learning loop to life — looking at the daily coaching habits that turn what you now know about how adults learn into something you actually do. Subscribe so you don't miss it.