;

CPO Kit Brainstorming

Featured Image

Make the Old New, Then Prove Which Idea Earns Its Build

Most brainstorming sessions don't fail for lack of ideas. They fail because nobody decides, on the way out of the room, which idea is actually going anywhere.

SCAMPER is a seven-lens technique for generating exactly that range of ideas. Developed by Bob Eberle in 1971 to teach children creative thinking, and built on Alex Osborn’s earlier brainstorming principles from Applied Imagination, it takes something that already exists – a product, a process, a service – and re-examines it through seven prompts: what can we Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, or Reverse. Rather than starting from a blank page, you start from what’s already true and interrogate it from seven different angles. The acronym exists purely so the questions are easy to recall under pressure, in a workshop, on a whiteboard, mid-conversation.

The instinct is to dismiss this as a gimmick, or worse, to run it as an unstructured free-for-all where the loudest voice in the room wins.

Let’s reverse both assumptions. The evidence on group brainstorming is not kind to the free-for-all format: shy or introverted contributors stay quiet, people quietly withhold their more extravagant ideas for fear of judgement, and groups tend to converge on agreement rather than genuine divergence. Structure isn't the enemy of creativity here; it's the fix. SCAMPER's seven separate lenses force each individual to pass through a problem that counters groupthink before anyone compares notes.

McDonald’s is the proof this compounds rather than being a one-off exercise. A menu that began with hamburgers, cheeseburgers, fries, and milkshakes now runs to over a hundred items, built by repeatedly substituting ingredients (chicken, fish, plant-based patties) and modifying formats to fit new markets. When public appetite shifted toward healthier eating, they adapted, dropping the "Super-Size" option and reframing around “fresh” and “organic.” None of this came from one legendary brainstorm. It came from repeatedly applying the same seven lenses over decades.

This is precisely where SCAMPER belongs inside Design at Scale™: Design Shaping. We define that stage explicitly as "the initial stage of divergent and exploratory thinking,” the point where the job is "determining which idea yields the best possible solution," and its own tools call for a “Design-Shaping Workshop" because, as we put it, "no great design is created in isolation." SCAMPER is a ready-made engine for exactly that workshop, seven structured questions to interrogate an existing proposition rather than a blank-page session hoping for inspiration to strike.

But DaS™ doesn’t stop at generating range. Design Shaping’s own Capture Documentation tool exists because ideation without a record is just an entertaining afternoon, and whatever idea survives is expected to earn its way into the Proposition Identification Document’s High-Level Requirements before it goes anywhere near delivery. That’s the piece SCAMPER alone doesn’t give you: a rule for which of the seven-lens ideas actually gets built. Our own Journal carries a lighter, individual version of the same discipline in its Silly Ideas practice, one or two ideas jotted in a notebook daily, reviewed quarterly, precisely the "write it down before you share it" habit that counters groupthink in the first place. After reviewing 274 design methods over two decades, we keep landing on the same gap: it isn’t a shortage of good exploration techniques; it's the gap between exploration and actual delivery.

"This is just a gimmick acronym, real creativity can't be forced into seven boxes"

Is the most common objection. The seven lenses aren’t creativity itself; they’re the retrieval cues Eberle designed so a team under time pressure doesn’t need to invent structure from scratch. Constraint is what produces range here, not a cage around it.

"Group brainstorming is groupthink theatre”

Is the second, and it has its own built-in fix. SCAMPER already asks each lens as a separate, specific question, which naturally produces an individual pass through the problem before the group compares answers, the same "write first, share second" principle that counters the exact failure mode critics point to.

"We run these sessions constantly and nothing ever ships”

Is the third, and it's not a SCAMPER problem. It's a documentation problem, identical to the one we’ve flagged before with the Value Proposition Canvas: good ideation evaporates the moment nobody captures which idea was chosen, and why.

SCAMPER is a genuinely well-evidenced way to generate range before you commit to depth. But range without a documented decision is just a longer meeting. Design at Scale™ doesn’t ask you to abandon SCAMPER, or any of the 274 methods it draws from; it asks you to give whichever one you choose a documented place to land once the workshop ends.

Next time you run a SCAMPER session, don’t just capture the ideas on the whiteboard. Capture which one you're taking forward, and why. That’s the difference between exploration and delivery. More Supply resources at designatscale.co/spy.

REFERENCES

SUMMARY

  • SCAMPER re-examines an existing product or process through seven lenses (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) rather than starting from a blank page.
  • Structured, individual-first ideation (SCAMPER’s design) counters the documented failure modes of free-form group brainstorming: silenced introverts, withheld ideas, groupthink convergence.
  • McDonald’s decades-long menu evolution shows the technique compounds through repeated, disciplined use, not a single workshop.
  • SCAMPER belongs inside DaS™'s Design Shaping stage, but its output still needs Capture Documentation and a route into the PiD to survive past the workshop.
  • The problem was never a shortage of ideation methods (274 reviewed) — it's the same recurring gap between exploration and delivery.

https://www.figma.com/community/file/1383527548130483313/das-cpo-kit-brainstorming

Happy scaling through design!

Hey, I’m Jiri Mocicka.
London-based Product Design Director, Trusted Advisor and Author of Design at Scale™. The method that empowers individuals to shape the future organisation through design.
If you have a question, join our Community and reach out to like-minded individuals who scale design propositions. An online Academy can help you to define teams of 01, 10, and 100, and 1% is supported by Grid Magazine and Supply section, where we bring more insights weekly on how to become a design leader in your Agentic Organisation

Jiri Mocicka

AVATAR

inResearch

21

inWriting

45

Released

260
EMT

Related.

Featured Image
Empathy as Infrastructure: The Internal User Experience of Scaled Systems The ultimate metric of any enterprise system is a deceptively simple question: Does it …
February 16, 2026
 · 
4 min read
Featured Image
Organisations trimming entry-level positions in pursuit of AI-driven efficiencies are engaging in a calculation that appears eminently rational when viewed through the lens of …
April 3, 2026
 · 
7 min read
Featured Image
Aligning Human Senses and Technical Communication to Unlock Enterprise Scale In a quickly evolving global corporate environment, cross-functional alignment is the ultimate metric of …
April 6, 2026
 · 
4 min read
Featured Image
Yes, let's begin. Where shall we start? The newsletter, articles, posts and many other forms of content are generated in order to scale your …
January 30, 2020
 · 
2 min read
Featured Image
Write the Press Release Before You Write a Line of Code Most teams write documentation to justify what they’ve already decided to build. Amazon’s …
February 15, 2023
 · 
5 min read
Featured Image
Build Down From Why, Or You’re Just Building Features Most product visions get written backwards: the feature list comes first, and a mission statement …
February 8, 2023
 · 
5 min read
Featured Image
Build the Fit Before You Build Anything Else A product doesn’t usually fail because the build was bad. It fails because nobody has proved …
January 11, 2023
 · 
5 min read
Featured Image
Make the Old New, Then Prove Which Idea Earns Its Build Most brainstorming sessions don't fail for lack of ideas. They fail because nobody …
February 1, 2023
 · 
5 min read
Featured Image
Make It a Habit, Not a Poster Most Value Proposition Canvases die the same way: printed for a workshop, filled in over an afternoon, …
January 18, 2023
 · 
5 min read

GRID Magazine

Explore OUR 
Articles

Every week we bring set of stories reflecting on communication, operation and technology.

Newsletter

Subscribe.

We share our 20 years of experience in creating, managing and scaling products and services that allow individuals to shape organisations through design.

Design at Scale™

LINE_MAGENTA_050_301

Categories

LINE_MAGENTA_050_301

Data

LINE_MAGENTA_050_301

Share

Internal

Collaborate

Resources

IBM PlexSan
Regular
Charcoal

Design at Scale™ is defined by three models, which form the Method. Each model operates in a different part of the business and collects and informs parties on design and engineering decisions that have a direct impact on the delivery.

All brands and trademarks presented on the Design at Scale™ website are owned by their relevant companies or agencies. The projects represent collaborations between designers, developers and product owners. Do not copy or publish any of the projects shown here without written approval from Design at Scale™ (alternatively GIVE™, 9V™) and/or relevant companies and agencies.

SOC_Twitter
SON_LinkedIn
SON_Instagram
SOC_-Medium
View