The Effective Feedback Protocol

The Problem

You have a team member who's underperforming. You know it. They probably know it. And for the last six weeks, you've been telling yourself you'll "find the right time" to bring it up.

You won't. There is no right time. There's only the growing distance between what you see and what you say — and that distance is where trust goes to die.

Most founders avoid hard feedback because they think clarity is cruel. They soften, hint, sandwich criticism between compliments, or wait until the performance review forces the issue. By then, resentment has calcified on both sides.

Brené Brown calls it plainly: clear is kind. Unclear is unkind.

The vague "Hey, can we tighten things up a bit?" that feels gentle? It's not. It leaves people guessing what they did wrong, whether their job is at risk, and whether you respect them enough to say the actual thing. Kindness is telling someone exactly what you see, exactly what it costs, and exactly what "better" looks like. That's the whole protocol.

Who This Is For

Founders, operators, and leaders who know a conversation needs to happen — and keep not having it. People who confuse being liked with being trusted. People who've watched small problems metastasize into team-wide dysfunction because nobody said the obvious thing out loud.

What You'll Need

• Time commitment: 20 minutes to draft the pre-game script. 15–30 minutes for the conversation itself.
• Prerequisites: Genuine investment in the other person's success. If you're looking for a tool to justify firing someone you've already given up on, this isn't it.
• Tools: A document you can draft in — email, Notes app, anything with a cursor. You'll write the feedback before you deliver it.

The Protocol

Core Principles

Clear is kind. Specificity is generosity. Vagueness is cowardice dressed as politeness.

Feedback builds trust. Not the comfortable, "great job on the presentation" kind. The kind where you say the hard thing and the other person walks away thinking: they told me the truth because they believe I can handle it. That's a trust deposit, not a withdrawal.

Reciprocal. You own your part. Always. The feedback conversation is never a prosecution. If you contributed to the problem — unclear expectations, insufficient resources, a missed signal you should have caught — you say so before asking them to change.

The goal is growth. Not punishment. Not documentation for HR. Not catharsis for your frustration. Growth. If you can't hold that intention, postpone the conversation.

Phase 1: Pre-Game Checklist

Before you schedule the meeting, answer four questions. All four must be Yes.

Am I ready to sit next to them, not across from them?

This is literal and metaphorical. Brené Brown's test: can you have this conversation from the posture of "I want you to succeed" rather than "I want to punish you for failing"? Check your body. If your jaw is tight and you're rehearsing how to win the argument, you're not ready. Come back tomorrow.

Am I ready to own my part?

Every feedback conversation has a mirror in it. Did you set the expectation clearly enough? Did you provide what they needed to hit it? Did you let the problem slide for weeks before addressing it? That delay is your contribution. Name it.

Am I ready to credit the specific impact?

Not "this is a problem." How does the behavior affect the team, the customer, the funding timeline, the revenue target? If you can't name the consequence in concrete terms, your feedback is an opinion. Opinions are easy to dismiss. Consequences are not.

Draft the script.

Write the full four-step feedback (below) as if you were sending it in an email. Use the actual words you plan to say. Don't send it. Use it as your guide in the live conversation. After the meeting concludes, you can send it as a written follow-up so both sides have the same record.

Phase 2: The Script

Four steps. In order. Don't skip.

Step 1 — The Observation (Data)

Apply the Camera Test. A camera doesn't record "laziness." A camera records arriving at 9:15 when the standup starts at 9:00. A camera doesn't record "not caring." A camera records three consecutive sprints where the test coverage dropped below 40%.

Your job here is to describe what a camera would see. No opinions. No generalizations. No "always" or "never."

Wrong: "You've been really disengaged lately."

Right: "In the last four weeks, you've missed three sprint deadlines and arrived after standup started on seven occasions."

The Camera Test strips out your interpretation and leaves the fact. Facts are hard to argue with. Interpretations are easy to deflect.

Step 2 — The Impact (Consequence)

What did the observation cost? Be specific. Name the number, the team, the customer, the outcome.

Not: "It's causing problems."

Instead: "Engineering blocked for two days waiting on the spec. That pushed the release past the investor demo window. We missed a $40K expansion conversation."

No exaggeration. You don't need it. If the impact is real, the real version is damning enough. Inflating it gives them a reason to argue about your numbers instead of their behavior.

Step 3 — The Story I'm Telling Myself (Interpretation)

This is the Brené Brown move that separates this protocol from every other feedback framework.

Own your interpretation as your story, not as truth. Say it out loud:

"When I see [Observation], the story I tell myself is [Fear]. This conflicts with our value of [Value]."

Example: "When I see three missed deadlines in a row, the story I tell myself is that this role isn't a priority for you anymore. That conflicts with the ownership culture we've built here."

Why frame it as a story? Because it might be wrong. They might have context you don't have. A sick parent, a mental health crisis, a dependency on another team that's invisible to you. By saying "the story I tell myself," you leave the door open for them to correct you — without either of you losing face.

But here's the discipline: even if your story turns out to be wrong, the observation and the impact remain. The data doesn't change. The cost doesn't change. Only the interpretation shifts.

Step 4 — The Reality (The Ask)

What does "done" look like? Not vibes. Not "better." A specific expectation with a specific timeline.

"Starting Monday, I need specs delivered 48 hours before sprint planning. If something's going to be late, I need a heads-up by Thursday end of day, not Monday morning."

Give them a finish line they can actually see. Ambiguous expectations produce ambiguous performance.

Worked Example A: Founder to PM

Observation: "In Q1, four of six feature specs arrived after engineering had already begun sprint planning. The last two arrived on the morning of planning day."

Impact: "Engineering burned 22 hours rebuilding sprint plans around late specs. The authentication feature shipped 11 days late. That delay pushed us past the retention window — we missed our Q1 retention target by 8%."

Story: "When specs arrive late repeatedly, the story I tell myself is that you're overcommitted and this product isn't getting your full attention. That scares me, because our Series A hinges on Q2 retention."

Ask: "I need specs locked 72 hours before sprint planning. If that timeline isn't realistic given your current load, tell me now and we'll reprioritize together. But 72 hours is the number."

Worked Example B: VP Sales to AE

Observation: "Your activity numbers are strong — 47 calls a week, 12 demos booked in March. But your close rate is 0%. Zero of 12 demos converted. In our last pipeline review, you attributed all 12 losses to 'marketing sending unqualified leads.'"

Impact: "We invested $18K in pipeline generation for your territory in Q1. Zero return. The SDR team is questioning whether to keep routing leads to your patch."

Story: "When I see high activity and zero conversion, the story I tell myself is that something in the demo itself isn't working — the pitch, the qualification, the discovery questions. When I hear the losses attributed entirely to marketing, the story I tell myself is that you're not looking at your own reps yet."

Ask: "I want to shadow your next four demos. Not to judge — to see what's happening in the room. After that, we build a 30-day improvement plan together. If the close rate is still at zero after 30 days and four observed demos, we have a different conversation."

Phase 3: The Handover

You've delivered the script. Now shut up.

Ask one question: "What does this look like from your perspective?"

Then listen. Actually listen. Not the kind of listening where you're reloading your next point. The kind where you're genuinely curious whether your story matches theirs.

The 24-Hour Rule. For serious feedback — the kind that challenges someone's identity or threatens their role — give them 24 hours before expecting a response. Tell them directly: "You don't need to respond to this right now. Take a day. We'll reconnect tomorrow at [time]." People process hard truths at different speeds. Demanding an instant commitment under emotional pressure produces compliance, not change.

The Safety Valve. If emotions flood — tears, raised voices, visible shutdown — call a time-out. "I can see this is hitting hard. Let's pause and come back to this at 2pm." This isn't retreat. It's protecting the conversation from the moment.

What You'll Find

The draft is where the real work happens. When you sit down to write the four steps before the meeting, you'll discover gaps in your own case. You'll realize the "impact" you were furious about is actually thinner than you thought — or that the observation you were planning to lead with is contaminated by interpretation. The script forces you to separate what you saw from what you felt about what you saw. That separation is the difference between a conversation that changes behavior and one that just damages a relationship.

You'll also discover your own contribution faster than you expect. Writing "I need specs 72 hours before sprint" prompts the question: did you ever actually say that? Or did you assume it was obvious and then resent them for not reading your mind? Most founders who run this protocol for the first time find at least one expectation they never made explicit.

The biggest shift is what happens after the fourth or fifth time you use it. People stop being surprised by feedback. They start expecting it. And something strange happens — they start giving it back to you, using the same structure. That's the sign the culture has moved. Feedback becomes a tool the whole team owns, not a weapon the boss deploys.

Adaptations

When you're the one receiving. Ask the person giving you feedback to run the Camera Test on their observation. "Can you help me understand — what specifically did you see?" is a non-defensive way to separate data from interpretation. If their feedback is vague ("you seem checked out"), you're allowed to ask for the footage. You need specifics to act on it.

Peer-to-peer, no authority. The protocol works without a power differential, but Step 4 changes. You can't assign a deadline to a peer. Instead, co-create the ask: "What would we both need to do differently for this to work?" The observation and impact steps stay identical.

Repeated pattern, same person. If you've run this protocol twice on the same issue with the same person and the behavior hasn't changed, the conversation shifts from feedback to fit. That's a different protocol. Don't use a growth tool to avoid a separation decision.

High-emotion relationships (co-founders, family businesses). Add a 10-minute co-regulation step before the script. Walk together. Side by side, eyes forward. Let the nervous system settle before you ask the brain to process hard data. The Co-Regulation Protocol covers this in detail.

Written-first cultures (remote, async). Send the four-step script as a written document. Give 24 hours for a written response. Then schedule a live call to discuss. The written version prevents the "I didn't say that" revisionism that plagues hard conversations over Zoom.

Where This Came From

The structure draws from Brené Brown's Dare to Lead, specifically the "rumbling with vulnerability" framework and the phrase "the story I'm telling myself" as a tool for owning interpretation. The Camera Test comes from behavioral psychology — the discipline of describing behavior without attributing motive, which shows up in everything from cognitive behavioral therapy to police witness interview training. Kim Scott's Radical Candor provides the philosophical backbone: care personally AND challenge directly. Most people do one or the other. The protocol demands both in the same conversation.

Related Protocols

• The Co-Regulation Protocol — When the feedback conversation triggers a strong emotional response in either party, co-regulation tools keep both people resourceful enough to finish.
• The Location of Leadership (The Line) — How to check whether you're operating from openness or defensiveness before you walk into the room. If you're below the line, the feedback will land as attack regardless of your words.
• The Radical Calibration Protocol — The operating system for honest self-assessment. Pairs with this protocol as the internal work that makes external feedback credible.