LEADERSHIPMonths to result

Trusting Teams Framework

A Circle of Safety is the prerequisite for everything else

Problem it solves

ineffective leadership

Best for

["Leaders inheriting broken or fear-based cultures","Organizations where people hide mistakes rather than learning from them","Teams where information does not flow freely across silos","Leaders who want truth-telling to replace political maneuvering"]

Not ideal for

["Leaders who are not willing to be personally vulnerable first","Organizations looking for a quick cultural fix rather than sustained investment","Leaders who believe fear is an effective long-term motivator"]

Overview

Why this framework exists

Trusting Teams are groups of people who feel safe to be vulnerable around each other. Safe to admit mistakes, point out gaps in their training, share fears and anxieties, and ask for help with the confidence that others will support them rather than exploit that vulnerability. The foundation of Trusting Teams is what Sinek calls the Circle of Safety, an environment of psychological safety that the leader must build and maintain.

Building trust is not a one-time event but an ongoing practice. It starts with the leader taking the first risk. The leader must demonstrate vulnerability before expecting others to be vulnerable. Then employees must reciprocate by stepping into the Circle of Safety. Trust must be continuously and actively cultivated through small, consistent actions: listening, caring, protecting, and following through. True trust takes time, and some people need more time than others.

The framework emphasizes a critical reframing of leadership responsibility: leaders are not responsible for the results; leaders are responsible for the people who are responsible for the results. The best way to drive performance is not to demand it but to create an environment in which information flows freely, mistakes can be highlighted without fear, and help can be offered and received. When this environment exists, performance follows naturally.

Core principles

5 total
  1. Leaders are not responsible for the results; leaders are responsible for the people who are responsible for the results
  2. The leader must take the first risk of vulnerability before expecting anyone else to be vulnerable
  3. Trust is built in small, consistent actions over time, not through grand pronouncements or team-building events
  4. When people fear the consequences of honesty, they will hide the truth; when truth is hidden, problems compound until they become catastrophic
  5. A Circle of Safety must be actively maintained; without ongoing effort, fear will fill the void

Steps

5 steps
  1. Build the Circle of Safety first
    Before trying to improve performance, invest in making people feel safe. Chief Cauley at Castle Rock PD built a fence around the parking lot because employees felt unsafe walking to their cars at night. That simple act sent a profound message: I hear you and I care about you. Start with whatever the equivalent of 'the fence' is in your organization.
    Pro tipHold listening sessions with every member of your team. Ask what they need to feel safe. Act on what you hear.
  2. Model vulnerability as the leader
    Share your own mistakes, uncertainties, and areas where you need help. This gives others permission to do the same. When Mulally celebrated the first honest red status report instead of punishing it, he modeled that truth-telling was safe. If the leader never shows vulnerability, no one else will either.
    WarningSaying 'my door is always open' is not the same as modeling vulnerability. You must go first and go often.
  3. Reward truth-telling, not just good news
    When someone admits a mistake, raises a concern, or reports bad news, your response defines the culture. If they are punished, truth goes underground. If they are thanked and supported, truth flows freely. Mulally's response to Mark Fields' red report transformed Ford's culture in a single moment.
    Pro tipThe next time someone brings you bad news, your first words should be some version of 'Thank you for telling me. How can I help?'
  4. Give second chances based on coachability
    When trust has been broken, assess whether the person is coachable and willing to change. Chief Cauley gave Officer Coyle a second chance because he suspected the culture, not the officer, was the root cause. Coyle responded by becoming one of the most trusted members of the department. Not everyone will respond this way, but many will if given the opportunity.
    Pro tipStay personally involved in the growth of people you give second chances. Check in regularly, coach actively, and hold them accountable while providing a safe space.
  5. Maintain the Circle of Safety through ongoing practices
    Trust is not a destination. It requires continuous cultivation through regular listening sessions, consistent follow-through on commitments, and unwavering protection of the team from outside pressures. Chief Cauley still does his listening sessions. Mulally held his BPR meetings every week without exception. The practice must be permanent.
    Pro tipCalendar your trust-building activities. If it is not on the calendar, it will not happen when the pressure mounts.

Checklist

Saved in your browser

Examples

3 cases
Alan Mulally and Ford's Color-Coded Turnaround

Ford was losing $17 billion when Mulally arrived. Executives hid problems because admitting them meant career consequences. Mulally created a color-coded reporting system and waited patiently for someone to tell the truth. When Mark Fields finally reported a genuine problem with a red chart, Mulally celebrated him instead of punishing him. Within weeks, the truth flowed freely, problems were addressed, and Ford became the only major American automaker to survive the 2008 crisis without a government bailout.

OutcomeDemonstrated practical value
Castle Rock Police Department: From Fear to Trust

Chief Jack Cauley inherited a police department where officers were told they were replaceable, rookies feared advancing ideas, and performance was measured solely in tickets written. He held listening sessions with every member, built a fence for parking lot safety, gave a problem officer a second chance, and transformed the culture from fear-based to trust-based. Jake Coyle went from wanting to leave to being the officer responsible for training new recruits.

OutcomeDemonstrated practical value
The Shell URSA Crew: Trust Under Pressure

When Rick Fox was put in charge of the Shell URSA deep-water oil rig, he built trust by creating an environment where roughnecks, typically macho and stoic, could be vulnerable about their fears and limitations. The result was one of the highest-performing crews in Shell's fleet. Trust first, performance followed.

OutcomeDemonstrated practical value

Common mistakes

3 traps
Building psychological safety only at the top
Trust must extend throughout the organization, not just among the senior leadership team. If frontline employees still fear their direct supervisors, the Circle of Safety is incomplete. At Ford before Mulally, even senior executives feared admitting problems. The fear cascaded downward through the entire organization.
Expecting instant results from trust-building
True trust takes time. Some people take longer than others to step into the Circle of Safety, especially in organizations with entrenched histories of fear-based management. Patience is essential. Leaders who expect immediate cultural transformation will abandon the effort before it takes hold.
Confusing team-building events with trust-building
Ropes courses, retreats, and happy hours can be enjoyable but they do not build lasting trust. Trust is built in the daily interactions: how you respond to mistakes, how you allocate credit, how you handle bad news, how you make decisions about who stays and who goes.

Origin story

How this framework came to be

Sinek draws this framework from multiple sources, but the most vivid is Alan Mulally's transformation of Ford Motor Company. When Mulally arrived as CEO in 2006, Ford was losing billions. He instituted weekly Business Plan Review meetings where executives coded their projects green (on track), yellow (concerns), or red (problems). For weeks, despite the company hemorrhaging money, every executive coded everything green. No one would admit to problems because admitting a problem in the old culture meant getting punished. Mulally kept waiting. Finally, one executive, Mark Fields, showed up with a chart coded red, reporting a serious product issue. The room went silent, expecting Fields to be fired. Instead, Mulally clapped and said 'Great visibility. Who can help Mark with this?' The next week, the room was full of reds and yellows. The truth, previously hidden by fear, finally emerged, and Ford became the only major American automaker to avoid a government bailout during the 2008 financial crisis.

Source

Traced to primary
Source · BOOK
The Infinite Game
Simon Sinek · 2019
Open source →

Related frameworks

Browse all Leadership →