Soft-Skills-the-Hard-Way

### Leadership Playbook: Psychological Safety in Engineering Teams

**Extracted from Chapters 1-3 of *Soft Skills the Hard Way* by Alex Chen**

**Key Lessons on Psychological Safety:**
- **Lesson 1: Normalize failure as a learning tool** – Alex learns that his team’s reluctance to share mistakes stems from a fear of blame. He realizes that celebrating failures (e.g., the botched deployment that taught the team how to roll back safely) fosters experimentation.
  - *Actionable Tip:* Start each sprint retrospective by sharing one "failure of the week" and what the team learned. Example: "Last sprint, our API latency spike taught us to add circuit breakers—here’s the post-mortem."

- **Lesson 2: Ask questions instead of assuming** – Alex notices his team hesitates to challenge his ideas. He adopts a "5 Whys" approach in meetings to uncover root causes instead of jumping to solutions.
  - *Actionable Tip:* Replace "Why didn’t this work?" with "What assumptions did we make here?" in code reviews. Example: "The test failed—what assumptions did we make about the user’s data format?"

- **Lesson 3: Make space for introverts** – Alex realizes his loudest engineers dominate discussions. He introduces silent brainstorming (e.g., Slack polls or async docs) to ensure quieter voices are heard.
  - *Actionable Tip:* Use Sortd’s Kanban boards in Gmail to assign discussion topics to specific team members before meetings. Example: "@Maria, your turn to share thoughts on the database schema—add your notes to the Sortd card by EOD."

**Team Name:** DevOps Avengers
**Next Steps:** Schedule a 15-minute retro to test the "failure of the week" tip and review Sortd’s task assignments for the next sprint planning meeting.