When stakes are high and the team is under pressure, resistance feels like the last thing we want to hear. We want alignment. We want speed. We want the team to move. And the teams that survive are the ones that stop fighting resistance and start using it.
Why does the team resist when pressure is highest?
Pressure reveals what everyone actually cares about. Under ordinary conditions, team members stay quiet. Under pressure, they fight for what matters. When we meet resistance under pressure, we're not looking at obstruction. We're looking at information about where the real risks live.
The teams we work with at Save the Titanic are in high-stakes moments. Mergers. Crisis decisions. Leadership transitions. Survival depends on alignment. And every single time, resistance emerged. Every single time, the resistance pointed to a gap we'd missed.
The Problem = Solution Model
The thing the team resists is the breakthrough. Not the obstacle. The breakthrough.
The problem the team avoids IS the solution you need.
When a team resists a decision, they're not saying "don't do this." They're saying "this creates a problem you haven't named yet." Name the problem together. Solve it together. The team moves from resistance to resourcefulness in one conversation.
What does this look like in practice?
RBC merged two leadership teams during a major reorganization. One team wanted to move fast. The other wanted to preserve relationships and institutional knowledge. They resisted each other hard.
Instead of forcing alignment through hierarchy, we created a space where both teams could say what they actually feared. The fast-movers feared lost momentum. The relationship-builders feared losing talented people. In three hours, they named both problems. And then they solved them together. They decided which decisions would move fast and which would slow down. They committed to preserve key relationships while moving forward.
The merger stayed on track. The teams stayed together.
In practice: RBC leadership teams surfaced their deepest alignment gaps in a single 3-hour immersive experience. What looked like resistance was actually the map to what mattered most to each group. Once they could see the map, they built a path forward together.
How do we turn resistance into resourcefulness?
Four things happen when we create the right conditions:
First, the team names what they're protecting. The fast-movers weren't avoiding relationships. They were protecting momentum. The relationship-builders weren't avoiding speed. They were protecting people. Once those protections were visible, we could honor both.
Second, the team realizes the problem is shared. Both groups wanted the merger to succeed. Both groups wanted the organization to thrive. They'd been fighting over method, not mission. That realization changes everything.
Third, the team owns the solution. We don't impose a compromise. We create conditions where they build a solution that holds both truths. Fast decisions and preserved relationships. Not one or the other. Both.
Fourth, the team commits together. Because they built it, they own it. Commitment isn't compliance. It's the team saying "we made this together, and we're going to live it."
Try this today:Pick the resistance that's slowing you down. Don't push it away. Ask it a question: "What problem are we avoiding by ignoring this resistance?" The answer is usually the problem you need to solve.
When does Save the Titanic matter most?
When a team must own an outcome and implement under real pressure. When the cost of misalignment is real. When the stakes matter enough to slow down and get it right.
That's when resistance stops being an obstacle and becomes the resource that saves the mission.
See how high-pressure teams turn resistance into resourcefulness in 2 minutes.
Watch the Demo