Most founders are bad at giving feedback.
Not because they don’t care. Because they were never taught how. They either avoid the conversation until the problem is too big to ignore, or they give feedback in a way that feels like criticism and produces defensiveness rather than change.
Here’s the framework that changes both.
Why Most Feedback Doesn’t Work
Feedback fails for three reasons.
It’s too vague to act on. “You need to communicate better” is not feedback. It’s a judgment. The person receiving it doesn’t know what to change because they don’t know specifically what’s wrong.
It’s delivered too late. Feedback six weeks after an event asks someone to recall context they no longer have. The closer the feedback is to the behaviour, the more useful it is.
It conflates the person with the behaviour. “You’re disorganised” is a character assessment. “The project plan didn’t have clear owners or deadlines” is an observation about a specific piece of work. The first produces shame. The second produces a plan.
The Framework That Works
Every piece of effective feedback has four components:
Observation: What specifically happened. Not your interpretation — the observable fact. “In yesterday’s client call, you interrupted the client three times before they finished their question.”
Impact: What effect it had. “The client looked frustrated, and I noticed they stopped asking questions after the third interruption.”
Question: What was going on for them. “What was happening for you in that moment?” This is the part most people skip. It’s also the part that makes the feedback a conversation rather than a verdict.
Request: What specifically you’d like to be different. “In the next client call, I’d like you to let the client finish their question completely before responding. Can you do that?”
This is the SBI framework — Situation, Behaviour, Impact — with a question and request added. It takes longer than “you need to communicate better.” It works.
How to Prepare for Difficult Feedback Conversations
Use this prompt before any difficult feedback conversation:
“I need to give feedback to [describe the person and their role] about [describe the issue]. The specific behaviour I observed was [what happened]. The impact was [what effect it had]. I want them to [specific change you’re asking for]. Help me: (1) Open the conversation in a way that doesn’t put them on the defensive, (2) Deliver the feedback using specific observable language rather than character judgments, (3) Anticipate how they might respond and how to handle defensiveness, (4) Close with a clear agreement on what changes.”
The Feedback You’re Avoiding
Every founder has at least one piece of feedback they’re avoiding giving. Usually because the stakes feel high — it’s a critical team member, or the relationship is important, or the conversation feels too hard.
The cost of not giving it is almost always higher than the cost of giving it poorly.
The feedback you avoid giving doesn’t go away. It compounds. The person continues the behaviour, the problem grows, and when you finally have the conversation it’s six months later than it needed to be. The relationship is usually harder to repair at that point than if you’d had the conversation when the problem was small.
One rule that helps: give feedback within 48 hours of the event that prompted it. Not 6 weeks later. Not in the annual review. Within 48 hours.
Getting Feedback as a Founder
The other side of this — feedback you need to receive — is harder.
Most founders get very little honest feedback because the power dynamic makes it difficult for people to tell them what’s actually true. The team learns what the founder wants to hear and delivers that.
Break this pattern deliberately. After every significant meeting, ask one person who was in the room: “What did I do in that meeting that made it harder for others to contribute?” Not “how did I do?” — that question produces “great!” every time.
The specific question produces the specific answer you need.
Get the Full Founder Prompt Library
50 prompts for leadership, decision making, hiring, and ops — free download.