The Radical Reception Protocol

Turning Conflict into Calibration

The Problem

Most leaders think they're good at receiving feedback. They're not.

Here's what actually happens. Someone says something hard. Your chest tightens. Your brain starts composing a rebuttal before they finish their sentence. You nod. You say "I appreciate the feedback." Then you explain why they're wrong — politely, of course — and walk away convinced they just don't have the full picture.

That's not receiving feedback. That's PR.

Your ego — call it PR Brain — treats every piece of critical input as a threat to your identity. And PR Brain is fast. Before you even register the content of what was said, it's already spinning a defense. The armor goes up. You explain. You contextualize. You redirect. You shut down. All of it happens Below the Line, and none of it looks like listening.

The cost is invisible but massive. Your team stops telling you the truth. Not because they don't see it — because they've learned it isn't safe. You end up leading inside a reality distortion field of your own making, surrounded by people who've decided silence is less dangerous than honesty.

The goal of this protocol isn't to make you agree with every piece of feedback. It's to make you calibrated. Feedback is data about how your reality maps onto someone else's. That's it. You don't have to accept the data. But you have to actually receive it first.

The mantra is Brene Brown's: Strong Back, Soft Front.

Strong Back means: I know who I am. This feedback doesn't define my worth. I can hear hard things without crumbling.

Soft Front means: I remain open to data even when it stings. I don't armor up. I let it land.

Most leaders have the ratio backward — soft back, hard front. They look tough on the outside while quietly spiraling on the inside. This protocol flips it.

Who This Is For

Founders, executives, and team leaders who suspect their people aren't telling them the full truth — and who want to fix that, even though fixing it means hearing things they'd rather not.

Also for anyone who's been told they're "defensive" and genuinely doesn't understand why. (That confusion is the symptom.)

What You'll Need

• One person willing to give you honest feedback (a direct report, co-founder, partner, coach)
• A private space — not a hallway, not a Slack thread, not a team meeting
• 20–30 minutes of uninterrupted time
• The willingness to feel uncomfortable and not fix it immediately
• The After-Action Audit checklist (end of this document)

The Protocol

Five phases. Each one has a specific job. Skip a phase and the whole thing collapses.

Phase 1 — ASK (Extraction)

Feedback is an asymmetric bet for your team. If they tell you the truth and you react badly, they pay the price — your anger, your distance, a subtle shift in how you treat them. If they stay quiet, nothing happens. Silence is the rational choice.

Your job is to change the math. Pull the truth out. Don't wait for it to arrive.

The trap: "My door is always open." Every leader says this. It means nothing. An open door is passive. It puts the burden on them to walk through it, which requires exactly the kind of courage you're supposed to be creating conditions for. Low-trust environments don't produce brave truth-tellers. They produce skilled avoiders.

The fix: create a specific container. Give the feedback a shape before it exists.

The Brain Chamber Method:

"I want to ask you something, and I want you to think before you answer. Please don't say it yet — just think it. What's the one thought you're afraid to tell me because you think it'll hurt my feelings or make things awkward between us?"

Pause. Let them sit with it.

"Do you have it? Is it in your brain chamber?"

Wait for a nod or a yes.

"Okay. Now please say it."

This script works because it separates the decision to speak from the act of speaking. By the time they open their mouth, they've already committed internally. The activation energy drops.

Use it in one-on-ones. Use it after a rough project. Use it when you notice someone pulling back. The question isn't whether they have something in the brain chamber. They always do.

Phase 2 — REGULATE (Pivot)

This is the moment of impact. They've said the thing. Your amygdala wants to fight.

One rule: Do. Not. Explain.

Explaining is defense. Defense is war. The second you start explaining context, offering justification, or correcting their perception, you've told them their experience is wrong. And they'll never bring you truth again.

Your only script here:

"Tell me more."

That's it. Say it. Mean it. Then shut up.

Internal check: if you're formulating your rebuttal while they're still talking, you're Below the Line. You're listening to respond, not to learn. Notice that. Name it internally. Let the rebuttal go. You can pick it up later if you still want it — you almost never will.

This phase is physical. You'll feel heat in your chest, tension in your jaw, a pull to interrupt. Those sensations are PR Brain loading its weapons. Let the sensations exist. Don't act on them.

Phase 3 — ACKNOWLEDGE (Mirror)

Prove you heard them. This is the phase most people skip, and it's the one that matters most.

If you don't mirror back what they said, they assume one of two things: you dismissed it, or you're storing it for later retaliation. Neither builds trust. Neither gets you more truth next time.

Repeat their words back. Use their language, not yours. And amplify the emotion slightly.

Why amplify? If you tone it down, they won't feel heard — they'll think you're minimizing. If you exaggerate, they'll correct you downward: "Well, it's not quite that bad." Either way, you converge on accuracy. But starting too low kills the conversation.

The script:

"I think I heard you say [summary in their words, emotion included]. Is that right?"

Then: "Is there more?"

Keep asking "Is there more?" until they say "That's everything" or "No, that covers it." People deliver feedback in layers. The first thing they say is the safest version. The real thing lives two or three layers down. "Is there more?" is the shovel.

Final check:

"Do you feel heard?"

Don't move on until the answer is yes.

Phase 4 — APPRECIATE (Gift)

This is a transaction, and you need to honor it.

They just gave you a dangerous gift. Truth, in most organizations, is career risk. They trusted you with something that could blow up in their face. Pay for it with genuine gratitude.

The script:

"Thank you. I know that was hard to say, and I appreciate you trusting me with it."

No qualifiers. No "Yes, but..." No "I appreciate that, and here's my perspective..." The appreciation stands alone. Full stop. Anything you attach to it dilutes it.

If the feedback was wrong — factually, completely wrong — you still say thank you. Because the act of telling you was brave regardless of the content. And if you punish inaccurate truth-telling, you won't get accurate truth-telling either. You'll get silence.

Phase 5 — ACCEPT & ACT (Contract)

You are not a slave to feedback. Receiving it fully doesn't obligate you to obey it. The tyranny of the feedback-giver is just as destructive as the tyranny of the leader who won't listen. You have to be explicit about what you're doing with what you heard.

Option A — Reject with principle.

You've heard it. You've mirrored it. You've thanked them. And after sitting with it, you disagree. Say so directly:

"I've thought about what you said. Here's where I landed and why: [principle or reasoning]. I'm not going to change this, but I want you to know I took it seriously, and I want you to keep telling me things like this."

Rejection with transparency preserves trust. Silent rejection destroys it.

Option B — Accept and co-create.

You agree the feedback points to something real. Now build the contract together:

• What specifically will you change?
• By when?
• How will they know it happened?

Then — and this is the part almost nobody does — report back when you've done it.

"Remember when you told me I was steamrolling in product reviews? I've been holding my comments until everyone else has spoken for the last two weeks. Have you noticed a difference?"

"I did X because you told me Y" is the most trust-building sentence in leadership. It closes the loop. It proves the feedback mattered. It guarantees they'll give you more.

What You'll Find

The first time through, Phase 2 will be the hardest. Your body will revolt. You'll formulate six different explanations and swallow all of them, and it will feel like holding your breath underwater. That's normal. That's PR Brain throwing a tantrum because you took away its favorite toy.

By the third or fourth time, something shifts. You start to notice a gap between hearing and reacting — a beat where you can choose. That gap is the whole game. It gets wider with practice.

You'll also discover that most of the feedback you've been dreading is smaller than you imagined. The monster behind the door is almost always shorter than the door. People aren't stockpiling devastating critiques. They're holding back observations they think you can't handle. When you prove you can, the observations get more useful and less charged.

The unexpected payoff: your own feedback improves. Once you've practiced receiving at this level, you understand what it feels like to be heard. You stop delivering feedback like a verdict and start delivering it like a gift. The protocol is contagious.

One warning. Some people will test you. They'll give you something small first — "The meeting ran long" — to see if you flinch. Pass that test and the real feedback follows. Fail it and they file you under "says they want honesty, doesn't mean it." You only get a few shots at this before the verdict sticks.

Adaptations

For co-founders: Run this protocol in both directions in the same sitting. Twenty minutes each. Use a timer. The reciprocity matters — it prevents the dynamic where one person is always the feedback-giver and the other is always the subject. Swap roles every time, no exceptions.

For remote teams: Video on, not audio only. You need to see their face during Phase 3 to know if your mirror landed. If video isn't possible, over-index on "Is there more?" and "Do you feel heard?" — you're flying without instruments, so check your altitude more often.

For feedback you violently disagree with: Complete all five phases anyway. Sleep on it. Revisit Phase 5 in 48 hours. Your first reaction to feedback you hate is almost never your best reaction. Give your nervous system time to come down before you decide what to do with it.

For written feedback (Slack, email, surveys): The protocol still applies but Phase 2 is where it breaks. Written feedback gives you unlimited time to craft a defense, and PR Brain will use every second of it. Write your first response. Delete it. Write "Thank you for sharing this" instead. Then do Phases 3–5 in a live conversation, not in text.

For people who cry when they receive feedback: Strong Back. The tears aren't weakness — they're your nervous system processing threat. Let them happen. Don't apologize for having them. Don't let the other person comfort you out of finishing the conversation. Regulate, then continue.

After-Action Audit

Run this after every feedback conversation:

• Did I use the Brain Chamber (or equivalent) to pull the feedback out, rather than waiting for it?
• Did I say "Tell me more" instead of defending or explaining?
• Did I mirror their words back until they confirmed "yes, that's it"?
• Did I say thank you with nothing attached?
• Did I explicitly accept or reject the feedback — out loud, to their face?
• If I accepted: did I set a specific date to report back on what I changed?
• Did I report back when the date arrived?

Score yourself honestly. Anything you missed, do it retroactively. A late close is better than an open loop.

Where This Came From

The five-phase structure is adapted from Matt Mochary's 5 A's framework (Ask, Acknowledge, Appreciate, Accept, Act), which he teaches to founders and CEOs as part of his operating system for high-performance teams. This protocol extends the framework with specific scripts, the Brain Chamber extraction method, and the report-back mechanism that closes the trust loop.

The "Strong Back, Soft Front" framing comes from Brene Brown's Dare to Lead, where she traces it to Buddhist teacher Joan Halifax. Brown's research on vulnerability and armor connects directly to what this protocol calls PR Brain — the reflexive self-protection that masquerades as strength.

The Below the Line concept comes from the Conscious Leadership Group's framework, where "above the line" means open, curious, and committed to learning, and "below the line" means closed, defensive, and committed to being right.

Related Protocols

• The Radical Calibration Protocol — The other half of this conversation: how to deliver feedback so it actually lands
• The Co-Regulation Protocol — When the feedback conversation triggers a full nervous system response in either party
• The Location of Leadership — The Above/Below the Line framework that underpins Phase 2's internal check