Psychological Safety in Service Teams

Psychological Safety in Service Teams examines Amy Edmondson's psychological safety construct and its critical role in determining whether contact center teams achieve high performance or merely achieve compliance.

Overview

Psychological safety is a shared belief held by members of a team that the team is safe for interpersonal risk-taking. Introduced by Amy Edmondson (1999) through her research on hospital nursing teams, the concept explains a counterintuitive finding: the best-performing teams reported more errors, not fewer. High-performing teams did not make more mistakes — they operated in an environment where reporting mistakes was safe, enabling learning and improvement.

Google's Project Aristotle (2012-2015), the most comprehensive study of team effectiveness in corporate history, identified psychological safety as the single most important factor differentiating high-performing from low-performing teams — more important than team structure, individual talent, or workload. Teams with high psychological safety were rated as effective twice as often, generated more revenue, and were rated as effective by executives 2x more frequently.

In contact centers, psychological safety determines whether agents report system issues, escalate difficult interactions before they become complaints, share workarounds that improve efficiency, and flag compliance concerns. Management approaches that optimize for adherence through surveillance and punishment systematically destroy psychological safety — and ultimately destroy the performance they seek to protect.

Theoretical Framework

Edmondson's Original Research (1999)

Studying 51 work teams across a manufacturing company, Edmondson found that team psychological safety predicted team learning behavior, which predicted team performance. The mechanism: when people feel safe, they engage in learning behaviors — asking questions, seeking feedback, experimenting, discussing mistakes — that drive performance improvement.

Her seven-item measure includes:

If you make a mistake on this team, it is often held against you (reverse)
Members of this team are able to bring up problems and tough issues
People on this team sometimes reject others for being different (reverse)
It is safe to take a risk on this team
It is difficult to ask other members of this team for help (reverse)
No one on this team would deliberately act in a way that undermines my efforts
Working with members of this team, my unique skills and talents are valued and utilized

Distinguishing Psychological Safety

Psychological safety is NOT:

Trust — trust is between individuals; PS is a team-level climate property
Niceness — PS enables candor, which can be uncomfortable; "nice" teams that avoid conflict have low PS
Low standards — Edmondson's 2x2 matrix: high PS + high standards = "learning zone"; high PS + low standards = "comfort zone"; low PS + high standards = "anxiety zone"
Consensus — PS enables disagreement; it does not require agreement
Personality-driven — PS is primarily created by leader behavior, not team member personality

The Learning Zone

Edmondson's (2018) framework in The Fearless Organization maps teams on two dimensions:

	Low Standards	High Standards
High Psychological Safety	Comfort Zone (pleasant but unproductive)	Learning Zone (high performance)
Low Psychological Safety	Apathy Zone (disengaged)	Anxiety Zone (compliant but brittle)

Most contact centers operate in the Anxiety Zone: high standards (adherence, quality, handle time targets) with low psychological safety (surveillance, punitive quality management, rigid exception handling). This produces compliance without improvement — agents do what's measured while hiding problems that would help the organization learn.

Google Project Aristotle

Methodology

Google studied 180+ active teams over three years, analyzing:

Team composition (personality types, demographics, tenure)
Team dynamics (norms, communication patterns, conflict resolution)
Performance outcomes (manager ratings, peer ratings, revenue impact, team satisfaction)

Key Finding

"Who is on a team matters less than how team members interact, structure their work, and view their contributions."

The five dynamics of effective teams, in order of importance:

Psychological safety — Can we take risks without feeling insecure or embarrassed?
Dependability — Can we count on each other to do high-quality work on time?
Structure & clarity — Are goals, roles, and execution plans clear?
Meaning — Are we working on something personally important?
Impact — Do we believe our work matters?

Psychological safety was foundational — without it, the other four dynamics could not develop. Teams with high PS were:

2x as likely to be rated effective by executives
Generated more revenue
Rated as effective by executives 2x more often
Had lower turnover
Harnessed diverse ideas more effectively

Psychological Safety in Contact Centers

The Adherence Paradox

Contact center management typically relies on adherence — conformance to schedule states at specified times. The implicit contract: be exactly where you're supposed to be, doing exactly what you're supposed to be doing, at every measured interval.

This creates a low-PS environment through:

Surveillance signaling — agents know every second is monitored; the message is "we don't trust you"
Exception punishment — deviations from schedule (even for legitimate reasons) require justification
Quality as weapon — QA findings used punitively rather than developmentally
Escalation risk — agents who escalate "too many" calls are flagged as underperformers

The paradox: strict adherence management produces worse operational outcomes because it:

Discourages agents from extending interactions to resolve issues properly (drives repeat contacts)
Prevents agents from reporting system problems that affect many customers
Stops agents from sharing efficient workarounds (because they might require off-schedule time)
Creates "malicious compliance" — following the script exactly even when it's clearly wrong for the situation

What Agents Hide in Low-PS Environments

In environments where psychological safety is low, agents routinely conceal:

System bugs — workarounds become tribal knowledge rather than reported defects
Process failures — broken processes persist because reporting them feels like criticizing management
Near-miss compliance events — potential regulatory failures go unreported until they become actual failures
Customer intelligence — patterns, complaints, competitive mentions go unshared
Personal struggles — fatigue, mental health, personal issues that affect performance remain invisible until crisis
Better methods — agents who find more efficient approaches keep them private rather than risk being told "that's not the process"

Leader Behaviors That Build PS

Edmondson (2018) identifies three categories of leader behavior:

Setting the Stage:

Frame work as a learning problem, not an execution problem
Acknowledge own fallibility ("I may miss something — I need your eyes on this")
Model curiosity

Inviting Participation:

Ask proactive questions — don't wait for people to speak up
Create structured forums for input (not just "any questions?")
Use inclusive language ("What are we missing?" not "Does anyone disagree?")

Responding Productively:

Express appreciation for candor (even when the message is uncomfortable)
Destigmatize failure — distinguish between blameworthy and praiseworthy failures
Sanction clear violations (accountability is not incompatible with PS)

Team Leader Impact

In contact centers, the frontline supervisor (team leader) is the primary determinant of psychological safety. Gallup's extensive research confirms: 70% of variance in team engagement is attributable to the manager. A team leader who responds to mistakes with curiosity ("What happened? How can we prevent this?") creates safety. One who responds with blame ("Why didn't you follow the process?") destroys it.

This has WFM implications: team leader assignment, span of control, and supervisor development directly determine whether PS exists. These are structural decisions, not soft skills.

Measurement

Direct Measurement

Edmondson's 7-item scale, administered at team level. Important: individual responses are meaningless — PS is a team-level construct. Analyze at team level, report at team level, intervene at team level.

Behavioral Indicators

Observable behaviors that indicate PS level:

High PS: Agents ask questions in team meetings; quality calibrations generate debate; agents flag system issues proactively; error reporting is voluntary and timely; agents experiment with approaches
Low PS: Silence in team meetings; quality feedback accepted without discussion; issues discovered only through monitoring; agents request not to be recorded; adherence exceptions never challenged

Proxy Metrics

Error reporting rate — high PS environments have more self-reported errors (because reporting is safe)
Suggestion volume — ideas submitted through improvement channels
Escalation patterns — appropriate escalation (not over-escalation from anxiety or under-escalation from fear of appearing incompetent)
Meeting participation — speaking distribution in team huddles
Grievance rate — paradoxically, moderate grievance rates indicate safety to raise issues; near-zero rates may indicate suppression

WFM Applications

Adherence Philosophy

Shift from conformance-based adherence (were you in the right state at the right time?) to outcome-based adherence (did you deliver your scheduled availability with acceptable results?):

Allow agents to manage their own micro-breaks within utilization targets
Measure adherence at 30-minute intervals rather than real-time (removes surveillance feeling)
Create "adherence credit" systems where consistent performance earns schedule flexibility
Eliminate adherence as a punitive metric — use it diagnostically (agent struggling with adherence may need support, not discipline)

Quality Management Approach

Coaching-first QA — quality findings lead to development conversations, not performance improvement plans (unless repeated and willful)
Agent self-assessment — agents evaluate their own interactions before receiving supervisor feedback
Calibration participation — agents participate in quality calibration sessions, developing shared understanding of standards
Positive exception recognition — when agents deviate from script/schedule to achieve better outcomes, recognize this rather than punishing the deviation

Team Structure

Span of control ≤15 — enables supervisor to build genuine relationship with each team member (see Team Size, Span of Control, and Dunbar's Number)
Stable team membership — PS develops over time; constant team restructuring destroys it
Team-level autonomy — where possible, give teams control over internal scheduling, task allocation, and process improvement

Reporting Systems

Non-punitive error reporting — agents can flag mistakes, near-misses, and system issues without consequence
Anonymous feedback channels — supplement (not replace) direct communication
Response commitment — every report receives acknowledgment and outcome communication within defined SLA
Systemic action — pattern analysis leads to system fixes, not individual blame

Maturity Model Position

Level	Description
Level 1 — Fear-Based	Quality used punitively; adherence surveillance dominant; agents hide errors; silence in meetings; high grievance and attrition
Level 2 — Inconsistent	Some leaders create safety; others don't; no organizational standard; PS depends on which team you're on
Level 3 — Intentional	Leader behaviors trained; PS measured at team level; adherence philosophy shifting from surveillance to outcomes; error reporting encouraged
Level 4 — Embedded	PS scores tracked as operational metric; WFM policies designed to preserve PS; quality management integrated with coaching; agents participate in process design
Level 5 — Generative	High PS + high standards = organizational learning zone; agents drive continuous improvement; errors are learning opportunities; innovation emerges from frontline

References

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383.
Edmondson, A. C. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
Google re:Work (2015). Guide: Understand team effectiveness. https://rework.withgoogle.com/guides/understanding-team-effectiveness/
Duhigg, C. (2016). What Google learned from its quest to build the perfect team. The New York Times Magazine.
Gallup (2017). State of the American Manager. Gallup Press.
Nembhard, I. M., & Edmondson, A. C. (2006). Making it safe: The effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams. Journal of Organizational Behavior, 27(7), 941-966.

Anonymous

Search