There’s a moment I think about often. Early in running PipelineRoad, I reviewed a landing page one of our team members had written for a client. It wasn’t good. The messaging was off, the structure was confused, and the CTA made no sense for the buyer persona. I sat on it for three days, trying to figure out how to say something without demoralizing them.
When I finally gave feedback, I said something like: “This is a great start, just needs some tweaks. Maybe tighten up the messaging a bit?”
They made a few cosmetic changes and sent it back. Still not good. I ended up rewriting it myself at midnight, which helped nobody — not the team member, not me, not the process.
That experience taught me something I now consider fundamental: kind feedback and honest feedback are not the same thing, and conflating the two helps no one.
The Vagueness Problem
The most common failure mode of feedback is vagueness. “This could be stronger.” “The design feels off.” “I think we need to take this in a different direction.” These statements feel like feedback because they express dissatisfaction. But they contain almost no usable information.
When I tell someone their copy “could be stronger,” what have I actually communicated? That I don’t like it. That’s it. I haven’t told them what specifically isn’t working, why it isn’t working, or what good would look like. I’ve transferred my dissatisfaction without any of the thinking behind it.
Good feedback is specific to the point of being almost surgical. Not “the messaging is off” but “the opening paragraph assumes the reader already knows they have a problem, but our research says most of this audience doesn’t realize their current process is broken. We need to start with the symptom, not the solution.”
That kind of specificity requires more work from the person giving feedback. You have to actually diagnose the issue, not just register that something feels wrong. But that work is the whole point. If you haven’t done the thinking, you’re not giving feedback — you’re giving a reaction.
The Timing Problem
The second failure mode is delay. Feedback that arrives three weeks after the work was done is archaeology, not coaching. The person has already moved on mentally. They can barely remember the decisions they made or why. Your observations, however accurate, land in a vacuum.
I now operate on a simple rule: feedback within twenty-four hours or it’s probably not worth giving. This doesn’t mean a formal review within a day — it might just be a quick voice note saying “Hey, I looked at the email sequence. The first two emails are exactly right — punchy, specific, good pain-point framing. Email three loses the thread. Let’s talk about it in our 1:1.”
That takes sixty seconds to record. It preserves the context. And it tells the person exactly where they stand before they’ve had time to assume everything was perfect.
The Softness Problem
This is the one that trips up well-intentioned leaders the most. The instinct to cushion feedback until it’s barely recognizable. The “feedback sandwich” where you wedge a criticism between two compliments, ensuring that the actual message is lost in a pile of reassurance.
I understand the impulse. Nobody wants to be the person who makes someone feel bad about their work. But consider what happens when you consistently soften feedback to the point of opacity: people don’t improve. They keep making the same mistakes. And then, months later, when the accumulated frustration finally boils over — or when a performance review forces a reckoning — the honest feedback arrives all at once, and it feels like an ambush.
“You never told me this was a problem” is a devastating sentence to hear from a team member. And if you’ve been giving soft, vague, indirect feedback for months, they’re right.
What It Actually Sounds Like
The best feedback I’ve ever received was from a client early in my career who told me: “Alexander, the strategy deck is well-researched, but you’re burying the recommendation on slide fourteen. I should know what you think I should do by slide three. Right now this reads like a graduate thesis, not a decision brief.”
That feedback was specific (the recommendation is buried), contextual (this is a decision brief, not a thesis), actionable (move the recommendation up), and direct (no hedging, no sandwiching). It took him about fifteen seconds to say it. I have never made that mistake again.
Here’s the pattern I try to follow now, and that I coach my team to use with each other:
Observation. What specifically did you notice? Not an interpretation or a judgment — just the thing itself. “The blog post opens with three paragraphs of background before reaching the main argument.”
Impact. Why does it matter? “Most readers will bounce before they reach the point. We lose them in the preamble.”
Direction. What would better look like? “Lead with the argument. Move the background to the middle, where it becomes evidence rather than preamble.”
That’s it. Observation, impact, direction. No compliment sandwich. No “but overall great job!” at the end. Just clarity.
The Emotional Layer
None of this means feedback should be delivered coldly or without empathy. Directness and warmth are not opposites — in fact, the most effective feedback I’ve ever given combined absolute clarity with genuine care.
The trick is in the framing. When I give difficult feedback, I try to make clear that I’m invested in the person’s growth, not just the quality of the output. “I’m telling you this because I’ve seen what you’re capable of, and this piece isn’t there yet” hits differently than “this needs work.”
People can absorb hard truths from someone they trust. The relationship is the delivery mechanism. This is why 1:1s matter so much — they build the relational foundation that makes honest feedback possible. If the first real conversation you have with someone is a critique of their work, it won’t land well regardless of how well you frame it.
Building a Feedback Culture
The ultimate goal isn’t to become a better feedback-giver yourself. It’s to build a team where everyone gives each other clear, specific, timely feedback as a matter of course. Where “that doesn’t work because…” is a normal sentence, not a confrontational one.
At PipelineRoad, we’re not fully there yet. But we’re closer than we were a year ago, and the shift started when Bruno and I began modeling the behavior we wanted to see. We give each other direct feedback in front of the team. We thank people publicly when they push back on our ideas. We treat “I disagree” as a contribution, not a challenge.
The result is a team that catches mistakes faster, iterates more efficiently, and wastes less time on polite ambiguity. It’s not always comfortable. But comfort was never the point. Growth was.