You did everything right. You sorted the decisions. You wrote the guides. You gave real authority to real people and told them the calls were theirs.
And then someone got it wrong.
What happens next is the most important moment in this entire series. Because how you respond when your team makes a mistake determines whether the whole system holds — or quietly falls apart. One reaction either builds decision capacity or destroys it. And most leaders don’t realize which one they’re choosing.
The Two Responses That Undo Everything
The first response is the takeover. Someone makes a call that doesn’t go the way you’d hoped, and you step in immediately. You handle the fallout yourself, correct the situation, and maybe have a sharp conversation about what should have happened. Then you go back to making that decision yourself, at least for now.
It feels like the responsible move. It is not. The message your team hears is clear: when it matters, you can’t trust me to handle it. The next time something is on the line, they won’t decide. They’ll ask. And the time after that. And the time after that.
The second response is the disappearing act. You notice the mistake, you say nothing, you fix it quietly, and you move on. This one feels like grace. It isn’t. Your team learns that outcomes don’t get reviewed, that mistakes don’t generate feedback, and that nothing they do is quite real enough to matter. That erodes confidence in a different way — not through fear, but through disconnection.
Neither one teaches anything. Neither one makes the next decision go better. And both leave you back at the center of everything.
What the Mistake Is Actually Telling You
When someone on your team gets a decision wrong, there are only a few real causes. And knowing which one you’re dealing with changes what you do next.
The first cause is a gap in the guide. The decision rule wasn’t specific enough, or the boundary was unclear, or the edge case wasn’t covered. If this is what happened, the person didn’t fail — the documentation did. That’s your responsibility to fix, not theirs to absorb.
The second cause is a skill gap that wasn’t caught earlier. The person had the authority but not quite the judgment yet. This one calls for coaching, not correction. There’s a difference. Correction says you got it wrong. Coaching says here’s what I’d want you to see next time, and here’s how to get there.
The third cause — and this one matters — is that the person made a call outside their lane. They had a decision that belonged in bucket two or bucket three, and they treated it like bucket one. That is a different conversation. Not a harsh one, but a clear one. The boundary needs to be reaffirmed, calmly and without drama.
Knowing which cause you’re dealing with before you respond keeps you from punishing the wrong thing.
The Conversation That Builds Capacity
Imagine a front office lead who processes a tuition credit that falls outside your written policy. A family asked, she wanted to be helpful, and she approved it without escalating. The guide said to escalate anything outside the written criteria. She didn’t.
Here’s the conversation that builds capacity: “I saw the credit you processed for the Nguyen family. I want to walk through it with you, because I think this one fell outside the guide. Can you tell me what you were thinking?”
You listen. You understand the reasoning. Then you say: “I get why you wanted to help them. Here’s why this one needed to come to me — once we start making exceptions outside the policy, families compare notes, and it creates a fairness problem we can’t easily fix. The guide exists to protect you from that pressure. Next time, let’s say the office will follow up within a day, and bring it to me. Does that make sense?”
Then you update the guide. Add a line about families who have a history of late payment, or who have already received a credit this year. Close the gap so the same edge case doesn’t come up twice.
That conversation takes ten minutes. It makes the next decision better. And it tells your team member something important: I am not angry. I am building the system with you.
When the Mistake Was More Serious
Some mistakes carry real weight — a miscommunication about a child’s allergy, an enrollment decision made without your review, a family situation handled in a way that caused damage to trust. These deserve more than a ten-minute debrief.
Even here, the principle holds. Start by understanding what happened before you respond. Find the cause. Address the system failure and the skill gap separately. Then hold the line clearly on the authority issue without making it personal.
What you’re trying to preserve is your team’s willingness to keep deciding. The worst outcome of a serious mistake isn’t the mistake itself — it’s that your team shuts down completely and starts asking you about everything again. A team that’s afraid to decide is not safer than a team that decides imperfectly. It’s just a team that’s shifted the risk back to you.
The Culture That Makes This Sustainable
Over time, how you handle mistakes becomes part of how your school operates. If your team has seen you respond to errors by updating the guide rather than pulling back authority, they’ll keep deciding. If they’ve seen you use a mistake as a teachable moment rather than a reason to micromanage, they’ll come to you with problems earlier instead of hiding them.
That culture is what makes the whole system in this series actually work long-term. You can write every guide, sort every decision, and protect every block of time — but if your team doesn’t believe that mistakes are recoverable, they’ll quietly stop using any of it.
Build the kind of environment where getting it wrong is something that makes the system better. That’s how you lead without being the ceiling.
Where the Series Leaves You
Across these six posts, the central idea has stayed the same: decisions should be made at the lowest capable level. The person closest to the situation, with the right information and the right authority, should own it. Your job is to design that system — not to be the answer to every question.
That takes time to build. It takes honest diagnosis, written guides, protected time, and the willingness to let your team make mistakes without taking back the authority you gave them. None of it is especially complicated. All of it requires intention.
Start with one thing. One gap diagnosed. One guide written. One decision handed off for real. Then let it stand.
For leadership training, operational resources, and consulting for preschool owners and directors, visit chelseareue.com.
