Section 1 - Instruction

You've learned that psychological safety is the foundation of high-performing teams, and that modeling vulnerability is the key to building it. Now let's practice identifying and creating safety-building behaviors.

The goal is recognizing what builds trust versus what accidentally shuts it down during technical discussions and code reviews.

Engagement Message

What's one safety-building behavior you want to practice in your next code review or technical discussion?

Section 2 - Practice

Type

Sort Into Boxes

Practice Question

Sort these leader responses during technical discussions based on whether they build or undermine psychological safety.

Labels

  • First Box Label: Builds Safety
  • Second Box Label: Undermines Safety

First Box Items

  • "I haven't used this"
  • "Help me understand"
  • "What's your approach?"
  • "I was wrong here"

Second Box Items

  • "This code is bad"
  • Cuts off explanations
  • Sighs during demos
  • "Use the pattern"
Section 3 - Practice

Type

Multiple Choice

Practice Question

When a team member says "I'm worried this API design might not scale," which response best models psychological safety?

A. "We've already committed to this architecture, so let's stick with it" B. "Let's stay focused on shipping and optimize later" C. "Thanks for raising this. What specific scalability concerns do you have?" D. "Does anyone else see scaling issues?"

Suggested Answers

  • A
  • B
  • C - Correct
  • D
Section 4 - Practice

Type

Sign up
Join the 1M+ learners on CodeSignal
Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal