SCAMPER is a checklist of seven prompts for generating variations on an existing idea: substitute, combine, adapt, modify, put to another use, eliminate and reverse. It was devised by Bob Eberle in 1971 from Alex Osborn's earlier question lists. It is a divergence tool, useful when a team keeps producing the same three options, and it has no mechanism for judging whether any option is good.
When you have something concrete to vary and the team keeps returning the same handful of options. It is useless with nothing to operate on, and it produces quantity rather than quality, so it needs a separate evaluation step afterwards.
What SCAMPER is
SCAMPER is a checklist of seven prompts for generating variations on something that already exists: substitute, combine, adapt, modify, put to another use, eliminate, reverse.
Bob Eberle assembled it in 1971 from lists of idea-spurring questions published by Alex Osborn, the advertising executive who originated brainstorming, in the 1950s.
It is a divergence tool. It generates options and has no mechanism whatsoever for judging them, which is not a flaw so much as a division of labour that people forget to complete.
- Seven prompts, one at a time The constraint is the value
All seven at once is ordinary brainstorming with a mnemonic attached.
- It varies; it does not originate Needs something to work on
Applied to a blank page it produces nothing, and people blame the technique.
- Eliminate is the productive one And the least used
Removing capability feels like loss, so teams skip to the comfortable prompts.
- No quality signal at all By design
Forty variations is raw material. Something else has to judge.
Why it matters
A group asked to generate ideas produces about four, then stops. This is reliable and it has a specific cause: in an ordinary meeting each idea is evaluated as it appears, and evaluation is the mode that ends generation.
SCAMPER interrupts this twice. It hands you a prompt so nobody is staring at a blank page, and it forces you to stay on one prompt after the obvious answers have run out. The interesting material appears specifically in that uncomfortable stretch.
It does not feel like the interesting material at the time. It feels like a meeting that should have finished, which is precisely why most sessions stop at four ideas.
The seven prompts
What could we swap out? A component, a material, a rule, a person.
Replace the dashboard with a weekly email. Nobody has to log in to get value.
What could we merge this with? Another product, another step, another team.
Merge feedback collection with the sprint planning tool, so it lands where decisions happen.
What works elsewhere that we could borrow?
Adopt the triage model support teams use, rather than a flat inbox.
What could we magnify, shrink, or change the shape of?
Shrink to a single weekly summary. Magnify to a permanent always-on channel.
Who else could use this, for what?
The same summarisation aimed at sales call notes rather than at product feedback.
What could we remove entirely? Especially the expensive or assumed-essential parts.
Remove tagging altogether. If summarisation works, the taxonomy nobody maintains is dead weight.
What if the order, or the core assumption, were inverted?
What if fewer options were better? Ship one recommendation rather than a ranked list.
Take one prompt, set a count, and generate to the count before judging anything. The useful answers arrive after the obvious ones are exhausted, which is exactly when a normal meeting moves on.
Reverse the belief, not just the order
The Reverse prompt is usually run as “what if we did it backwards”, which produces novelty and rarely produces anything usable.
The stronger version inverts an assumption rather than a sequence. What if customers wanted fewer choices? What if the slower version were better? What if the thing everyone treats as the core feature were the part to remove?
What if we did the steps in the opposite order?
"Send the summary before collecting the feedback." Novel, and rarely usable.
What if the opposite of our core assumption were true?
"What if customers want fewer options?" Ship one recommendation instead of a ranked list.
Most belief reversals will be wrong, which is fine, because generating them costs almost nothing. The occasional one that is not wrong is the reason to run the prompt at all.
When to use it
- The team keeps producing the same three options and cannot get past them.
- You have something concrete to vary: a product, a process, a pricing model.
- A solution has been assumed for so long nobody remembers deciding it.
- You need volume of options quickly, before a selection process.
- The obvious answers have all been tried and none worked.
- You have nothing concrete to vary yet. Use Design Thinking →
- You have too many options and need to choose. Use ICE scoring →
- You do not know what problem you are solving. Use Jobs to be Done →
- You need factors nobody in the industry competes on. Use Blue Ocean Strategy →
Against the alternatives
What variations of this thing have we not considered?
Gives you: Volume of options, with no quality signal
Which factors should we eliminate, reduce, raise and create?
Gives you: A divergent value curve. Structurally similar, with a strategic goal attached
What problem are we solving, and for whom?
Gives you: A framed problem. SCAMPER can sit inside its ideate stage
How has this problem been solved elsewhere?
Gives you: Borrowed mechanisms. A more specific version of Adapt
SCAMPER in practice: the Post-it Note
Put to another use, running in slow motion over twelve years, inside a company that already owned the material.
3M, the Post-it Note · 1968 to 1980
A failed adhesive, sitting unused for five years, put to another use.
Spencer Silver produced an adhesive in 1968 that was, judged against its brief, a failure: it stuck lightly, came away cleanly and would not hold anything. He spent years presenting it internally with no application to attach it to.
Art Fry, who sang in a choir, was annoyed that the paper scraps marking his hymnal kept falling out. The adhesive that would not hold properly was exactly the adhesive that job required.
The product went national in 1980, twelve years after the invention.
- Adhesive invented
- 1968
- Application found
- 1974
- National launch
- 1980
What it shows: This is Put to another use, and the case shows what makes that prompt hard. The material had been in the building for six years. What was missing was not the idea but a specific job to test it against.
When it won’t help you
- It cannot originate, only vary
Every prompt operates on something that exists. With no starting object the technique produces nothing at all, and teams reasonably conclude it is empty rather than that they applied it wrongly.
Instead: Get to a concrete candidate first, by research or by any other route. Then vary it.
- It produces quantity with no quality signal
A good session ends with forty variations and no way to choose between them. The technique has no theory of what makes an option good and is not pretending to.
Instead: Score separately, in a different session, with something that ranks. Judging in the same room stops the generating.
- The variations tend to stay close to the original
Prompts anchored on an existing thing produce adjacent options. SCAMPER will not find you a fundamentally different business, and expecting it to is a category error.
Instead: Use it for adjacent exploration. For a different position entirely, the four actions or the six paths have a strategic goal built in.
- It is very easy to perform without producing anything
Seven prompts, a full wall of notes, a satisfying session, and nothing anyone would build. The format supplies the feeling of productivity independently of the output.
Instead: Judge the session on whether anything surprised anyone. If nothing did, it did not work, however full the wall.
Further reading
- Bob Eberle, SCAMPER: Creative Games and Activities for Imagination Development (1971).
- Alex Osborn, Applied Imagination (1953), where the underlying question lists originate.
- Blue Ocean Strategy. The four actions, which are SCAMPER with a strategic objective attached.
- Design Thinking. The process whose ideate stage this fits inside.
- Biomimicry. A more specific version of the Adapt prompt.
- ICE scoring. What to do with forty options.
How to apply SCAMPER
- 1
Start from something specific and existing
A product, a feature, a process, a pricing model. SCAMPER varies things; it does not originate them. Applied to a blank page it produces nothing, which is the most common reason people conclude it does not work.
- 2
Take one prompt at a time and stay on it
Working through all seven simultaneously collapses into ordinary brainstorming. The value comes from the constraint: being forced to answer 'what could we substitute' when you have run out of obvious substitutions is where the unobvious ones appear.
- 3
Generate without judging, and set a count
Aim for a number, five or ten per prompt, before you evaluate anything. Judging as you go stops generation after the safest few options, which is the default behaviour in any meeting and the thing the technique exists to interrupt.
- 4
Spend real time on Eliminate
Consistently the most productive prompt and consistently the least used, because removing capability feels like loss. What would this look like with the most expensive component gone? With the feature everyone assumes is essential removed?
- 5
Use Reverse on assumptions, not just on sequence
Not only 'what if we did it backwards' but 'what if the opposite of our core assumption were true'. What if customers wanted fewer options? What if the slow version were better? Reversal of belief produces more than reversal of order.
- 6
Evaluate separately, later, with something else
SCAMPER produces quantity and has no view on quality. A list of forty variations is raw material. Score them with a prioritisation instrument in a different session, because the mode required to judge is the one that stops generation.
Common mistakes
- **Using it with nothing to operate on.** SCAMPER varies an existing thing. Applied to a blank page it produces nothing, and people conclude the technique is empty rather than misapplied.
- **Running all seven prompts at once.** That is ordinary brainstorming with a mnemonic attached. The constraint of staying on one prompt is where the value is.
- **Judging while generating.** Evaluating each idea as it appears stops generation after the safest few, which is exactly the failure the technique was designed to interrupt.
- **Skipping Eliminate.** The most productive prompt and the least used, because removing something feels like loss rather than like a move.
- **Reversing sequence but not assumptions.** 'What if we did it backwards' is the weak version. 'What if the opposite of our core belief were true' is where the useful answers come from.
- **Treating the output as a plan.** Forty variations is raw material with no quality signal attached. Something else has to do the judging.
How ShipFit operationalizes this
ShipFit runs the SCAMPER Methodology in Stage 5 (What's V1?), alongside Biomimicry and Cross-Industry Analysis, to generate feature and scope variations. Its precondition is met by the earlier stages rather than by a workshop: there is a defined buyer from Stage 2, a ranked problem list from Stage 3 and a chosen solution approach from Stage 4, so there is something specific to vary and a reason to prefer some variations over others.
ShipFit runs 55 frameworks across 9 decision stages
SCAMPER is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What does SCAMPER stand for?
When should I use SCAMPER?
Which SCAMPER prompt is most useful?
Is SCAMPER just brainstorming?
What are the limits of SCAMPER?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.
Four survey questions, four cumulative curves, four intersections. How to run the Van Westendorp price sensitivity meter, plot it, and read the price range.
Most product launches fail not because the product was bad, but because the launch was a list of channels nobody mapped to a buyer. Here is the template that fixes that.
Default-prompted AI is a slop machine: agreeable, plausible-sounding, useless for validating an idea. Here's how to use AI for the parts where it actually adds signal, and where to keep it out of the way.
How many units a month before the math stops bleeding?
Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.
Validation for non-technical founders using AI builders and no-code. The bottleneck isn't building anymore, it's deciding what to build. ShipFit decides.
AI Cofounder runs 26 parallel AI agents to produce investor-ready pitch decks and business reports. ShipFit runs 9 sequential decisions with live G2 / Reddit data, Van Westendorp pricing and a 24% Kill rate. Parallel agents skip decisions. Sequence forces them.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.