Should you invest in a Problem Framing Workshop? A checklist to help you decide

_{A Problem Framing workshop is worth the investment when the problem itself is unclear, the stakes are high, and stakeholders disagree on what to prioritize — and it isn't worth it when the problem is already well-defined and the team is genuinely aligned. The five questions below tell you which situation you're actually in.}

What is a Problem Framing workshop, briefly

A Problem Framing workshop is a one-day session that brings six to eight senior decision-makers into the same room to align on what's actually worth solving, before any time, budget, or engineering resources are committed to a solution. It's preceded by two to three weeks of preparation that turns existing research, customer data, and business context into evidence the room can engage with. The output is a clear, agreed problem statement (or several) that every key stakeholder has signed off on.

For the full method, see What is Problem Framing?. For how it compares to a Design Sprint, see Should you run Problem Framing or a Design Sprint?. This article is for the upstream decision: should you be running one at all?

What does the investment actually look like?

Before the checklist, it helps to know what you're committing to. A facilitated Problem Framing workshop typically involves three pieces of investment:

Preparation: two to three weeks before the workshop. This is where most of the work happens. A facilitator reviews existing research, gathers internal data, runs short interviews with key stakeholders to surface what each one believes the problem is, and turns the inputs into visual artifacts the room can debate against — customer journey maps, industry context maps, evidence walls. When DSA facilitates, this is done by us. When an internal facilitator runs it, it usually lands on a Product Manager, Innovation Manager, UX Lead, or Agile Coach who already understands the organization's dynamics.

The workshop day: six to eight senior leaders, eight focused hours. The whole point is to have the people with real authority in the same room at the same time, interacting with the same evidence. Without the right stakeholders, the workshop produces output that won't hold when they leave it.

Synthesis: one to two weeks after. The facilitator turns the outputs into a clean problem statement and a short, actionable report that becomes the brief for whatever comes next — a Design Sprint, targeted research, a roadmap decision, or a go/no-go on the problem itself.

The cost of a fully facilitated Problem Framing engagement with DSA is €25K, with an optional Moving Forward Workshop add-on at €10K. The cost of skipping Problem Framing and building the wrong thing is anchored at whatever the engineering team would have spent — which is almost always an order of magnitude more.

Most teams skip this step anyway. A Harvard Business Review study found 85% of executives agreed their organizations are bad at diagnosing problems, and 87% said this flaw carries significant costs. The checklist below is built to tell you whether your specific situation is one of the ones worth not skipping.

The six-question checklist

Use this checklist with the specific decision your team is about to make in mind — not Problem Framing in the abstract. If your answers point to four or more yeses, the investment is justified. One important note before you start: Question 6 is heavily weighted. If senior stakeholders are misaligned with personal agendas in play, that alone often justifies the workshop — even when the other questions score lower.

Question 1: Is the problem fuzzy — hard to define or explain in one sentence?

If your team can't articulate the challenge in one clear sentence — or keeps circling back to redefine it every meeting — the problem is fuzzy, and that's the strongest single signal that Problem Framing fits.

Fuzziness isn't a sign of a weak team. It usually means the situation has more than one plausible problem hiding inside it, and the room hasn't yet had a structured moment to surface them and choose. Problem Framing is built for exactly that — moving a room from "we know something is wrong" to a single, agreed articulation of what.

The test: ask three people on your team to write the problem in one sentence. If you get three different problems back, the fuzziness is real.

Question 2: Has this problem not been solved before — by you or anyone in your industry?

If there are no obvious benchmarks, no past internal projects that cracked it, and no competitor playbook to copy, the problem is genuinely new — and new problems reward structured framing more than execution speed.

This comes up often with AI initiatives, new customer segments, platform transitions, regulatory shifts, and any situation where leadership has decided the company needs to move into territory it hasn't operated in before. The pattern is consistent: the absence of a reference point makes teams jump to action faster, not slower, because uncertainty feels uncomfortable. Problem Framing slows the moment down enough to define what you're actually moving toward.

The test: if you searched internally for the last time anyone tackled this problem and came up empty, treat that as a yes.

Question 3: Is the problem people-related — affecting customer, employee, or stakeholder behavior?

If the challenge involves human behavior — adoption, perception, trust, motivation, resistance — dashboards alone won't surface the answer, and the workshop pays for itself by combining business evidence with customer reality.

Questions that sound like "we don't understand why customers aren't doing X" or "the team keeps resisting the new workflow" or "brokers are frustrated but we can't pin down where" sit in this territory. They have quantitative symptoms — churn, drop-off, NPS, ticket volume — but the root causes live in behavior, and behavior needs to be made visible before it can be acted on.

The test: if the most important question your team is asking starts with "why are people (not) doing X," treat that as a yes.

Question 4: Is the problem blocking business growth or putting competitive position at risk?

If solving the problem badly carries a real cost — missed OKRs, lost revenue, wasted development cycles, a strategic initiative stuck in committee — the investment in framing it correctly pays back the first time it prevents the wrong call.

The inverse is also useful: if the answer is "it would be nice to solve, but nothing big breaks if we don't," Problem Framing is probably not the right move yet. The workshop is most valuable when there's real consequence behind getting it right. It's least valuable when used to dress up a low-stakes initiative as more strategic than it is.

The test: if you can name what specifically gets harder, slower, or more expensive in the next two quarters if the problem stays unsolved, treat that as a yes.

Question 5: Is the problem tied to a strategic goal — but the path to get there is unclear?

If leadership has named the destination ("grow in segment A," "improve retention," "modernize the broker experience") but no one has named the obstacles or the route, Problem Framing is the work that turns the destination into a problem statement teams can actually act on.

This is the most common pattern at the Director and Head-of level. A senior leader sets a direction. The teams below them break into separate initiatives, each with a different theory of what the destination requires. Six months in, the initiatives diverge and the leader notices. Problem Framing earlier in the cycle would have given the teams a shared problem statement to organize around, rather than a shared destination with no agreed path.

The test: if your leadership has handed down a goal, and you can list at least two credible interpretations of what the team should be working on to hit it, treat that as a yes.

Question 6: Are senior stakeholders misaligned — with personal agendas, political stakes, or competing priorities in play?

If your senior team agrees the problem exists but can't agree on what to do about it — or if different stakeholders are quietly defending different solutions because their function, budget, or reputation rides on them — Problem Framing is one of the few formats built to surface that openly and force a shared decision.

This is the question most teams underweight, and it's often the one that matters most. A problem can be reasonably well-defined and still need framing because the room hasn't actually committed to it. Personal agendas don't make a team dysfunctional — they make a team human. But they do make decisions stick to the loudest voice instead of the strongest evidence, and they're the reason workshops without structured facilitation tend to collapse into political theater.

Problem Framing addresses this directly by putting evidence in front of the room before opinion, surfacing each stakeholder's view in a structured way, and using a Decider with the authority to make the final call. The workshop earns its place not by solving the political dynamics, but by giving them a productive container.

The test: if you can name two senior stakeholders who would push for different directions if you asked them today — for reasons that aren't purely analytical — treat that as a yes.

Note: a complicated problem (many moving parts, requires expertise to navigate) is exactly the kind of situation where Question 6 surfaces. A complex problem (genuinely unpredictable, no right answer until you act) is a different category and may need experimentation rather than framing.

Scoring the checklist

Count your yeses. The threshold is straightforward, but Question 6 carries extra weight.

A real example: a property and casualty insurance carrier

One of our clients — a property and casualty insurance carrier — came to us with a business need framed at the highest level: "We need to update our strategy and services to remain competitive in the market."

When we worked with their Business and Operations team to translate that into something more specific, they landed on: "We're struggling to meet brokers' expectations with our processes and tools. This frustrates brokers, makes them look elsewhere, and creates missed business opportunities for us."

Nobody on the team disagreed that the problem was real. They disagreed on what to do about it. Some leaned toward redesigning the tools brokers used. Others wanted to invest in broker relationship management. A few weren't sure where the root cause actually was.

We ran the situation through the six-question checklist before recommending anything:

1. Fuzzy? Yes — the root causes were tangled across outdated tools, communication gaps, and process fragmentation. Different leaders carried different theories.
2. Unsolved? Yes — previous fixes like static guides and one-off communications had not addressed the core friction.
3. People-related? Yes — brokers, underwriters, product teams, and customer service were all affected, and the symptoms showed up in broker behavior.
4. Growth impact? Yes — broker frustration was producing lost deals and putting competitive position at risk.
5. Strategic fit? Yes — strengthening broker relationships was already a top-three strategic priority for the year.
6. Stakeholder misalignment? Yes — the Business team wanted to redesign the tools, the Operations team wanted to invest in broker relationship management, and the Product team thought the friction was upstream. Each had budget implications for their function. The disagreement wasn't analytical; it was structural.

Six yeses. That clarity gave the team — and the executive sponsor signing the budget — the confidence to commit to a facilitated Problem Framing workshop. The output became the brief for their next sprint and the redirection of their product roadmap for the following two quarters.

The point of the example isn't that the workshop was magic. The point is that the checklist made the investment decision concrete enough to defend upward, which is usually the harder part of the call.

What to do if you don't reach four yeses (and Q6 is no)

If the checklist comes back below the threshold and stakeholder misalignment isn't in play, the honest call is usually one of three things.

The problem is more defined than you assumed. Sometimes a Director or Head of senses there's a problem to frame, but a structured conversation with the team reveals that everyone is actually aligned and the perceived ambiguity is one person's hesitation. The right move is to surface that, name the alignment that already exists, and move into execution.

The stakes don't yet warrant a full facilitated day. Not every problem needs a workshop. A focused stakeholder interview round, a shorter alignment session, or a written one-pager circulated for sign-off can solve smaller alignment issues without the prep overhead of a full Problem Framing engagement.

The timing is wrong. Sometimes the problem will mature into a clearer Problem Framing situation in a quarter or two, as more is at stake or as the team accumulates the data to surface the disagreement. Running framing too early — before stakeholders have enough context to debate against — produces a thin workshop that everyone leaves unconvinced by.

In any of these cases, the right answer is to wait, not force the investment.

The strategic takeaway

If your current challenge checks at least four of the six boxes — or if Question 6 is a clear yes on its own — you're not looking at a problem you can power through with execution. You're looking at a strategic blind spot, a stuck room, or both. Neither one fixes itself.

Problem Framing doesn't slow teams down. It prevents the wrong work from being done at scale. When the cost of getting it wrong is high — which is most of the time at Director and Head-of level — framing the problem properly is the cheapest decision your team can make.

Frame it before you fix it.

Want to see how Problem Framing actually works?

The fastest way to decide whether Problem Framing fits your situation is to see the method run end-to-end — the preparation, the workshop structure, the exercises, and how a room moves from misalignment to a single agreed problem statement in a day.

That's exactly what the Problem Framing on-demand course shows you. It walks through the full method DSA uses with senior stakeholders at SAP, HSBC, Adidas, RGAx, and eBay— the same structure used in every facilitated engagement.

About six hours of core content, self-paced. You can take it as a reference library while running your own session, or as the basis for facilitating Problem Framing yourself if that's the path that fits.