You Pitched a Solution. You Should Have Pitched the Problem.

It’s Tuesday afternoon. You’re in the Q3 planning review, five slides into your deck. You click to the slide with the beautiful mockups. This is it—the elegant, clever solution your team has been designing for weeks. You’re excited to show it off.

You finish your pitch. Silence.

The VP of Sales squints at the screen. "I don't get it. How does this help my team close deals?" The CFO asks, "What’s the ROI on this? It looks expensive." Your engineering director, who you thought was aligned, says, "This is way more complex than the one-pager described."

Your pitch just died. You had the right answer, but you asked the wrong question. You spent all your time selling the what, and you completely forgot to sell the why.

Stakeholders Don't Buy Solutions; They Buy Solutions to Problems

When you lead with a solution, you force your audience to work backward. They have to reverse-engineer the context, guess the customer pain, and try to connect your beautiful mockups to a business goal they care about. Most won't bother. They'll just poke holes in your idea or tune out.

A solution without a well-defined problem is just a cool project. A problem without a solution is a crisis. Stakeholders are paid to solve crises and fund opportunities, not to approve cool projects.

Selling the problem first changes the dynamic. It shifts the conversation from "Do we like this specific idea?" to "Do we agree that this problem is urgent and worth solving?" Once you get a "yes" on the problem, presenting your solution becomes a formality. It’s the logical next step.

How to Make the Problem Painfully Clear

Getting alignment on the problem isn't about being a pessimist. It’s about being a realist. Your job is to make the problem so tangible that your stakeholders feel the user's pain and see the business cost.

1. Quantify the Pain with Hard Numbers

Abstract problems get ignored. Specific, quantified problems get resources. Go beyond saying "users are frustrated." Find the metric that proves it.

• Instead of: "The checkout process is confusing."

• Try: "We see a 45% cart abandonment rate on the payment page, which we estimate cost us $250k in revenue last quarter. Our top three competitors have a one-click checkout option."

• Instead of: "Our internal dashboard is slow."

• Try: "Our account managers spend an average of 30 minutes a day waiting for customer reports to load. Across the 50-person team, that’s 125 hours of wasted time per week, costing us over $5,000 in salary."

2. Tell the User's Story

Data creates urgency, but stories create empathy. Find a single, powerful example that makes the problem human. Pull a quote from a user interview, a clip from a Gong call, or a support ticket filled with frustration.