Leadership Lessons: Constructive Feedback

Everyone knows that constructive feedback is important. But what is key, is doing it well under the constraints of startup reality: limited time, high stress, and relationships you can’t afford to damage.

Bad feedback either goes unsaid (the problem festers) or goes badly (the relationship suffers). Neither serves your team or your product.

What We’ll Cover

This piece explores how to build feedback skills that work in resource-constrained environments. We’ll look at laying foundations when you’re small, scaling feedback practices as you grow, and navigating the inevitable trade-offs between speed and thoroughness.

Building Early Foundations

What to Prioritise

When you’re small, formal feedback systems feel like overhead. You don’t need quarterly reviews or 360 assessments, you need teammates who can have honest conversations with each other.

The foundation is normalising directness. In early-stage teams, feedback often doesn’t happen because everyone’s too nice, too busy, or too worried about damaging fragile team dynamics. This politeness creates debt that compounds.

Start by making feedback expected, not exceptional. When someone does good work, say so specifically. When something could be better, say that too. The more ordinary feedback becomes, the less charged any individual piece of feedback feels.

Model receiving feedback well. When someone gives you feedback, thank them genuinely, engage with the substance, and visibly act on it when appropriate. Your response to feedback teaches others whether giving it is safe.

Establish that feedback is about work, not worth. The goal is making the work better, not judging people’s value. This framing makes both giving and receiving feedback less threatening.

Quick Wins

Same-day feedback: Address issues the same day they happen. Delayed feedback loses context and accumulates emotional charge. The quicker you address something, the more matter-of-fact the conversation can be.

One-on-one rituals: Even informal weekly check-ins create space for feedback that doesn’t fit into Slack messages or standups. Guard these conversations—they’re where real issues surface.

Feedback starters: Some people freeze when trying to give feedback. Offer simple structures: “When X happened, I noticed Y, and I think Z would work better.” The structure reduces cognitive load and makes feedback more accessible.

“The startups I’ve seen handle feedback well made it boring. It was just part of how they worked, not a Big Conversation to be dreaded.”

Scaling for Growth

When to Formalise

As teams grow, informal feedback becomes insufficient. What worked with five people breaks down with fifteen. You need more structure, but not too much.

Signs you need more formalisation:

Feedback isn’t reaching people who need it
Managers are bottlenecks for all feedback
New hires don’t know what good looks like
Performance problems aren’t being addressed

When these appear, add structure incrementally. Don’t leap from nothing to a comprehensive performance management system. Start with regular 1:1s with feedback components, then add peer feedback, then add more formal review cycles as needed.

The key is adding structure that actually serves feedback, not structure that creates busy work. Every process should answer: “How does this help feedback happen that wouldn’t happen otherwise?”

Team Evolution

As teams grow, feedback patterns need to evolve:

From founder-to-everyone to manager-to-team: Early on, founders give most feedback directly. This doesn’t scale. Build managers who can give effective feedback so the founders aren’t bottlenecks.

From ad-hoc to rhythmic: Some feedback should happen in regular rhythms (weekly 1:1s, quarterly reviews) so important conversations don’t slip.

From purely informal to partially documented: At some scale, you need records of feedback conversations. Not to create bureaucracy, but to track patterns and ensure accountability.

From individual to multi-directional: Add peer feedback and upward feedback as you grow. Managers need feedback too, and they often don’t get it.

Throughout these evolutions, protect what made feedback work when you were small: directness, timeliness, and focus on the work rather than the person.

The Startup Reality

Resource Constraints

Startups don’t have time for lengthy feedback processes. The 45-minute feedback conversation that HR recommends isn’t realistic when you’re sprinting to hit milestones.

Adapt to your constraints:

Micro-feedback over macro-sessions: Many small pieces of feedback work better than occasional comprehensive reviews. A two-minute conversation right after something happens beats a 30-minute scheduled discussion next week.

Written async feedback: Not everything needs to be a conversation. Sometimes a thoughtful Slack message or document comment is more efficient and equally effective.

Focus on what matters most: You can’t give feedback on everything. Prioritise feedback that affects outcomes significantly. Minor style preferences can wait.

Leverage natural conversations: Feedback often fits naturally into existing discussions—project debriefs, design reviews, code reviews. Build feedback into these rather than creating separate feedback events.

Speed vs. Quality Tradeoffs

Sometimes you have to choose between giving feedback well and giving it at all. When time is extremely limited, imperfect feedback is usually better than none.

That said, some shortcuts create more problems than they solve:

Don’t skip empathy: Even in quick feedback, acknowledge the person’s perspective. “I know you were under pressure when…” takes five seconds and dramatically improves reception.

Don’t be vague to save time: Vague feedback wastes more time than it saves because the recipient doesn’t know what to change. Be specific even if brief.

Don’t give feedback publicly to save scheduling time: Public feedback—especially critical feedback—creates unnecessary defensiveness and embarrassment. Take the 30 seconds to pull someone aside.

Don’t rely solely on written feedback for sensitive topics: Text strips context and tone. If the feedback is significant or sensitive, make time for a real conversation.

Key Takeaways

Normalise directness early, feedback should be ordinary, not exceptional
Model receiving feedback well to show others it’s safe to give it
Add structure incrementally as you grow, only what actually serves feedback
Adapt feedback practices to startup constraints with micro-feedback and async methods
Never skip empathy or specificity, even when you’re short on time

Resources for Deeper Learning

The best way to improve at feedback is practice with reflection. After feedback conversations, ask yourself: Did that land? What could I do differently next time?

Build a trusted peer relationship where you can give each other feedback on giving feedback. This meta-practice accelerates improvement dramatically.

And remember: giving good feedback is a skill that compounds. The investment you make now pays dividends for your entire career.

Have questions or thoughts? Get in touch - I’d love to hear from you!