Why This Mode Exists
Briefs are written by people with agendas, blind spots, and organizational pressures. The stated problem is rarely the real problem. A brief asking for "awareness" might actually need repositioning. A brief asking for a "campaign" might need a product fix.
Problem Definition is the mode that earns the most value. Everything downstream — insights, propositions, creative work — is only as good as the problem it's solving. Get this wrong and you'll produce elegant solutions to the wrong question.
The Process
Surface assumptions, then stress-test them
Every brief contains 3-5 embedded assumptions that nobody has examined. "Our audience is millennials" assumes the audience definition is correct. "We need to increase awareness" assumes awareness is the bottleneck. For each assumption, the mode asks: "What if this isn't true?" — not to be contrarian, but to ensure you're building on solid ground.
Three conflicting viewpoints
The mode analyzes the problem from three deliberately opposing perspectives: the client stakeholder who wrote the brief (what are they accountable for?), a skeptical executive questioning the investment (where are the holes?), and the end consumer who doesn't care about any of this (what actually matters to them?).
Where these perspectives conflict is where the real problem lives.
The 5 Whys
Borrowed from root cause analysis, the 5 Whys technique chains "why?" from the surface problem down to its root cause. "Sales are declining" → "Why?" → "Market share is shifting to competitors" → "Why?" → and so on, until you hit the causal mechanism that the brief's stated problem was only a symptom of.
Three reframes
The stated problem gets reframed three ways: human-centric (what does this look like from the audience's experience?), strategic (what do the competitive and market dynamics actually suggest?), and provocative (what if our core assumption is simply wrong?). Each reframe reveals different solutions that the original framing hides.
Defining winning
Using Roger Martin's "Playing to Win" frame, the mode asks: what does winning actually look like for this brand? Not "success" — the ambitious end state. This often reveals that the brief is solving a smaller problem than the one that matters, or that the winning aspiration and the brief's scope are misaligned.
When to Use This Standalone
This is arguably the most valuable WRKFLW mode to use on its own. Anytime you receive a brief, a project request, or even an internal problem statement — run it through Problem Definition before doing anything else. The 15 minutes you spend interrogating the problem will save days of solving the wrong one.
A well-defined problem is half-solved. A poorly-defined problem produces work that looks impressive but changes nothing.