Use this when you're staring at an existing product, process, or business model and need to generate a high volume of non-obvious variations. SCAMPER gives you seven systematic lenses — Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse — that force your thinking beyond the incremental improvements your brain defaults to, producing options you wouldn't reach through unstructured brainstorming.
Section 1
What This Tool Does
The blank page is not actually the hardest creative challenge. The hardest challenge is the full page — the existing product, the established process, the business model that works well enough. When something already exists, your brain locks onto it as an anchor. You see the thing as it is, not as it could be. Psychologists call this functional fixedness: the cognitive bias that makes you perceive objects and systems only in terms of their current function. Hand someone a brick and ask them to list uses for it. They'll say "build a wall" and stall. The brick's existing purpose dominates their imagination so completely that "doorstop," "weapon," "bookend," "counterweight" require genuine cognitive effort to surface.
SCAMPER is a systematic antidote to functional fixedness. Bob Eberle formalised it in 1971, drawing on Alex Osborn's earlier brainstorming checklists from the 1950s. The insight behind the tool is that most innovations are not creations from nothing — they are transformations of something that already exists. Uber didn't invent transportation. It substituted a smartphone app for a dispatcher, eliminated the need to own vehicles, and reversed the traditional model so drivers came to riders. Each of those moves maps to a specific SCAMPER operation. The tool works by giving you seven distinct verbs — seven different ways to manipulate what already exists — and forcing you to apply each one systematically rather than waiting for inspiration to strike.
The seven operations: Substitute (swap a component, material, person, or process for something else). Combine (merge two features, products, or functions into one). Adapt (borrow an idea from a different domain or context). Modify (change the scale, shape, colour, frequency, or intensity of something). Put to other use (deploy the existing thing for a completely different purpose or audience). Eliminate (remove a component, step, or feature entirely). Reverse (flip the sequence, invert the relationship, or do the opposite of the current approach). That's the whole toolkit. Seven verbs, applied to whatever you're trying to improve.
The core cognitive shift: SCAMPER replaces "How can we make this better?" — a question so open it paralyses — with seven specific, answerable questions that each constrain your thinking in a different productive direction. Constraints, paradoxically, generate more ideas than freedom does. When you ask "What could we substitute?" your brain has a concrete operation to perform. It scans for alternatives. It finds them. Then you move to "What could we combine?" and a completely different set of possibilities opens. The structure doesn't limit creativity; it channels it. Seven passes through the same subject, each from a different angle, will reliably produce 20–40 ideas in under an hour. Most will be mediocre. Some will be obvious. But three or four will be genuinely surprising — combinations and inversions that nobody in the room would have reached through freeform brainstorming. Those three or four are why the tool exists.
One thing SCAMPER is not: an evaluation framework. It generates options. It does not rank them, filter them, or tell you which ones to pursue. That's a feature, not a limitation. The generation phase and the evaluation phase require different cognitive modes — divergent and convergent thinking, respectively — and mixing them kills both. SCAMPER is pure divergence. Evaluation comes later, with different tools.
Section 2
How to Use It — Step by Step
Instructions on the left. Worked example — "How might a mid-market B2B SaaS company that sells project management software generate new product and business model ideas?" — on the right.
Step 1 — Define
Identify the specific subject you want to transform
Name the product, process, service, or business model you're working on. Be concrete. "Our onboarding flow" is better than "our product." "The way we price enterprise contracts" is better than "our business model." The more specific the subject, the more specific — and therefore more useful — the SCAMPER outputs will be. Write a one-sentence description of the subject as it currently exists, including its key components. This becomes your baseline.
Worked example
B2B project management SaaS
Subject: "TaskFlow Pro — a cloud-based project management tool for teams of 20–200, sold via annual subscription at $12/user/month. Core features: Kanban boards, Gantt charts, time tracking, file sharing, integrations with Slack and Jira. Primary buyer: VP of Engineering or PMO lead. Onboarding takes ~3 weeks with a dedicated CSM."
Step 2 — Apply Each Lens
Run through all seven SCAMPER operations sequentially
Take each letter in order. Spend 5–8 minutes per operation. For each one, ask the corresponding question and generate as many ideas as possible — aim for at least three per operation. Write everything down without filtering. Quantity matters more than quality at this stage. If an operation feels unproductive for your subject, spend two minutes on it and move on. Not every lens will yield breakthroughs for every subject. That's expected. The power is in the aggregate.
Worked example
Running the seven lenses on TaskFlow Pro
S — Substitute: What if we substituted AI-generated project plans for manual setup? What if we replaced the dedicated CSM with a self-serve onboarding bot? What if we substituted usage-based pricing for per-seat pricing?
C — Combine: What if we combined project management with contract management into one tool? What if we merged time tracking with automated invoicing? What if we bundled TaskFlow with a design collaboration tool and sold a "product team suite"?
A — Adapt: What if we adapted the sprint retrospective format from Scrum into an automated team health feature? What if we borrowed the "stories" format from Instagram for async project updates? What if we adapted airline overbooking logic to flag resource over-allocation?
M — Modify: What if we made the Gantt chart interactive and 3D for complex programmes? What if we dramatically simplified the UI to only five actions? What if we increased the default project template library from 12 to 200, covering niche industries?
P — Put to other use: What if construction firms used TaskFlow for job site coordination? What if we repositioned the time-tracking data as a workforce analytics product sold to HR? What if freelancers used it as a client-facing project portal?
E — Eliminate: What if we eliminated Gantt charts entirely and bet on Kanban-only? What if we removed the annual contract and went month-to-month? What if we eliminated the integrations layer and built a standalone ecosystem?
R — Reverse: What if instead of the PM creating the project plan, the team members built it bottom-up? What if we reversed the pricing model — free for managers, paid for contributors who want premium views? What if we reversed the sales motion from outbound to pure product-led growth?
Step 3 — Capture and Cluster
Organise raw ideas into thematic groups
You'll have 20–40 raw ideas. Many will overlap. Some will be variations of the same underlying insight. Group them into clusters: ideas about pricing, ideas about new audiences, ideas about feature changes, ideas about business model shifts. Label each cluster. This step transforms a chaotic list into a navigable landscape of possibilities. You'll typically end up with 4–7 clusters.
Apply convergent criteria to pick the most promising ideas
Switch from divergent to convergent mode. For each cluster, ask: Does this address a real unmet need? Can we build or test it within our current capabilities? Does it create defensible differentiation? Use a simple scoring method — a Decision Matrix or even a quick impact-effort assessment. Select 2–3 ideas to develop further. The rest go into a parking lot, not the bin. Ideas that seem impractical today may become viable when circumstances change.
Worked example
Selecting from TaskFlow clusters
The team scores each cluster on market demand, feasibility, and strategic fit. AI-powered automation scores highest — it addresses a real pain point (project setup takes too long), leverages available LLM technology, and differentiates against competitors still relying on manual templates. New audiences (freelancers) scores second — the freelancer market is large, the product needs minimal modification, and it opens a product-led growth channel. Data monetisation is parked — interesting but requires significant data infrastructure and raises privacy questions that need legal review. The team commits to prototyping AI project plans and a freelancer-tier pricing experiment.
Section 3
When It Works Best
✓
Ideal Conditions for SCAMPER
Dimension
Best fit
Problem type
Improving, extending, or reimagining something that already exists. SCAMPER is a transformation tool, not a creation-from-scratch tool. It needs a concrete subject to operate on — a product, a workflow, a pricing model, a customer experience. The more tangible and well-understood the subject, the more productive the session.
Team composition
Works with individuals or small groups (3–8 people). Diverse functional backgrounds help — an engineer, a designer, a salesperson, and a customer success lead will generate radically different ideas from the same SCAMPER prompt. The tool is structured enough that it doesn't require a skilled facilitator, though one helps.
Innovation stage
Early ideation, when you need volume and variety of options. Particularly valuable when a team feels stuck — when they've been iterating on the same product for months and can't see past incremental improvements. SCAMPER breaks the pattern by forcing non-obvious angles.
Time constraints
A full SCAMPER session takes 45–90 minutes. A quick solo pass takes 20 minutes. This makes it one of the fastest structured ideation methods available. When you need ideas by Thursday and it's Tuesday, SCAMPER delivers.
Competitive pressure
Section 4
When It Breaks Down
⚠
Failure Modes
Failure pattern
What goes wrong
What to use instead
Surface-level application
Teams treat each lens as a box to tick rather than a genuine thinking prompt. They generate one safe idea per letter and declare the exercise complete. The output looks like a SCAMPER session but contains nothing that wasn't already on the roadmap. Seven minutes of real thinking beats seventy minutes of performative brainstorming.
Pair with Abstraction Laddering to redefine the subject at a higher level before applying SCAMPER — this forces more ambitious transformations
Wrong problem entirely
SCAMPER generates variations of an existing thing. If the existing thing shouldn't exist — if the market has shifted, if the customer need has evaporated — then generating clever variations of a doomed product is wasted effort. Rearranging deck chairs, systematically.
First Principles Thinking or Reframing to question whether the subject itself is the right starting point
No evaluation discipline
Teams fall in love with a clever SCAMPER idea because it's novel, not because it's viable. "Reverse the pricing model!" sounds exciting in a brainstorm. Whether it survives contact with unit economics is a different question. SCAMPER without a rigorous evaluation step downstream produces innovation theatre.
The most dangerous failure mode is no evaluation discipline — and it's dangerous precisely because it feels like success. A SCAMPER session that produces 30 ideas feels productive. The team is energised. The whiteboard is full. But ideas are cheap. The hard part is determining which of those 30 ideas are worth the engineering hours, the market risk, the opportunity cost of not doing something else. Teams that treat SCAMPER output as a to-do list rather than a hypothesis list will scatter their resources across too many experiments and finish none of them well. The antidote is simple: schedule the evaluation session before you run the SCAMPER session. Put it on the calendar. Make it non-negotiable. The generation meeting and the evaluation meeting should be separated by at least 24 hours — enough time for the novelty glow to fade and for the team to assess ideas on merit rather than excitement.
Section 5
Visual Explanation
Section 6
Pairs With
SCAMPER is a generation engine. It produces raw material. What you do before and after it determines whether that material becomes strategy or stays on a whiteboard.
Use before
Abstraction Laddering
Before applying SCAMPER, use Abstraction Laddering to move up and down the problem hierarchy. "Improve our project management tool" is one level. "Help teams coordinate work" is higher. "Reduce the cost of miscommunication" is higher still. Running SCAMPER at different abstraction levels produces fundamentally different — and often more ambitious — ideas.
Use before
Reframing
SCAMPER transforms an existing subject. Reframing questions whether you've defined that subject correctly. If your team is running SCAMPER on "our onboarding flow" but the real problem is "customers don't understand what our product does," you'll generate elegant variations of the wrong thing.
Use after
Decision Matrix
Once SCAMPER produces 20–40 ideas, you need a structured way to evaluate them. A Decision Matrix lets you score each idea against weighted criteria — feasibility, market impact, strategic fit, time to implement — and surface the two or three that deserve real investment.
Use after
Impact-Effort Matrix
A faster, rougher evaluation tool than a full Decision Matrix. Plot SCAMPER outputs on a 2×2 grid of impact versus effort. The high-impact, low-effort quadrant is your starting point. Particularly useful when you need to move quickly from ideation to action.
Section 7
Real-World Application
Netflix — systematic transformation of the video rental model
The scenario
In 1997, Reed Hastings and Marc Randolph were looking at Blockbuster's dominant video rental model and asking a question that maps almost perfectly to a SCAMPER exercise: how many ways could this existing business be reconfigured? Blockbuster's model had clear, concrete components — physical stores, late fees, limited inventory per location, browse-and-rent behaviour, new-release windows, per-rental pricing. Each component was a surface for SCAMPER-style manipulation. Whether Hastings and Randolph explicitly used the framework is beside the point. The moves they made correspond to its operations with striking precision.
How the tool applied
Substitute: Physical stores replaced with mail delivery, then later with streaming. The rental medium changed; the core job-to-be-done (watch a movie at home) stayed constant. Eliminate: Late fees — Blockbuster's most hated feature and, paradoxically, a significant revenue source — were removed entirely. This single elimination became Netflix's most powerful early marketing message. Modify: The inventory constraint was transformed. A physical store could stock perhaps 3,000 titles. A centralised warehouse network could stock over 100,000. Netflix modified the scale of selection by an order of magnitude, which unlocked the long tail of niche content that Blockbuster couldn't economically serve. Reverse: Instead of customers going to the store, the product came to the customer. Instead of per-rental pricing, Netflix introduced a flat monthly subscription — reversing the transaction model from pay-per-use to all-you-can-watch. Combine: The recommendation algorithm merged browsing behaviour with content metadata to create a personalised discovery engine — combining what had previously been two separate activities (choosing what to watch and finding where to get it).
What it surfaced
The cumulative effect of these SCAMPER-style moves wasn't a slightly better video rental service. It was a categorically different business model. Each individual transformation — substitute mail for stores, eliminate late fees, reverse the pricing model — was relatively straightforward. The insight was in applying multiple transformations simultaneously. Blockbuster could have copied any single move. Copying all of them would have required dismantling its own business model, which is precisely why it didn't.
Section 8
Analyst's Take
Faster Than Normal — Editorial View
SCAMPER gets dismissed by sophisticated strategists as a creativity exercise for workshops — something you'd use in a design thinking bootcamp, not in a board room. That dismissal is a mistake. The tool endures because it solves a real cognitive problem that doesn't go away with experience or seniority. Functional fixedness actually gets worse as you gain expertise in a domain. The more deeply you understand how something works, the harder it becomes to imagine it working differently. A ten-year product veteran sees their product's architecture as load-bearing walls. SCAMPER forces them to ask: what if that wall is actually furniture? The checklist format — often criticised as simplistic — is the mechanism that makes this possible. You don't need sophistication to overcome a cognitive bias. You need a prompt that redirects attention. Seven prompts, applied systematically, do the job.
The failure mode I see most often: teams apply SCAMPER to the wrong level of abstraction. They run it on features when they should be running it on the business model. "What if we substituted a different colour for the button?" is technically a valid SCAMPER output. It's also useless. The tool produces ideas proportional to the ambition of the subject you feed it. Run SCAMPER on "our checkout flow" and you'll get UX tweaks. Run it on "how our customers discover, evaluate, purchase, and derive value from our product" and you'll get strategic options. Same tool, radically different outputs. The subject definition in Step 1 is doing 80% of the work, and most teams spend about 30 seconds on it.
The highest-leverage modification: run SCAMPER twice, at two different abstraction levels, and look for ideas that appear in both sessions. First pass: apply it to the specific product or feature. Second pass: apply it to the business model or value chain. Ideas that emerge independently at both levels — a pricing inversion that shows up when you SCAMPER the product and again when you SCAMPER the revenue model — are almost always worth pursuing. They represent structural opportunities, not surface-level tweaks. This double-pass approach takes an extra 45 minutes and consistently produces the two or three ideas that actually change the trajectory of the business. Everything else is incremental.
Section 9
Top Resources
01
Scamper: Creative Games and Activities for Imagination Development — Bob Eberle (1996)
Primary source
The original source, updated from Eberle's 1971 edition. Written for educators, which means the examples skew young — but the framework itself is presented with a clarity that later business adaptations often muddy. Read this for the pure method before layering on strategic applications. The book is short, under 100 pages, and the core technique occupies about 20 of them.
02
Applied Imagination — Alex Osborn (1953)
Book
The intellectual ancestor of SCAMPER. Osborn's checklist of "idea-spurring questions" — which Eberle later condensed into the SCAMPER acronym — appears in Chapter 12. The broader book is a foundational text on structured creativity, covering brainstorming rules, deferred judgement, and the separation of divergent and convergent thinking that makes tools like SCAMPER effective. Dense but essential for anyone serious about systematic ideation.
The "Eliminate-Reduce-Raise-Create" grid in Blue Ocean Strategy is essentially a strategic-level cousin of SCAMPER's Eliminate and Modify lenses. Kim and Mauborgne show how systematically removing and reconfiguring features creates uncontested market space. Read alongside SCAMPER for the strategic framing that Eberle's original lacks — particularly the value curve analysis that turns SCAMPER-style outputs into competitive positioning.
The Business Model Canvas gives you the nine building blocks of any business model — and each block is a perfect subject for SCAMPER. Substitute the revenue model. Combine two customer segments. Eliminate a key activity. Osterwalder and Pigneur's visual framework turns SCAMPER from a product-level tool into a business-model-level tool, which is where the highest-value applications live.
05
Thinkertoys: A Handbook of Creative-Thinking Techniques — Michael Michalko (2006)
Book
Michalko devotes an entire section to SCAMPER and places it within a broader toolkit of structured creativity methods. The book's strength is its worked examples across industries — advertising, manufacturing, technology, services — showing how the same seven lenses produce radically different outputs depending on the domain. The best practical guide for someone who wants to see SCAMPER applied beyond the standard workshop context.
Especially useful when competitors are converging on similar features and you need to find differentiation. The "Reverse" and "Eliminate" lenses in particular tend to surface contrarian moves that competitors haven't considered — precisely because those moves feel counterintuitive.
Organisational culture
Low-risk entry point for teams new to structured creativity. The checklist format feels concrete and manageable, unlike open-ended brainstorming which can intimidate analytical thinkers. Engineers and operators who resist "creative exercises" often engage productively with SCAMPER because it feels like a systematic process, not an improv class.
Follow with a Decision Matrix or Cost-Benefit Analysis to filter ideas against real constraints
Greenfield problems
When you're building something genuinely new — no existing product, no existing process — SCAMPER has nothing to operate on. It needs a concrete subject to transform. Asking "What could we substitute in our product?" when you don't have a product yet is an empty exercise.
Zwicky Box or Productive Thinking Model for generating options from scratch
Solo echo chamber
When one person runs SCAMPER alone, they tend to generate ideas within their own domain expertise and miss the cross-functional combinations that produce the best insights. The "Adapt" lens in particular requires exposure to other industries and disciplines that a solo practitioner may lack.
Delphi Method or Six Thinking Hats to bring in diverse perspectives
Complexity mismatch
For deeply systemic challenges — redesigning a healthcare delivery model, restructuring a supply chain — SCAMPER's seven lenses are too blunt. The tool works at the product or feature level. At the system level, you need methods that account for interdependencies, feedback loops, and second-order effects that SCAMPER's checklist format can't capture.
Scenario Planning or Causal Loop Diagrams for systemic redesign
SCAMPER applied to TaskFlow Pro — the seven lenses and their highest-potential outputs, with the two ideas selected for prototyping highlighted.
Use after
Pre-Mortem
Pick the most promising SCAMPER idea and run a Pre-Mortem on it before committing resources. "It's six months from now and this idea failed spectacularly. Why?" This stress-tests the idea against failure modes that the excitement of the brainstorm obscured.
Mental model
First Principles Thinking
SCAMPER transforms what exists. First Principles Thinking asks what should exist if you rebuilt from fundamental truths. Use them as complementary lenses: SCAMPER for evolutionary innovation (variations on the current), First Principles for revolutionary innovation (reimagining from zero). The best product strategies use both.
The non-obvious factor
Netflix's evolution reveals something important about SCAMPER that most practitioners miss: the lenses compound. Substituting the delivery mechanism (mail, then streaming) made the elimination of late fees economically viable, which made the subscription model possible, which funded the recommendation engine, which increased engagement, which justified the content library expansion. Each SCAMPER operation enabled the next. The tool is typically taught as seven independent lenses, but the most powerful applications treat the outputs as combinatorial — asking not just "what if we substitute X?" but "if we substitute X, what does that make possible to eliminate, reverse, or combine?" That second-order question is where the real strategic leverage lives.
