Sign inGet started
Skills / Productivity-habits

Simplex Process

Most people spend too much time solving problems and not enough time finding them. The most creative act is not generating ideas — it's noticing the right problems to solve.

The Basadur Simplex Process is a rigorous 8-step creative problem-solving cycle that begins where most frameworks don't — with proactive problem finding. Developed by Michael Basadur at Procter & Gamble and refined at McMaster University, it pairs divergent and convergent thinking at every step to produce concrete outputs at each stage: from a vague 'fuzzy situation' all the way to an implemented, stakeholder-accepted solution. Unlike generic brainstorming, Simplex treats problem formulation as serious intellectual work before any solution generation begins.

By Min (Michael) Basadur · Free
Specimen 01 · Live diagnosisSimplex Process
Input

“Our product team keeps shipping features but customer adoption is terrible. We've tried user interviews, redesigned onboarding twice, and nothing…”

Diagnosis
Welcome to the Simplex Process.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

Find the right problem first, then solve it — eight steps from fuzzy to fixed

The Simplex Process is an 8-step cyclical wheel organized into three macro-phases, each step using a paired diverge-then-converge structure. Phase 1 (Problem Formulation) begins with Problem Finding — proactively sensing fuzzy situations before they become crises — followed by Fact Finding to gather relevant information, and Problem Definition to craft a 'How Might We…?' springboard statement that opens solution space. Phase 2 (Solution Formulation) uses Idea Finding to generate creative options without judgment, then Evaluate & Select to assess ideas against user-defined criteria. Phase 3 (Solution Implementation) produces an Action Plan with concrete tasks and timelines, a Gaining Acceptance strategy that anticipates stakeholder resistance before execution, and Taking Action — which naturally surfaces new problems and restarts the cycle. A validated thinking-style instrument, the Basadur Profile, identifies whether individuals lean toward Generator, Conceptualizer, Optimizer, or Implementor modes across the wheel.

The problem

Most teams jump straight to solutions before they've properly defined the problem — or they're solving a symptom while the real issue festers underneath. Generic brainstorming produces long lists of ideas that go nowhere because no one asked the right question first. The Simplex Process attacks this root cause: the fuzzy front end, where most innovation efforts quietly collapse before they even begin.

The solution

By walking every step of the Simplex cycle — from sensing a fuzzy situation to executing a stakeholder-accepted plan — you'll stop solving the wrong problems faster and start delivering solutions that stick because the right people helped shape them.

You bring
  • A fuzzy situation, nagging challenge, or half-formed opportunity you can't quite articulate
  • Relevant facts, observations, and feelings about the situation — even incomplete or contradictory ones
  • Criteria you actually care about when evaluating potential solutions
  • Knowledge of the stakeholders who will need to support or approve the solution
You get
  • A crisp 'How Might We…?' springboard statement that reframes your problem at the right level of abstraction
  • A structured idea list evaluated against your own criteria — not just the loudest idea in the room
  • A concrete action plan with tasks, owners, timelines, and success metrics
  • A stakeholder acceptance strategy that anticipates resistance before it derails implementation
In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01The same situation, two ways
Specimens A · B
Specimen AVague
Unaided

“Your team is in its fifth meeting about a feature with 12% adoption. Someone wants another round of user interviews. Someone else is convinced it's an onboarding problem. A third person thinks it's a marketing message issue. You're debating solutions with no agreed-upon problem statement, and the next sprint starts in two days.”

×Vague — nothing concrete to act on.
Specimen BCalibrated
With Simplex Process

“You've completed Simplex's Problem Formulation phase. The whole team owns a single 'How Might We' springboard statement. You have an idea shortlist evaluated against explicit criteria — not whoever spoke loudest. You know which three stakeholders need to approve the top idea and what each one's objections will be. The next sprint has a concrete first action, not another brainstorm.”

Specific, grounded, and ends with one clear next step.
Fig.02A real session, unedited
In-app · assistant
Simplex ProcessClaude
Simplex Process
Welcome to the Simplex Process. Before we jump to solutions, I want to make sure we're solving the right problem — Basadur calls this the most neglected step in innovation.
We'll start at Step 1: Problem Finding. Don't worry about defining your problem precisely yet. That comes later. Right now, just tell me: what's the fuzzy situation on your mind? Describe what's nagging at you, even if it's incomplete or contradictory.
Our product team keeps shipping features but customer adoption is terrible. We've tried user interviews, redesigned onboarding twice, and nothing seems to stick.
Good — that's a real fuzzy situation, which is exactly right for this stage. Notice you've already framed it as a solution problem ('adoption is terrible') rather than a problem-finding challenge. Simplex asks us to resist that pull and look wider first.
Step 1 starts with diverging: generating many possible problem statements before committing to one. Use these springboard starters — shoot for 8 or more, no filtering:
- 'We have a problem with…'- 'I wish we could…'- 'What bugs me is…'- 'It would be great if…'
Don't edit. Quantity before quality.
Okay: We have a problem with features not matching real needs. I wish we knew which features would actually get used. What bugs me is that we don't talk to customers until after we've built. We have a problem with how we prioritize. I wish customers could see the roadmap before we build it. What bugs me is that engineering and product have different definitions of 'done.' We have a problem measuring success after launch. I wish onboarding felt like using the product rather than reading a manual.
Eight distinct fuzzy problems — excellent diverge phase. Now let's converge. Don't ask 'which is easiest to fix.' Ask: which of these, if solved, would make the others less painful?
I notice a cluster: late customer contact, missing shared definition of 'done,' and the gap between roadmap and customer expectations. These suggest the root issue lives in your discovery process, not your onboarding.
Let's move to Step 3: Problem Definition. I'll draft your 'How Might We…?' statement at three levels of abstraction:
1.
Narrow: 'How might we bring customer input into feature decisions during sprint planning?'2. Mid: 'How might we align our product roadmap with what customers actually need before we build?'3. Broad: 'How might we build a feedback loop that makes every feature launch smarter than the last?'
Which level opens the right solution space — without locking in an answer you already have?
The mid-level one. 'How might we align our roadmap with what customers actually need before we build?' — that feels like where the real gap is.
Locked in. Your Simplex springboard statement:
'How might we align our product roadmap with what customers actually need before we build?'
Phase 1 complete. Now we move to Phase 2: Solution Formulation.
Step 4 is Idea Finding — same rule: diverge first, no judgment. I'll apply a few of Basadur's generative prompts to get past the obvious:
- Reverse it: What if customers designed the roadmap entirely?- Borrow it: What does Amazon's 'working backwards' press release method do at this stage?- Eliminate it: What if you shipped nothing for one quarter and only watched customers work?
What ideas surface for you?
The working backwards press release is interesting — we've never done that. We could show customers rough prototypes before sprint planning even starts. Or create a customer advisory group that reviews the roadmap quarterly. Or tie prioritization scores to actual interview data rather than PM intuition.
Four solid ideas. When you're ready, Step 5 (Evaluate & Select) scores these against criteria you define — things like implementation speed, stakeholder support needed, and expected customer impact — so the best option surfaces, not just the most familiar one.
Here's your Simplex Phase Summary so far:
Fuzzy Situation: Feature adoption consistently below expectations despite repeated fixes.How Might We Statement: 'How might we align our product roadmap with what customers actually need before we build?'Idea Shortlist: Working backwards press release · Pre-sprint prototype feedback sessions · Quarterly customer advisory board · Interview-driven prioritization scoring
Shall we move into evaluation now, or add more ideas to the list first?
Reply to Simplex Process
What the skill is doing
01Fuzzy Front End Navigation
02How Might We Statement Crafting
03Diverge-Converge Facilitation
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
SPSimplex Processtyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
Our product team keeps shipping features but customer adoption is terrible. We've tried user interviews, redesigned onboarding twice, and nothing seem…9:14✓✓
Welcome to the Simplex Process.9:14
Before we jump to solutions, I want to make sure we're solving the right problem — Basadur calls this the most neglected step in i…9:15
We'll start at Step 1: Problem Finding.9:15
Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

Reads the situation, names the pattern, returns one concrete next move.
Delivered in seconds, inside a conversation that already exists.
Specimen · WhatsApp Business API · live
Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Fuzzy Front End Navigation

Most problem-solving methods start too late — with a problem already declared. Simplex starts earlier, in the 'fuzzy front end' where you sense that something is wrong but can't fully articulate it yet. This capability helps you generate a rich list of potential problem areas before committing to any single definition, using Basadur's divergent Problem Finding techniques to surface hidden challenges.

Based on Basadur's Step 1 (Problem Finding), which treats the proactive sensing of incomplete situations as a creative skill that can be systematically practiced — not a passive waiting for problems to arrive fully formed.
CapabilityC-02

How Might We Statement Crafting

The single most powerful output of Simplex's Problem Formulation phase is a well-formed 'How Might We…?' question at the right level of abstraction. Too narrow and it locks in a predetermined solution; too broad and it generates unusable ideas. This capability uses Basadur's laddering and springboard techniques to find the precise framing that opens a rich solution space.

Based on Basadur's Step 3 (Problem Definition), which uses 'Why-What's-Stopping-Us' laddering to move up and down the abstraction ladder until the HMW statement is specific enough to act on and open enough to invite creative options.
CapabilityC-03

Diverge-Converge Facilitation

Every one of Simplex's 8 steps follows the same micro-pattern: first diverge (generate without judgment), then converge (select with criteria). This capability enforces that structure throughout the session, preventing premature closure during generation phases and ensuring rigorous, criteria-based selection afterward. Users who mix these modes often mistake the first plausible idea for the best one.

Based on Basadur's foundational principle that divergent and convergent thinking are distinct cognitive modes requiring different psychological conditions — and that mixing them simultaneously kills both.
CapabilityC-04

Thinking Style Calibration

Basadur's research identified four natural thinking styles corresponding to positions on the Simplex wheel: Generators (problem sensing and finding), Conceptualizers (abstract idea generation), Optimizers (evaluation and refinement), and Implementors (action-taking and execution). Understanding your dominant style — and your team's gaps — lets you direct attention to the steps where you're naturally weakest, not just where you're most comfortable.

Based on the Basadur Profile psychometric instrument, which maps individuals onto the Simplex wheel to reveal natural creative strengths and the blind spots teams systematically skip when solving problems.
CapabilityC-05

Stakeholder Acceptance Mapping

Implementation fails not because the idea was wrong, but because the people who needed to say yes never did. Simplex dedicates an entire step — Step 7, Gaining Acceptance — to identifying key stakeholders, anticipating their specific objections, and designing persuasion strategies before execution begins. This turns stakeholder management from an afterthought into a designed creative activity.

Based on Basadur's Step 7 (Gaining Acceptance), which treats organizational buy-in as a creative problem requiring the same diverge-converge discipline as the rest of the process — generating a wide range of potential resistance points before converging on the most important ones to address.
Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces
OutputD-01

How Might We Springboard Statement

A precisely crafted 'How Might We…?' question at the right level of abstraction, including the reframing rationale, alternative framings considered and rejected, and notes on why this level of scope was chosen. The team's shared problem definition.

OutputD-02

Idea Evaluation Matrix

A structured grid mapping generated ideas against user-defined selection criteria — speed, feasibility, impact, stakeholder support — with convergent scoring that surfaces the most promising option rather than the most vocal one.

OutputD-03

Stakeholder Acceptance Plan

A named-stakeholder map with anticipated objections and tailored persuasion strategies for each key influencer, completed before execution begins. Designed to prevent the implementation derailment that kills most good solutions.

OutputD-04

Simplex Session Summary

A structured record of all divergent outputs and convergent decisions from each completed phase — fuzzy problem lists, HMW statement, selected ideas, action commitments, and next steps — usable as a team communication artifact or handoff document.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Min (Michael) Basadur

Min (Michael) Basadur is the creator of the Simplex creative problem-solving system, developed during his tenure leading innovation at Procter & Gamble and refined over decades as Professor Emeritus at McMaster University's DeGroote School of Business. His methodology has been deployed in corporate innovation programs at P&G, Toyota, and Frito-Lay, and he developed the Basadur Profile — a validated psychometric instrument for assessing creative thinking styles — used in organizational development programs worldwide.

Status · Inspired by Min (Michael) Basadur’s work — not yet claimed. Are you Min (Michael) Basadur?
Primary sourceS-01

The Power of Innovation (1995); Simplex: A Flight to Creativity (1994)

by Min (Michael) Basadur

Creator of Simplex CPS; former innovation leader at Procter & Gamble; Professor Emeritus, McMaster University DeGroote School of Business; developer of the Basadur Profile validated psychometric assessment.

Read the original ↗
Citationbasadur.com
In the build queue

Be first to run it.

Simplex Process is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail
At launchI have a situation that keeps nagging at me but I can't define the actual problem yet. Can we start with Simplex's Problem Finding step? I want to make sure I'm not just solving the wrong problem faster.