Building a Culture Where the Truth Doesn't Hurt: The 2025 Surton Feedback System

At Surton, we’ve transformed feedback cultures in 20+ engineering organizations—from teams where “honesty” meant public shaming, to teams where truth is routine, safe, and drives rapid improvement. We’ve learned that psychological safety isn’t about being nice; it’s about being direct without being destructive.

This guide is our complete feedback system. It includes the SBI framework we teach, postmortem templates, psychological safety metrics, and our own cultural transformation case study.

Quick Take

High-trust teams make honest feedback routine, timely, and focused on learning not blame. The SBI model works: Situation (when/where), Behavior (observed facts), Impact (effect on team). Build psychological safety through modeling (leaders admit mistakes), normalizing (feedback weekly not annually), protecting (no punishment for honest mistakes), and rewarding dissent. Give constructive feedback within 48 hours, never when emotionally flooded. Postmortems should be blameless: what happened, what did we miss, what will we change. The goal is faster learning—shortening the distance between problem and improvement.

The Cost of Unsafe Cultures

When feedback feels dangerous, teams optimize for self-protection over improvement.

Symptoms of Low Psychological Safety

Symptom	Cost	Detection
Silence in meetings	Bad decisions go unchallenged	Same 2-3 people talk; others never contribute
Late feedback	Problems grow until crisis	Issues surface 3+ weeks after they started
Softened messages	Critical info gets lost	”Maybe we should consider…” instead of “This is wrong”
Covering/blame	Learning stops, politics starts	Postmortems become defense sessions
High-performer attrition	Best people leave	Exit interviews cite “culture” or “communication”

Surton Data: Teams with low psychological safety (safety score <60%) have:

• 2.5x longer incident resolution time
• 40% higher defect rates
• 3x higher voluntary attrition of senior engineers

Surton Case Study: The Unsafe Culture Turnaround

A 30-person engineering team at a growth-stage company had a “direct” culture that was actually toxic:

• Public criticism in Slack channels
• Postmortems with “you should have” blame
• Silent meetings (fear of wrong answer)
• 6 senior engineers left in 12 months citing “culture”

The transformation (6 months):

Month 1: Assessment and Foundation

• Psychological safety survey: 42% (crisis level)
• Leadership training: SBI model, emotional regulation
• New norm: Leader admits mistake in all-hands first

Month 2-3: New Feedback Systems

• Weekly 1:1s required with SBI training for managers
• Postmortem template: Blameless format mandatory
• “Red flag” system: Anyone can raise concern without retribution

Month 4-6: Reinforcement

• Praised publicly: Person who raised hardest truth
• Protected: No retaliation for honest mistakes
• Measured: Monthly pulse surveys

Results:

• Safety score: 42% → 81%
• Incident resolution: -40% time
• Senior attrition: Dropped to 1 in following 12 months
• Team quote: “Now we can actually talk about problems”

The SBI Feedback Model

The Situation-Behavior-Impact model separates observation from judgment.

The Framework

S - Situation: When and where did it happen?
”In yesterday’s client presentation…”

B - Behavior: What specifically did you observe? (Facts, not interpretation)
“You interrupted the client three times when they were explaining their problem”

I - Impact: How did it affect you, the team, or the outcome?
”The client became defensive, we didn’t get to the root issue, and I’m concerned about the relationship”

SBI vs. Non-SBI Examples

Non-SBI (Judgment)	SBI (Observation)
“You’re disrespectful in meetings"	"In yesterday’s meeting, you talked over Sarah twice when she was presenting data, and she stopped contributing"
"Your code quality is bad"	"In the last PR, 12 of 15 files had linting errors and the reviewer found 3 logic bugs, which delayed release by 2 days"
"You’re not a team player"	"This week you committed code at 2am three times without PR review, which broke the build twice and required others to clean up”

The Full Conversation Structure

1. Ask permission: “Can I share some feedback on [topic]?”
2. Deliver SBI: Situation, Behavior, Impact
3. Pause: Let them process
4. Invite perspective: “What’s your view of what happened?”
5. Listen: Understand their context
6. Agree on next steps: “What can we both do differently?”
7. Follow up: Check in on progress

When SBI Doesn’t Fit

Urgent safety: Immediate correction needed
Pattern, not incident: Multiple instances, address trend
Performance management: Formal documentation required

Psychological Safety: The Foundation

Amy Edmondson’s research defines psychological safety as “a shared belief that the team is safe for interpersonal risk-taking.”

The 4 Levels of Psychological Safety

Level	Indicator	Intervention
Inclusion safety	Do I belong?	Ensure everyone’s voice heard in meetings
Learner safety	Can I grow?	Praise questions, treat mistakes as learning
Contributor safety	Can I make a difference?	Give meaningful work, credit contributions
Challenger safety	Can I speak up?	Protect dissenters, reward hard truths

Surton’s 8-Question Safety Survey (Quarterly, Anonymous)

1. If I make a mistake, it won’t be held against me
2. Members of this team can bring up problems and tough issues
3. People on this team sometimes accept others for being different
4. It’s safe to take a risk on this team
5. It’s easy to ask other members of this team for help
6. No one on this team would deliberately act in a way that undermines my efforts
7. Working with members of this team, my unique skills and talents are valued and utilized
8. I can be my authentic self at work

Scoring: 1-5 scale, 80%+ “agree” (4-5) = healthy, <60% = crisis

Building Safety: The Leadership Actions

1. Model Vulnerability First

• Share your own mistakes in team meetings
• “I was wrong about X, here’s what I learned”
• Ask for feedback on your leadership directly

2. Frame Work as Learning

• “We’re figuring this out together”
• Treat experiments as learning regardless of outcome
• Postmortems for successes too (what almost went wrong?)

3. Make Failure Safe

• First failure: Learning opportunity
• Same failure twice: System problem (not personal)
• Repeated negligence after training: Performance issue

4. Invite Dissent Explicitly

• “What am I missing?” in every decision meeting
• “Devil’s advocate” role rotates
• Reward people who raise hard truths

Postmortems: Learning from Incidents

The blameless postmortem is a critical tool for building safety.

The Surton Postmortem Template

INCIDENT POSTMORTEM: [Title]
Date: [Date of incident]
Severity: [S1/S2/S3 - customer impact scale]

1. WHAT HAPPENED (Timeline)
   [Chronological facts only, 5-min granularity]
   14:03 - Monitoring alert fired
   14:07 - Engineer X acknowledged pager
   ...

2. DETECTION (How did we know?)
   - Alert source: [Which monitor]
   - Time to detect: [Minutes]
   - Could we have known sooner? [Yes/No, how]

3. RESPONSE (What did we do?)
   - Actions taken: [List]
   - Time to mitigate: [Minutes]
   - Time to resolve: [Minutes]

4. IMPACT (Who was affected?)
   - Customers: [Number, severity]
   - Data: [Any loss/corruption]
   - Revenue: [If applicable]

5. ROOT CAUSES (5 Whys)
   Why did X happen? → Because Y
   Why did Y happen? → Because Z
   ... (continue to 5 levels)

6. WHAT WE MISSED (Signals available)
   - Earlier indicators: [List]
   - Monitoring gaps: [What wasn't watched]
   - Process gaps: [What procedure failed]

7. ACTION ITEMS (Specific, owned, dated)
   | Action | Owner | Due Date | Priority |
   |--------|-------|----------|----------|

8. LESSONS (Pattern for future)
   - What should we watch for?
   - What process needs changing?

Facilitator: [Name]
Attendees: [Names]
Date completed: [Date]
Distribution: [Team, management, broader if needed]

The Blameless Rule

Forbidden phrases:

• “You should have…”
• “Why didn’t you…”
• “That was careless”
• “Someone made a mistake”

Required framing:

• “We missed…”
• “The system didn’t catch…”
• “We didn’t have visibility into…”
• “The process gap was…”

Exception: Performance management issues (pattern of negligence) are handled separately, outside postmortem.

Receiving Feedback: The Leader’s Skill

How leaders receive feedback sets the tone for the entire culture.

The “Thank You, Let Me Think” Protocol

Step 1: Listen Fully

• No defending, no explaining
• Take notes if helpful
• Body language: Open, not closed

Step 2: Clarify

• “Can you give me a specific example?”
• “What impact did you see?”
• “When else have you noticed this?”

Step 3: Acknowledge

• “Thank you for telling me”
• (Not: “But…” or “Actually…”)
• Even if you disagree, thank them for the input

Step 4: Take Time

• “Let me think about this and get back to you tomorrow”
• Sleep on it if emotional
• Reflection: Is there 20% truth here?

Step 5: Respond

• What will you change?
• What won’t you change and why?
• Close the loop with the giver

Step 6: Act

• Visible change based on feedback
• Or: Explain why you disagreed, but took it seriously

Implementation: The 90-Day Feedback Culture Sprint

Month 1: Foundation

• Leadership training: SBI model for all managers
• Psychological safety survey (baseline)
• Postmortem template deployed
• Leader vulnerability: Share mistake in all-hands

Month 2: Systems

• Weekly 1:1s mandatory with feedback component
• First blameless postmortem (facilitated)
• “Red flag” system for raising concerns
• Training: Receiving feedback for all

Month 3: Reinforcement

• Public praise: Someone who raised hard truth
• Monthly pulse survey
• Postmortem review: Are we learning?
• Quarterly safety survey (compare to baseline)

When Surton Can Help

If your team:

• Avoids difficult conversations
• Has silent meetings or “yes” cultures
• Loses good people to “cultural issues”
• Does postmortems with blame
• Has low psychological safety scores

Surton offers Culture & Feedback Consulting where we:

1. Assess current psychological safety
2. Train leadership on SBI and safety-building
3. Implement postmortem systems
4. Coach through difficult conversations
5. Measure and sustain improvement

Typical engagement: 3-6 months, $30k-60k
ROI: Reduced attrition ($200k-500k savings), faster incident learning, better decision quality

---

Related Resources

• Your Best Engineer Might Be Your Worst Manager — Feedback for new managers
• Developer Onboarding is Your Most Expensive Product Failure — Safety for new hires
• Building a Culture Where the Truth Doesn’t Hurt (Original) — The Blueprint edition

---

This is Surton’s definitive 2025 feedback culture system. For the original newsletter version, see The Blueprint.