Have you ever quietly fixed something a member of your team already turned in, instead of sending it back?
Recently a client came to me second guessing herself and wondering if she was confident and delegating the right way. A teammate had turned in a quarterly report with a few real errors and some rough writing. So, she sat down that evening and fixed it herself — numbers, language, all of it.
“It only took me twenty minutes,” she said. “It would’ve taken longer to explain what was wrong.”
Then she got quiet. “But he’s going to turn in the exact same kind of report next quarter. I know that.”
Key Takeaways
If you’ve ever quietly corrected a teammate’s work instead of taking the time to train them, here’s what’s actually happening — and what it costs both of you.
- Fixing it yourself doesn’t just save time — it skips the one conversation that would have actually taught them something.
- Correct it and say nothing, and they learn only that you’ll always catch it. Explain it after the fact, and it lands as criticism, not coaching — the moment for real learning already passed.
- What looks like efficiency is often a confidence gap — doubt in your own ability to develop someone without it turning into an ordeal.
- Real teaching is about being confident and delegating. That means talking through what’s in the way, then staying close and encouraging progress until you can step back — an investment worth making.
Two Bad Options, Same Root Cause
Once she’d fixed the report, she was stuck between two options, and neither one was good.
She could hand it back and make light of it — “just cleaned up a few things” — which protects the relationship but means he never learns what was wrong. Over time, that costs them both: his performance, her credibility as his leader.
Or she could sit him down and walk through every correction after the fact — a harder conversation than it would have been before, and one that risks landing as “here’s everything you did wrong” instead of “let’s work through this together.”
Either way, she loses a night cleaning up a report that wasn’t hers to clean up, and he loses the one thing that would have actually helped him: the chance to work through it with her coaching, instead of getting the finished version handed to him.
What She Was Actually Avoiding
This took my client a minute to sit with. What she was avoiding was the slower work of developing someone: talking through what wasn’t ready, offering principles instead of answers, and trusting he’d get there — maybe not on the first try.
That’s a different kind of confidence than the one we usually talk about. It’s not “can I speak up in this meeting.” It’s “can I sit with someone while they get something wrong, without fixing it, and still come out the other side with the relationship intact.” A leader without that confidence reaches for the keyboard instead of the conversation — a fast and certain result, rather than the slower process of really helping someone’s skills improve.
I told my client what I tell most clients here: you don’t build a team by protecting them from the discomfort of learning.
You build a great team by trusting yourself, and trusting them, enough to make it safe to learn — treating mistakes as opportunities and letting them try again.
It takes time to be confident and delegating in a way that’s encouraging, not awkward — to believe in someone’s growth even when they don’t yet believe in it themselves. Your quiet confidence in them is part of what helps them grow.
If this resonates with you, join me live on September 30 — we’ll go deeper on exactly this kind of pattern.
Keep Learning
Stop Second Guessing Yourself: A Confidence Webinar — Sept. 30.
Find out more about the framework here.
FAQ
Was the client wrong to fix the errors in the first place?
Not exactly — real errors in a report about to circulate need to get fixed. The mistake was fixing them silently instead of flagging them and letting her teammate fix them himself.
How do you correct real errors without just taking over the work?
Best done in person. Flag what’s wrong, talk through why, and help them understand the principle behind a better answer — then let them fix it and review it again. It takes longer than fixing it yourself, but that’s where the learning happens.
Why is this a confidence problem instead of a training problem?
Because most leaders in this pattern already know how to explain the fix — they just don’t want to sit through the conversation. That’s not a skills gap. It’s avoidance, and avoidance is usually confidence in disguise.
What should the client have done instead, now that she’d already fixed it?
Once it’s fixed, there’s no clean option left — the moment that mattered was earlier, before she started editing. Next time, flag the errors the moment she spots them.
