Contents
Use this when you have a problem worth solving but need to resist the gravitational pull of your first idea. The Productive Thinking Model walks you through six deliberate steps — from understanding the real problem to generating dozens of possible solutions to building an actionable plan — ensuring you don't collapse the creative space before you've actually explored it.
Section 1
What This Tool Does
The most expensive mistake in problem-solving isn't choosing the wrong solution. It's solving the wrong problem with the right one. Teams burn quarters — sometimes years — executing brilliantly against a problem statement that was never interrogated, building features nobody asked for, restructuring departments around a diagnosis that felt obvious but was never verified. The Productive Thinking Model exists to prevent that specific failure.
Tim Hurson introduced the framework in his 2007 book Think Better, drawing on decades of applied creativity research — particularly the foundational work of Alex Osborn and Sidney Parnes in Creative Problem Solving (CPS). What Hurson did was distill the sprawling CPS methodology into six discrete, memorable steps that a team could execute in a single working session or across several days, depending on the problem's weight. The six steps: What's Going On? What's Success? What's the Question? Generate Answers. Forge the Solution. Align Resources. Each step has a specific cognitive function, and the sequence matters. You don't get to generate solutions until Step 4. Three full steps of problem definition come first. That ratio — half the process devoted to understanding the problem, half to solving it — is the model's most radical claim.
The core cognitive shift: separating the act of understanding a problem from the act of solving it, and giving the understanding phase equal or greater weight. Most people, confronted with a challenge, leap to solutions within seconds. Psychologists call this "satisficing" — accepting the first adequate option rather than searching for the best one. Hurson calls the first idea "the monkey mind's answer," and his model is designed to make you hold that answer at arm's length while you do the harder, slower work of figuring out what you're actually dealing with.
The mechanism is structured divergence followed by structured convergence, repeated across all six steps. In each step, you first generate as many options as possible (diverge) — problem definitions, success criteria, questions, solutions — and then select the most promising ones (converge). This dual rhythm prevents two failure modes simultaneously: premature closure (picking the first idea) and analysis paralysis (generating ideas forever without choosing). The model gives you explicit permission to be expansive and explicit instructions to narrow down. Both, in sequence, every time.
What makes the Productive Thinking Model distinct from generic brainstorming or design thinking is its insistence on problem definition as a creative act. Steps 1 through 3 don't just clarify the problem — they reframe it, often multiple times, until the team arrives at a question that, when answered, would actually constitute progress. That reframing process is where most of the value lives. A team that enters the session asking "How do we reduce churn?" might exit Step 3 asking "How might we make the first 72 hours so valuable that customers never consider leaving?" Same domain. Entirely different solution space.
Section 2
How to Use It — Step by Step
Instructions on the left. Worked example — a mid-stage B2B SaaS company whose enterprise sales cycle has lengthened from 45 days to 90+ days over two quarters — on the right.
Step 1 — Explore
What's Going On?
Map the current situation from multiple angles. List what you know, what's bugging you, who's affected, and what you've already tried. This is an inventory, not an analysis. Use Hurson's "DRIVE" framework: what do you want that you Don't have? What are you getting that you don't want (Remove)? What do you have that you want to keep (Invest in)? What don't you have and don't want (Void)? What's the broader context (Environment)? Generate at least 15–20 observations before filtering. Then circle the 3–5 that feel most important or surprising.
Worked example
SaaS enterprise sales slowdown
Don't have: Deals closing in under 60 days. Clear visibility into where deals stall. Confidence in pipeline forecasts. Remove: Procurement bottlenecks that add 3–4 weeks. Redundant demo stages requested by different stakeholders. Invest in: Strong champion relationships at target accounts. High win rate once deals reach final stage (78%). Void: Don't want to compete on price discounting to accelerate deals. Environment: Two new competitors entered the space in Q2; economic uncertainty making CFOs scrutinise all new spend. Circled priorities: procurement bottleneck, stakeholder demo redundancy, CFO scrutiny on new spend.
Step 2 — Define
What's Success?
Describe the future state you want — vividly and specifically. Hurson calls this the "Target Future." Write it as if you're describing what the world looks like after the problem is solved. Include observable outcomes, measurable targets, and emotional states. Then list the criteria any solution must satisfy (the "ITCH" — Influence, Time, Cash, How measured). This step prevents the common failure of solving a problem without knowing what "solved" looks like.
Worked example
Defining the target future
Target Future: "Enterprise deals close in 60 days or fewer. Sales reps spend less than 20% of their time on procurement logistics. Every stakeholder who needs to see a demo sees one within the first two weeks, not scattered across months. Pipeline forecasts are accurate within ±15%. The sales team feels momentum, not dread, when they see an enterprise opportunity." ITCH criteria: Must not require adding headcount (budget frozen). Must show measurable improvement within one quarter. Must not compromise deal quality or win rate. Success measured by median days-to-close and forecast accuracy.
Step 3 — Reframe
What's the Question?
Convert your understanding into catalytic questions — questions that, if answered well, would bridge the gap between current reality and the target future. Use the stem "How might we...?" to keep questions open and generative. Generate at least 10–15 different questions, then select the 2–3 most powerful. The best question is often not the most obvious one. Look for questions that reframe the problem entirely — questions where the phrasing itself suggests a different solution space than you started with.
Worked example
Generating catalytic questions
Brainstormed questions: How might we eliminate the need for multiple demo stages? How might we get procurement involved in week one instead of week eight? How might we make the CFO's risk calculus work in our favour? How might we compress the stakeholder alignment phase? How might we make our product so self-evident that demos become optional? How might we turn the 78% final-stage win rate into a selling point itself? How might we restructure the deal so the buyer feels urgency, not us? Selected: (1) "How might we get every decision-maker aligned in the first two weeks?" (2) "How might we make procurement a partner in acceleration rather than a bottleneck?" (3) "How might we make the cost of not buying obvious to the CFO within 30 days?"
Step 4 — Generate
Generate Answers
Now — and only now — brainstorm solutions. Take each catalytic question and generate as many answers as possible. Aim for quantity: 20–30 ideas per question. Use "third-third" thinking: the first third of ideas will be obvious (everyone has them), the second third will be more creative, and the final third — when you push past the feeling of being tapped out — is where the genuinely novel ideas live. No evaluation during this phase. Write everything down. Then select the 5–8 most promising ideas using your ITCH criteria from Step 2.
Worked example
Generating solutions for question #1
First third (obvious): Send pre-demo materials. Schedule a group demo. Create a stakeholder map earlier. Second third (creative): Build an interactive product sandbox that stakeholders can explore asynchronously. Create a 3-minute "executive briefing" video customised per account. Have the champion run an internal demo using our materials. Third third (novel): Host a "value workshop" in week one where all stakeholders co-design their implementation plan — making the demo a collaborative working session, not a presentation. Offer a 14-day pilot with real data so stakeholders experience the product instead of watching slides. Create a "deal room" portal where every stakeholder can see progress, materials, and ROI projections in real time. Selected ideas: Value workshop, deal room portal, executive briefing video, 14-day data pilot.
Step 5 — Evaluate
Forge the Solution
Take your shortlisted ideas and stress-test them. Hurson recommends the "POWER" criteria: Positives (what's good about this idea?), Objections (what could go wrong?), What else (how could we modify it to address the objections?), Enhancements (how could we make it even better?), Remedies (what's the fallback if it fails?). This structured evaluation prevents both uncritical enthusiasm and reflexive dismissal. The goal is to transform raw ideas into robust solutions.
Worked example
Forging the value workshop concept
Positives: Gets all stakeholders in one room early. Shifts the dynamic from "vendor pitching" to "collaborative planning." Creates emotional investment in the outcome. Objections: Hard to get 6–8 senior people in one room. Requires significant prep from our team. Could expose product gaps in a live setting. What else: Offer it as a 90-minute virtual session with a pre-recorded product walkthrough sent 48 hours before. Assign a solutions engineer to prep a custom environment. Enhancements: Include a live ROI calculation using the prospect's actual data — makes the CFO's decision easier. Remedies: If attendance is low, the deal room portal serves as the asynchronous fallback. Combined solution: a "Week One Value Sprint" — virtual workshop with pre-work, live ROI modelling, and a persistent deal room for follow-up.
Step 6 — Plan
Align Resources
Convert the forged solution into an action plan. Identify who does what, by when, with what resources. Hurson emphasises identifying "assistors" (people and factors that will help) and "resistors" (obstacles and objections you'll face). Build your plan to leverage the assistors and neutralise the resistors. Set specific milestones and define how you'll know the solution is working.
Worked example
Action plan for the Week One Value Sprint
Actions: (1) Solutions engineering builds a customisable workshop template — owner: SE lead, 2 weeks. (2) Sales enablement creates the executive briefing video framework — owner: marketing, 3 weeks. (3) Product team provisions sandbox environments for pilot accounts — owner: product ops, 2 weeks. (4) Sales team pilots the new process on 5 enterprise deals in Q1 — owner: VP Sales. Assistors: Champion relationships are strong (leverage them to convene stakeholders). 78% win rate at final stage means the product sells itself once people see it. Resistors: Sales reps may resist the upfront prep work. Procurement teams may not engage early without incentive. Milestones: Median days-to-close for pilot deals vs. control group, measured at 90 days. Target: 55 days or fewer.
Section 3
When It Works Best
✓
Ideal Conditions for the Productive Thinking Model
| Dimension | Best fit |
|---|---|
| Problem type | Open-ended challenges where the problem definition itself is uncertain or contested. The model earns its keep when different stakeholders would describe the problem differently — a signal that the real problem hasn't been articulated yet. Strategic pivots, product-market fit questions, go-to-market redesigns, organisational friction that everyone feels but nobody can name precisely. |
| Team composition | Cross-functional groups of 4–8 people with diverse perspectives on the problem. The divergent phases need cognitive diversity to work — if everyone in the room has the same mental model, you'll generate 30 variations of the same idea. Include at least one person who is close to the customer and one who is far from the problem domain. |
| Stakes and complexity | High enough to justify 4–8 hours of structured thinking. The model is too heavy for tactical decisions ("which vendor for office supplies?") and too structured for pure exploration ("what should our 10-year vision be?"). Its sweet spot is consequential decisions with a bounded solution space — problems where the answer exists but isn't obvious. |
| Organisational culture | Teams willing to tolerate ambiguity for the first half of the process. If the room demands solutions in the first 20 minutes, the model will collapse under political pressure. It requires a facilitator — or a cultural norm — that protects the problem-definition phase from premature convergence. |
| Time horizon | Decisions with implementation timelines of weeks to months. The model produces actionable plans, not philosophical insights. If you need a decision in the next hour, use something faster. If you're exploring a decade-long strategic direction, the model's action-planning step will feel premature. |
| Prior attempts | Especially powerful when the team has already tried the obvious solution and it didn't work. That failure is evidence that the problem was misdiagnosed — exactly the condition the first three steps are designed to address. The model's value increases in direct proportion to how "stuck" the team feels. |
Section 4
When It Breaks Down
⚠
Failure Modes
| Failure pattern | What goes wrong | What to use instead |
|---|---|---|
| Rushing to Step 4 | The team treats Steps 1–3 as bureaucratic preamble and races to "Generate Answers." The catalytic questions are vague or identical to the original problem statement. The solutions generated are the same ones the team would have produced without any framework at all. The model's entire value proposition — reframing the problem before solving it — is gutted. | Enforce a time minimum on Steps 1–3 (at least 40% of total session time). Use a facilitator whose sole job is to block premature solution talk. |
| Solo application without external input | One person runs all six steps alone. The divergent phases produce narrow output because a single mind has a single set of assumptions. The "third-third" ideas never materialise because there's no cognitive friction to push past the obvious. The model degrades into a structured journaling exercise. | At minimum, bring in 2–3 other perspectives for Steps 3 and 4. Even informal input from people outside the problem domain can break the pattern. |
| Crisis or time-critical decisions | The model requires 4–8 hours of deliberate work. In a genuine crisis — server down, PR disaster unfolding, cash running out in weeks — that time doesn't exist. Attempting the full six steps under extreme time pressure produces shallow work at every step, which is worse than a fast heuristic applied well. | OODA Loop for fast-cycle decisions. Pre-Mortem if you have 60 minutes. Reversible vs. Irreversible Decisions to triage what actually needs deep analysis. |
| Well-defined technical problems | If the problem is already precisely defined and the solution space is constrained by physics, regulation, or engineering requirements, the first three steps add overhead without insight. You don't need to reframe "the API is returning 500 errors" — you need to debug it. | 5 Whys or Ishikawa Diagram for root cause analysis of known problems. Issue Trees for decomposing well-defined challenges. |
| Convergence failure | The team excels at divergence — generating dozens of problem framings, success criteria, and ideas — but cannot converge. Every idea seems equally promising. Nobody wants to kill anyone else's contribution. The session ends with 40 ideas and no decision. Productive thinking becomes productive procrastination. | Use a Decision Matrix to force-rank ideas against criteria. Apply the ITCH criteria ruthlessly. Assign a single decision-maker for each convergence point. |
| Facilitation vacuum | Without a skilled facilitator, the diverge-converge rhythm collapses. Dominant voices hijack the brainstorm. The group evaluates ideas during generation (killing novelty) or generates ideas during evaluation (preventing closure). The six steps blur into an unstructured conversation with a fancy name. | Designate a facilitator who does not contribute content. Use silent writing for all divergent phases. Time-box each step explicitly. |
The most dangerous failure mode is rushing to Step 4 — and it's nearly universal. The pressure to produce solutions is biological, organisational, and cultural all at once. Executives feel unproductive during problem definition. Team members want to demonstrate value by proposing fixes. The facilitator feels the room's impatience and abbreviates the exploration phase. What results is a model that looks complete on the whiteboard — all six steps checked off — but where the catalytic questions in Step 3 are just the original problem restated with "How might we...?" prepended. "Our sales cycle is too long" becomes "How might we shorten our sales cycle?" That's not reframing. That's decoration.
The protection is structural: allocate at least 90 minutes to Steps 1–3 before anyone is allowed to propose a solution. Make the rule explicit at the start of the session. When someone blurts out a solution during Step 2 (and someone will), write it on a "parking lot" board and return to the problem definition. The discomfort of sitting with an unsolved problem for 90 minutes is the point. That discomfort is the creative pressure that produces genuinely different questions in Step 3 — questions that open solution spaces the team couldn't see from their original framing.
Section 5
Visual Explanation
The Productive Thinking Model's six steps — populated with the enterprise sales cycle worked example. Each step alternates between divergent thinking (expand) and convergent thinking (select).
Section 6
Pairs With
The Productive Thinking Model is a complete problem-to-action pipeline, but it has clear entry points where other tools sharpen its output — and clear handoff points where specialised frameworks take over.
Use before
Reframing
If the team enters the session with a locked-in problem definition, Steps 1–3 become performative. Reframing before you begin — challenging whether the stated problem is the real problem — ensures the Productive Thinking Model starts from genuine uncertainty rather than false clarity. The model can do its own reframing in Step 3, but arriving with an open frame accelerates the process.
Use before
5 Whys
When the problem has a diagnostic component — something broke, performance degraded — running 5 Whys first gives the Productive Thinking Model a sharper starting point. You enter Step 1 knowing the root cause, not just the symptom, which means the catalytic questions in Step 3 target the right level of the system.
Use after
Decision Matrix
Step 5 (Forge the Solution) can leave you with 2–3 strong candidates that all passed the POWER evaluation. A weighted Decision Matrix breaks the tie by scoring each solution against your ITCH criteria from Step 2. The Productive Thinking Model generates the options and criteria; the Decision Matrix makes the final call.
Use after
Pre-Mortem
Before committing resources in Step 6, run a Pre-Mortem on the chosen solution. "It's six months from now and this failed. Why?" The Pre-Mortem surfaces implementation risks that the POWER evaluation in Step 5 may have missed — particularly social and political risks that teams are reluctant to name during a creative session.
Mental model
Abstraction Laddering
Abstraction Laddering — moving up ("why?") and down ("how?") the ladder of abstraction — is the cognitive engine inside Step 3. If your catalytic questions are too abstract ("How might we be more innovative?") or too concrete ("How might we change the demo script?"), laddering helps you find the level where the question opens the most useful solution space.
Mental model
Six Thinking Hats
De Bono's Six Thinking Hats can structure the divergent phases within each step. White hat for facts in Step 1, yellow hat for positives in Step 5, black hat for objections. The Productive Thinking Model tells you what to think about at each stage; the Hats tell you how to think about it. They're complementary operating systems.
Section 7
Real-World Application
Procter & Gamble — Connect + Develop and the reinvention of innovation sourcing
The scenario
In the early 2000s, Procter & Gamble faced a problem that most consumer goods companies would have diagnosed as "we need more R&D spending." Innovation success rates were declining. The percentage of new products meeting financial targets had dropped. Internal R&D, despite billions in annual investment, was producing diminishing returns. The obvious solution — spend more, hire more scientists — had already been tried. CEO A.G. Lafley wanted a fundamentally different approach, and the team tasked with designing it used a structured creative problem-solving process closely aligned with the Productive Thinking Model's architecture.
How the tool appliedThe team's critical move happened in the equivalent of Steps 1–3. Instead of asking "How do we improve our R&D productivity?" — the question everyone expected — they reframed through multiple iterations. The exploration phase surfaced a striking data point: roughly 1.5 million scientists and engineers outside P&G had relevant expertise in the company's core technology areas. Only about 9,000 worked inside P&G. The target future wasn't "better internal R&D" — it was "access to the world's best ideas regardless of where they originate." The catalytic question that emerged: "How might we source 50% of our innovations from outside the company while maintaining quality and IP control?"
That question — which would have been unthinkable under the original problem framing — opened an entirely different solution space. The team generated dozens of mechanisms for external innovation sourcing, evaluated them against criteria (speed, IP protection, cultural fit, scalability), and forged what became the Connect + Develop programme.
What it surfacedThe reframing revealed that P&G's problem wasn't insufficient R&D capacity — it was an artificial boundary between internal and external knowledge. The company had been optimising within the wrong frame for years. Connect + Develop ultimately contributed to products like the Swiffer Duster (technology licensed from a Japanese competitor), Olay Regenerist (formulation developed with an external partner), and Tide Pods (packaging technology sourced externally). By 2006, P&G reported that more than 35% of new products had elements originating outside the company, up from roughly 15% in 2000.
The non-obvious factorWhat made this application remarkable wasn't the external innovation concept itself — open innovation was already being discussed in academic circles, notably by Henry Chesbrough. It was the discipline of spending the majority of the problem-solving effort on reframing before generating solutions. A team that jumped to Step 4 would have produced ideas for improving internal R&D efficiency — better lab equipment, faster testing protocols, more scientists. All reasonable. All wrong. The value of the structured process was in preventing the team from solving the problem they walked in with, and forcing them to discover the problem they actually had.
Section 8
Analyst's Take
Faster Than Normal — Editorial View
The Productive Thinking Model occupies an unusual position in the decision tools landscape. It's neither as famous as design thinking nor as academically cited as Creative Problem Solving, yet it's arguably more practical than both. Design thinking's five stages are evocative but vague — "empathise" and "ideate" don't tell you what to actually do for the next 20 minutes. CPS's full methodology is rigorous but unwieldy, with enough sub-stages and variants to fill a graduate seminar. Hurson's contribution was editorial: he cut the process to six steps, gave each one a plain-English name, and embedded specific techniques (DRIVE, ITCH, POWER, third-third thinking) that a facilitator can deploy without a certification. The model endures because it's the right level of structure — enough to prevent the common failure modes, not so much that it becomes the thing the team is managing instead of the problem.
The failure I see most often isn't a failure of the model — it's a failure of nerve. Teams complete Steps 1–3 and arrive at a genuinely novel catalytic question, one that reframes the problem in a way that's uncomfortable because it implies the previous strategy was wrong. Then they flinch. They retreat to a safer question that keeps the existing approach intact. The whole point of the model — the creative tension built through three steps of disciplined exploration — dissipates in a moment of organisational self-protection. The facilitator's hardest job isn't managing the brainstorm. It's holding the room in the discomfort of a question that challenges what they've been doing for the last two years.
The highest-leverage modification I've found: run Step 3 twice. Generate your first round of "How might we...?" questions, select the top three, then ask the team: "What question are we afraid to ask?" That meta-question reliably surfaces the catalytic question that the group self-censored — the one about the business model, the founder's pet project, the partnership that isn't working. Write those questions on the board alongside the "safe" selections. Often the question the team was afraid to ask is the one that, when answered, actually moves the needle. The Productive Thinking Model gives you the architecture. The courage to use it honestly is on you.
Section 9
Top Resources
01
Think Better: An Innovator's Guide to Productive Thinking — Tim Hurson (2007)
Primary sourceThe definitive source. Hurson walks through all six steps with worked examples, facilitation guidance, and the cognitive science behind each phase. The book is more accessible than most creativity methodology texts — Hurson writes like a practitioner, not an academic. Chapters 7–12 cover the six steps in detail; Chapter 6 on "Monkey Mind" versus "Elephant Mind" thinking is the conceptual foundation that makes the rest click.
02
Book
The scientific backbone for why the Productive Thinking Model works. Kahneman's research on anchoring, the availability heuristic, and substitution explains precisely why humans leap to the first plausible solution and why a structured process that enforces divergence before convergence is a genuine cognitive intervention. Read Part I on the two systems of thinking — it's the theoretical justification for every step Hurson designed.
03
Book
Lafley's account of strategic decision-making at Procter & Gamble, including the reframing discipline that produced Connect + Develop. The book's "strategic choice cascade" — Where to Play, How to Win — mirrors the Productive Thinking Model's insistence on defining success criteria before generating solutions. Chapter 2 on framing the strategic question is directly applicable to Step 3.
04
Book
Cagan's product discovery process shares deep structural DNA with the Productive Thinking Model — particularly the discipline of separating problem understanding from solution generation. His concept of "opportunity assessment" maps to Steps 1–3, and his emphasis on generating multiple solution approaches before committing maps to Step 4. The best modern translation of productive thinking into a product management context.
05
Book
The academic framework behind the P&G case study in Section 7. Chesbrough's argument that innovation should flow across organisational boundaries is itself a product of the kind of reframing the Productive Thinking Model demands — questioning the assumption that R&D must be internal. Read alongside the Hurson book to see how a reframed question ("What if we sourced ideas externally?") can restructure an entire industry's approach to innovation.
Decision Tools Library — Browse by phase
Why this matters next
mental modelsLeverage
Reframing applied the Leverage mental model
mental models5 Whys
Reframing applied the 5 Whys mental model
mental modelsMomentum
Reframing applied the Momentum mental model
mental modelsOODA Loop
Reframing applied the OODA Loop mental model
mental modelsQuality
Reframing applied the Quality mental model
mental modelsEnvironment
Reframing applied the Environment mental model
Continue exploring
INSCZB
Decision tool
Inversion
Ask what would guarantee failure and design your solution to avoid those conditi
Decision tool
SCAMPER
Systematically generate variations by Substituting, Combining, Adapting, Modifyi
Decision tool
Zwicky Box
Generate novel solutions by combining dimensions of a problem in unusual ways
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.