The Approval Problem
You know your team needs development. Your leader needs a business case. These are two different conversations. The first is about people. The second is about money. You need to win the second one to do the first one.
Most business cases for team development fail because they lead with the wrong argument. They talk about engagement, morale, and team spirit. The decision-maker is thinking about revenue, margin, and competitive advantage.
Here's how to build the case that gets approved the first time.
Step 1: Quantify the Problem
Don't start with the solution. Start with the cost of the current problem.
Slow decisions. How many days does your team spend on decisions that could take hours? Multiply the delay by the daily fully-loaded cost of the people involved. For a 10-person team averaging $150K salary, one extra week per decision costs roughly $29,000 in lost productivity. If that happens monthly, that's $348,000 per year in decision delay alone.
Idea suppression. Your team kills ideas without realizing it. The Stop Killing Ideas problem is universal and nearly invisible. You can't quantify every lost idea. You can point to competitors who moved first on opportunities your team discussed and abandoned.
Communication waste. Studies consistently show that 20-30% of project time is wasted on communication failures. Rework. Misunderstanding. Duplicated effort. For a team running $2M in annual projects, that's $400,000-$600,000 in preventable waste.
Turnover. Teams with poor dynamics lose people. Replacing a mid-career professional costs 50-200% of their salary. If your team loses two people per year at $150K each, you're spending $150,000-$600,000 on replacement before you factor in lost institutional knowledge.
Step 2: Present the Evidence
Now show what happens when other organizations fixed these problems.
ArcelorMittal (via Duke CE): 710 leaders went through the Save the Titanic experience and left committed to specific courageous leadership actions. This is direct evidence from a major global organization.
Bell MTS: Revenue grew from $800M to $1.4B after investing in Learn2's experiential approach. Multiple factors contributed. The team development was the multiplier that made everything else work.
Freedom Mobile: Save rates jumped from 47% to 86% after a Learn2 experience. That's $4M per year in retained revenue. The payback period was weeks, not months.
Forzani Group: $26M in additional profit within one year after investing in Learn2's experiential coaching approach.
Rogers: 26,000 customers converted in 6 weeks after a Learn2 experience.
AMEX: 147% increase in insurance sales after a Learn2 experience.
Wharf Hotels: 173% increase in global sales revenue after a Learn2 experience.
These are real results from real organizations. Not projections. Not estimates. Documented outcomes.
Step 3: Build the ROI Model
Keep it simple. Three scenarios.
Conservative: The experience improves your team's decision speed by 20%. Calculate the value of faster decisions across your annual project portfolio. If faster decisions reduce project timelines by even one week each, the savings add up fast.
Moderate: The experience improves a specific revenue metric by 10%. Map it to your team's actual revenue responsibility. Even a small improvement against a large number produces significant returns.
Aggressive: Map the experience to a specific business challenge similar to one of the proof points above. Freedom Mobile's save rate. AMEX's sales conversion. Rogers' customer acquisition. Show what a comparable improvement would mean for your organization.
Present all three. Let the decision-maker pick the one they believe. Even the conservative scenario almost always shows positive ROI.
Step 4: Address the Objections
"We did team building before and nothing changed." That's because most team building is entertainment, not development. Escape rooms aren't team development. The Save the Titanic experience installs six specific, transferable frameworks with measurable workplace applications.
"We can't afford to take the team offline for a day." The experience runs in 3.5 hours. Compare that to the hundreds of hours your team wastes in unproductive meetings, slow decisions, and communication failures every month. The decision tax you're paying right now costs more than a half-day investment.
"How do we measure the impact?" Agree on metrics before the experience. Decision speed. Meeting productivity. Specific revenue or retention metrics. Measure baseline before. Measure again at 30, 60, and 90 days after. The 90-day framework provides a clear measurement structure.
How to measure team development outcomes
Pick a baseline before you start, then measure the shift: decision speed, meeting productivity, and retention at 30, 60, and 90 days. Numbers a CFO trusts beat a satisfaction score every time.
Step 5: Make the Ask
Close with specifics. The investment amount. The expected return range. The measurement plan. The certification option for scaling across the organization.
Don't ask for a meeting to discuss it further. Ask for approval to proceed. Every day between now and the experience is another day of paying the decision tax, losing ideas, and wasting communication effort.
Book a 20-minute walkthrough and I'll help you build the specific business case for your team's situation with numbers your decision-maker will respect.
The strongest case is a clear outcome: a high-performing team that decides faster and solves problems together. Anchor the business case to that.
Read next: How to Justify Premium Team Experiences to Procurement