How to combine psychological safety with high standards
Combine psychological safety with accountability by protecting honest reporting while reviewing the work against clear commitments. Thank people for surfacing a problem, establish what happened, and decide what correction or consequence is warranted. Do not make respectful speaking up itself the offence, or assume that reporting a mistake removes responsibility for it.
Psychological safety is a shared belief that a team is safe for interpersonal risk taking, following Amy Edmondson’s 1999 research. In practical terms, consider whether someone can ask for help, acknowledge uncertainty, or challenge a proposal without expecting interpersonal punishment. Accountability, as used here, means an explicit obligation to explain and follow through on agreed work. It is an operating definition for this method, not a separate research scale.
Psychological safety differs from comfort and agreement. A candid review can be uncomfortable without making it unsafe to contribute. It also differs from trust in a particular colleague. Edmondson’s 2002 discussion of team learning examines that distinction. Do not use either term as permission to stop checking consequential work.
Notice the bargain your team thinks you have made
Consider this composite. You are at a school event, checking a message beneath the table while your family waits for you to look up. A project lead has reported a missed customer milestone. You respond, “Thank you for flagging it,” then spend the evening drafting a message about how unacceptable the failure is. In the morning you announce that everyone should speak openly, but refer to the project lead’s admission as proof they cannot be trusted.
The problem is not that you need to accept the missed commitment. The problem is that you have mixed the reporting behaviour with the delivery failure. Separate those events before you decide what happens next. Ask what the team knew, when they knew it, what they were expected to do, and whether they used the available escalation route.
If the missed milestone has employment implications, involve the appropriate people professional and employment counsel. A leadership framework does not replace a fair fact-finding or disciplinary process. Keep the review focused on verified conduct and responsibilities rather than the person’s willingness to bring you bad news.
Use the speaking-and-delivery matrix
Review two dimensions independently: whether the person raised relevant information responsibly, and whether the commitment was met. This proposed matrix is a discussion aid. It is not a validated diagnostic or an instruction to assign consequences automatically.
| Situation | Response to speaking up | Response to the work |
|---|---|---|
| Commitment met, useful concern raised | Acknowledge the contribution | Examine whether the concern changes future plans |
| Commitment missed, issue raised promptly | Protect the reporting behaviour | Establish causes, correction, and appropriate accountability |
| Commitment met, relevant issue withheld | Explore the omission and reporting expectations | Assess any concealed risk without rewriting the successful result |
| Commitment missed, issue withheld | Establish what the person knew and could reasonably disclose | Review the missed work and concealment separately through the proper process |
Use the matrix to check an easy shortcut: treating a successful result as proof that behaviour was acceptable, or a bad result as proof that the reporter acted badly. You still need evidence about each event. A person may have lacked information, misunderstood an escalation threshold, or knowingly ignored it. Those possibilities require different responses.
Do not turn the matrix into a league table. Use it to organize questions and responsibilities. Apply your normal employment procedures when conduct or capability is at issue. Tell the person which concern you are examining and give them a meaningful chance to correct your account.
Run the separate-response review
1. Recognize the disclosure precisely
Say what the person did that helped the organization. “You told us the acceptance test failed before the customer release” is more useful than broad praise for courage. Do not promise that the underlying mistake has no consequence. Protecting a reporting channel and approving everything reported through it are different commitments.
If you received the information through another person, establish how it arrived before assigning credit or blame. Do not claim someone hid a problem because they did not use your preferred channel when a different reporting route was authorized. Verify the expectation that existed at the time.
2. Reconstruct the commitment
Write down the outcome, owner, due point, dependencies, and escalation condition. Separate the commitment people actually accepted from the version you now wish they had accepted. Ask who could authorize a change and whether that authority was used. Where the record is missing, state the uncertainty rather than assigning a retrospective standard.
A useful question is: “What did you understand you were responsible for delivering, and what would have told you to stop or ask for help?” Listen for a concrete answer. If the agreement was ambiguous, correct the agreement as part of the response. Do not convert ambiguous delegation into a character judgement.
3. Distinguish constraints from choices
Identify resources, approvals, conflicting instructions, and information that affected the work. Then examine the decisions within the person’s control. A system constraint does not automatically explain every choice, and an individual error does not explain away a broken process. Hold both lines of inquiry open until you have enough evidence.
Ask each party to describe an action they could reasonably have taken with the information available. Avoid the claim that the right action was obvious merely because the outcome is now known. If an escalation route was impractical, design a usable replacement instead of demanding that people use it more enthusiastically.
4. Agree the correction and its proof
Specify what must change, who will do it, and how completion will be checked. For a customer milestone, the correction may include a revised acceptance test, a confirmed delivery plan, or a controlled change in scope. Do not settle for “better communication” when the failure concerned a missing decision or an unclear handoff.
Make the proof proportionate. Routine work should not require a new committee. A consequential risk may justify an independent check. Explain why the check is needed and when it can be removed. That distinguishes a temporary control from an indefinite statement that the person is no longer trusted.
5. Address consequences through the proper channel
Discuss the work, conduct, and reporting behaviour separately with the responsible manager. Use established policies and relevant advice. If a formal consequence is being considered, let employment counsel and your people team guide the process. Do not announce an outcome during a meeting convened to understand the event.
Communicate the operating correction to others who need it. Keep personal details restricted. You can say what standard has changed and which controls now apply without sharing an employee’s private record. A team does not need a public punishment story in order to understand a clear expectation.
6. Check the response to the next warning
The next issue is a chance to inspect whether your process works. When someone raises an early concern, acknowledge it, route it, and report what happened. Do not measure success only by whether the meeting felt frank. Look for a usable sequence from disclosure to decision to correction.
Track whether issues arrive early enough to act, whether owners receive a response, and whether agreed corrections are completed. Treat these as process observations, not a psychological safety score. A quiet month could mean fewer problems, less reporting, or missing information. Ask what would distinguish those explanations.
Keep high standards specific
High standards should name the work. “Be excellent” does not tell someone when a release is ready, a forecast is acceptable, or a customer handoff is complete. Define the relevant acceptance criteria and make them accessible before the deadline. Include what to do when the criteria cannot be met.
For relationship risk, Mayer, Davis, and Schoorman’s trust model distinguishes trust from the act of taking a risk. Apply that distinction cautiously: choosing to verify a consequential output is not, by itself, a declaration of distrust. Explain the purpose of the verification and apply it consistently to comparable work.
Challenge your own exemptions. If a favored executive misses the same obligation without review while another person is scrutinized, your written standards will not settle the discrepancy. Examine the decisions, explain any material difference, and correct an inconsistent response. Avoid asking the team to accept fairness as a statement of your intentions.
Test the boundary before the next failure
Ask your managers to work through a hypothetical example in which a dependable colleague reports an error early. Have each manager describe the response to the disclosure and the response to the underlying work. Compare the answers. If some managers interpret openness as immunity and others interpret accountability as public criticism, resolve that disagreement before relying on a shared policy. Write a model response using a real obligation but fictional people. Check that the model neither promises automatic forgiveness nor implies that the act of reporting creates guilt. Use the exercise to clarify authority and process, not to score managers on the language they choose.
Make a difficult conversation usable
A proposed opening is: “Raising this issue was the right step. We also need to examine the missed commitment. I want to separate what made delivery difficult, what decisions were within your control, and what we will change. I have not decided the explanation before hearing your account.”
Then describe the specific gap. Ask the other person to correct your timeline. Summarize the points you agree on and list the contested facts. Close with a next obligation rather than a demand for a better attitude. If the facts require formal review, say who will conduct it and how the person can contribute.
For persistent team friction, connect this review with the wider trust and conflict process. Where executive groups have split into camps, use the faction conflict approach to establish a common decision question. When your own promise has been broken, address it through trust repair before asking others to rely on a new one.
Your aim is an environment where people can disclose problems and still be answerable for their work. Keep those responsibilities visible in separate sentences. Protect the information the business needs, examine the obligation fairly, and make the next commitment clear enough to verify.