Good Is Not Great
Good teams deliver. They hit deadlines. They follow processes. They execute plans competently. In stable conditions, good teams look great.
Then the plan fails. The client changes scope. The market shifts. The key person leaves. The deadline moves up by three weeks. And in that moment, the difference between good and great becomes visible.
Good teams freeze, regroup, escalate, wait for new instructions, and lose days or weeks before momentum returns. Great teams adapt in real time. They don't wait for new instructions because they understand the intent behind the original ones. They adjust the approach while preserving the outcome.
The behavior that makes this possible is simple to describe and difficult to develop: great teams build on each other's thinking instead of evaluating it.
What Building Looks Like
In the Save the Titanic experience, participants face a cascading crisis. The iceberg has struck. Water is rising. The situation changes every few minutes. Plans that worked 20 minutes ago are obsolete.
The behavior difference is stark. In good teams, someone proposes an idea. Others evaluate it. "That won't work because..." "We tried something like that before and..." "The problem with that is..." Each evaluation slows the team. By the time they've finished evaluating, the situation has changed and the idea is moot anyway.
In great teams, someone proposes an idea. Others build on it. "Yes, and we could also..." "If we do that, then we could also..." "Building on that, what if we..." The idea evolves in real time, incorporating multiple perspectives and adapting to changing conditions simultaneously.
This is Yes And in action. It's one of the six key learnings in the Save the Titanic experience, and it's the behavior that most reliably separates teams that adapt from teams that stall.
The Evidence
When ArcelorMittal put 710 leaders through the experience with Duke Corporate Education, the data was clear. Teams that defaulted to building behavior outperformed evaluating teams on every measure: more passengers saved, faster decision cycles, and more creative solutions to problems that didn't have obvious answers.
The pattern holds across every Learn2 client engagement. Freedom Mobile's save rate jumped from 47% to 86% ($4M annual value) when frontline teams shifted from evaluating customer solutions to building on them. Representatives who said "Yes, and here's another option..." retained customers that "well, the policy says..." lost.
Bell MTS grew from $800M to $1.4B. The sales teams that grew revenue weren't the ones with the best individual performers. They were the ones where team members built on each other's customer insights instead of competing with each other.
Why Evaluating Feels Right and Performs Wrong
Evaluating feels like rigor. Critical thinking. Due diligence. Organizations reward the person who spots the flaw. "Good catch" is a compliment. "That won't work because of X" signals intelligence.
The problem is that evaluation kills momentum. In stable environments with plenty of time, rigorous evaluation improves quality. In dynamic environments where speed matters — which is most of business today — evaluation creates a bottleneck that great teams avoid.
Building doesn't mean accepting bad ideas uncritically. It means engaging with the intent behind the idea rather than attacking the form it takes. When someone says "we could contact all 500 clients this week," a building response isn't "sure, let's do that impossible thing." It's "the intent to reach clients quickly is right — could we prioritize the top 50 and contact them today?"
The idea improved. The momentum continued. The person who proposed it feels valued instead of shut down. They'll propose again next time instead of going quiet.
Developing the Behavior
You can't develop this behavior by telling people to do it. Telling a team "be more collaborative" is like telling someone "be funnier." The instruction doesn't contain the mechanism.
The behavior develops through practice under pressure. In a 3.5-hour immersive simulation, teams experience the consequences of evaluating versus building in real time. When evaluation costs them passengers and time, the lesson is visceral. When building produces creative solutions to impossible-seeming problems, the habit begins forming.
The debrief makes it conscious. Participants identify the moments where building worked and the moments where evaluating stalled them. They develop language for recognizing each pattern in daily work. "We're evaluating right now — could we try building?" becomes a team correction that requires no authority to invoke.
The Compound Effect
Great teams that build consistently develop advantages that compound. They make decisions faster because building produces workable solutions in minutes instead of evaluation cycles that take days. They attract better talent because high performers want to work where their ideas get built on, not shot down. They innovate more because innovation requires hundreds of ideas refined through building, not dozens of ideas filtered through evaluation.
The results organizations achieve through this single behavior change are consistently impressive. Not because building is magic. Because building unlocks the team's existing capability that evaluation was suppressing.
The Simple Shift
In your next meeting, try one thing. When someone proposes an idea, respond with "Yes, and..." instead of "Yes, but..." or "The problem with that is..." Do it once. Notice what happens to the conversation. Notice what happens to the energy in the room. Notice what happens to the quality of the idea after three people have built on it.
That's the behavior. That's the difference between good and great. It's available to every team starting in their next meeting.
The Save the Titanic experience doesn't just teach this behavior. It proves its value under pressure, creates shared commitment to practicing it, and gives the team vocabulary for sustaining it. One experience. One behavior. A fundamental shift in team performance.
Book a 20-minute walkthrough and I'll show you how the simulation reveals whether your team builds or evaluates — and the performance difference it makes.
Read next: How to Justify Premium Team Experiences to Procurement