Catalog
method#Product#Delivery#Governance

SCAMPER Model

A structured creativity method for systematic idea generation using seven prompting techniques to rethink products, processes and offerings.

The SCAMPER model is a structured creativity method using seven perspectives (Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse) to systematically rethink existing products, processes, or problems.
Established
Medium

Classification

  • Medium
  • Business
  • Design
  • Intermediate

Technical context

Virtual whiteboards (Miro, Mural) for collaborative idea capture.Project/task management (Jira, Trello) for follow-up.Documentation tools (Confluence, Google Docs) for storing outcomes.

Principles & goals

Use a systematic prompt pattern instead of spontaneous ideation.Cross-functional participation increases perspective diversity.Prototyping and fast validation are part of the workflow.
Discovery
Domain, Team

Use cases & scenarios

Compromises

  • Focus on quantity over quality of ideas.
  • Dominance of certain participants can reduce diversity.
  • Insufficient follow-up leads to discarded results.
  • Form small, heterogeneous groups for diverse perspectives.
  • Timebox each SCAMPER prompt to maintain focus and momentum.
  • Document outcomes immediately and assign owners.

I/O & resources

  • Description of the product or process under review.
  • Participant list with roles and expectations.
  • Facilitation materials and documentation templates.
  • Catalog of ideas with short concept descriptions.
  • Prioritized actions and next steps.
  • Prototype or test proposals for validation.

Description

The SCAMPER model is a structured creativity method using seven perspectives (Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse) to systematically rethink existing products, processes, or problems. Teams use it for idea generation, rapid prototyping and exploring solution variants in facilitated workshops.

✔

  • Enables structured generation of many ideas in a short time.
  • Encourages creative reinterpretation of existing resources.
  • Suitable for heterogeneous teams and different domains.

✖

  • Requires facilitation; otherwise outcomes can be superficial.
  • No guarantee of economic feasibility of the ideas.
  • Not suited for deep technical architecture decisions without further analysis.

  • Number of ideas generated

    Raw idea count per session; indicator of divergence.

  • Idea-to-prototype ratio

    Share of ideas that lead to prototypes or experiments.

  • Time-to-validation

    Time from workshop end to first validation of a proposal.

Onboarding feature variations

Team used SCAMPER to design several onboarding flow variants and prepare A/B tests.

Shortening approval process

Using Eliminate and Combine prompts, redundant checks were identified and removed.

New use-cases from existing components

Adapt and Put to other use led to two new business models based on existing modules.

1

Define objectives, select participants, and prepare materials.

2

Introduce SCAMPER and session rules.

3

Group work: each group works through the seven perspectives.

4

Merge, cluster and prioritize the results.

5

Derive prototypes/experiments and assign responsibilities.

⚠️ Technical debt & bottlenecks

  • Unclear documentation of outcomes hinders later implementation.
  • Unexecuted experiments create expectations without value.
  • Lack of integration into product backlog leads to dispersion.
Facilitation capacityTime for validationDecision transparency
  • Using SCAMPER as the sole basis for technical architecture decisions.
  • Collecting ideas quantitatively only, without evaluation criteria.
  • Workshops without clear objectives or follow-up.
  • Premature criticism blocks creative freedom.
  • Focusing on unusual ideas without feasibility checks.
  • Lack of prioritization leads to implementation backlog.
Facilitation and time management.Methodical creativity knowledge (SCAMPER principles).Domain knowledge about the product/process discussed.
Need for fast idea generation with low investment.Cross-disciplinary collaboration for problem solving.Focus on experimental learning and prototyping.
  • • Requires sufficiently heterogeneous participants for good results.
  • • Workshops need time slots free from daily operations.
  • • Results are not directly implementable without validation.