Psychological safety at work

{{whyLabel}}: Your behavior as a leader is the primary driver of team safety; awareness of your own triggers is the first step.

{{howLabel}}:

• Reflect on the last three meetings: Did you interrupt anyone or react defensively to a challenge?
• Identify your 'stress response': Do you shut down or become overly critical when things go wrong?
• Commit to 'Active Listening' by waiting 3 seconds after someone finishes speaking before responding.

{{doneWhenLabel}}: A written list of 3 personal leadership behaviors to improve is completed.

{{whyLabel}}: Quantitative data from Amy Edmondson’s validated scale provides an objective starting point.

{{howLabel}}:

• Use an anonymous survey tool to ask the 7 standard questions (e.g., 'If you make a mistake on this team, it is often held against you?').
• Use a 1-5 Likert scale (Strongly Disagree to Strongly Agree).
• Ensure the team knows the data is aggregated and anonymous to encourage honesty.

{{doneWhenLabel}}: Survey results from at least 80% of the team are collected.

{{whyLabel}}: Disproportionate speaking time is a leading indicator of low psychological safety.

{{howLabel}}:

• In your next 2 meetings, track who speaks and for how long without participating yourself.
• Note if dissenting opinions are voiced or if everyone simply agrees with the highest-paid person (HiPPO effect).
• Calculate the 'Speak-up Ratio': Total voices heard vs. total team members.

{{doneWhenLabel}}: A simple tally of speaking distribution for two meetings is recorded.

{{whyLabel}}: Explicit norms reduce the social anxiety of 'unwritten rules.'

{{howLabel}}:

• Define how the team handles disagreements (e.g., 'Challenge the idea, not the person').
• Set a rule for 'Intelligent Failure': Mistakes during experimentation are celebrated as data.
• Include a 'Right to be Wrong' clause to encourage early-stage idea sharing.

{{doneWhenLabel}}: A one-page draft of team communication norms is ready for review.

{{whyLabel}}: A formal launch signals that psychological safety is a strategic priority, not a 'soft' HR initiative.

{{howLabel}}:

• Block 90 minutes for a dedicated session (not part of a regular status update).
• Prepare a presentation showing the link between safety and performance (referencing Google's Project Aristotle).
• Formulate the invite to emphasize 'co-creation' of the team culture.

{{doneWhenLabel}}: Meeting invite is sent and accepted by the team.

{{whyLabel}}: Vulnerability is contagious; if the leader admits a mistake, the team feels safe to do the same.

{{howLabel}}:

• Share a specific professional failure from your past and what you learned from it.
• Use 'The 3 Words': "I don't know" or "I was wrong" during the session.
• Ask for feedback on your own leadership style during the workshop.

{{doneWhenLabel}}: The Kick-off is held and a personal mistake has been shared.

{{whyLabel}}: This ensures that introverts and junior members have a guaranteed space to contribute.

{{howLabel}}:

• At the end of every agenda item, give 2 minutes of silence for everyone to write down thoughts.
• Go around the 'room' (Round Robin) to hear from everyone before a decision is made.
• Start with the most junior person to avoid 'anchoring' to senior opinions.

{{doneWhenLabel}}: The rule is applied in at least 3 consecutive team meetings.

{{whyLabel}}: 'Why' questions often trigger defensiveness; 'How' or 'What' questions trigger curiosity and problem-solving.

{{howLabel}}:

• Instead of "Why did this fail?", ask "What were the factors that led to this outcome?"
• Instead of "Why didn't you ask for help?", ask "How can we make it easier to flag roadblocks earlier?"
• Practice this in all 1-on-1s for the next month.

{{doneWhenLabel}}: A 'Defensiveness-to-Curiosity' cheat sheet is used in 5 1-on-1 sessions.

{{whyLabel}}: Normalizing failure removes the stigma and accelerates the team's collective learning curve.

{{howLabel}}:

• Dedicate 15 minutes every Friday to discuss one 'intelligent failure' from the week.
• Focus on the 'Lesson Learned' rather than the error itself.
• Reward the person who shares with a 'Learning Award' (e.g., a small generic token or public praise).

{{doneWhenLabel}}: Four consecutive 'Failure Friday' sessions have been completed.

{{whyLabel}}: Safety is destroyed if people speak up and nothing changes; visible action builds trust.

{{howLabel}}:

• Every two weeks, send a brief message highlighting one piece of feedback received and the specific action taken.
• If an idea cannot be implemented, explain the 'Why' transparently.
• Use a public channel to ensure visibility for the whole team.

{{doneWhenLabel}}: Three bi-weekly updates have been sent to the team.

{{whyLabel}}: Comparing data to the baseline proves whether the interventions are working.

{{howLabel}}:

• Use the exact same 7 questions from the baseline survey.
• Analyze the delta (change) in scores, specifically looking for improvements in 'Risk Taking' and 'Asking for Help'.
• Share the progress (and remaining gaps) with the team to maintain transparency.

{{doneWhenLabel}}: A '90-Day Progress Report' comparing baseline vs. current safety scores is created.

{{whyLabel}}: Moving from ad-hoc safety to systemic safety requires integrating it into standard workflows.

{{howLabel}}:

• Add a mandatory 'Safety & Learning' section to every project post-mortem.
• Ask: "Did anyone feel they couldn't speak up during this project?" and "What did we learn that we didn't know at the start?"
• Update the Team Charter based on these recurring insights.

{{doneWhenLabel}}: The project post-mortem template is updated and used for one full project cycle.