Giving Feedback (Performance & Coaching)

The manager-employee practice of delivering, structuring, and inviting feedback — critical and positive — to correct behavior, build skill, and sustain motivation without triggering defensiveness.

Also known as: critical feedback, constructive feedback, feedback delivery, negative feedback, performance feedback, two-way feedback conversation, feedback-seeking culture

How authors use it

Oldest first (extraction date when no publication date is known).

Documents (7)

• Maya Knight's Post Maya Knight · 2026-09-23 Reader 🖥️
  Psychological safety, properly understood per Edmondson, is about enabling interpersonal risk-taking — disagreement, challenge, honesty — not about comfort; "comfortable culture" is often avoidance masquerading as respect, and it undermines team performance.
• Anders Aukland's Post Anders Aukland · 2026-08-19 Reader 🖥️
  The best teams win not by being nicest but by being most honest with each other immediately and without softening — and most Norwegian workplaces underperform not from too much conflict but from too much silence.
• Is Your Organizational Culture Too Nice? Ron Ashkenas, Gali Cooks · 2026-08-19 source ↗ Reader 🖥️
  Organizational cultures of "niceness" — which prioritize harmony, comfort and consensus over candor, accountability and results — measurably compromise performance, and leaders can reverse this by modeling peer candor at the senior-team level (starting with the CEO), demonstrating the results of rigor through data-backed pilots, and redesigning operational review and governance meetings so they require substantive debate rather than ratify decisions as a fait accompli.
• Amy Gibson's Post Amy Gibson · 2026-08-02 Reader 🖥️
  What determines whether a meeting works is not its agenda, room, technology, or timing, but what people walk away with — feeling heard, clear on priorities, energized — and Gibson proposes five distinct, differently-cadenced meeting types (weekly sync, monthly 1:1, monthly all-hands, quarterly strategy session, annual culture touchpoint) as the mechanism for reliably producing that outcome.
• Why Mentoring Matters More in the AI Era Marlo Lyons · 2026-07-24 Reader 🖥️
  Because AI is automating the routine work that once built professional judgment and pattern recognition through repetition, organizations must replace that lost experiential foundation with deliberately engineered, intentional mentoring — not the ad hoc, exposure-dependent mentoring models that assumed hands-on learning was already happening.
• Our Favorite Management Tips on Giving Feedback HBR Editors · 2026-05-21 Reader 🖥️
  Feedback works when it separates the person from the behavior and is delivered inside a relationship the recipient already trusts: define what feedback must never do (attack character), structure it around a specific behavior plus its impact plus a next step, invite it proactively rather than only issuing it top-down, calibrate its intensity and timing to the relationship's maturity and the issue's severity, and treat it as a two-way, purpose-conferring conversation rather than a one-way verdict. The eight tips are different tactical answers to one underlying claim: feedback's effectiveness is gated by psychological safety and behavioral specificity, not by the giver's honesty or courage alone.
• How to Build a Superteam That Keeps Getting Better Harvard Business Review · 2026-05-01 source ↗ Reader 🖥️
  In periods of rapid change, teams win not because they start with the best plans or the most talent but because their leaders build a continuous-improvement culture — one that makes experimentation, curiosity, early problem-surfacing, hands-on involvement, non-threatening feedback, and growth-oriented investment in people the daily default — so the team's rate of learning, not its starting position, determines whether it becomes a 'superteam.'

Propositions touching this concept (7)

By publication month, oldest first (extraction month when no publication date is known).

2026-05

• explicitdevelopedNegative feedback is not personal; treat it as a gift because it improves the idea.
  Getting Buy-In for Your Next Big Idea · p15
• explicitestablishedCritical feedback helps people grow only when explicit guardrails (never shame, humiliate, or attack character), a three-part behavior/why/next-step structure, a deliberate pause before responding, and a fast repair when it lands badly are all present — any one missing turns feedback into an attack that shuts the recipient down.
  Our Favorite Management Tips on Giving Feedback · p1
• explicitWithholding constructive feedback doesn't just fail to improve performance — it actively deprives employees of a sense of purpose, because meaning at work comes from visible mastery, visible impact, and feeling seen, all of which depend on the manager actually giving feedback.
  Our Favorite Management Tips on Giving Feedback · p5
• explicitPerformance-review harm often comes not from the criticism itself but from three compounding factors: escalating minor issues that didn't need formal feedback, tying critique directly to compensation (which triggers defensiveness), and leaving evaluation criteria unexplained (which reads as unfairness) — so effective negative feedback requires proportionality, decoupling from pay, and transparency about standards.
  Our Favorite Management Tips on Giving Feedback · p7

2026-07

• explicitThe campaign's actual outcome was mixed but net favorable: strong engagement and appreciation for the technology, some negative reaction, but the negative feedback tracked general public anxiety/backlash about AI rather than a museum- or Harvard-specific reputational failure.
  How a Museum Marketing Team Used AI to Bring People Closer to Art · p9
• explicitcontestedHuman brains stay most valuable in taste, judgment, vision and strategy: you don't ask an AI to originate a strategy (only to give feedback within bounds you set), and directing AI 'looks more like management' — defining what success looks like, choosing how prescriptive to be, and giving feedback along the way.
  Adam Mosseri: AI is a tailwind for authenticity · p16

2026-08

• explicitcontestedAdding a second agent as an independent reviewer -- examining the specification, giving feedback, and running additional checks including adversarial probes -- can further reduce human intervention and raise code quality beyond what a single looping agent achieves.
  Zero to Agent in 30 Minutes: From Prompting to Loop Engineering with Ofer Mendelevitch · p3

Open gaps (16)

• illogicalThe Compounding Test's own worked example opposes 'giving a high-potential employee feedback every time they make a mistake' to 'continuous mentoring and development,' as if the two were alternatives — but frequent, timely feedback is one recognized mechanism of ongoing mentoring, not necessarily its opposite; the example doesn't establish what distinguishes reactive feedback from genuine development beyond frequency or intent, which it never specifies.
  3 Questions to Pressure-Test Your Priorities — read next: Read against the corpus's giving-feedback and coaching-styles material on what separates corrective feedback from developmental coaching.
• incompleteNo context is given on team size, function (e.g. engineering vs. sales), growth stage, or remote/hybrid setup; the specific cadences and durations (30 min weekly, 45-60 min monthly 1:1s, quarterly 2-3hr sessions) are presented as universal defaults with no acknowledgment that they'd need adaptation for, say, a large distributed engineering org.
  Amy Gibson's Post — read next: Compare against context-sensitive team-design frameworks (e.g. your own pattern language on cross-disciplinary team spaces) that make cadence and structure conditional on team size, distribution, and work type rather than fixed.
• illogicalThe post explicitly denies that agenda, room, tech, or timing matter ("It's not the agenda... Not the room. Not the tech, or even perfect timing"), then immediately prescribes agenda-like structural mechanics for every type (30-minute cap, RAG status colors, 24-hour follow-up SLA, employee-set agenda, fixed durations) — undercutting the opening claim that structure doesn't matter. The more defensible position — structure alone is insufficient, but still matters — is collapsed into an either/or.
  Amy Gibson's Post — read next: Note the self-undermining move as a genre pattern in LinkedIn leadership content: a catchy "it's not X, it's Y" hook followed by content that is substantially about X.
• incompleteThe post closes with explicit LinkedIn engagement-bait ("If this resonates, repost for your network... Follow Amy Gibson for more leadership insights"), signaling the piece functions primarily as personal-brand content rather than a rigorously developed framework — consistent with the taxonomy's genericness (weekly sync / 1:1 / all-hands / quarterly review / annual event maps closely to common existing practice rather than introducing a novel mechanism).
  Amy Gibson's Post — read next: No further reading needed on this point; treat the piece as low-density input best skimmed rather than studied.
• illogicalThe post conflates two different phenomena: 'kritikkverdige forhold' (reprehensible/reportable conditions — closer to whistleblowing territory, e.g. safety or ethics violations) in the cited Ledelsesbarometer statistic, with routine peer performance feedback in the anecdote and thesis ('you're falling behind'). The 39%-fear-of-consequences and 33%-disloyalty findings describe barriers to reporting misconduct upward under real power asymmetry and retaliation risk — a materially different risk calculus than a peer bluntly critiquing an equal's performance during physical training with no formal hierarchy between them. Treating both as the same 'silence problem' may overstate how directly the Helvetesuka lesson transfers to the survey's actual finding.
  Anders Aukland's Post — read next: Read alongside whistleblowing and psychological-safety literature that separates upward disclosure of misconduct (protected by policy, law, anonymity) from lateral peer-to-peer candor (protected by team norms and trust) — e.g. Amy Edmondson's psychological safety research, which explicitly distinguishes speaking up about errors/concerns from routine task feedback.
• incompleteThe post asserts that 'how it's said' and 'what happens in the minutes afterward' are what separate a good hard environment from a bad one ('dette er viktig') but never explains what good delivery or good repair actually consists of — it's flagged as the crux and then left unaddressed, doubling as a hook for his paid-speaking pitch rather than a resolved point.
  Anders Aukland's Post — read next: Read HBR's management-tips article on giving feedback (extract-hbr-management-tips-giving-feedback), which specifies concrete guardrails — no shaming, a behavior/why/next-step structure, a deliberate pause, and fast repair when feedback lands badly — for exactly this gap.
• incompleteNo tip in the piece cites primary data, sample sizes, or effect sizes for its central claim, even where a named source is credited (e.g., Levitt et al. for midpoint timing, Wetzler for feedback-seeking culture). The reader is asked to trust the compiled prescription without being shown the evidence that presumably backs the original longer articles.
  Our Favorite Management Tips on Giving Feedback — read next: The full HBR source articles linked inline (Wetzler on feedback-seeking culture; Levitt et al. on early-positivity research; Hirsch on two-way feedback) for the underlying studies and their limitations.
• incompleteThe eight tips are never reconciled with each other where they could conflict: Tip 3 says withhold critique until midpoint; Tip 1's guardrails and Tip 7's conversational approach imply feedback can and should happen continuously and immediately when behavior needs correcting. A manager following the piece literally has no guidance on which tip governs an urgent, early-project problem.
  Our Favorite Management Tips on Giving Feedback — read next: Literature on feedback frequency and timing (e.g., continuous feedback vs. periodic review models) that would let a reader adjudicate when 'start with positivity, defer critique' should yield to 'address it now.'
• incompleteNone of the tips address feedback across power or identity asymmetries — feedback from a junior employee to a senior manager, cross-cultural feedback norms, or feedback where the recipient has structurally less power to push back or seek recourse if the giver's guardrails fail. The bias-auditing prescription in Tip 1 is the closest the piece comes, but it addresses giver bias, not the receiver's structural vulnerability.
  Our Favorite Management Tips on Giving Feedback — read next: Research on upward feedback, psychological safety across hierarchy, and cross-cultural management (e.g., Erin Meyer's work on feedback norms across cultures) would fill this.
• uninformedAs 'tip of the day' content compiled from separate prior articles, none of the eight tips engages with counter-evidence or failure modes of its own prescription — e.g., whether structured feedback templates can themselves feel bureaucratic and insincere, or whether a feedback-seeking culture can produce feedback fatigue or performative asking. The genre (curated positive digest) selects for confident, uncontested advice.
  Our Favorite Management Tips on Giving Feedback — read next: Critiques of over-formalized feedback culture and of performance-review theater in the broader management literature.
• incompleteThe article calls for protected mentor time and more senior-leader involvement in daily narrated teaching, but doesn't engage the corpus's contemporaneous finding that organizations are simultaneously flattening management layers and pushing more hands-on technical work onto senior/advanced individuals — exactly the population this article expects to have spare capacity to mentor. The prescription and the structural trend may be in tension.
  Why Mentoring Matters More in the AI Era — read next: extract-postman-engineering-leadership-report-2026 (management-layer flattening + rising hands-on work among advanced/senior staff) and extract-you-dont-get-to-create-anything-beck-shoup#g4 (the apprenticeship channel under high manager-to-report ratios).
• uninformedThe prescriptions (real-time narration before/after meetings, 15-to-30-minute as-you-work reviews) implicitly assume synchronous, often co-located or at least highly available working relationships. There is no engagement with how this translates to distributed, asynchronous, or cross-timezone teams, where spontaneous narration is much harder to arrange.
  Why Mentoring Matters More in the AI Era — read next: Remote-work and asynchronous-collaboration literature; any corpus material on distributed team practices.
• uninformedCitations are underspecified throughout: the Journal of Organizational Behavior study on manager involvement gives no sample size, effect size, or definition of 'manage from a distance'; the Frontiers in Psychology moonlighting study names a sample size (324) but no effect size or engagement instrument; every leader-behavior percentage (33%, 43%, 53%, 56%, 59%, 90%+) is reported without a confidence interval, base rate, or description of how 'average team' leaders were sampled.
  How to Build a Superteam That Keeps Getting Better — read next: The original Journal of Organizational Behavior and Frontiers in Psychology papers directly; Ron Friedman's book 'Superteams' (Simon & Schuster, 2026), from which this article is adapted, for full survey methodology.
• illogicalSurvivorship bias in case selection: every illustrative organization (Thunder, Meta, Netflix, Amazon, Spotify, LinkedIn, Microsoft, Airbnb, Adobe, Estée Lauder, HubSpot, Keap, Basecamp, Haberman) is a documented success story for the practice it illustrates. No case of a team that experimented boldly and failed, admitted uncertainty and lost credibility, or had a hands-on leader who tipped into micromanagement is discussed, so each practice's downside risk and failure rate are invisible by construction.
  How to Build a Superteam That Keeps Getting Better — read next: Base-rate and survivorship-bias literature (e.g., Mlodinow, Taleb) applied to management case studies; accounts of experimentation cultures or hands-on leadership that did not pay off.
• incompleteThe central causal claim — that niceness culture measurably compromises financial performance and rigor culture measurably improves it — rests entirely on the authors' own consulting anecdotes plus a single Bain survey about behavior prevalence (not about performance outcomes). No controlled comparison, industry benchmark, or correlational study directly connects "niceness" to performance metrics.
  Is Your Organizational Culture Too Nice? — read next: Organizational-culture research with actual performance correlations (e.g., Kotter & Heskett's culture-and-performance work, or Denison culture-survey studies) to test whether the niceness/performance link holds outside these authors' own client base.
• illogicalThe Bain statistic ("only one in five of the highest-performing teams consistently exhibit these behaviors") is used to argue candor is rare and valuable, but on its face it also shows four in five top-performing teams do NOT consistently exhibit these behaviors — i.e., high performance is evidently possible without them most of the time. The article doesn't reconcile this tension.
  Is Your Organizational Culture Too Nice? — read next: The original Bain "At the Top, It's All About Teamwork" study, to see whether Bain's own analysis treats these behaviors as necessary, sufficient, or merely correlated with top-quintile performance.