SCAMPER Method: Seven Creative Thinking Lenses for Better Ideas

What this unblocks:

A team stuck on an existing product or process with no idea where to change it, and a brainstorm that keeps returning the same few obvious answers. SCAMPER needs a subject with parts to interrogate; it will not move against a blank page or an abstract goal.

What the output lets you do:

Take the ideas it produces into an idea evaluation matrix before committing resources to any of them. SCAMPER generates volume, not quality, so the output needs a scoring pass before you decide.

What you have at the end:

A lens-by-lens idea set across all seven transformations, a voted shortlist of two or three ideas with an owner named against each, and the ready-to-use prompt bank, thirty-five questions across the seven lenses, to run the next session against a new subject.

Where SCAMPER comes from

Osborn wrote the checklist, Eberle built the mnemonic.

Alex Osborn, the advertising executive who coined “brainstorming”, published an idea-spurring checklist of questions in his 1953 book “Applied Imagination”. The checklist asked what could be adapted, modified, magnified, minified, substituted, rearranged, combined, or reversed about an existing idea- the same seven moves SCAMPER now organises under one mnemonic.

Bob Eberle, an American school administrator, took that checklist and arranged it into the seven-letter acronym in his 1971 book “SCAMPER: Games for Imagination Development”. Eberle was not writing for business leaders. He built the tool to teach creative thinking to schoolchildren, and the mnemonic’s simplicity- seven letters mapped to seven verbs- was designed for a classroom exercise, not a boardroom one.

Businesses adopted it later.

Design and innovation teams adopted Eberle’s mnemonic decades after he wrote it, pointing the same seven questions at products, services, and business models instead of the classroom exercises he designed it for. The logic travelled well because it was never tied to a particular subject: each lens forces a specific kind of transformation, regardless of what sits in front of the group. The audience changed, not the method.

The SCAMPER method

Run a session in five stages.

1. Define the focus before the session. Pick one concrete product, service or process, not an abstract goal. This costs about ten minutes of preparation and decides whether the session produces anything specific.
2. Work through each lens for five minutes. Two minutes of silent individual writing, three minutes of round-robin sharing with no critique. Seven lenses at five minutes each cost 35 minutes.
3. Vote and select in ten minutes. Give each participant three votes, and carry forward the two or three ideas with the most support.
4. Expand the selected ideas in 15 minutes. Ask what the idea looks like in practice, what would make it succeed, and what the first step is.
5. Close and assign ownership in five minutes. Name an owner for each idea and when you will check on it. An idea with no owner rarely survives the week.

A full run costs about 75 minutes for a group of five to eight people.

Substitute: what you can replace

Examine each part of your subject, materials, people, process, timing, or approach, and ask what could take its place.

Core question:

What can we substitute or change in our product, problem, or process?

In practice:

A restaurant replaced human order-taking with tablet ordering. Staff moved from taking orders to serving tables, and both errors and wait times fell. An email client replaced threaded conversations with a single priority-based stream. That changed how people work through their inbox.

Combine: what you can merge.

Look for value created by merging separate elements, so the result does more than either part did alone.

Core question:

How can we combine two or more parts of our product, problem, or process, so the whole does more?

In practice:

UK offset mortgage accounts combine a savings account and a loan account in one product. A customer’s savings reduce the interest charged on their mortgage, and they keep access to the money. Starbucks combined a coffee shop with somewhere to sit and work, and built its positioning around the “third place”, a term the sociologist Ray Oldenburg coined for a social space that is neither home nor work.

Adapt: what you can borrow.

Look outward, to other industries, other contexts, other time periods, for a solution that might transfer.

Core question:

What can we adapt from elsewhere into our product, problem, or process?

In practice:

Self-checkout systems adapted the airline kiosk check-in model for retail. Hospital teams have adapted aviation’s pre-flight checklist into surgical safety checklists, a shift credited with fewer preventable errors in operating theatres. Velcro adapted the way burr seeds hook onto fur: the Swiss engineer George de Mestral noticed it on a dog walk in 1941 and patented the hook-and-loop fastener a decade later.

Modify: what you can change.

Explore changes in scale, intensity, frequency, or form. This lens covers both magnifying and minifying an attribute.

Core question:

What can we modify, or emphasise more or less, in our product, problem, or process?

In practice:

Same-day delivery shifted the e-commerce fulfilment timeline and became a speed competition. Tapas restaurants shrank the portion, and turned dining from individual plates into shared exploration. Micro-learning platforms cut lesson length from hour-long sessions to five minutes, matching the format to how people give attention today.

Put to another use: what else this can serve.

Reframe the product or capability itself. Ask what other problem it might solve, what other audience it might serve, what other context it might fit.

Core question:

How can we put the thing to other uses?

In practice:

Pfizer originally developed sildenafil, sold as Viagra, for heart conditions. A side effect became the product. Bubble wrap was originally designed as textured wallpaper; its second life as packaging material built an entirely different business. Baking soda found new uses in cleaning, deodorising, and personal care long after it started as a baking ingredient.

Eliminate: what you can remove.

Fight complexity and feature creep by questioning necessity. Often the most successful products win through removal rather than addition.

Core question:

What can we eliminate or simplify in our product, design, or service?

In practice:

Apple has removed a component with nearly every major redesign: the floppy drive from the original iMac in 1998, the optical drive from the MacBook Air, the headphone jack from the iPhone 7. Each removal drew complaints at launch and was followed within a few years by the rest of the industry. Twitter, now X, eliminated long-form posting; the character limit became a communication style in its own right, not a constraint people resented.

Rearrange: what you can reorder.

Examine sequence, layout, hierarchy, and structure. Reordering often changes the experience more than any single addition or removal would.

Core question:

How can we change, reorder, or reverse the product or problem?

In practice:

Letting a customer check out as a guest, rather than forcing registration first, reverses the traditional browse-then-register sequence and often improves conversion. Netflix and the streaming services that followed it rearranged television from scheduled programming to on-demand access. IKEA rearranged the furniture shopping sequence, placing the warehouse after the showroom rather than treating them as separate visits.

Push further after the first pass:

through all seven lenses individually, three techniques generate ideas the single pass misses. Combine two lenses in one prompt, “what could we substitute and eliminate at the same time?”, since the most useful ideas often sit at the intersection. Add a harsh constraint after the first pass, “now do this again assuming the budget is 10 per cent of what it is today”, since a real constraint forces answers a comfortable brief never will. Or run SCAMPER in reverse: ask how to make the subject worse on purpose, then invert every answer into something to avoid.

Ready-to-use prompts by lens

Substitute

• What materials could be replaced with cheaper, stronger, or more sustainable alternatives?
• What if AI or automation replaced a human process?
• What if we changed the business model, subscription versus purchase, service versus product?
• What if we substituted digital for physical, or physical for digital?
• What conventional approach in our industry could we replace with an unconventional one?

Combine

• What features could merge to reduce complexity while increasing value?
• What partnership could create an offering neither party could deliver alone?
• What customer segments could we serve with one combined offering?
• What if we combined a premium element and an accessible one?
• What product do our customers already buy alongside ours that we could integrate?

Adapt

• What do successful companies in an unrelated industry do that we could adapt?
• What historical solution might apply now, with modern technology?
• What approach from our most sophisticated market might transfer to others?
• What emerging trend could we adapt before competitors do?
• What solution from a consumer market might work in a business one, or the reverse?

Modify

• What if we multiplied a key attribute, speed, size, price, quantity, tenfold?
• What if we made it dramatically simpler, or dramatically more complex?
• What if we changed the frequency: daily, hourly, once a year?
• What if we modified it for an extreme user segment, a total beginner or an expert?
• What would a luxury version look like? A budget version?

Put to another use

• What unexpected use have customers already discovered?
• What capability could solve a problem in an adjacent market?
• What by-product or data could create value somewhere else?
• What if we targeted the opposite demographic?
• What job, beyond our current positioning, could this do?

Eliminate

• What feature does a small minority of users engage with?
• What step in the process exists for historical reasons but adds no value now?
• What would a stripped-down version eliminate?
• What industry convention could we drop?
• If we had to cut half the features, what would remain?

Rearrange

• What if we reversed the typical sequence?
• What if customers controlled the order of operations themselves?
• What would happen if we reordered our own priorities?
• What if we decentralised what is currently centralised, or the reverse?
• What if the timing shifted: real-time, asynchronous, scheduled, on demand?

A worked example

Take one subject: a project management app’s onboarding flow, the screens a new user sees in their first ten minutes. A team of six runs a single 75-minute session against it.

Substitute produces the most ideas early: swap the tour video for an interactive checklist, swap default sample data for the user’s own first project, swap a single onboarding path for role-based paths for managers and individual contributors. Fifteen ideas in five minutes.

Combine merges onboarding with the trial’s usage tracking, so day-one behaviour flags the features a new user needs to see next. Eleven ideas.

Adapt borrows a mobile game’s progress bar to show setup completion, and a hotel check-in app’s single-screen summary before the tour starts. Nine ideas.

Modify stretches the tour from three screens to seven for enterprise accounts, which need more configuration, and shrinks it to one screen for solo accounts, which need almost none. Eight ideas.

Put to another use repurposes the onboarding screens as a permanent help menu, since much of what a new user needs to see, an existing user asks for again in month three. Seven ideas.

Eliminate removes the account-type selector entirely, sending every signup down one path and inferring account type later from usage. Six ideas.

Rearrange moves the payment step from before the tour to after it, so users experience the product before being asked to commit money. Ten ideas.

Sixty-six ideas across seven lenses in 35 minutes of generation. The team votes with three sticks each, narrows to three ideas, the role-based path, the check-in-style summary screen, and moving payment after the tour, and spends the remaining 25 minutes turning each into a one-paragraph brief with a named owner.

Where SCAMPER fails

It optimises for volume, not quality.

SCAMPER’s structure guarantees output: seven lenses, each one forces at least a few ideas even from a team with nothing much to say. That guarantee is also the weakness: a forced idea is not a good idea, and I have ended sessions with 60 ideas and no way to separate the strong three from the other 57. I pair a SCAMPER session with a scoring pass; an idea evaluation matrix works well before I call any of it progress.

The lenses collapse into each other on an abstract problem.

The seven lenses stay distinct only when the subject is concrete. Point SCAMPER at something abstract, “improve our culture” or “be more innovative”, and I watch Substitute, Adapt, and Combine collapse into the same handful of generic answers, because there is no component to substitute and no object to combine. I will not run the method on a goal, only on a subject with parts: a policy, a product screen, a single process step.

It needs something to modify, and cannot start from nothing.

Every lens asks what to change about an existing thing. I find SCAMPER useless in front of a genuinely blank page, no current product, no current process, nothing built yet to interrogate. When a team has nothing on paper, I reach for a generative method such as crazy eights or mind mapping first, then bring SCAMPER in afterwards to work on what the team has made.

Common questions

How does SCAMPER differ from ordinary brainstorming:

Brainstorming has no structure beyond quantity, so ideas tend to cluster around whatever the loudest voice in the room reached for first. SCAMPER forces the group through seven specific transformation types in turn, so teams can’t unconsciously skip the uncomfortable ones.

Which lens matters most:

None on its own, but Eliminate is the one teams skip most often, because removing something feels riskier than adding it. Teams that force themselves through Eliminate anyway tend to find its ideas among the strongest.

How many ideas should a session produce:

There is no fixed target worth chasing. What matters is coverage across all seven lenses. If one or two produced almost nothing, the subject was probably too abstract for that lens, not that the team ran dry, and a narrower subject is worth trying before repeating the session.

Does SCAMPER work for services as well as products:

Yes. Every lens asks about a component, and a service has components just as a product does: touchpoints, steps, timing, the people delivering it. The questions transfer without much rewording.

How often should a team run it:

Regularly enough to build fluency with the questions, rather than as a one-off exercise pulled out only when a big decision is stuck. A monthly session on a real, current problem builds more skill than an annual one on a hypothetical.

Key facts, current as of September 2026