Organisational psychology
Psychological safety: help teams speak up
Build psychological safety through everyday team practices: invite concerns, respond to mistakes and keep clear standards for accountability.
Your meeting ends with agreement. Afterwards, a colleague sends a private message explaining why the plan might fail. The concern existed during the meeting, but saying it aloud felt harder than staying quiet.
Psychological safety concerns that interpersonal risk. It is a shared belief about whether the team is a place where people can ask questions, acknowledge uncertainty and raise concerns. It is not a promise that everyone will feel comfortable, and it is not permission to ignore the quality of the work.
If you lead a digital team, the practical goal is to make relevant information easier to surface before it becomes expensive to act on. Start by changing the response to a concern, then examine whether your meeting and decision practices support that response.
Understand the concept before choosing an exercise
Amy Edmondson’s original study connected psychological safety with learning behaviour in work teams. That association is a research finding, not a guarantee that introducing a particular meeting ritual will improve your results.
The concept describes a team context. You cannot infer it from one outspoken individual, a lively chat channel or a successful offsite. A team can be friendly while making certain subjects difficult to discuss. People might joke freely but avoid questioning a deadline or reporting an error.
Look for the subjects that disappear from the conversation. Do colleagues ask for help only in private? Does somebody wait for the manager’s opinion before contributing? Are concerns raised after a decision because the group treats disagreement as disloyalty? These observations are prompts for investigation. They do not establish what someone feels without asking.
Keep standards and speaking up together
Suppose a developer reports that a release check was skipped. A useful response has two parts. First, acknowledge the information and examine the immediate risk. Second, establish what the work standard required and what happened.
Removing the second part would make accountability unclear. Starting with accusation may make future information harder to obtain. You need both an honest account and a fair process for addressing the missed check.
Distinguish an error during reasonable work, a poorly designed process and a deliberate breach of an agreed requirement. These may require different responses. Make those distinctions through evidence and the relevant organisational procedures, rather than deciding in a meeting that somebody has the wrong attitude.
This is also why a manager should avoid promising that speaking up will have no consequences. Some issues require investigation or action. You can promise to take the information seriously, explain the process and avoid retaliating against a person for raising a legitimate concern.
Change what happens in the first minute
The response to a concern is an observable behaviour you can practise. Listen without interrupting. Ask what happened, what may be affected and what help is needed. Avoid making the first question a defence of your previous decision.
For an ordinary delivery issue, you might say: “Thanks for raising it. Which part is uncertain, and what do we need to check before proceeding?” This is illustrative wording, not an attributed quotation or a universal script.
If the person is still assembling the evidence, separate the signal from the conclusion. You can acknowledge a possible risk without treating an unverified allegation as fact. Name the next check, its owner and the point when you will return to the concern.
Your response matters after the meeting too. A concern that receives a polite acknowledgement and then vanishes can teach the team that raising it changes nothing. Close the loop even when you decide not to change the plan. Explain the evidence and the decision boundary.
When you also need to address a performance concern, prepare difficult feedback around facts and consequences. Receiving a report and discussing a specific behaviour are separate steps; make the purpose of each clear.
Design meetings that allow independent views
Asking “Does everyone agree?” after presenting your preferred option is a weak invitation. The social and practical costs of dissent are already built into the sequence.
Before you declare a preference, let people record their assessment independently. Ask for the strongest risk to the proposal, a missing assumption or a dependency the team has not addressed. Choose a question that belongs to the decision, instead of asking people to perform general negativity.
Invite relevant expertise, including from people with less status. Nembhard and Edmondson’s study of leader inclusiveness examined this issue in healthcare teams. Applying it to a product team requires care; professional hierarchies and working conditions differ.
Give people another route to contribute when a live meeting is difficult: a written review, a private discussion or an accessible document with a clear response deadline. Do not require a personal disclosure or a public demonstration of courage to prove participation.
A hypothetical release review
Imagine a team preparing to release an AI-assisted customer support feature. This example is hypothetical. A junior analyst notices that some answers cite the wrong policy version. The team has already celebrated the launch date, and the analyst worries about looking obstructive.
The lead starts the review by naming an unresolved question: whether the policy retrieval works reliably on the actual support cases. Each person records one case the feature handles well and one that needs further review. The analyst contributes the outdated-policy example.
The team does not reward the concern with applause and immediately ship. It records the affected cases, assigns verification and decides which use cases remain outside the release. The launch owner explains how the decision changes the schedule.
At the next review, the lead reports what was fixed and what is still excluded. The analyst can see that the concern entered a decision process. The team checks whether other people now raise ambiguous cases earlier, while continuing to assess answer quality. No improvement is assumed from this imagined sequence; it illustrates the behaviours you can make explicit.
Use a speaking-up response checklist
Keep this checklist beside the agenda for a decision meeting or retrospective. It is a practical aid, not a psychological assessment scale.
Swipe or use the arrow keys to see every column.
| Moment | Action | What to avoid |
|---|---|---|
| Before discussion | State what is unresolved and who decides | Presenting a settled decision as an open consultation |
| During contributions | Ask for the observation and its implications | Inferring motives or interrupting to defend yourself |
| When evidence is incomplete | Assign a proportionate check | Treating uncertainty as either proof or irrelevance |
| After a concern | Record the owner and response point | Thanking the person while leaving the issue without a route |
| At review | Explain what changed or why it did not | Reopening the conversation without an update |
Choose one item to practise rather than announcing that the team is now psychologically safe. Ask a colleague to observe the meeting process, with participants aware of the purpose. Look at what you did, not whether you performed the right vocabulary.
Observe signals without turning them into targets
Useful signals include when risks surface, whether clarification happens before a handover and how the team responds to an error. Combine process evidence with voluntary feedback about working conditions.
More reported problems can mean the work is getting worse, or that people are becoming more willing to report what was already happening. Fewer reports can mean a safer process, or silence. Do not reward a manager simply for reducing the number of concerns.
Likewise, counting how often each employee challenges a decision creates pressure to perform dissent. Some people contribute by documenting a risk carefully or helping somebody else articulate a concern. A simple speaking-up leaderboard would miss that work and may expose individuals.
Use small-team feedback carefully. Removing names does not necessarily make a comment anonymous when the incident identifies its author. Explain access, retention and how the feedback will be used. If you need a formal assessment, involve qualified specialists and an appropriate instrument.
Recognise the situations a team ritual cannot resolve
Bullying, harassment, retaliation and serious safety concerns need the appropriate reporting and investigation routes. A retrospective is not a substitute. Do not ask an affected person to debate their experience publicly to help the team learn.
Psychological safety also cannot compensate for impossible workloads, unclear authority or a reward system that penalises missed deadlines regardless of the circumstances. Examine the work arrangement as well as the conversation. The organisational psychology guide provides that wider frame.
For ordinary disagreement, distinguish the contested task from personal attacks using the guide to task and relationship conflict. When motivation is the concern, examine autonomy and task support. These situations overlap, but need different decisions.
Begin with a response you can sustain
At your next meeting, state one uncertainty before requesting views. Listen to the first concern without explaining it away. Give it a clear route and return with an answer.
Then ask whether the process worked. Did the invitation reach people who had relevant information? Was the response fair? Did the final decision remain understandable? A routine you can sustain is more credible than a grand declaration followed by the old behaviour.
The same caution applies when interpreting customers: observed behaviour and psychological explanations are different kinds of evidence. An unanswered question is often more useful than a confident label.
If an AI initiative depends on people reporting uncertainty early, tell me where concerns currently get lost. We can work through the decision process and the practical conditions for raising them.
Apply this to your project
Tell me the decision you are facing, the constraints and what you have already tried.
Keep exploring
Motivation at work: give autonomy a clear shape
Understand motivation and autonomy at work: clarify choices, support competence and design responsibilities people can exercise in practice.
Organisational culture: look at everyday behaviour
Understand organisational culture through decisions, rewards and everyday responses, then turn stated values into working practices you can review.
Organisational psychology: a practical team guide
A practical guide to organisational psychology for digital teams: understand friction, clarify decisions and improve how people work together.