📖
Tech Fleet User Guide
  • 🌿START HERE
    • 🔢Get Started
      • 1️⃣What is Tech Fleet?
      • 2️⃣Tech Fleet FAQ
      • 3️⃣Start With the Community Collective Agreement
      • 4️⃣First Steps in the Tech Fleet Community
      • 5️⃣How to Get Discord Roles in Tech Fleet
      • 6️⃣How to Become an Apprentice on Projects
      • 7️⃣How to Become a Co-Lead on Projects
      • 8️⃣How to Register for Masterclasses
  • 😃About us
    • 🤟About Our Org
      • 👋Hello World
      • 💗Mission and Values
      • 🤝We Live by the Collective Agreement
      • 🌎Diversity, Equity, and Inclusion in Action
  • 📰TRAINING OPENINGS
    • 📡Current and Upcoming Program Openings
      • 📜Project Openings
        • 🏃‍♀️Projects to Apply To Now
        • 🧙‍♀️Upcoming Projects
        • 🔥Live Project Phases in Tech Fleet
        • 🙈See It All In One Place
      • 🎓Masterclass Openings
    • ℹ️Application Forms
  • 🚀Join The Community
    • How to Join Tech Fleet Discord
    • 🛠️Onboarding to Tech Fleet
      • 😍Book a Community Onboarding Call
      • 📧Join our Mailing List
      • 📹Onboarding Videos
      • 🖥️Information Website
      • ✨Community Happenings
  • ⚙️RESOURCES
    • 🛠️Quick Links
      • 🤖Join Tech Fleet Discord
      • 🎨Figma Community Templates from Tech Fleet
      • 📅Tech Fleet Web Calendar
      • 📰Tech Fleet's Project Repository on Notion
      • 📧Join our Mailing List!
      • 🧭Tech Fleet's Roadmap
      • 🔗Common Links
      • 🚩Tools Used in Tech Fleet Programs
    • 🏫Community Tutorials
      • 🌠Portfolio Case Study Guide
      • The Great Tech Fleet Discord Migration Video Tutorials
        • ❔Discord FAQ
        • 🌐Discord Basics
        • ✍️Sign Up Process for Tech Fleet Discord
        • 🐎Common Channels in Tech Fleet Discord
        • 🔐Security Protocol in Tech Fleet Discord
        • 🧵Basic Chatting Abilities in Discord
        • 🤝Get a Tech Fleet Buddy
        • 🗓️Managing Events in Tech Fleet Discord
        • 🆘Get Technical Support in Tech Fleet Discord
        • ‼️Using Roles for Alerts, Notifications, and Channel Access
        • 🦮Getting Career Guidance in Tech Fleet Discord
        • 💼Getting on Projects in Tech Fleet Discord
          • 👀Observers in Tech Fleet Discord
          • 🌿Apprentices In Tech Fleet Discord
          • 🪜Co-Leads in Tech Fleet Discord
          • 🫂Mentors in Tech Fleet Discord
        • 🎓Masterclasses in Tech Fleet Discord
      • 🅰️Community Glossary
      • 🎨Join the Tech Fleet Figma Educational Space
      • 🤓How to Get Technical Support
    • 🏗️Project Team Tutorials
      • 🪄Product Milestone Workbook
        • 🎖️Milestone Basics
        • 👟MVP Milestones
        • 🎯MMP Milestones
        • ✅Milestone Checklist
      • ⌛Project Kickoff Workbook
  • 🏃‍♀️Agile Portal
    • 🤝Agile Training in Tech Fleet
    • 🛹Agile Handbook
      • Start the Agile Handbook Here
        • 👓Contents of the Agile Handbook
        • 🌎What You Read About Agile May Be Different From What You See in the World
        • 🎬Agile Manifesto Trailer
        • 🔑Introduction to the Agile Handbook
        • 🤖Can AI Replace Agile Teams?
      • 🧘‍♀️Agile Philosophies
        • 🌊Waterfall Ways of Work
        • 📜Agile Ways of Work
        • 🚂Applying Agile Philosophies to Work
        • 🎢Building MVP's and MMP's with Agile
      • 🤝Agile Teamwork
        • 💪Making Strong Agile Teams
          • 🌿Prioritizing Growth Over Skills
          • 🌻The Four Stages of Team Growth
          • 🚀Self-Actualized Agile Teams
            • 🏗️Building Agile Mindsets
            • Psychological Safety
            • Service Leadership
            • Self-Organization
            • Continuous Improvement
            • Iterative Value Delivery
        • 🫂Day-to-Day on an Agile Team
          • 👩‍🏭Cross-Functional Agile Teamwork
          • 🪜Leadership on Agile Teams
          • 😎Daily Life on Agile Teams
          • ♥️Resolving Team Conflict as Service Leaders
          • 📑The Process for Resolving Conflicts
          • ❌Collective Agreement Violations
      • 🧑‍🔬Agile Methods
        • 🏃‍♀️Scrum Method
          • 🤔What is Scrum?
          • 🧖Scrum Team Functions
          • 🗓️Scrum Meetings
          • ✍️Common Agile Deliverables
        • 🙉Other Agile Methods
      • 🪐Agile-Related Outputs and Deliverables
        • ⏲️Timeline for Agile Outputs
        • 🙌Team Outputs for Agile
          • Agile Team Outputs Before Projects Begin
            • 🏇Client Kickoff
            • 👁️Agile Team's Vision
            • 👩‍🏫Agile Team Process
            • 🍱Backlogs and Kanban Boards
            • 🦾RACI Charts
            • 🤗Working Agreements
            • 📈Project Phase Roadmaps
          • Agile Team Outputs During Projects
            • 🧑‍💼Sprint Planning Items
            • 👩‍💻Sprint Demo Presentations
            • 🦸‍♀️Sprint Retro Boards
            • 📏Agile Team Maturity Measurement
            • 🏁Project Hand-Off Document
        • 🚧Agile Product Development Deliverables
          • 👟Achieving Milestones on Agile Teams
          • 🔬Research Test Plans
          • ⁉️Agile Product Requirements
            • 🧐Where's the PRD (Product Requirements Document)?
            • 🧠Documenting Problems, Needs, and Goals
            • ⁉️Mapping Product Assumptions
            • 🔢Prioritizing Problems and Future Work
            • 😎Release-Level Vision
            • 🤠Release-Level Scope
            • 📯Product Release Roadmaps
            • 🏭Epics, Features, and Work Tasks
            • ✌️User Story Statements
            • ✅Acceptance Criteria
            • 🔷Behavior-Driven Development Scenarios
            • 🤔Use Case Scenarios and Task Flows
        • 🖥️Deliverables Dashboard
      • 📑Agile Glossary
    • ✨Service Leadership Handbook
  • 🌳PROJECT PORTAL
    • 🌱Learn About Project Training
      • ℹ️Tech Fleet Projects are Training, Not Volunteer Work or Employment
      • 🧑‍🤝‍🧑Our Approach to Learning
      • 🌎Team Structure on Tech Fleet Projects
      • ⛓️Commitment vs. Job Function vs. People on Teams
      • 🎢Team Functions
        • 🪐Product Strategy Function
        • ⌛Project Management Function
        • 🌏User Experience Functions
          • 🎨UX Design Function
          • 🤓UX Research Function
          • ✍️UX Writing Function
        • 🤖Development Function
        • 👩‍🔬Solutions Architecture Function
      • 🤝UX Research Ethics
    • 📃Applying to Tech Fleet Project Training
      • 😎How Tech Fleet Project Applications Work
      • 🔢Steps to Apply to Project Training
      • ✔️Application Requirements
      • 🤠Project Timelines and Application Process
      • ⁉️Project Application Questions
        • ❔Tech Fleet General Application Questions
        • ❔Tech Fleet Project Phase Application Questions
      • 🤔Updating the General Application
      • 🌠Application Tips
      • 🗞️See the Latest Project Openings
    • 🔍Interview Guide for Tech Fleet Project Team Building
      • 👀Key Traits We Look For in Team Mates
      • 🪜Co-Lead Interview Guide for Project Coordinators
      • 🪴Apprentice Interview Guide for Co-Leads
      • 📨Email Templates for Communicating to Applicants
  • 🎓MASTERCLASS-PORTAL
    • 🗞️Masterclass Openings
  • 👀OBSERVER PORTAL
    • 😎Observer Dashboard
    • 🙈Life as an Observer
    • 🕵️‍♀️Observer Handbook
      • 🎢Read the Agile Handbook First
      • 🙈What's a Tech Fleet Observer?
      • ❤️The Benefits of Observing
      • ❓Observer Frequently Asked Questions (FAQ)
      • 🚶‍♀️Daily Expectations of Tech Fleet Observers
        • 👩‍🎓Read the Handbooks before Observing
        • 🐐Join Tech Fleet Discord Before Observing
        • Observer Role in Discord
        • 👈Pick Projects to Observe
        • Seeing Project Deliverables as an Observer
        • 👀Day-to-Day as an Observer
        • 🤔Reflecting on Observations in Tech Fleet Discord
        • 🫂Get Support as an Observer
        • ⚒️Using Tools as an Observer
          • 🎨Tech Fleet Figma Educational Account for Observers
        • 🙌Knowing When you're Ready to Finish Observing
      • ❤️Code of Conduct for Observers
      • 🏁Start Observing Today
  • 🪴APPRENTICE PORTAL
    • 🖥️Project Dashboard for Apprentices
    • 🧑‍🚀Apprentice Handbook
      • 🫴Life as an Apprentice
      • Application Process for Apprentices
      • Becoming an Apprentice
      • Discord for Apprentices
      • 🎨Tech Fleet Figma Educational Account for Apprentices
      • Code of Conduct for Apprentices
      • Upholding Community Values as an Apprentice
      • Communication as an Apprentice
      • Leaving Your Project Early
      • Meetings
      • Working styles
      • Using Tools as an Apprentice
      • Organization for Apprentices
  • 🫶CO-LEAD PORTAL
    • 🖥️Project Dashboard for Co-Leads
    • 🪜Co-Lead Handbook
      • 🔥Life as a Co-Lead
      • Application Process for Co-Leads
      • Discord for Co-Leads
      • Code of Conduct for Leads
      • Lead Role Breakdown
      • Upholding Community Values as a Lead
      • Principles as a Lead
      • Day-to-Day Lead Expectations
      • How to Select Your Apprentices as a Lead
      • Interviewing Apprentices as a Lead
      • Leaving Your Project Early
      • Using Tools as a Lead
      • 🎨Tech Fleet Figma Educational Account for Co-Leads
  • ❤️COMMUNITY CODE OF CONDUCT
    • 💟Code of Conduct and Anti-Harassment Policy
    • 🏠Safe Space
  • 📐Policies
    • 🌏Community Collective Agreement
      • 🤗Community Core Values
        • 🫴Tech Fleet's Mission and Values
        • 🤝Tech Fleet Members' Rights
        • ❤️Tech Fleet Pledge of Purpose
        • 🫂Tech Fleet Pledge of Community
      • ❌Prohibited Activity in Tech Fleet
      • 📣Reporting and Resolving Issues
      • 🙅‍♀️Community Enforcement
      • 🌐Transforming Tension & Conflict
    • 👩‍⚖️Tech Fleet's Policies
      • 💼Legal Disclaimers
      • 🖱️Slack and Discord Policy
      • 👩‍🎓Masterclass Terms and Conditions
      • ⏪Services Refund Policy
      • 📓Tech Fleet Bylaws
      • 👤Tech Fleet Board Member Covenant
      • 👁️‍🗨️Conflict of Interest Policy
      • 🔎Information Security Procedures
  • 🏗️GUILD PORTAL
    • 💻Tech Fleet Operations
      • 🥳Tech Fleet Operations Workbook
      • ⚖️Governance
      • 👩‍⚖️Board of Directors
    • 👣Guild Directory
      • 🎓Growth and Development Guild
      • 🚧Infrastructure Guild
      • 🙏Leadership Guild
      • 🪐Product Team Guild
      • 🕧Project Coordinator Guild
      • 📼Video Production Guild
    • ⚒️Guild Handbook
      • 🐣Creating Change in Tech Fleet
      • Code of Conduct for Guilds
      • Guilds in Tech Fleet
      • Creating a new Guild
      • Operating a Guild
      • Guild Bylaws Template
  • 🫶Project Coordinator Portal
    • ⚙️Project Coordinator Handbook
      • Code of Conduct for Project Coordinators
      • Project Coordinator Process
      • Using Tools as a Project Coordinator
      • Project Intake Process
      • Getting the Team Formed
      • Pre-Kickoff as a Project Coordinator
      • Kickoff as a Project Coordinator
Powered by GitBook
On this page
  • Video Version
  • Where We Are in the Agile Pyramid
  • Psychological Safety
  • Psychological Safety Factors
  • Psychological Safety includes Trust
  • Psychological Safety includes Empathy
  • Psychological Safety includes Respect
  • Psychological Safety includes Inclusion
  • Psychological Safety includes Openness
  • Psychological Safety includes Risk Taking and Failure
  • Psychological Safety checklist
  • How to Build Psychological Safety
  • Psychological Safety Video
  • Head to the Next Lesson
  1. Agile Portal
  2. Agile Handbook
  3. Agile Teamwork
  4. Making Strong Agile Teams
  5. Self-Actualized Agile Teams

Psychological Safety

Self-actualized Agile teams must provide space for people to disagree, voice concerns, experiment, and take risks. Learn more below.

PreviousBuilding Agile MindsetsNextService Leadership

Last updated 2 months ago

Video Version

Where We Are in the Agile Pyramid

We are all the way at the bottom of the Agile pyramid for strong teams. Psychological safety is the first thing that must be built in order to build self-actualized Agile teams.

Psychological Safety

Psychological Safety is the core foundation on all Agile teams.

Psychological safety is a shared understanding that team members will not reject or punish people for speaking out, taking risks, or failing.

Psychological safety is a required pre-requisite for Agile work. Without it, Agile teams cannot become fully Agile. Agile teams who have a shared mission, responsible collectively, require psychological safety in order for collaboration to happen. It provides space for people on teams to take risks that are healthy for team progress. With it, they can organize themselves and grow.

If teams can't speak out about things that need to be improved, how can they respond to change? How can they collaborate? How can they produce working results?

Psychological Safety Factors

Psychological Safety includes Trust

Team mates must trust each other to proceed in their work. Trust is earned as teams understand each other and feel comfortable with each other.

Trust happens in many ways. Teams must trust that activities will play out. Teams must trust that even when work fails, the team will progress together. Teams must trust that teammates have each others' backs.

Team mates should not be reprimanded for taking risks or speaking dissent about things that move a team forward. There must be a shared understanding that teams can fail safely knowing they will progress and adjust.

Psychological Safety includes Empathy

Teams should be built with many diverse perspectives and backgrounds. To build psychological safety, each person needs to understand perspectives and people. They need to acknowledge each other, share an understanding, and listen to what they are saying before responding.

Teams that build empathy with each other produce strong psychological safety to be themselves around the team. This is important for empowering teams.

Psychological Safety includes Respect

In addition to trust and empathy, team mates need to respect each other in their work. Respect shows itself in providing room for people to own work, or asking others' opinions before deciding.

Teams who have strong psychological safety discuss and convene to build consensus after listening to each person's perspective who wants to be involved in the conversation.

Psychological Safety includes Inclusion

Team mates need to feel a strong sense of ownership, and value on their team.

Dynamics of power should be shifted and distributed such that each teammate is included in decision making. Each teammate should be included in ownership of work, and have choices of how they get involved.

Each teammate should feel the power of belonging, and feel their work has meaning. Teams should provide inclusive environments for personalities and perspectives to build a strong psychological safety.

Psychological Safety includes Openness

People need to provide space for team mates to be vulnerable and open with each other. Conflict can only be resolved when people know about it, and can speak about it constructively. Disagreements and dissenting opinions should be encouraged when they help a team progress in their work and when teams can talk it out constructively.

They must always respect and empathize with each other through their open conversations. Teammates should be open with each other and candidly discuss items that bring out growth in teamwork, even when they are uncomfortable to discuss.

Every person on the team has a role to play in providing room for open discussions and open perspectives.

Psychological Safety includes Risk Taking and Failure

Strong teams not only allow work failure, they embrace failure as part of their culture. They provide room for people to take risks if it will progress the team in their work.

By giving each other room to try new things, to experiment, they will produce stronger work together and build stronger trust with each other.

Psychological Safety checklist

Here's a way you can check to ensure that psychological safety is strong on your team:

  1. Make every member of the team feel like they have room to speak their mind.

  2. Actively listen when others have things to say, and make team feel like their voice matters.

  3. Give people the room for people to bring their own personalities and unique capabilities to the table in the way THEY want to do so.

  4. Allow room for team mates to challenge the status quo, and experiment with new ways of working.

  5. Encourage failing “fast”, i.e. failure and quick reflection and quick adjustment based on what the team thinks they should do.

  6. Let people take the risks that THEY decide to take, that could lead to failure or disaster, for the purposes of allowing them to build up decision making prowess.

How to Build Psychological Safety

When teams feel a lack of psychological safety, they may be afraid to speak up, and they may lose their motivation to work. They may become more distant or absent in the team. They may think there's no point in bringing feedback up. These are signs that psychological safety may be lacking on the team. When psychological safety is lacking, the team will storm.

This could be due to many things. You as a teammate should work to understand what's going on in the team dynamics before concluding how to resolve it. Teams must work together to identify issues with open conversation and respect toward each other.

Every team member plays a role in success here. Leaders, managers, or team peers may contribute to a lack of psychological safety equally.

To uncover opportunities to build psychological safety, It may be best to proceed with one-on-one conversations, or discuss things in sprint retrospectives constructively. It's important to build empathy and respect for individuals so that they're heard in these discussions. You can only build a psychologically safe team together, united, as one team. Everyone needs to be bought into psychological safety.

Psychological Safety Video

Here's a video about psychological safety and agile:

Head to the Next Lesson

🏃‍♀️
🛹
🤝
💪
🚀
Credit: Tech Fleet
https://youtu.be/E_d01Me8GgU
Credit:
https://www.youtube.com/watch?v=9S4wMnIcdP4