Managers should generally not attend retrospectives unless they have explicitly been invited by the team and psychological safety is already high. Their presence — even with good intentions — often causes team members to self-censor, undermining the honest reflection that makes retrospectives valuable. There are exceptions, but they require deliberate handling.

The Core Tension

Why It Matters

Manager Attends	Manager Absent
Hears issues firsthand	Team speaks more freely
Can take action on blockers	Team owns their process
Shows support and investment	Psychological safety higher
May influence discussion	Team develops autonomy

The Real Question

It’s not “Should managers attend?” but:

• What’s the impact on psychological safety?
• Does their presence help or hinder honest discussion?
• What’s the manager’s role when present?

Arguments for Manager Attendance

Benefits

1. Direct awareness of issues Managers hear problems firsthand rather than filtered through summaries.

2. Faster action on blockers Issues requiring manager authority can be addressed immediately.

3. Demonstrated investment Attendance shows the team that their improvement matters.

4. Context for decisions Managers understand why the team needs certain changes.

5. Part of the team Many managers are working members of the team.

When Attendance Makes Sense

• Manager is an active team member (player-coach)
• High trust already exists
• Team wants manager there
• Manager practices good retrospective behavior
• Issues require manager action

💡 RetroFlow supports anonymous input even when managers attend—free, no signup required.

📖 Explore more: psychological safety in retrospectives

Arguments Against Manager Attendance

Concerns

1. Reduced psychological safety Team members may self-censor with authority present.

2. Focus shifts to manager Discussion becomes about pleasing/informing the manager.

3. Power dynamics Disagreeing with manager is harder than disagreeing with peers.

4. Performance anxiety Team may feel evaluated rather than reflective.

5. Problem solving vs. reflecting Managers may jump to solutions rather than letting team process.

When Absence Makes Sense

• Trust hasn’t been established
• Manager is part of the problem being discussed
• Team has explicitly requested manager-free retros
• Sensitive topics need to be surfaced
• Team needs to develop autonomy

What the Research Says

Psychological Safety Research

Amy Edmondson’s research on psychological safety shows:

• Power dynamics affect speaking up — People are less likely to voice concerns with authority present
• Leader behavior is crucial — How leaders respond determines safety
• Consistency matters — Unpredictable responses create fear

This matters because Google’s Project Aristotle found psychological safety is the #1 factor in team effectiveness. When managers attend, the risk of undermining that safety is real.

Practical Observations

Teams report:

• More honest feedback when managers are absent
• Different topics raised with vs. without managers
• Self-censorship is real, even with good managers
• Trust builds over time with consistent good behavior

Guidelines for Manager Attendance

If You Attend: Rules for Managers

1. Listen more than speak

• Aim for 80% listening, 20% speaking
• Don’t dominate discussion
• Let team lead the conversation

2. Don’t react defensively

• Accept criticism without justification
• Thank people for raising issues
• Don’t explain why you did what you did

3. Don’t evaluate

• Retrospectives aren’t performance reviews
• Don’t judge contributions
• Focus on team improvement, not individuals

4. Support, don’t solve

• Ask: “How can I help?” not “Here’s what I think you should do”
• Let team own their solutions
• Offer resources, remove obstacles

5. Follow through

• Take action on issues raised
• Report back on progress
• Demonstrate that speaking up leads to change

Sample Manager Behavior

Good:

Team member: “Our standups are too long and not useful.” Manager: “Thank you for raising that. What would make them more useful for you?”

Poor:

Team member: “Our standups are too long and not useful.” Manager: “Well, we need standups for coordination. Maybe you’re not using them right.”

Models for Manager Involvement

Model 1: Full Participation

Manager attends as a team member, following the rules above.

Best when:

• Manager is truly part of the team
• High trust exists
• Manager practices good retrospective behavior

Model 2: Observer Only

Manager attends silently, observes, doesn’t participate.

Best when:

• Manager wants awareness without influencing
• Building toward full participation
• Team is working on trust

Manager instruction:

“I’m here to listen and support. I won’t speak unless asked directly. Please pretend I’m not here for the discussion.”

Model 3: Partial Attendance

Manager attends some portion—opening, closing, or action items.

Options:

• Opening only: Sets context, then leaves
• Actions only: Joins for commitments that need support
• Closing only: Hears summary, offers support

Model 4: No Attendance, Written Summary

Manager doesn’t attend; team shares written summary afterward.

Best when:

• Team needs maximum safety
• Sensitive topics to discuss
• Building trust incrementally

Model 5: Periodic Manager-Free Retros

Manager attends most but periodically skips to allow uninhibited discussion.

Pattern:

“Every fourth retrospective, I’ll step out so you can discuss anything freely.”

Some formats naturally encourage more open feedback. Explore options in our retrospective formats guide.

Making the Decision

Ask the Team

Directly:

“Would it be helpful for me to attend retrospectives, or would you prefer to have them without me?”

Anonymously: Collect anonymous input on manager attendance preference.

Read the Signals

Signal	Interpretation
Discussion dies when manager speaks	Too much influence
Team asks manager to leave for certain topics	Need more safety
Same issues raised with/without manager	Trust may be sufficient
Team asks for manager’s input	Manager presence valued
Retro is more productive without manager	Consider absence

Trial Periods

Experiment:

• Try 3 retros with manager, 3 without
• Compare feedback, participation, outcomes
• Ask team which they preferred

Specific Situations

New Manager

Recommendation: Start with limited attendance

• Build trust first
• Demonstrate good behavior in other settings
• Attend when invited
• Start with partial attendance

Manager Is Part of the Problem

Recommendation: Step out

• If issues involve manager, team can’t speak freely
• Ask for anonymous feedback separately
• Have facilitator share relevant themes

Team Is Struggling

Recommendation: Supportive presence with guardrails

• Attend to show support
• Be extra careful about behavior
• Consider having facilitator manage your participation
• May need to step out for portions

High-Performing Team

Recommendation: Follow team’s preference

• Trust the team’s judgment
• Attendance may not matter much either way
• Let team evolve their preference

Creating Safety With Manager Present

Facilitator Tactics

Anonymous input: Use anonymous contributions so items aren’t attributed. Retrospectives with anonymous feedback see 42% more participation from introverts (State of Agile Report), which is especially important when authority figures are present.

Manager guardrails:

“As a reminder, [Manager] is here to listen and support. They won’t solve—that’s our job.”

Check-ins:

“How’s the discussion going? Is everyone comfortable?”

Manager exclusion option:

“For this topic, would it be helpful to discuss without [Manager]?”

Manager Tactics

Explicit vulnerability:

“I know my presence might change the dynamic. I really want you to be honest—I can take it, and I need to hear it.”

Permission to discuss you:

“I’m part of this team and fair game for feedback. Don’t hold back on my account.”

Gratitude for honesty:

“Thank you for being honest about that. It’s exactly what I need to hear.”

Run Safer Retrospectives with RetroFlow

Support psychological safety:

• ✅ Anonymous input regardless of who attends
• ✅ Structured formats that prevent domination
• ✅ Equal voice through voting
• ✅ Written before verbal levels the field
• ✅ 100% free — No limits, no credit card
• ✅ No signup required — Accessible to all

Start Free Retrospective →

Summary

Manager attendance in retrospectives:

• Not inherently good or bad — depends on behavior and context
• Ask the team what they prefer
• If attending, follow rules — listen, don’t defend, support don’t solve
• Consider alternatives — partial attendance, periodic absence
• Monitor impact on psychological safety and honesty
• Prioritize team needs over manager desire to know

The goal is effective retrospectives, not manager attendance. Choose what serves that goal. Teams that run regular retrospectives are 24% more productive (State of Agile Report), so anything that threatens the quality of those sessions deserves careful consideration.

Frequently Asked Questions

Should managers attend sprint retrospectives?

There is no universal answer — it depends on the team’s level of psychological safety and the manager’s behavior. If trust is high and the manager listens more than speaks, attendance can be beneficial. If the team self-censors when the manager is present, it is better for the manager to step out or attend only portions of the session.

How does manager attendance affect psychological safety in retrospectives?

Research by Amy Edmondson shows that power dynamics significantly affect whether people speak up. Even with well-intentioned managers, team members may self-censor, shift discussion toward pleasing the manager, or avoid raising sensitive topics. Using anonymous input tools like RetroFlow can help mitigate this effect by allowing honest contributions regardless of who is in the room.

What rules should managers follow when attending retrospectives?

Managers should aim for 80% listening and 20% speaking, avoid reacting defensively to criticism, and resist jumping to solutions. Their role is to support and remove obstacles, not to evaluate performance or dominate the conversation. Following through on issues raised is critical because it demonstrates that speaking up leads to real change.

What are the alternatives to full manager attendance at retrospectives?

Common models include observer-only attendance where the manager listens silently, partial attendance where they join only for opening or action items, periodic absence where the manager skips every fourth retrospective, and no attendance with a written summary shared afterward. Teams can experiment with different models and compare participation and feedback quality.

How do you decide whether a manager should attend a specific retrospective?

Ask the team directly, either verbally or through an anonymous survey about their attendance preference. Watch for signals like discussion dying when the manager speaks, or the team requesting manager-free time for certain topics. Running a trial period of three retrospectives with and three without the manager, then comparing feedback and outcomes, provides concrete data for the decision.

Related Articles

• Creating Retrospective Culture
• Psychological Safety in Retrospectives - Foundation for honesty
• Building Trust Before Retrospectives - Trust fundamentals
• Retrospective Facilitation Tips - Facilitation skills
• Signs of Unhealthy Retrospectives - Warning signs