Building Psychological Safety During Organizational Change

1. What Psychological Safety Is (and Isn't)

The term "psychological safety" is often misunderstood. It is not about being "nice," lowering standards, or creating a conflict-free environment. It is about creating a climate where candor is expected and welcome.

Let's start with the foundational expert on this topic, Harvard Business School professor Amy Edmondson.

Edmondson defines psychological safety as "a belief that it's absolutely okay, in fact it's expected, to speak up with concerns, with questions, with ideas, with mistakes."

During your transformation—especially the shift to microservices and AI—your team members will constantly be in situations where they risk looking:

• Ignorant: "How does this new API authentication work again?"
• Incompetent: "I've spent a day on this bug in the new service and I'm stuck."
• Intrusive: "Are we sure this is the right component to migrate next?"
• Negative: "This new AI-powered feature is promising, but I see a huge data privacy risk."

If people stay silent in these moments, your transformation will be crippled by hidden problems, slow learning, and missed opportunities.

The Performance Zone: Safety + Accountability

A common fear among leaders is that fostering psychological safety means sacrificing accountability and performance. This is a false dichotomy. True high performance exists where psychological safety and accountability are both high.

This 2x2 matrix, adapted from Amy Edmondson's work, illustrates that psychological safety is not about comfort. The goal is the 'Learning Zone' or 'High-Performance Zone', where high accountability is matched with high psychological safety, enabling teams to learn, innovate, and perform at their best, especially under the pressures of a transformation.

During your transformation, you are asking people to operate in a context of high uncertainty and interdependence. This is precisely when psychological safety moves from being a "nice-to-have" to a non-negotiable driver of performance.

2. A Strategic Roadmap: The 4 Stages of Psychological Safety

Thinking about "creating safety" can feel abstract. Dr. Timothy R. Clark provides a practical, phased framework that serves as a strategic roadmap. It breaks down the journey into four progressive stages, aligning with fundamental human needs.

This model gives you a powerful diagnostic tool and a clear, sequential path for your transformation efforts.

Here's how the four stages apply directly to your transformation context:

1. Inclusion Safety (The Need to Belong): Before people will risk learning or contributing, they must feel accepted. During an organizational restructuring, this is the first stage to be threatened. Your first job is to ensure everyone, especially those in changed roles, feels they have a secure place on the new team.
2. Learner Safety (The Need to Learn): This is the heart of your technical transformation. Your teams are learning new architectures (microservices) and new technologies (AI). They will make mistakes. Learner safety means they feel safe to ask "dumb" questions, experiment, and fail without fear of humiliation.
3. Contributor Safety (The Need to Make a Difference): Once team members have learned, they need to feel safe to contribute. This means empowering an engineer to apply their new skills to build a service, or allowing a salesperson to help redesign the GTM messaging for the new modular product.
4. Challenger Safety (The Need to Make Things Better): This is the ultimate goal. You need your teams to feel safe enough to challenge the transformation plan itself. You want the junior developer who spots a flaw in the migration strategy to speak up. You want the customer success manager who foresees a customer backlash to raise the alarm. Without challenger safety, you are flying blind.

3. The Leader's Toolkit: Actionable Strategies to Build Safety

Knowing the stages is one thing; activating them is another. As a leader, you are the primary architect of psychological safety. Your behaviors and the systems you design have an outsized impact.

Let's organize the practical strategies from the resources into three key areas.

Strategy 1: Model Vulnerability and Curiosity

Safety starts with you. Your team is constantly looking to you for cues on what is and isn't acceptable behavior.

Her advice, supported by the other resources, forms the core of your personal leadership practice:

• Frame the Work as a Learning Problem: Constantly repeat that you are in uncharted territory. Use phrases like, "We've never built a product with this AI layer before, so we're going to have to learn our way to the solution. We'll need everyone's brains in the game." This makes mistakes an expected part of the process.
• Acknowledge Your Own Fallibility: Model vulnerability by admitting your own mistakes and knowledge gaps. Say things like, "I could be wrong about this timeline, I need you to poke holes in it," or "I don't fully understand the technical trade-off here, can you explain it to me?"
• Model Curiosity and Ask Powerful Questions: Shift from telling to asking. Actively invite input with open-ended questions like:
  • "What are your thoughts on this?"
  • "What are we missing?"
  • "Who has a different perspective?"

Strategy 2: Re-engineer Team Interactions and Rituals

Embed safety into the team's daily operating rhythm by changing how you meet, give feedback, and handle failure.

Here are some high-impact practices to implement:

• Establish Team Charters: Run a workshop where the team collaboratively defines its own rules of engagement. How will you disagree respectfully? How will you share concerns? This creates shared ownership of the team's culture.
• Conduct Blameless Post-Mortems: This is vital for your engineering teams. When a deployment fails or a bug is discovered, the review process must focus 100% on "What can we learn from this to make the system more resilient?" rather than "Whose fault was it?"
• Structure Meetings for Inclusion:
  • Start meetings with a brief, human check-in.
  • Use structured dialogue, like a round-robin, to ensure everyone gets a chance to speak.
  • Provide multiple channels for input (e.g., a shared document for pre-meeting thoughts) to include those who are less comfortable speaking up on the spot.

Strategy 3: Hardwire Safety into Organizational Systems

Your personal actions and team rituals can be undermined if the formal systems of the organization send a different message. Your background in Org Design and L&D makes you perfectly suited to champion these systemic changes.

• Performance Management: Shift reviews to focus on learning and growth, not just outcomes. Acknowledge the learning curve of a new technology; don't penalize an engineer whose initial velocity drops while they are mastering a new microservice pattern.
• Incentive Structures: Ensure that bonuses and recognition don't create zero-sum competition. Reward team-based collaboration on new initiatives and "assisting" activities that promote shared learning.
• Feedback and Reporting Channels: Create clear, reliable, and confidential channels for raising concerns about the transformation without fear of retaliation.

This image presents a useful cyclical model for this kind of continuous effort.

Practical Application Exercise

Let's apply this to a scenario within your transformation program.

Scenario: You are leading the transformation. One of the product teams is tasked with integrating a new AI-driven recommendation engine into a core product. It's a high-stakes project. In a steering committee meeting, the team lead reports that everything is "green" and on track. However, in a separate, informal conversation, a junior engineer from that team mentions to you that they are struggling with unexpected data quality issues and that the AI model's performance in their staging environment is far below what was promised. They quickly add, "But I'm sure we'll figure it out."

Your Task (10 minutes):

1. Diagnose the Situation: Using the 4 Stages of Psychological Safety, at which stage(s) is this team most likely struggling? Explain your reasoning.
2. Develop a Three-Part Strategy: Outline three specific, actionable steps you would take to address this situation. Your strategy should include:
   • An immediate leadership action (modeling behavior).
   • A team-level process change (re-engineering an interaction).
   • A question to ask about the organizational system (to see if it's contributing to the problem).

Conclusion

In this lesson, we have moved from the abstract concept of psychological safety to a concrete set of strategies for building it. You've learned that it is not about being soft but about enabling high performance, especially in the face of uncertainty.

Key Takeaways:

• Psychological safety is the prerequisite for success in transformation. It allows teams to learn, make mistakes, and voice concerns openly—all of which are essential for navigating change.
• It is built systematically through four stages: Inclusion, Learner, Contributor, and Challenger Safety. This provides a clear developmental roadmap.
• Leadership is the catalyst. Creating safety starts with you modeling vulnerability, humility, and curiosity.
• It must be embedded in daily rituals and formal systems. Safety is created through consistent practice in meetings, feedback sessions, and performance reviews.

Preview of the Next Lesson

Creating psychological safety allows difficult truths and anxieties to surface. One of the most potent anxieties in your specific transformation will be the fear of job displacement due to AI. Having created the space for this fear to be voiced, you must be prepared to address it directly.

In our next lesson, we will tackle this head-on. We will focus on how to address job displacement fears arising from AI transformation with transparency and empathy, applying the principles of psychological safety to one of the most sensitive aspects of your program.