3. Invite Correction Before You Demand Correction¶
The project was finishing.
Twenty-plus people on the team. The department was the company's core engine at that moment, so anything that happened to its credibility happened to more than itself.
The work had been uncharted from the first day. Nobody in the room had run this kind of thing before. I had been acting as supervisor and shield — absorbing the criticism from above so the team could keep moving without flinching every time the pressure changed shape.
We were close to the line.
I reviewed the work and saw a missing piece. Small on the surface. Not small in effect — it would change the project's course.
Time was tight. I made a quick call to fix it.
A mid-level on the team interrupted me. In front of the others.
He proposed a different option. Two parts, not one. A different technical path. And a different way to handle the stakeholder conversation that would land afterward.
He said the second part out loud. Said his version would also avoid demoralizing the people who had been executing the work for weeks.
Then he stopped and looked at me.
My first reaction was silence.
Not the silence of having no answer.
Not the silence of ego freezing up.
The silence of running the question I had learned to run — and this is where this chapter touches the last one — the clear-mind diagnostic from the previous chapter, in real time. What is happening here. What is he actually saying. What does the team need in this moment, not what does my ego need.
The fear inside the silence was specific.
That accepting his correction publicly would cost me credibility. That the rest of the team would read me as not knowing what I was doing. That whatever structure was holding the room together would fracture if the call I had just made got walked back in front of everyone.
That fear was real to me at the time.
It was also wrong.
What I did next was simple. I trusted the mid-level's instinct. I asked the rest of the room if anyone else had something to add. We executed his version.
The project landed. Decent result.
The bigger gain was not the project. It was what the team did with what had just happened. Nobody read me as incompetent. In the post-mortem, they said the opposite. The credibility I had been afraid of losing went the other direction.
The fear was baseless.
But here is the part that matters most about this story, and it is the part that is easy to miss.
The mid-level did not correct me because I asked him to in that moment. There was no time for that. He corrected me because he had heard me say, many times, in calmer rooms — please speak up, feel free to correct me, even in crisis. I need you to become a better manager, so I can help you become better — enough times to act on it under pressure.
The invitation was already installed.
By the moment of the correction, there was no time to start trusting it. Trust had to already be there.
That is the whole thing.
What bad leadership usually does¶
The default move is to wait for the crisis to ask for upward feedback.
The leader notices, somewhere late, that they are not hearing pushback. The team has gone quiet. Updates are clean. Risks are not surfacing. So the leader says, in a meeting, with feeling — please, challenge me. I want to hear it.
And then the room stays quiet.
The leader takes the silence as agreement. Or worse, as proof the team is not capable of strategic-level critique.
But the silence is not the team's failure.
The silence is what happens when the rule is announced in the room where the team has to use it. Nobody trusts a rule they are hearing for the first time. Especially not from a leader they have not yet seen handle being corrected.
The first correction is the tuition. What the leader does with it is the curriculum.
If the leader has not paid that tuition yet — has not been corrected and shown the team how they handle it — then the invitation is words. The team can hear words. The team cannot stake their position on words.
So the team stays quiet.
And the leader concludes that the team does not have anything to say.
The principle¶
A leader cannot expect the team to accept feedback if the leader cannot accept feedback first.
The invitation has to be installed in calm. It cannot be issued in a crisis.
Why it matters¶
A team that cannot correct the leader will eventually only report good news.
A team that only reports good news will eventually hide the bad news.
By the time the bad news reaches the leader, the damage is usually larger than it would have been if the team had said it the first time it crossed their mind.
That is the structural cost.
There is also a quieter cost, and it is one most leaders never see clearly. The leader who cannot be corrected loses access to the parts of reality that the team can see and the leader cannot. Those parts of reality keep existing. They just stop reaching the desk where the decisions get made.
The decisions get worse.
Slowly.
Not because the leader got dumber. Because the room got quieter.
A leader who cannot be corrected becomes one of the team's biggest risks — and usually the last one to find out.
What better leadership looks like¶
The work is not in the moment of the correction.
The work is in the months before.
It is the calm-room repetition. The stated position said many times, in low-stakes conversations, in 1-on-1s, in retros, in the quiet space between projects — please speak up, even when it is uncomfortable, even when I have already decided, even when I am the one in the room with the most authority.
Said often enough that, by the time the room is hot, the rule does not need to be re-stated. It is already there.
And then the work is in the first time someone uses it.
Because the team is watching what happens.
If the leader gets defensive, the rule is dead. The team will read defensiveness once and remember it for years.
If the leader runs the diagnostic — what is the person actually saying, what does the team need here, is this person right — and acts on what they find, the rule stays alive. The room learns the rule is real.
That is the curriculum.
There is also a craft to it. Not every correction is correct. Not every disagreement is well-formed. Some pushback is a tone problem dressed up as a truth problem.
The leader does not owe the team agreement.
The leader owes the team a fair hearing, a clear answer, and a response that does not punish the act of speaking up.
If the correction is right, admit it and adjust.
If the correction is wrong, explain why — without making the person feel costly for raising it.
The decision still belongs to the leader. This is not democracy. The team is not voting on the call. What the team has access to is the room before the call. That is what the principle is protecting.
A second story¶
Years later. New team.
All seniors. Five-plus years of experience on average. Quarterly planning meeting.
I presented an alternative idea on one of the plans. I asked, explicitly, for feedback. I said the words.
Nobody spoke up.
Including the people I knew were normally vocal.
I sat with that silence for a moment, and the diagnosis did not point back at me first. It pointed at what the room had been before me. The team had come up under previous leadership where formal meetings followed a specific shape — leader presents, team agrees, dissent happens later or not at all. Disagreement in the formal setting had been unsafe.
The seniors were carrying that conditioning into my room.
But the diagnosis did not stop there. Because earlier, when I had set expectations with the team, I had said a version of: I am a democratic leader. But once I decide, I expect us to row in the same direction. No second-guessing.
The intent was clean. Argue before the decision. Execute after. That was the rule I was working from.
The way the team likely heard it was less clean. The discussion phase is risky if you guess wrong about whether it has already ended.
So part of the silence was inherited from the leader before me.
Part of it was my own framing, misread.
A stated invitation is not a trusted invitation. I had stated it. They had not yet trusted it.
What I did next is the part of this I want to be honest about.
I did not push harder.
I did not say come on, speak up, I want to hear it. That move would have raised the cost of silence and asked the team to pay it. The team had been trained for years to not pay that cost. Asking them to override the training in that meeting would have produced compliance, not voice.
I changed the meeting itself.
I said it out loud — this is not the previous team. This is not me being in charge in the way you knew it. This is brainstorming. This is not a final decision.
I re-presented the idea in simpler language. Concrete examples. Small simulations. I made the question small enough that any senior could answer it without putting their position on the line.
I lowered the cost of speaking up rather than demanding that the team pay the cost they had been trained to avoid.
The seniors started to speak. The room became chatty. The trust dynamic shifted.
The juniors still stay quiet in formal meetings. When I find them one-on-one, they will talk. That gap is the part of this work I still have not finished.
What another leader trains into a team is real. It is slow to fade. Not all of the silence is inherited — some of it is just people still finding their footing — but the part that is inherited does not lift just because a new leader walked in.
The principle is not "say it once and the team will speak."
The principle is install it in calm, re-earn it in every room, and keep working at the levels where it has not yet reached.
A practical tool¶
The Standing Invitation¶
The standing invitation is what the team will trust at 11pm in a crisis.
It cannot be installed at 11pm.
Test it with four checks.
1. Have I said clearly, more than once, what kinds of disagreement are welcome and at what stage of a decision they are welcome?
A one-time announcement does not install a rule. Repetition does. The team needs to hear it in calm rooms, in 1-on-1s, in low-stakes settings, until the rule becomes ambient.
The other half of this check is naming the stage. Disagreement before a decision is one thing. Disagreement after a decision is committed and being executed is a different thing. The team should not have to guess which phase they are in. The leader should name it out loud, every time. This is brainstorming, not a final decision. That sentence tells the room which rules are live.
2. Has anyone on the team actually corrected me publicly, and did I respond in a way that taught the room it was safe?
The first correction is the tuition. What the leader does with it is the curriculum.
If no one has corrected the leader publicly yet, the standing invitation is untested. The team is still running on words, not on evidence. That is a fragile state. It will not hold under pressure.
3. Do junior team members speak in the room, or only one-on-one?
If juniors only talk one-on-one, the invitation has not reached them yet. The work is not done.
This is also where the leader has to lower the cost rather than raise the demand. When a level of the team is not using the invitation, pushing harder does not work. Reframing the room does. Simpler language. Smaller questions. Naming what kind of meeting it is. Make it cheap enough to speak that the cost stops being the reason for the silence.
4. When I get pushed back on, is my first reaction a clear-mind diagnostic, or a defense of the call?
This is the leader's tell. The team can read it from across the room.
The diagnostic asks: what is this person actually saying, what does the team need, is this correction right. The defense asks: how do I keep my call standing. The team can tell which one is happening, even when the leader cannot.
If the first reaction is consistently defense, the rest of the standing invitation does not matter. The room already knows.
The ethical boundary¶
Inviting correction is not the same as running every decision by committee.
The team is not voting on the call. The leader still decides. The principle is about access to dissent before the call — not consensus on the call.
It is also not the same as accepting every correction as correct. Bad-faith pushback exists. Tone problems exist. A team member who is wrong is wrong, and the leader does not owe them agreement.
Separate the tone problem from the truth problem. Hear the truth. Address the tone separately if it needs addressing.
And — this is the one that catches leaders most often — being correctable is not the same as performing humility. Real correctability has a price tag. The price tag in my first story was concrete — the public credibility I was afraid of losing in the moment the mid-level corrected me. That fear was the honest version of the cost. Performed humility is what happens when a leader wants the credit for being correctable without actually paying the price for it. The team can tell the difference.
The responsibility is for what the leader's blind spot will cost the team if nobody is allowed to name it.
Simple rules¶
- Install the invitation in calm. Do not wait for the crisis to ask for it.
- Say what kinds of disagreement are welcome, and at what stage of a decision.
- Name the phase out loud. This is brainstorming, not a final decision.
- The first time you are corrected publicly, run the diagnostic, not the defense.
- Separate tone problems from truth problems. Address them separately.
- When a level of the team will not use the invitation, lower the cost. Do not raise the demand.
- The decision still belongs to the leader. Access to dissent is the principle, not consensus on the call.
Reflection questions¶
- When was the last time someone on my team corrected me in front of others? What did the room learn from how I handled it?
- Have I said the standing invitation enough times in calm rooms that the team would trust it under pressure?
- Do my juniors speak in the room, or only one-on-one? If only one-on-one, what is the cost I am asking them to pay that they cannot yet afford?
- When I set up argue before, execute after, did I name the phase clearly enough that the team can tell which one we are in?
- Is my first reaction to pushback a diagnostic, or a defense?
- Am I performing humility, or actually paying the price of being corrected?
- What part of the room I am leading has inherited a culture of silence from a leader before me — and what am I doing about it?
Reminder¶
The standing invitation is what the team will trust at 11pm. It cannot be installed at 11pm.
A leader who cannot be corrected becomes one of the team's biggest risks — and usually the last one to find out.