• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Psychological safety underpins delivery practices

Purpose and Strategic Importance

This standard ensures psychological safety is treated as a foundational condition for effective delivery. When team members feel safe to speak up, share concerns, admit mistakes, and challenge ideas without fear of blame or retribution, delivery becomes more resilient, collaborative, and innovative.

It supports our policies to “Make Delivery Sustainable for People” and “Foster Shared Ownership of Delivery” by creating the trust required for shared responsibility and continuous improvement. Without psychological safety, communication suffers, risks go unspoken, and collaboration breaks down—limiting team effectiveness and learning.

Strategic Impact

  • Increases team resilience and adaptability under pressure
  • Enables honest reflection and continuous learning
  • Encourages diversity of thought and constructive dissent
  • Reduces silent failure, hidden work, and unaddressed risk
  • Strengthens team cohesion, morale, and long-term sustainability

Risks of Not Having This Standard

  • Team members withhold concerns, feedback, or ideas
  • Mistakes are hidden, repeated, or punished
  • Delivery becomes reactive, cautious, or compliance-driven
  • Blame culture undermines trust and collaboration
  • Retention and engagement drop due to stress and fear

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Speaking up is rare and often discouraged.
- Fear of blame leads to silence or avoidance.
Process & Governance - Retrospectives and meetings avoid sensitive issues.
- Psychological safety is not discussed or prioritised.
Technology & Tools - Tools focus on compliance, not collaboration or feedback.
Measurement & Metrics - No visibility into team safety or psychological wellbeing.

Level 2 – Managed

Category Description
People & Culture - Individuals may voice concerns in private, not public forums.
- Team leaders acknowledge the need for a safe environment.
Process & Governance - Some efforts are made to check in on team wellbeing.
- Ground rules for retrospectives are introduced.
Technology & Tools - Informal feedback tools or wellbeing surveys used occasionally.
Measurement & Metrics - Some anecdotal or periodic indicators of safety gathered.

Level 3 – Defined

Category Description
People & Culture - Psychological safety is discussed openly within teams.
- Leaders and team members model vulnerability and active listening.
Process & Governance - Retrospectives, stand-ups, and reviews include inclusive practices.
- Teams reflect on how safe it feels to take risks or share ideas.
Technology & Tools - Team health check tools or structured feedback mechanisms are used.
Measurement & Metrics - Safety is tracked as part of team performance and health.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Feedback culture is monitored and discussed regularly.
- Teams hold each other accountable for upholding safe behaviours.
Process & Governance - Psychological safety influences team formation, planning, and leadership.
- Data from safety measures is used to inform improvement work.
Technology & Tools - Tools capture anonymous feedback and emotional tone of delivery rituals.
Measurement & Metrics - Psychological safety is benchmarked across teams and time.

Level 5 – Optimising

Category Description
People & Culture - Teams proactively surface difficult topics and use conflict constructively.
- Safety is seen as a shared responsibility and actively nurtured.
Process & Governance - Learnings from safety data drive systemic change (e.g. org design, policies).
- Practices evolve through experimentation to enhance safety and performance.
Technology & Tools - Feedback loops and wellbeing signals are integrated into delivery systems.
Measurement & Metrics - Leading indicators of safety (e.g. voice participation, dissent rates) inform team health strategy.

Key Measures

  • Psychological safety scores from regular team health surveys
  • % of team members who feel safe to challenge or admit mistakes
  • Retrospective participation and openness indicators
  • Volume and follow-through of improvement ideas
  • Leader behaviours linked to team safety and trust scores
Associated Policies
Associated Practices
  • Actionable Retrospectives
  • Explicit Workflow Policies
  • Pairing and Mob Programming
  • Shared Team Working Agreements
  • Regular Cross-Disciplinary Syncs
  • Cross-Functional Team Composition
  • Psychological Safety and Inclusive Communication
  • Servant Leadership in Practice
  • Modelling Psychological Safety
  • Enabling Working Agreements
  • Regular 1:1s with Coaching Intent

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering