01 · Purpose and boundaries
Purpose and boundaries
SCAMPER is a structured creativity method that changes an existing product, service, or process through seven prompts: substitute, combine, adapt, modify, put to another use, eliminate, and reverse or rearrange. Wording variants exist, especially around modify and reverse. The prompts stimulate alternatives; they do not certify that an idea is useful or safe.
Select a sufficiently concrete object of redesign. A parcel-packing sequence or replenishment route is manageable; an entire supply chain is usually too broad for one pass. Describe its current purpose, steps, resources, and constraints. Identify what must remain true, such as correct identity, safe handling, traceability, and customer service. The method expands possibilities within that functional understanding.
02 · How the method works
How the method works
Substitute asks what material, role, information source, or mechanism could replace the current one. Combine asks which compatible activities or resources could work together. Adapt asks whether a principle from another context could address the same function. Modify asks whether size, timing, quantity, layout, or another characteristic could change.
Put to another use asks whether an existing resource has an additional suitable function. Eliminate asks whether a step or requirement is genuinely unnecessary, not merely inconvenient. Reverse or rearrange asks whether sequence, direction, responsibility, or timing could change. Work through the prompts deliberately but do not force an idea for every letter.
Record each candidate with its operating mechanism and assumptions. Separate generation from evaluation, then apply must-pass requirements and compare alternatives. Check interactions: combining two checks may lose independence; reversing a sequence may require information earlier than it exists. Develop selected concepts and test them in a bounded pilot.
03 · Worked logistics example
Worked logistics example
Fictional ReedPoint packs 500 subscription orders daily. Each order requires selecting a carton, adding a product insert, applying a label, and checking contents. The process takes four minutes of direct work per order, with periodic searching for inserts. The objective is to reduce search and handling while preserving correct product and label identity.
Substitute produces an approved digital insert for eligible customers. Combine suggests presenting the correct insert with the product kit. Adapt borrows a pharmacy-style item identity check. Modify suggests adjustable point-of-use slots. Put to another use suggests a returned empty tote as a replenishment signal. Eliminate challenges duplicate transcription of the order number. Rearrange suggests checking the kit before sealing rather than reopening a carton afterward.
The team selects kit-presented inserts and removal of duplicate transcription after confirming the warehouse system already preserves the required identity record. A five-day pilot of 100 orders daily reduces direct work from four to 3.4 minutes per order: 0.6 × 500 = 300 minutes across the pilot. Two wrong inserts are detected before sealing, prompting an additional kit identity control before expansion.
04 · Interpretation and decisions
Interpretation and decisions
SCAMPER creates alternatives, but the pilot must determine their operational effect. The 300-minute reduction applies to the 500 pilot orders over five days, not to every daily order in the warehouse. If sustained across all 500 daily orders, the estimate would become 300 minutes per day, subject to mix, support work, and capacity conditions.
The detected wrong inserts show that combining kit presentation with picking creates a new interface risk. Add prevention or source detection before claiming the redesign preserves quality. The digital-insert concept remains deferred because some customers require printed documents. An idea can be valuable for a segment without being appropriate for everyone.
05 · Common misapplications
Common misapplications
Using the acronym as a checklist of mandatory changes produces contrived ideas. Some prompts will be unproductive, and several may lead to the same concept. Preserve the functional objective instead of forcing novelty.
Eliminate is particularly prone to misuse. Removing a required control, traceability record, or safety task is not improvement merely because it saves time. Substitute may introduce material compatibility, privacy, or supplier risks. Combine may reduce independence or create workload peaks. Reverse may violate information dependencies. Ask what new failure modes each transformation creates and what evidence is needed before implementation.
06 · Advanced adaptation
Advanced adaptation
Apply SCAMPER to individual functions rather than only visible objects. For label application, substitute the identity mechanism, combine verification with application, adapt a keyed interface, modify timing, reuse a completion signal, eliminate transcription, or rearrange printing and handling. This exposes deeper design choices than changing furniture or colors.
For digital services, transform statuses, authorization, notifications, and recovery paths. For material flow, transform container size, route frequency, and handoff ownership. Combine promising concepts carefully and test their interfaces. Use observed failures to refine prompts for a second round. The method remains a disciplined source of hypotheses whose value depends on operational development and verification.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce scamper within a clearly named operating boundary. Identify the product family, shift, equipment, and handoffs affected; record what happens immediately before and after that boundary. A change that improves one task while exporting its delay to another department has not established an improvement. Agree who can stop the trial, who handles exceptions, and which customer commitment takes priority when the normal rule cannot be followed.
Establish a baseline from actual work rather than a single demonstration. Include normal variation in order mix, replenishment timing, staffing, and workload. Keep the denominator visible: minutes per order, defects per shipment, or completed lines per available hour answer different questions. Record the workload and conditions alongside each observation so that a quiet trial period cannot masquerade as better performance. Observe the process with the people who do it; their explanation of interruptions often changes the proposed design.
Start with a reversible pilot large enough to expose handoff problems. Explain the expected mechanism before launch: which action changes, which delay or failure it removes, and which result should respond. Train all affected shifts and support roles using the same operating definition. During the pilot, capture exceptions as information about the design. Do not conceal them through unofficial stock, unrecorded overtime, or a specialist who quietly repairs every failure.
Review customer service, safety, quality, work content, and inventory together. A faster average with more severe late orders may be unacceptable; a lower inventory level with repeated emergency deliveries may have displaced the cost. Investigate variation before declaring success. If the expected mechanism does not appear, revise the design or return to the baseline rather than defending the idea. A promising observation is a reason to test more conditions, not proof that every operating context will behave identically.
After a successful trial, make the new rule part of daily work. Give an accountable owner responsibility for the operating standard, change control, training, and periodic review. Specify the abnormal condition that requires escalation and the person who responds. Check whether the improvement remains effective when a trained colleague is absent or demand changes. Sustain the mechanism through routine management and learning; documentation is useful only when it describes the process people actually follow.
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.