Creating Psychological Safety Around AI Use
Fear of looking foolish, using the tool wrong, or producing bad work is the primary barrier, often below the surface. Managers control whether failure in front of the team is safe.
Lesson 2
Fear of looking foolish is rational.
Safety is built by what you do: share your own bad outputs, respond to failure with curiosity ("what did the prompt need?"), name learning in public misses.
Psychological safety for AI use
Core principles
- Job concerns: "less valuable" vs "redundant" need different responses, AI handles volume; judgment, relationships, and accountability stay human.
- Be direct about job replacement fear; connect AI to removing friction so more judgment work is possible.
- Do not perform vulnerability, actually share a weak first draft and what you fixed.
Check yourself
What does this lesson identify as the primary barrier to AI adoption on most teams?
Fear of looking foolish is often below the surface and rarely named, but it shapes what people are willing to try in public. Managers control whether failure is safe. The signal is what you do: share your own bad outputs, respond with curiosity, name learning out loud.
Do this in Copilot
Share one honest read on a recent team AI attempt, what you expected, what happened, what you would do differently.
Paste this into Copilot Chat and work through it before moving on.
Team conversation starter
Draft three open questions I can ask my team in our next meeting to surface honest AI experiences, including times it did not help, without making people feel evaluated.
- Psychological safety
Did you run this in Copilot? Mark complete when you have tried it.
RecordedNext lesson: Running Team Experiments That Actually Work →
Navigate: press j for next lesson, k for previous.