The Founder's Guide to Giving Feedback That Lands

There are a few reasons founders struggle with feedback:

• You don't have much practice receiving it. You've been right more often than wrong, or at least that's what the market told you. When someone questions your instinct, your brain interprets it as "they don't get it" instead of "they have useful information."
• You're under time pressure. Someone made a mistake and you need them to not make it again immediately. So you point it out sharply. The time you save being blunt costs you twice over in lost trust.
• You're scared. You're building something that might fail. When someone drops the ball, your fear comes out as criticism. You criticize harder because you think it will change behavior. It doesn't. It just makes people more nervous.
• You confuse feedback with evaluation. You think feedback is about ranking performance. But feedback is about helping someone improve right now. Those are different things.
• You assume everyone processes information like you do. You want the blunt truth. So you give blunt feedback assuming that's what everyone wants. But many people need context first. They need to understand why before they hear the what.

There's a simple structure that makes feedback land better. Situation. Behavior. Impact.

Step 1: Situation

Establish the specific moment. Not in a judgmental way. Just the facts.

• "In the meeting with the client yesterday."
• "When we reviewed the code this morning."
• "In the Slack thread about the timeline."

This anchors the feedback so there's no confusion about what you're referencing.

Step 2: Behavior

Describe what you observed. Again, just the facts.

• "You pushed back on the timeline estimate without asking why we came to that estimate."
• "You shipped the feature without testing on the staging environment."
• "You told the client we could build it in two weeks when our capacity is one week."

Precision matters here. Not "you're careless" (criticism). Not "you always shoot from the hip" (pattern judgment). Specific behavior in that moment.

Step 3: Impact

What happened as a result?

• "The client felt rushed and didn't trust our estimate."
• "We caught the bug in production instead of staging, which cost us four hours and embarrassed us."
• "Now the client expects something we might not be able to deliver, and we'll either overwork or disappoint them."

Step 4: The Ask

Then you say what you'd like to see instead:

• "Next time, ask me about the estimate before suggesting a different one."
• "Next time, check staging is up before assuming it's broken."
• "Next time, loop me in before committing to timelines with clients."

The structure is powerful because it's objective. You're not saying the person is bad. You're saying "here's what happened and here's what it caused." The person can process that without defensiveness.

This is the thing founders miss. You think feedback is about correcting mistakes. It's 50% correcting mistakes and 50% reinforcing what's working.

People need to know what to repeat. If someone does something right and you never mention it, they don't know whether you noticed or whether it matters. Then they might stop doing it.

Examples of Good Positive Feedback

• "You asked great questions in that design review and it led to a better outcome. I noticed you did that yesterday too. Keep doing that."
• "Your code is clean. It's easy to understand and modify. That matters."
• "The way you handled that customer complaint turned a churning user into an advocate. That's exactly the kind of ownership I want to see."

Short. Direct. Specific. People feel that and they repeat it.

The 5:1 Ratio

Research says people need about five positive feedback moments for every one critical feedback moment to feel supported. Most founders operate at the opposite ratio. They point out problems constantly and say nothing when things work.

If you want your team to trust your feedback, you need to give five times as much positive feedback as critical feedback. That might feel like coddling. It's not. It's how the human brain actually works.

If you want people to give you feedback, you need to receive it well.

Someone gives you feedback about how you handled something. Your instinct is to explain why they're wrong. But that shuts down the conversation. If you explain why you're right every time someone gives you feedback, they'll stop giving it. And then you don't improve.

The Magic Move

When someone gives you feedback: "That's useful. I hadn't thought about it that way. Let me think about that."

Then you actually think about it. Sometimes you change. Sometimes you don't. But you take it seriously.

When you model receiving feedback well, your team learns to give it. They see that you don't get defensive. They see that you change sometimes. They see that feedback is safe. Then they give each other feedback too.