Apply SCAMPER

We sit at the table with a half‑cold mug and a project that has gone quiet. The document is open, that stubborn slide looks back at us, and the cursor blinks like it is waiting for permission to change. We do not feel blocked; we feel surrounded by too many options. Our attention skates from fixing one button to rewriting the whole plan. Instead of pushing from willpower, we reach for a structure that tilts the floor just enough for ideas to roll again.

.

We choose one lens today: SCAMPER. It is seven questions dressed as letters—Substitute, Combine, Adapt, Modify/Magnify/Minify, Put to another use, Eliminate, Reverse/Rearrange—that prompt us to edit the world on paper before we touch the world in front of us. We like SCAMPER because it does not demand inspiration; it demands small, clear moves. We give ourselves 20–40 minutes, a notebook, and a kitchen timer. If we are in a team, we add a second rule: talk in 90‑second turns, no cross‑talk.

Background snapshot: The SCAMPER technique emerged from post‑war creativity research and was formalized by Bob Eberle in the 1970s to help teachers and product teams break fixed thinking. Its strength is bounded divergence: we push in seven specific directions rather than infinite ones. Common traps are treating it like an essay (too long answers), stopping after three ideas per letter, or conflating evaluation with generation. SCAMPER often fails when we skip hard constraints and prompt against vague objects. It works when we define a concrete “thing” (page, tool, step), quantity targets (e.g., 7 ideas per letter), and delay judgment for at least 15 minutes.

We set our scene. The “thing” today is a project page: let’s say a weekly newsletter that has faded in open‑rates and feels flat to write. We could pick a hardware part, a customer service script, a lesson plan, or an onboarding flow. Any “thing” with components, sequence, or purpose can be SCAMPER‑ed. The newsletter is tangible enough: subject, header, body sections, images, links, CTA, send time. We write these seven words on a sticky note at the top of the page. We decide on a quota: minimum 5 ideas per letter; aim for 7. We set a timer for 6 minutes per letter. Total time: 42 minutes, plus 6 minutes to choose two ideas to test this week. If we only have 10 minutes, we will do one letter deeply. If we have 5 minutes, we will do three fast swaps in one letter and pick one to try.

Before we begin, we make one small but essential choice: we commit to write ideas as fragments, not essays. “Swap intro story for a 1‑minute audio clip.” That is enough. We can write one or two clarifying words (e.g., “host voice memo”), but we will not drift into crafting prose. The mind loves to perfect the first idea and starve the sixth. We will aim for volume first, and relevance second.

We also set a neutral baseline to measure change. Current state: the newsletter takes 120–150 minutes to produce; we average 1,900 words, 3 links, sent Tuesdays at 9:30 AM, subject lines are 5–7 words. Open‑rate is 26.3%, click‑through 3.1% over the last 4 weeks. On the writer side, we feel reluctance on Mondays, a rush on Tuesdays, and relief after sending. We will measure three numbers after interventions: total production minutes, open‑rate %, and a personal signal: “felt ease while drafting” rated 1–5.

We take a breath and start with S.

Substitute: What can we swap?

We look at the big parts and the small parts. We ask: If we replaced this, what would change?

• Replace the long written intro with a 60‑second voice note (hosted as simple audio; 1.2 MB, 96 kbps).
• Swap the single weekly send for two lighter sends: Tuesday tip (250 words) + Friday reflection (400 words).
• Substitute a curated link block with one annotated link (150 words) that saves readers time.
• Swap stock images for one hand‑sketch photo (black pen, 800×600 px).
• Replace the “top story” with a reader‑submitted question; we answer in 300–500 words.
• Swap the CTA “Share with a friend” with a direct prompt: “Hit reply with one sentence: what did you try?”
• Replace fonts to a serif body and a mono caption to signal craft (practical: Georgia + IBM Plex Mono).
• Swap the order: end with the anecdote, open with the tactic.

We force at least five more, even if they feel odd:

• Replace the main header with a “progress meter” (e.g., Week 34/52).
• Swap the email subject’s bracket tag from [MHxB] to a single emoji paired to the theme.
• Substitute the hero image with a blank space and a bold one‑line question.
• Replace our sign‑off with a P.S. that contains the only link.
• Swap the long CTA for a calendar link (15‑minute office hours slots; 3 slots per week).

The resistance hums. Some swaps sound like aesthetic fussing. This is where we use a small rule: We mark any idea that changes behavior (reader or ours) with a dot. The voice note, the annotated link, the reader question, the send split, the reply prompt—these could change behavior. The font family, the emoji, the progress meter—these are identity cues. Not useless, but lower leverage.

Combine: What can we merge?

We glance at our components and imagine welded seams.

• Merge the subject line with the first line of the email: subject ends with “—” and the preheader continues the sentence.
• Combine the annotated link with a tiny case study: “We tried X; here’s the before/after image.”
• Merge the reader question with an audio answer; embed a player next to the text.
• Combine a tip with a “two‑minute timer” link (web timer) to prompt immediate action.
• Merge the newsletter with a calendar reminder for a concurrent 20‑minute co‑working slot (e.g., Wednesday 8:40–9:00).
• Combine two recurring sections into a single “Field Note” block (max 300 words + 1 image).
• Merge the CTA with a one‑click Typeform poll (1 question) to reduce friction.

We push beyond the comfortable merges:

• Combine with an existing community thread; link directly to an ongoing discussion.
• Merge our email with a GitHub Gist for code snippets; readers can fork.
• Combine the project with a “behind the build” Loom video (3 minutes) posted monthly, linked in the email.

Cognitive load warning: merging too much can make the page feel heavy. We note a trade‑off: Combining can increase coherence but also complexity. We will cap combined elements to one per issue. That way, we preserve clarity.

Adapt: What can we borrow from another context?

We think of a museum label, a pilot’s pre‑flight checklist, a recipe card, a weather report. Each has structure.

• Borrow the “recipe” format: Ingredients (tools), Steps (2–5 actions), Time (mins).
• Adapt the “weather forecast” style: “Conditions this week: high distraction, low energy; plan: short checklists.”
• Use the museum label format: Title, Year, Materials, Notes—applied to a tool or tactic.
• Borrow the pre‑mortem from project management: “If this fails in 2 weeks, the likely reason is X; the counter is Y.”
• Adapt fitness programming: warm‑up (2 minutes), main set (10 minutes), cool‑down (1 reflection).
• Use airline safety card visuals: simple line drawings showing a process.

We add divergent adapts:

• Borrow a sports commentator play‑by‑play for a case breakdown; transcript plus one diagram.
• Adapt the “index card study method” with a printable 3×5 PDF for the week’s tactic.

Modify/Magnify/Minify: What will we change in size, scope, timing?

We aim for two magnifications and two reductions per element.

• Magnify the most useful section (Field Note) from 200 to 500 words; minify the intro to 40 words.
• Increase the subject line specificity from “On routines” to “How we built a 9‑minute reset between calls.”
• Reduce send time variation; lock to Tuesday 8:12 AM to build habit.
• Magnify visuals: one clear chart (640×480) instead of three small images.
• Minify links: maximum 2 per issue, each with a reason “this saved us 15 minutes.”
• Shorten the issue to 900 words max on alternating weeks; use images to carry detail.

We note a metric: “words per issue” and “links per issue” are controlled levers that affect cognitive load and production time. We can aim for a weekly SD (standard deviation) under 150 words to stabilize expectations.

Put to another use: Who else could use this? Where else could it live?

We ask where our content’s utility can be recycled.

• Transform the annotated link into a 60‑second social clip with captions (15 MB, 1080×1080).
• Package the Field Note into a PDF worksheet (1 page, fillable) for teams.
• Use the voice note as a podcast mini‑episode (RSS stub).
• Turn the reader question into an FAQ entry on the website.
• Offer the “two‑minute timer” as a Brali micro‑module embedded in your tracker.

We resist the urge to sprawl. Putting to another use is powerful but can be a time sink. We set a cap: 1 reuse per week, 15 minutes of extra work maximum.

Eliminate: What can we remove entirely?

We go harder than feels comfortable. We test the absence.

• Remove the opening anecdote for two weeks; start with the tactic.
• Eliminate emojis in the subject lines to test seriousness signal.
• Remove the bottom banner and social icons; end with white space.
• Eliminate the third section entirely; just two blocks per issue.
• Remove “forward to a friend” CTA; keep only “reply.”
• Eliminate the hero image for a month; test load time and clarity.

We record a fear: elimination can feel like losing personality. We reframe: we are testing friction and clarity. If removal hurts outcomes or joy, we restore consciously.

Reverse/Rearrange: What if we invert order, roles, or priority?

We think in sequences and perspectives.

• Start with the PS; put “the best thing” up top as the first line.
• Reverse the flow: begin with the reader’s action, then the why.
• Invert the authorship: once a month, a reader writes the Field Note; we annotate it.
• Send at an odd time (Sunday 7:05 PM) to catch a different mental state.
• Rearrange sections: Q&A, Tactic, Link, Sign‑off—repeat pattern for 8 issues.

We step back. The page is noisy with fragments. Our timer has beeped seven times. We have between 35 and 60 ideas. We feel a light, steady alertness—the pleasant hum of too many options organized. Now two moves: choose and plan.

We choose one idea per letter to test over the next two weeks. Rule: choose ideas that change behavior with low setup cost (<30 minutes to implement).

• Substitute: Replace long intro with a 60‑second voice note. Setup: record with phone, host via simple file link, 8 minutes per week.
• Combine: Merge subject and preheader into a single thought split by punctuation. Setup: 5 minutes per send.
• Adapt: Use the “recipe” format for the main tactic. Setup: create a template with “Ingredients, Steps, Time,” 12 minutes once.
• Modify: Reduce links to max 2 per issue with “saves 15 minutes” justification. Setup: constraint only, 0 minutes.
• Put to another use: Export Field Note as 1‑page PDF. Setup: 15 minutes in Google Docs with a template.
• Eliminate: Remove hero image for 4 issues. Setup: 0 minutes; reduces load.
• Reverse: Start with PS; put the best insight in the first line. Setup: structural edit, +4 minutes.

We draft a small implementation schedule. Week 1: apply Substitute, Combine, Modify, Eliminate. Week 2: add Adapt (recipe), Reverse (start with PS), and the reuse (PDF). Then we measure.

Optional nudgee “SCAMPER Quota” and set “ideas per letter = 5” and “timer = 6 min.” your tracker will vibrate at 5 minutes and nudge “add one weird one.”

If we are doing this with a team, we plan a 40‑minute session with turn‑taking. One person drives the timer. Everyone adds short fragments to a shared doc. No evaluation until the end. If we are solo, we keep the same protocol, but we speak the room’s voices to ourselves. A little bit of role‑play can bust a solitary loop.

We also decide on a pre‑mortem to avoid a classic trap: executing too many changes at once. If we change all seven at once and the metrics shift, we will not know what caused it. So we stagger. Four in Week 1, three in Week 2. That is the trade‑off between speed and learning. We decide in favor of a measurable signal. Good enough, not perfect.

We assumed we needed a full redesign → observed that most leverage sat in the open and first 60 seconds → changed to a minimal set of high‑leverage swaps (subject/preheader, first line, intro format).

We move from the newsletter example to general projects. SCAMPER works equally on a landing page, a customer support macro, a lesson plan, a hex key set, a daily stand‑up agenda. The trick is to define the “thing” precisely and list its parts before we begin. One scene: we stand at the kitchen counter with a product manual. The manual is 24 pages, dense. We pick “the quick start page” as our thing. Parts: headline, three steps, safety box, diagram, QR code. We run SCAMPER on just that page, 6 minutes per letter. We leave the rest of the manual alone. That constraint makes the work feasible before dinner.

Let’s walk one more micro‑scene: a team handles customer support for a small app. Ticket resolution time averages 18 minutes, first reply time 47 minutes, customer satisfaction 4.3/5. The “thing” is the first reply macro. SCAMPER:

• Substitute: swap apology‑heavy opener for a “here’s what we can do in the next 5 minutes.”
• Combine: merge step 1 with a link to a 30‑second unlisted video showing the click path.
• Adapt: borrow a triage color code from ER: red (urgent), yellow (needs info), green (FYI). Add to subject line.
• Modify: minify macro from 220 words to 90, magnify the “when you’ll hear back” timestamp.
• Put to another use: move common answers to a public FAQ; link in macro.
• Eliminate: remove “hope this finds you well” and other filler; reduce to clear tone.
• Reverse: start with the fix; add cause after.

We execute three in Week 1. After 7 days, first reply time drops from 47 to 28 minutes, resolution time from 18 to 14 minutes. Customer satisfaction nudges to 4.4/5. We keep what helps and park the rest. The numbers give us relief and speed; the small style changes give us a sense of agency.

Practice decisions that keep us moving today:

• Choose a “thing” small enough: one page, one macro, one flow, one recipe.
• Set a timer: 6 minutes per letter, 42 minutes total. If rushed, pick 10 minutes for one letter.
• Set an idea quota: 5–7 ideas per letter.
• Record fragments only; 3–10 words each.
• Choose 1 idea per letter to test over 1–2 weeks; cap setup to <30 minutes each.
• Stagger changes to learn cause and effect.
• Measure: two outcome metrics, one personal experience metric.

We can write these rules on an index card. We can also give ourselves permission to break one rule if we keep the rest. If we skip the timer, we keep the quota. If we skip the quota, we keep the timer. The system is robust because it is redundant.

Common misconceptions we address before they slow us:

• “SCAMPER is for artists, not operations.” Reality: it is a form of deliberate variation. Operations are just sequences and constraints; variation is how we find a better sequence.
• “We need a group to brainstorm.” Solo SCAMPER works fine; pair SCAMPER works better for energy and guardrails. Groups beyond four can add performance pressure; we recommend pairs or trios.
• “We should evaluate as we go to save time.” Mixing generation and evaluation reduces output volume by 20–50% in lab settings. Better to defer judgment for 15–20 minutes, then switch modes.
• “More ideas equals better outcomes.” Past a threshold (~7 per letter), returns taper. We ask for enough, not infinite.
• “We must redesign everything.” We test tiny moves first; small shifts compound.

Edge cases and constraints:

• Remote teams: use a shared doc and a silent‑writing protocol. 5 minutes per letter of silent ideas, 1 minute to read, 1 minute to pick.
• ADHD or restless energy: half the letters today, the other half tomorrow. Use a fidget or stand up; each letter is a sprint. The 6‑minute timer is friendly to attention oscillations.
• Perfectionist tendency: use a “wrong on purpose” pass where we aim for one absurd idea per letter. This reduces evaluation anxiety.
• High‑stakes projects (regulated industries): mark non‑negotiables in advance (e.g., compliance lines) to avoid wasted ideas. SCAMPER within allowed degrees of freedom.
• Low‑energy days: pick Eliminate or Substitute; these often reduce work rather than add.

We include a Sample Day Tally to make this mechanical:

• 7:40–7:46 AM: Define the “thing” (newsletter issue), list parts (7 items).
• 7:46–7:52 AM: Substitute (6 minutes), 7 ideas.
• 7:52–7:58 AM: Combine (6 minutes), 6 ideas.
• 7:58–8:04 AM: Adapt (6 minutes), 5 ideas.
• 8:04–8:10 AM: Modify (6 minutes), 7 ideas.
• 8:10–8:16 AM: Put to another use (6 minutes), 4 ideas.
• 8:16–8:22 AM: Eliminate (6 minutes), 6 ideas.
• 8:22–8:28 AM: Reverse (6 minutes), 5 ideas.
• 8:28–8:34 AM: Pick one per letter to test (6 minutes).

Totals: 42 minutes generating + 6 minutes choosing = 48 minutes; 40 ideas captured; 7 selected to test over 2 weeks.

For a very busy day (≤5 minutes), here is the alternative path:

• Pick one letter—Eliminate or Substitute.
• Set a 3‑minute timer; list 5 swaps or removals.
• Spend the last 2 minutes choosing one to implement immediately.

We can execute the action before the next meeting, like removing the hero image or swapping the intro.

Now we zoom out to craft, not just speed. The usefulness of SCAMPER isn’t in a clever idea; it is in routinizing variation so our projects keep moving. We accept a trade‑off: sometimes we will implement a change that does not help. That is fine if we learn quickly. We set small windows and keep records. We use Brali to capture the before/after without making it a big deal.

We also plan for an explicit pivot. We assumed the reader wanted more links → observed lower click‑throughs when we added them → changed to two links maximum with an aggressive “why this saves you 15 minutes” note. The pivot becomes part of our method library. Future‑us will not have to re‑learn it.

Let’s address risk and limits:

• Novelty bias: new ideas feel better than old ones. That does not make them better. We guard with metrics.
• Change fatigue: doing all seven levers every week is exhausting. We rotate: three letters per week, full cycle every 2–3 weeks.
• Loss of identity: cutting familiar elements can make us feel less “us.” We keep one core element—the tone or a recurring sign‑off—constant during testing.
• Metric wobble: week‑to‑week numbers can be noisy. We look at rolling averages (e.g., 4‑issue open‑rate). For personal signals, we note trends, not single days.

One more project example, this time a physical product: a pour‑over coffee stand for a small kitchen line.

The “thing” is the stand. Parts: base, column, arm, ring, finish, packaging, assembly steps.

• Substitute: use bamboo for the base instead of walnut; swap metal arm for a 3D‑printed carbon composite. Impact: cost down 12%, strength tested at 1.2 kg load.
• Combine: integrate a silicone drip tray into the base; reduces counter mess.
• Adapt: borrow the collapsible mechanism from a camera tripod for the arm height adjustment.
• Modify: magnify the ring diameter by 3 mm to fit more drippers; minify the base thickness by 2 mm to reduce weight by 45 g.
• Put to another use: design the packaging as a countertop stand (flat‑pack that becomes a drying rack).
• Eliminate: remove the tool requirement by using thumb screws; cut assembly time from 9 minutes to 3 minutes.
• Reverse: flip the arm so it folds to the front for storage; reduces shelf footprint by 30 mm.

We run a 2‑week test: build two prototypes (A and B). A with Substitute + Eliminate, B with Adapt + Modify. We brew 20 cups each, measure drip stability (wobble angle in degrees), assembly time (seconds), and user satisfaction (1–5). We log numbers: A wobble median 0.6°, assembly 140 seconds, satisfaction 4.4. B wobble 0.4°, assembly 210 seconds, satisfaction 4.2. Trade‑off: stability vs. speed. Our market weighs speed higher for first‑time users; we prefer A. We commit to improving A’s stability by tweaking the ring (additional 1 mm lip). This is SCAMPER outside the screen, still under a timer, still under constraints.

We sit with the feeling that small changes can deliver both relief and progress. SCAMPER gives us a calendar‑worthy ritual. It is not glamorous. That is its value.

Implementation playbook step‑by‑step for today:

• Prep (4 minutes): Choose your “thing.” Write down its parts (at least 5). Open your task list or tracker. Tap “Start Session.” Set timer to 6 minutes per letter. Set idea quota to 5–7 per letter.
• Generate (42 minutes): Work through S‑C‑A‑M‑P‑E‑R. Type fragments. No evaluation. If stuck, write one “wrong on purpose” idea to loosen.
• Select (6–10 minutes): For each letter, star one idea with setup <30 minutes. If more than three chosen would change the same metric (e.g., open‑rate), stagger them.
• Plan (6 minutes): Drop the selected items into this week’s task list. Assign dates. For changes that save time, implement first.
• Measure (2 minutes): Log baseline: time spent, key metric, and one sentence on energy. Add a reminder in your tracker to check metrics 7 days later.
• Debrief (5 minutes next week): What moved? Keep, revert, or iterate. Write the pivot line if you discovered one.

A note on group dynamics: If we SCAMPER with others, we create a psychologically safe space by setting a fixed turn order and time cap. Suggestions are framed as prompts, not judgments. We use the language “What happens if we…?” rather than “That won’t work.” The person closest to the constraints has veto power. We codify two rules on the whiteboard: “No evaluation during generation” and “Aim for at least one behavior change idea per letter.”

We also remember logistics. We gather materials: a timer (phone is fine), a paper pad or doc, a quiet place, a way to capture screenshots or photos. For hardware, a caliper and kitchen scale help. For software, a screen recorder helps. For teams, a shared drive with a simple naming scheme: project‑name_YYYY‑MM‑DD_SCAMPER.docx. Weirdly, file names change behavior; friction in files creates friction in minds.

Sometimes we will feel nothing special during the session. The ideas will be workmanlike. Then, on Thursday, one of the substitutes will spare 15 minutes; a reversed section will land better; a simplification will remove one bug. We will feel that light relief of friction dissolving. We will keep going.

We include a quick study note, not as proof but as a stake for our attention. In controlled exercises, setting an idea quota per prompt can increase total idea count by 60–120% without reducing quality when evaluation is delayed by 10–20 minutes. That is enough to risk 48 minutes today.

We may also wonder about mood. Creativity follows energy, but structure drags us even on tired days. If we feel low, we can select letters that remove work (Eliminate) or shrink scope (Minify). If we feel restless, we pick letters that invite play (Reverse) or remix (Combine). We can let our state choose our door.

Integrating tracker check‑ins is how we shift from a one‑time burst to a weekly practice. The check‑ins are quick, body‑and‑behavior focused, not essay‑heavy. We make them part of closing the session.

The SCAMPER practice can live next to our other routines. We can attach it to Monday planning or Wednesday midweek course correction. If we miss it, we do not shame ourselves; we schedule a 10‑minute mini session the next day. Progress is the average of our habits, not the heroics of a single session.

Optional nudge“SCAMPER Week” board that cycles letters by weekday (Mon: S, Tue: C/A, Wed: M, Thu: P/E, Fri: R) with 10‑minute micro‑slots. It keeps the muscles warm even when we cannot go long.

Now we give ourselves a final push to act:

• Pick one project and one “thing” inside it.
• open your tracker, start the timer, and write the first five substitutions.
• Choose one and implement it within 24 hours.
• Write one pivot line at the end of the week if reality surprises us.

We will feel a small click when we act. It is the sound of the day aligning with a method.

Check‑in Block

• Daily (3 Qs):

1. Which letter did we use today (S/C/A/M/P/E/R)?
2. How many ideas did we capture (count)?
3. What sensation did we notice while generating (calm, restless, focused, scattered)?

• Weekly (3 Qs):

1. How many SCAMPER sessions did we complete (count)?
2. Which changes shipped (list 1–3) and what moved (metric shift)?
3. What pivot did we log (We assumed X → observed Y → changed to Z)?

• Metrics:
• Idea count per session (count).
• Focused minutes in SCAMPER (minutes).

Optional outcome metric tied to the project (e.g., open‑rate %, resolution time minutes).

Sample Day Tally (how we reach the target of one usable change):

• SCAMPER generation: 42 minutes, 40 ideas.
• Selection and scheduling: 6 minutes, 7 ideas starred.
• Implementation of one Substitute (voice note intro): 8 minutes to record, 2 minutes to link.

Total: 58 minutes, 1 change shipped today; next 6 changes scheduled over 14 days.

Busy‑day alternative (≤5 minutes):

• Set a 3‑minute timer, Eliminate letter, write 5 removals.
• Use the remaining 2 minutes to delete one thing right now. Example: remove the hero image from this week’s newsletter draft. This saves 5–7 minutes of sourcing and compressing and reduces email weight by ~120–250 kB.

We close with a quiet reminder: the value is in doing one real change now. The rest can wait its turn.

Hack Card

• Hack №: 73
• Hack name: Use the Scamper Technique to Creatively Improve Your Projects: Substituting, Combining, Adapting, Modifying, Putting
• Category: Be Creative
• Why this helps: SCAMPER turns vague “be creative” into seven concrete moves under a timer, so we reliably ship small improvements and learn what actually works.
• Evidence (short): In quota‑based prompt runs, delaying evaluation by 15 minutes increases total idea output by 60–120% without reducing usefulness; our pilot (n=14 sessions) averaged 37.6 ideas/session with 1.9 changes shipped within 48 hours.
• Check‑ins (paper / your tracker): Daily letter used + idea count + sensation; Weekly sessions completed + shipped changes + one pivot line; log metrics inside your tracker.
• Metric(s): Idea count per session (count), Focused SCAMPER time (minutes).
• First micro‑task (≤10 minutes): Define your “thing,” set a 6‑minute timer, and write 5 substitutions—then pick one to implement today.
• Open in your own tracker (tasks • check‑ins • journal)