Project managers running a team that is busy but not winning: the fix is not a new tool, a new methodology, or a bigger budget. Google spent two years and a great deal of money proving that.
In 2012 the company launched Project Aristotle, a study of its own teams, to find out why some of them consistently outperformed others. The researchers expected the answer to be talent: the right mix of skills, the smartest people, the strongest individual performers. It wasn’t. The teams that won were the ones where people felt safe to speak up, admit a mistake, ask a question, or disagree with the person running the meeting. The researchers called it psychological safety, and it predicted team performance better than anything else they measured.
First-Mouse Mistakes: 5 PMP Prep Errors That Spring the Trap
That finding is the spine of this five-post series on what elite teams actually do. Not the most talented teams. The ones that perform under pressure, on purpose, repeatedly. Mission control. A surgical team. A flight crew. A pit crew. They have almost nothing in common on paper, and one thing in common in practice: the junior person will speak, and the senior person will listen.
What “elite” means, and what it doesn’t
Elite doesn’t mean expensive, and it doesn’t mean military. It means a team whose performance on the worst day looks like its performance on a normal day, because the team has built habits that hold up when stress goes up. Every other characteristic of high-performing teams you’ll read about, clear goals, defined roles, accountability, mutual trust, depends on people being willing to say the uncomfortable thing out loud.
The evidence keeps stacking up. A Wiley Workplace Intelligence survey of more than 1,500 professionals found a 36-point performance gap between teams where people could speak freely without fear of judgment and teams where they couldn’t. Gartner found high-performing executive teams were 20% more likely to report psychological safety than low-performing ones. Different researchers, different populations, same variable.
Two stories show what that variable looks like when it’s missing and when it’s built in. One is from a cockpit in 1978. The other is from a software company in 2012.
Do You Have Wise Team Members? 5 Traits That Turn Project Chaos Into Calm (and How to Develop Them)
The night a cockpit went quiet
On December 28, 1978, United Airlines Flight 173 approached Portland, Oregon, with 189 people on board. When the crew lowered the landing gear, an indicator light failed to confirm it was locked. The captain, an experienced and well-regarded pilot, entered a holding pattern to troubleshoot and to prepare the cabin for a possible gear failure on landing.
He circled for about an hour. During that time the flight engineer mentioned the fuel state more than once, but tentatively, in the deferential way a junior officer spoke to a captain in that era. The captain was focused on the gear problem and didn’t register the warning as urgent. The engines flamed out one by one. The DC-8 came down in a wooded suburb six miles short of the runway. Ten people died.
The National Transportation Safety Board’s finding was blunt: the captain failed to monitor the fuel, and the other crew members failed to communicate their concern forcefully enough to break his fixation. The information that would have saved the flight was already in the cockpit. Nobody said it loudly enough, and nobody was listening for it.
The data that saves the project is usually already in the room. The question is whether anyone feels safe enough to say it, and whether the person in charge is listening for it.
Flight 173 became the turning point for what the aviation industry now calls Crew Resource Management, or CRM. Airlines rebuilt cockpit culture from the ground up: first officers and flight engineers are trained and expected to challenge the captain, and captains are trained to invite that challenge. CRM is standard on every major airline in the world today, and it’s one of the main reasons commercial aviation became the safest form of transport in history. A gear light in Portland did that.
How a craft marketplace solved the same problem in software
Thirty-four years later, an engineering leader at Etsy named John Allspaw published a short post on the company’s engineering blog describing how the team handled outages. When something broke, the engineers involved wrote up exactly what happened, in detail, in front of their peers. What they did not do was get punished for it. Etsy called the practice the blameless postmortem.
The logic was simple. If an engineer who pushed a bad change knows they’ll be blamed, they will describe the incident as vaguely as possible and the organization learns nothing. If they know they won’t be, they’ll tell you every detail, including the three things that looked fine at the time and turned out to matter. The team gets better information, fixes the underlying cause faster, and the same failure stops recurring.
The practice spread across the software industry and is now a default in site reliability engineering. Project managers already know it by an older name: lessons learned. The difference is timing and tone. Most lessons-learned sessions happen once, at the end of the project, when it’s too late to change anything, and they quietly turn into a search for who to blame. Elite teams run them after every significant incident, while the project is still live, and they take the blame out so the truth can come in.
Embracing Failure: How Project Managers Can Transform Setbacks into Stepping Stones
What this looks like on a project team
Psychological safety isn’t a feeling you announce. It’s a set of behaviors you model, and the first few weeks decide whether the team believes you. Here is what works, in the language of the PMP® exam’s People domain:
- Write it into the team charter. The charter is where you set ground rules, so put the rule there explicitly: any team member can raise a risk or stop a decision without needing permission. Toyota has run its production lines this way for decades. Any worker can pull the andon cord and stop the line, and managers treat the pull as a gift, not a problem.
- Go first. In the first retrospective, name a mistake you made. Not a humble-brag. A real one. The team is watching to see what happens to people who admit errors, and the safest way to show them is to be the first person it happens to.
- Reward the flag, not the fix. When someone raises a risk that turns out to be real, thank them in front of the team, specifically for raising it early. Most teams only celebrate the person who solved the problem. That teaches everyone to wait until they have a solution before they speak.
- Run blameless reviews within 48 hours. After any incident that cost the project time or money, hold a short review while memories are fresh. Ask what happened, what made the wrong choice look reasonable at the time, and what would make it impossible to repeat. Never ask who.
- End every status meeting with one question. “What are we not saying?” Then wait. The silence is uncomfortable for about four seconds, and then the thing that matters comes out.
How to Use the 5 Whys Technique at Work (Step-by-Step With Examples)
Why the exam cares about this
The PMP exam tests the People domain because PMI has watched projects fail for decades and knows where the failures come from. Leading a team, supporting team performance, removing impediments, managing conflict: every one of those tasks is easier on a team where people talk, and nearly impossible on one where they don’t. The exam doesn’t use the phrase psychological safety. It just keeps asking you what you’d do when a team member goes quiet.
The research base cited in this post: Google’s Project Aristotle (findings published via re:Work), the Wiley Workplace Intelligence high-performing teams survey (reported November 2025), and Gartner’s 2023 executive-team survey. PMI’s July 2026 update to the PMP exam kept people leadership at the center of the test while expanding business-context content.
Next in the series: elite teams are small and fast. What a 1943 aircraft program and a 2020 vaccine program taught us about agile project management.
Unleash Your A-Game: Building an All-Star Project Team (and Becoming an A Player Yourself)
Elite teams have a coach
One more thing every elite team in this series has in common: nobody on them learned the job alone. Flight crews train with instructors. Mission controllers were drilled by simulation supervisors. Surgical teams rehearse under senior surgeons. The self-taught elite team doesn’t exist.
From Pit Lane to Project Milestone: What System Project Leaders Can Learn from Formula 1 Drivers
| Prepare for the PMP® with an instructor in the room
The PMP Live Class is four days of live, instructor-led training, 35 contact hours that satisfy PMI’s education requirement, with practice questions and case studies worked through in real time, so the concept that trips you up gets answered the moment it trips you up. The Pro plan adds one-on-one coaching for the parts of the exam you want to pressure-test privately.
|