The Five Conditions of
Honest Feedback
Five self-paced modules, one condition per module, built on the Feedback Operating System™ from Honest by Design. Tools you can use in your next conversation.
No spam. Unsubscribe anytime. Your info is used only to track course enrollment.
The Five Conditions of
Honest Feedback
Five modules. One condition per module. The tools from Honest by Design, ready for your next conversation.
Welcome to the Course
Most organizations don't lack feedback activity. They lack a system where feedback is honest. The conversations that would fix performance, keep good people, and speed up decisions aren't happening. Not because leaders don't care, but because nobody built the conditions that make honest feedback safe, clear, and normal.
The Feedback Operating System™ names five conditions. They're the same in every organization; how you express them is unique to yours. They're also sequential and cumulative: skip one and the whole system weakens. This course gives you one condition per module, with the tools from the book you can use immediately.
What You'll Learn
Trust: Earn It Before You Need It
The four Trust Accelerators, the first-feedback challenge, and the Trust Audit.
Clarity: Know What You're Actually Saying
Three types of feedback, observation vs. interpretation, SBI+, the two-sentence test, and the feedback prep sheet.
Delivery: Say It So They Can Hear It
The 48-hour rule, setting and medium, the empathy calibration, and the five-minute conversation script.
Reception: Receive It Like a Pro
The three triggers, active listening, the constrained feedback request, and the post-feedback processing protocol.
Culture: Make Feedback Who You Are
The four operating rhythms, the leader's modeling role, the language diagnostic, and the Feedback Flywheel.
How It Works
Each module takes 15 to 20 minutes and ends with a field exercise to run with your team this week. Complete the modules in order; each builds on the one before it. When you finish, take the Feedback Culture Assessment to see where your organization stands across all five conditions.
Trust: Earn It Before You Need It
Without trust, feedback is filtered, distorted, or dismissed.
People don't resist feedback. They resist feedback from people they don't trust.
Why Trust Comes First
You can have the most specific, well-timed, perfectly delivered feedback in the world, and it will still be dismissed if the person receiving it doesn't trust you. Trust isn't a feeling. It's a judgment your team makes every day based on observable evidence. The question isn't whether you intend to be trustworthy. It's whether your behavior demonstrates it.
Three rules follow. You cannot skip trust. You cannot fake it. And you cannot assume it comes with your title, your tenure, or your good intentions. You build it, deliberately and specifically, before you need it to hold a hard truth.
The Four Trust Accelerators
Competence. People trust those who understand the work. Competence is demonstrated, not declared: intelligent questions, observations that show real understanding, insight grounded in experience.
Consistency. Trust is built through patterns, not moments. Give feedback regularly, not only when something goes wrong. Respond to feedback the same way every time. Apply the same standards to everyone, including yourself.
Care. The person believes you're invested in their success, personally and specifically. Care is demonstrated through attention: knowing what they're working toward, remembering what they told you, following up.
Candor. Honesty builds trust, not just the other way around. The people you trust most are the ones who tell you the truth. Their willingness to be uncomfortable for your growth is the strongest trust signal there is.
Inconsistency Creates Fear of Your Worst Moments
A CEO was surprised when his leadership team told him they were afraid of him. Most of the time he was approachable and fair. But every few weeks, under stress, he turned sharp and dismissive. It happened rarely enough that he didn't see the pattern. His team saw it clearly, and they organized their behavior around avoiding those moments. They withheld bad news and stopped challenging his ideas. Not because of who he was most of the time, but because of who he was some of the time.
The First-Feedback Challenge
The first piece of feedback you give in any relationship sets the template for every one that follows. If it's vague, harsh, public, or disconnected from any relationship, the other person learns that feedback from you is something to defend against. So don't wait for something to go wrong. Make your first feedback conversation a genuine acknowledgment of something the person does well. It builds trust and establishes that feedback is a normal part of how you work together.
The Trust Audit
Before you give feedback to anyone on your team, take five minutes and answer four questions about that relationship:
Competence: Does this person believe I understand their work well enough to give relevant feedback? When did I last demonstrate it?
Consistency: Have I been predictable in how I give feedback, how I respond to theirs, and how I follow through?
Care: Does this person believe I'm personally invested in their success? When did I last ask about their goals as a real conversation, not a checklist item?
Candor: Have I been honest with this person, or have I been hedging, sugarcoating, or avoiding?
If you find a gap, address it before your next feedback conversation. Feedback delivered into a trust gap doesn't land.
Run the Trust Audit for every person who reports to you. Score each accelerator 1 to 5 from their perspective, not yours. Find your lowest score. Take one specific action this week to close that gap with that person.
Clarity: Know What You're Actually Saying
Many leaders mistake vagueness for kindness. Unclear feedback is unkind.
If you can't write your feedback down in two sentences, you're not ready to say it.
Three Types of Feedback
Before any conversation, know which of three things you're doing. Appreciation reinforces what's working; it answers what should I keep doing? Coaching builds capability; it answers how do I get better? Evaluation tells someone where they stand against a known standard; it answers where do I stand?
Mixing them in one sitting is one of the most common errors leaders make. A manager opens with praise, shifts to development, then drops "we'll need to see improvement before we discuss a promotion." The employee's brain scrambles to find the real message, the coaching is lost, and the praise feels like a setup. The fix: separate conversations for separate types. Ask yourself, am I appreciating, coaching, or evaluating? If you're not sure, you're not ready.
Observation vs. Interpretation
An observation is a fact: something that happened, was said, or can be measured. An interpretation is the story you attached to it. "You arrived fifteen minutes late to the client meeting" is an observation. "You don't respect the client's time" is an interpretation. Interpretation-based feedback feels like a character judgment, so the conversation derails into a debate about motive instead of the behavior that needs to change.
A useful test: if someone could watch a video of the behavior and confirm what you're describing, it's an observation. If they'd need to read the person's mind, it's an interpretation. Lead with the observation.
The SBI+ Model
Built on the Center for Creative Leadership's SBI model, with a "+" added so the conversation ends on what should happen next.
Situation: the specific context. "In Tuesday's leadership meeting . . ." not "You always . . ."
Behavior: what you observed. ". . . you interrupted Diane twice while she was presenting the quarterly results . . ." not ". . . you were disrespectful."
Impact: the effect. ". . . which caused her to lose her train of thought, and two other team members disengaged."
+ Forward path: what right looks like. "In future meetings, hold your questions until the presenter finishes. If something is urgent, write it down and raise it in the discussion period."
Clear, specific, actionable, and about thirty seconds to deliver.
The Two-Sentence Litmus Test
Sentence one describes the observation and its impact. Sentence two describes the forward path. Compressing your message forces clarity: it strips out the hedging, the qualifiers, and the tangents, and makes you choose the one thing that matters most.
Write your two sentences down. The gap between what's clear in your head and what comes out of your mouth is the most preventable failure in any feedback system, and writing closes it. If the moment is emotionally charged, write the sentences while the observation is fresh, then reread them the next morning. The emotion drains out and the forward path sharpens.
The Feedback Prep Sheet
Five minutes, in writing, before any significant feedback conversation:
1. What type of feedback am I giving? (Appreciation, coaching, or evaluation?)
2. What specific behavior or outcome am I addressing? (Observation, not interpretation.)
3. What was the impact? (On me, the team, the project, the client, the organization?)
4. What is the forward path? (Specifically, what do I want to see?)
5. Can I write this in two sentences? (If not, sharpen further.)
6. What might the recipient hear differently from what I intend? (Where could this be misread?)
It's not a script. Don't read from it. Its job is to make sure the clarity is already there when you speak.
Pick one piece of feedback you need to give this week. Complete the prep sheet. Write your two sentences. Compare them to what you would have said off the cuff. Keep the sheet; you'll use it in Module 3.
Delivery: Say It So They Can Hear It
Timing, setting, tone, and sequencing decide whether the message lands or wounds.
The best feedback in the world is worthless if the other person can't hear it.
The 48-Hour Rule
Feedback is perishable. Delivered fresh, it's relevant and specific. Delivered months later, it's archaeology: the person can barely remember the situation and wonders why you sat on it. Whenever possible, deliver feedback within forty-eight hours of the behavior. That's long enough for your emotions to settle and short enough to keep the conversation concrete.
Two exceptions. Don't deliver in the heat of the moment; wait hours, not weeks, and write your two sentences while you cool down. And appreciation can be immediate. There is almost no scenario where timely, specific positive feedback backfires, and it costs nothing.
Setting and Medium
Praise in public, correct in private. It's one of the oldest rules in leadership and one of the most violated. When other people are present, the recipient stops processing the feedback and starts managing how they appear. Corrective feedback is one-on-one, behind a closed door, ideally in a neutral setting: a walk, a coffee, chairs side by side rather than across your desk.
For anything sensitive, use the richest medium available. In person first, then video, then phone. Written channels (email, text, Slack) are the worst medium for corrective feedback: no tone, no ability to respond to the reaction, and permanent enough to be reread and re-wounded. The exception is appreciation, which can be even more powerful in writing.
The Empathy Calibration
Tone is a dial that runs from very soft to very direct, adjusted for the person, the situation, and the stakes. Too soft and the message gets lost in qualifiers. Too hard and the person's brain shifts from learning to threat. The message doesn't change; the delivery adapts. Three steps to calibrate:
Start with acknowledgment. A sincere recognition of a strength or recent contribution. Not a feedback sandwich, which people see through and resent.
Deliver the core message clearly. Use SBI+. Be specific and direct. This is where most leaders lose their nerve and start softening. Trust your preparation.
Invite their perspective. "How do you see this?" It turns a monologue into a dialogue and may surface context you didn't have.
The Five-Minute Feedback Conversation
Part 1: Open (30 seconds). Set the context so they can orient: "I wanted to talk with you about the Henderson project timeline. Is now a good time?" If not, schedule a specific time within forty-eight hours.
Part 2: Deliver (2 to 3 minutes). Situation, behavior, impact, forward path. Don't rush, don't over-explain. Then pause: "How do you see this?"
Part 3: Close (1 to 2 minutes). Confirm the forward path. Summarize what was agreed. Ask: "Is there anything I can do to support you on this?" End in partnership, not authority.
Five to seven minutes. The conversations leaders lose sleep over take five to seven minutes when they're prepared and delivered well.
Take the prep sheet from Module 2. Rehearse the conversation using the three-part script. Have it within forty-eight hours, in private, in the richest medium you can. Afterward, write down how long it actually took and what you'd do differently.
Reception: Receive It Like a Pro
A leader who doesn't hear the truth is making decisions in the dark.
Your ability to receive feedback determines how much truth flows toward you.
The Leader's Blind Spot
The higher you go, the less unsolicited feedback you receive. People filter, soften, and omit, not because they don't see the truth but because they've learned it isn't safe to share. A leader who reacts defensively, even once, trains the whole team to stop. Your reception skill is the valve that controls the flow.
The Three Triggers
Drawn from Stone and Heen's Thanks for the Feedback. Most people are especially susceptible to one or two.
Truth triggers. The content feels wrong or unfair. "They don't have the full picture." The danger is that you dismiss the message before you've looked for the grain of truth inside an imperfect delivery.
Relationship triggers. Your reaction is about who is giving the feedback, not what they're saying. "Who are you to tell me this?" You've disqualified the source.
Identity triggers. The feedback threatens your sense of who you are. "If this is true, I'm not the leader I thought I was." A note about a missed deadline becomes an existential crisis.
Knowing your trigger doesn't eliminate it. It gives you a split second of awareness between the trigger and your response, and in that split second you can choose differently.
Listen Like You Mean It
Most people think they're listening when they're preparing their rebuttal. Four disciplines: stop formulating your response and sit in the silence after they finish; resist the explanation reflex, because leading with context sounds like defending; ask clarifying questions ("Can you give me a specific example?" "What would it look like if I did this well?"); and thank them, even when it's painful and even when you disagree. Thanking someone is not agreeing with them. It keeps the door open.
One CEO changed his leadership team's willingness to be honest with one habit: every time someone gave him feedback, he thanked them, wrote it in his notebook, and followed up within a week on what he was doing about it. He didn't act on all of it. But the consistent response made it safe.
The Constrained Feedback Request
"Do you have any feedback for me?" produces "You're doing great," because it gives no entry point for honesty. Ask this way instead:
Name what you're working on. "I'm working on being more concise in my communication . . ."
Narrow the scope. ". . . specifically in our team meetings."
Ask for both sides. "Can you give me one thing I do well in meetings and one thing I could do differently?"
Specific enough to answer, narrow enough not to feel like a trap, balanced enough to be safe.
The Post-Feedback Processing Protocol
Within forty-eight hours of any significant feedback, answer five questions in writing:
1. What is my emotional reaction, and which trigger is driving it?
2. Setting my reaction aside, what is the signal? What part, if I'm honest, has merit?
3. What context do I have that the giver might not? (This is where your explanation belongs: after processing, not during receiving.)
4. What, if anything, am I going to do differently? ("I'll try harder" is not a plan.)
5. How will I close the loop with the person who gave it? What and when will I tell them?
Ten minutes. It turns an emotional reaction into a deliberate response.
Make one constrained feedback request this week to a direct report or a peer. Listen. Thank them. Run the processing protocol on what you hear. Close the loop within a week.
Culture: Make Feedback Who You Are
The difference between a leader who gives good feedback and an organization that runs on it.
Feedback is not an event. It's an operating system.
From Skill to System
A company ran a two-day feedback workshop. For about three weeks, things were different: more one-on-ones, a few courageous conversations, SBI+ showing up in team discussions. Then it faded. The skills were real. The structure to hold them wasn't. The first four conditions are individual capabilities. Without rhythm, they decay, new hires never adopt them, and the system degrades.
The Four Operating Rhythms
Weekly one-on-ones. The single most important rhythm. Not a status update. Three questions: What's going well? What's not going well? What do you need from me? The third question invites upward feedback in a way that feels safe.
Team retrospectives. After every significant project: What worked? What didn't? What will we do differently? The leader goes first: "Here's what I could have done better."
Quarterly reviews. The pulse check on trajectory. Never any surprises; everything is a synthesis of the weekly conversations.
Annual strategic feedback. Peer, upward, and self-assessment tied to compensation and development. In a healthy culture it's the least important feedback event of the year, because everything in it has already been discussed.
Don't launch all four at once. Start with weekly one-on-ones. Once they're normal, usually sixty to ninety days, add retrospectives, then quarterly reviews. The annual process comes last.
You Can't Delegate the Culture
Culture isn't declared; it's demonstrated, and the cascade from the top is remarkably reliable in both directions. Four things the leader does personally: ask for feedback publicly ("What am I missing in this strategy?"); respond to it visibly ("Several of you said our meetings run long. Here's what's changing."); give feedback in real time, within forty-eight hours, not saved for a scheduled meeting; and acknowledge your own mistakes out loud. Vulnerability from the top creates permission at every level.
The Language Diagnostic
You can hear a feedback culture. Listen this week.
When a leader hears "somebody should tell him" and answers "why don't you?", that's the fifth condition in action.
The Feedback Flywheel
When all five conditions are in place and the culture sustains them, feedback becomes self-reinforcing. Each good feedback interaction makes the next one easier. Trust deepens, skills sharpen, norms solidify, and the flywheel accelerates on its own momentum.
The reverse is equally true and far more common. Each avoided conversation makes the next one harder, and reversing that momentum takes far more energy than maintaining it would have. Your goal isn't perfect feedback in every conversation. It's a flywheel that spins without you pushing.
What's Next
You've covered all five conditions. Two things to do now. First, measure where your organization actually stands. Second, put the system to work over ninety days with the full playbook in the book.
Honest by Design
The complete guide to the Feedback Operating System™, with every tool from this course, the stories behind them, and a 90-day playbook for deploying the system in your company.
Join the Book Waitlist →Take the Feedback Culture Assessment to see where your organization stands across all five conditions. Then book a conversation with Drew about deploying the FOS in your organization.