SCAMPER is a checklist of transformations — substitute, combine, adapt, modify, put to another use, eliminate, reverse — applied to something that already exists in order to generate alternatives to it. Treated as a recurring habit rather than an occasional workshop, it turns idea generation into scheduled work.
Quick Overview
The subject around this article is crowded, so its boundary is worth stating in one sentence. This is an account of a single named ideation technique operated as a recurring team habit — the SCAMPER transformations and the session discipline that keeps fragile ideas alive long enough to be judged — and not an account of the user-centred design process that runs from empathy through definition and ideation to prototype and test.
Both are legitimate and they answer different questions. A design process answers how do we discover what to build for this user, and begins by going outward to research. The technique here answers something narrower: we already have a thing — a process, a product, an offer — and we need alternatives to it by the end of this session. It works inward, on what exists, by deliberately deforming it.
The other distinction worth naming is one of cadence. Design processes are run as projects. What follows is run as a habit, in short slots, repeatedly, on ordinary problems rather than flagship ones — and the repetition is the point, because a capability exercised occasionally does not develop.
Why Waiting for Inspiration Fails
The assumption underneath most unsuccessful creative work is that ideas arrive rather than get produced, and that the team’s job is to be in the right mood when they do. It is a comfortable belief, because it makes the absence of ideas nobody’s fault.
The working alternative is unglamorous: structured prompts reliably outproduce open invitations. Asked to “think of something better”, a group returns whatever it already believes. Asked a specific and slightly odd question about the thing in front of it, the same group produces material it did not have a minute earlier — not because the question is clever, but because it forbids the default answer.
That is all this technique is: a set of constraints that make the obvious answer unavailable, applied to people who already know the subject.
The Transformations, One at a Time
Each prompt takes an existing product, process or problem and applies a single deformation to it. The value is in doing them one at a time — running the whole list at once produces a shallow pass at each.
- Substitute — what element could be exchanged for another? An onboarding built from meetings and slide decks becomes a guided interactive walkthrough the new joiner completes at their own pace.
- Combine — what two things that currently sit apart could be merged? A customer-relationship system joined to the satisfaction survey means the salesperson sees the client’s current standing before dialling, rather than after.
- Adapt — what solution from an unrelated field could be borrowed? A team improving business-to-business delivery visibility studies how consumer parcel tracking sets expectations, and adapts that mechanism rather than inventing one.
- Modify — what could be enlarged or reduced in scale? A long webinar shrinks into a series of very short practical clips, or expands into a multi-track virtual event; both are different products from the original.
- Put to another use — what existing asset could serve a purpose it was not built for? An internal troubleshooting knowledge base, simplified and published, becomes a marketing asset and reduces inbound support load.
- Eliminate — what could be removed entirely? A reporting process is examined and the fields nobody reads downstream are deleted — usually the fastest available improvement and the least attempted.
- Reverse — what happens if the order is inverted? The standard sequence of paying and then using becomes using and then, perhaps, paying — which is how trial and freemium models came to exist.
The prompts are deliberately mechanical. Their function is to occupy the evaluating part of the mind so the generating part gets a clear run.
Running It as a Habit, Not an Event
The common failure is to treat this as workshop material: an away-day, a facilitator, a wall of sticky notes, then nothing for another year. Capability does not accumulate that way. It accumulates through short, frequent, low-ceremony repetition.
A workable pattern is a standing slot, short enough to fit an ordinary working day without displacing anything, with one real problem and one transformation chosen in advance. Brevity is a feature, not a compromise: a tight slot removes the expectation of a breakthrough, and removing that expectation is what allows people to say the half-formed thing.
Use real problems, not exercises. Invented puzzles signal that the activity is training rather than work, and participation drops accordingly. A genuine irritation from the current sprint produces better engagement and occasionally something the team implements — the fastest way to establish that the slot is worth keeping.
Where the ambition is to build a facilitated capability across a group, the structured techniques and their facilitation are covered in the programme on creative problem solving in a team.
Protecting Ideas Long Enough to Judge Them
A team can know every technique available and still generate nothing, because ideas are killed before they finish being spoken. The mechanism is the same reflex every time: the immediate objection, introduced with “yes, but”. Someone proposes a customer conference; the response is that there is no budget; the idea is over, and the proposer has learned the cost of speaking first.
The countermeasure borrowed from improvised theatre is the “yes, and” rule — accept the proposal as offered and extend it, rather than test it. The conference becomes a small free online session to gauge whether the subject draws interest at all. The change is grammatical and its effect is not: it converts the group’s default posture from filtering to building.
This is the practical face of psychological safety. A team that meets a weak idea with curiosity gets to see the strong idea behind it, because most good ideas arrive badly expressed. A team that meets it with correction only ever sees the safe ones.
Separating Generation From Selection
The rule above is not an argument against critical judgement. It is an argument about sequence. Generation and evaluation are different activities requiring incompatible postures, and running them simultaneously means doing both badly — the generation is inhibited and the evaluation is applied to material too undeveloped to assess.
The fix is to announce the phases and keep them apart. During generation the target is quantity and objection is deferred; during selection, feasibility, cost and effort return in full force and most of the material is discarded, as intended. Delaying scrutiny costs nothing; applying it early costs the ideas. Teams that adopt the split find selection becomes easier, because there is finally enough material for a real comparison rather than a defence of the only surviving proposal.
What the Leader Actually Owns
The leader’s job is not to be the most inventive person present — that role, taken up enthusiastically, reliably suppresses everyone else. It is to own the conditions: that the slot exists and is protected from operational encroachment, that the phases stay separated, that the “yes, and” rule holds even when the leader is the one wanting to object, and that something generated is visibly acted on.
That last one carries most of the weight. A team whose ideas never go anywhere stops producing them, correctly concluding the activity is decorative. Implementing even a small suggestion, and saying where it came from, does more for the habit than any technique.
The broader process view — how structured ideation sits inside a user-centred design cycle — is set out in the material on the staged design thinking process, and its toolkit in the overview of design thinking tools for innovation and teams.
Frequently Asked Questions
What does SCAMPER actually stand for?
It is an acronym for a checklist of transformations: substitute, combine, adapt, modify (or magnify), put to another use, eliminate, and reverse or rearrange. Each is a prompt applied to something that already exists, and the method works by forcing a specific deformation rather than inviting general creative thought.
How is this different from brainstorming?
Brainstorming issues an open invitation, which tends to return whatever the group already believed and lets the loudest participant set the direction. A transformation checklist supplies a specific constraint instead, making the default answer unavailable and giving quieter participants a defined thing to respond to.
How long should a session be?
Short, fixed and repeated. A brief slot on a recurring basis outperforms an occasional long workshop, because the aim is a developed habit rather than a single yield of ideas. Keeping the slot tight also removes the pressure to produce a breakthrough, which is precisely the pressure that stops people offering unfinished thoughts.
Does this work for teams doing mostly routine work?
Yes, and often better, because routine work holds a large stock of unexamined process that responds well to the eliminate and reverse prompts. The candidates are the steps everyone performs without being able to explain why, which survive mainly because nobody has been given a structured occasion to question them.