Three Problem Framing principles that help senior leaders make better decisions
I've lost count of how many Directors and Heads of Product have told me the same thing: they spend more time in stakeholder meetings than actually moving work forward.
If that's your reality — where competing priorities, shifting opinions, and the same five debates take up the calendar long before anyone has pinned down the actual problem — you're not alone. And you're not the issue.
The issue is that most rooms full of senior leaders are structured to discuss problems, not to decide on them. Without a method that gets everyone to the same definition of what's worth solving, meetings become a loop. Opinions compound. Decisions stall. And the team underneath you waits.
There is a way out. I've seen it work with product teams at Google, insurance carriers in Europe, manufacturers running global launches, and more recently with organizations trying to make sense of AI. The method is called Problem Framing. We developed it inside Design Sprint Academy and launched it at Google in 2018. Today, I want to walk you through the three principles behind it — the ones that do the real work when a senior leadership room needs to move from debate to decision.
Why senior leaders get stuck — and why it's rarely about the people
The common story is that senior leaders are difficult. They have strong opinions. They push back. They don't commit.
That's the surface. The reality is more nuanced, and it's the reason most stakeholder workshops slowly fail.
By the time a Director, VP, or executive sponsor is in the room, they're carrying three things at once: accountability for a decision, a point of view shaped by their function, and very little structured space to articulate either. So they talk over each other. Or they stall. Or they agree politely and then do nothing.
None of this is a character problem. I think it's a facilitation problem. And it gets worse when the stakes are high — a product launch, a platform move, an AI initiative the CEO just green-lit.
What senior leaders actually need in a room isn't more airtime. They need a structure that does four specific things:
- Gives each leader a moment to be heard and validated, especially by peers at the same level
- Replaces gut-feel debates with evidence they can trust
- Bridges the gap between their helicopter view and what's actually happening on the ground
- Surfaces the silos between them, so they can see each other's constraints for the first time
Miss any one of these, and the meeting defaults back to the loudest voice. Problem Framing is the method built around all four.
What is Problem Framing?
Problem Framing is a structured, one-day workshop that moves a cross-functional group of senior stakeholders from vague ambition to a clear, agreed problem statement.
It's the step before a roadmap, before a Design Sprint, before any solution work. It decides what's worth solving — not how to solve it.
It's built for the moment when your team has a business goal but no clear path, or a mandate but no alignment on what the real challenge is. It's especially useful when the problem is fuzzy, new to the organization, or tangled up with customer behavior.
The workshop has four phases: contextualize the problem, justify the business need, understand the customer, and write the Problem Statement. But the phases aren't the point. The principles underneath them are.
The 3 Problem Framing principles that change how senior leaders decide
Here's the reframe:
Problem Framing isn't about running a better meeting. It's about changing the conditions under which senior leaders make decisions.
Three principles do that work.
1. Strategic empathy — understanding what your stakeholders actually care about
Strategic empathy isn't warmth. It's discipline.
It means being genuinely curious about why each leader in the room holds the position they hold. What metrics are they being measured on this quarter? What political pressure are they carrying? What would make them say no, even if the idea is a good one?
Most teams skip this. They walk into a leadership room with a proposal and wonder why the CFO pushes back on timeline, the Head of Engineering pushes back on scope, and the CMO pushes back on positioning. They're not being difficult. They're doing their jobs. You just didn't frame the conversation in a way that accounted for theirs.
In a Problem Framing workshop, strategic empathy shows up early. Before anyone debates the problem, each leader names their constraints, their success metrics, and what they're worried about. The result: the Director of Finance's insistence on restructuring suddenly makes sense to the Director of Product, who now understands the cost of waiting. The silo dissolves because the map finally shows the interdependencies.
Use it when: you're preparing a stakeholder session and you can already predict which two people will disagree. Map their incentives before the room opens.
2. Evidence-based decision-making — replacing hunches with data they can trust
Ask a senior leader to make a high-stakes call based on a hunch, and you'll get one of two reactions. They'll push back hard — questioning your assumptions, your logic, your process. Or they'll stall and delay the decision until someone else makes it.
Neither is bad behavior. It's self-protective. Uncertainty triggers fight or flight, and executives carry too much accountability to gamble on a gut feel.
Evidence-based decision-making is what lowers that anxiety. Before the workshop, the facilitator does the groundwork: user interviews, market data, operational metrics, customer journey research. During the workshop, that evidence is on the walls, not buried in a deck. Leaders aren't debating whose opinion is right. They're debating what the data is showing them.
This one shift changes the room. A leader who's no longer fighting or fleeing is free to do what they do best — make strategic calls with confidence.
Use it when: you're taking a fuzzy problem into a senior room. Invest three to four weeks of prep time before the session. Without it, the workshop will default to the loudest voice in the room.
3. Effective data visualization — making complexity legible in one session
Data you can't see means data you can't understand.
Most leadership debates go in circles because each person is holding a different mental model of the problem. The Head of Product sees it as a roadmap issue. The Head of Operations sees it as a capacity issue. The Head of Customer Success sees it as a retention issue. They're all right. They just aren't looking at the same picture.
Visualization solves this in a way research decks cannot. A customer journey map, a service blueprint, an opportunity landscape — these let leaders zoom in on the exact moment a user drops off, then zoom out to see how that moment connects to quarterly revenue. In one session.
The numbers behind this are hard to argue with. The human brain processes visuals roughly sixty thousand times faster than text. And when data is presented as text, about 68% of people find it credible. Present it visually, and that number jumps to 97%.
This isn't about pretty slides. It's about making complexity legible, fast, so a room full of busy executives can actually align on what they're looking at before they're asked to decide on it.
Use it when: your problem spans more than one function. If the issue touches product, operations, and customer success, none of them should show up to the workshop with just a spreadsheet. Turn the data into a shared map.
What this looks like in a real room
A few years ago, we ran a Problem Framing workshop with a property and casualty insurance carrier. Their business need came to us in one sentence: "We need to update our strategy to remain competitive."
We spent three weeks in preparation before anyone entered a workshop room. We interviewed brokers, underwriters, and product managers. We mapped the broker journey. We pulled internal data on where deals were being lost. We turned all of it into visuals on the walls.
On the day, six senior leaders walked in carrying six different versions of the problem. By the end of the day, they had one shared Problem Statement:
"Our brokers struggle to match clients with the right insurer when our processes fragment their workflow, which pushes them toward competitors and costs us new business."
That sentence became the brief for the next product sprint. No one needed to revisit the debate. The Problem Statement held.
This is the work Problem Framing does. It simply makes the decision stick.
When Problem Framing is the right investment — and when it isn't
Problem Framing is a real commitment. Three to four weeks of prep. Six to eight senior leaders for a full day. A facilitator who can hold a difficult, opinionated room without defaulting to the loudest voice.
That's worth the investment when:
- The problem is fuzzy — hard to articulate in a single sentence, or redefined every time someone new joins the conversation
- The problem is new to your organization or industry — common with AI initiatives, platform transitions, or emerging customer segments
- The problem is people-related — involving adoption, behavior, trust, or motivation that no dashboard will explain
- The problem is blocking strategic growth — churn, wasted engineering time, missed OKRs, competitive erosion
- The path is unclear even when the strategic goal is obvious ("we need to grow in Segment A" without a clear next move)
It's the wrong investment when you already have a validated problem and the team is aligned on what to do next. In that case, skip straight to a discovery track, or execution. Framing is for the step before.
The strategic takeaway
When you bring Problem Framing into a senior leadership room, you're not adding another meeting. You're changing the decision-making conditions.
Each leader gets the structured space to be heard. The data calms the part of them that's been operating in fight or flight. The visualization pulls them out of their silo and into a shared picture. And the output isn't a longer list of opinions — it's a Problem Statement the team can execute against.
Fewer debates. Faster decisions. And a product, platform, or initiative that hits the mark for the people who matter most — your customers, and the leaders who have to stand behind the call.
If you're tired of running the same debate with the same people and walking out with the same ambiguity — it's worth looking at Problem Framing. Not because it's a framework to adopt. Because it's the discipline most organizations skip, and the one that separates teams that build the right thing from teams that just keep building.
PS:
If you are a visual learner - 🎥 Watch our free video where we dive deeper into how Problem Framing helps senior leaders make better decisions. It’s packed with insights, real-world examples, and actionable tips to transform your approach.
.png)
