ZEMOSO PRODUCT STUDIO
June 5, 2022
8 min read

Real Talk: Lessons learned and evolved from 3M and Post-it®’s adoption of Crazy 8 methodology

In one of my earlier published articles: Working Backwards: Amazon's Culture of Innovation: My Notes, I briefly discussed Crazy 8’s — the design technique that UI/UX designers swear by, and a key tool in the Design Sprint toolbox. On further analysis, have we as a sprint-abiding community, restricted the true power of this particular tool by relegating it for designers’ use only? I say, Crazy 8 was meant for more than that: problem-solving, structured innovation in brainstorming sessions in a time-bound manner.

Ideation in teams is painful: Remote makes it like a trip to the dentist.

For every meme I’ve seen in the last two years about “meetings that could have been an email,” I’ve created another one in my head about “meetings that shouldn’t have resulted in a follow-up meeting.” 

No matter the task: a new product, a new process, or even a root-cause analysis of failures — productive brainstorming within teams leading to action items and solutions is elusive. 

My read is that focussed ideation is hard. In any given room, filled with knowledgeable and opinionated stakeholders, multiple people with diverging points of view come up with multiple ideas. Then that becomes hard to converge. Eventually you are left with another meeting on the books. 

How do people solve this problem today?

Imagine a Zoom call with Chief Product Officers, CEOs, developers, and entrepreneurs; everyone tries to arrive at some solution vocalizing their opinions. The result is a long-winded meeting that will spill over into another long-winded meeting.

Technically, COVID-driven boost to collaborative softwares like Miro or Mural and smarter project management tools should have made this easier. And yet, Zoom fatigue is real and conclusions remain unequivocally out-of-reach. There needs to be a better way to handle the process of getting hairy ideas to execution, within the span of one meeting.

Enter the unsung hero of design sprints: Crazy 8

In a tangential universe of UI/UX designers, Crazy 8 is essential and omnipresent. Designers use it to come up with eight screens, one minute per screen, allowing quick iterations, and getting you closer to your goal, fast.

design sprints

The double diamond design thinking methodology of diverging and converging is useful in this context. Crazy 8 speeds up the “diverge” part of the exercise by time-boxing it without limiting creativity.

As experienced innovators and top product company founders will be the first to tell you: “more is sometimes, just more, not better.” When diverging, you can do a lot with eight new ideas; you don’t need 80.

diverge - converge - design thinking methodology

Let’s say we want to create a digital calendar for artists. What a designer will do is express the challenge statement and quickly create eight different, low-fidelity screens or simple sketches. Then they will speak to their stakeholders, do a simple vote if needed, and converge into two or three top designs. These top options will be green-lit into development and testing.

low fidelity screens or simple sketches

Why is this process relevant? It connects directly to the problem at hand and then creates a fast way to move forward to testing a hypothesis in an innovation process or a meeting.

Unusual applications: Crazy 8’s, Vision Sprints, and Post-it®

During a Google Ventures Design Sprint with stakeholders from 3M (Parent company for Post-it®) — the goal was to springboard the analogous Post-it® product into the future, and bridge the digital divide for sprint hosts. What does that even look like?

When the problem statement is as large as that, what was rightly hosted was a “Vision Sprint.” While not a far cry from a design sprint— the prototypes at the end of such a sprint rarely look like an actual product. For Post-it®, it was a collection of ideas and value props that would help them transition into the future. After the sprint, two extremely successful Post-it® App launches could be directly tied back to this sprint.

How did Crazy 8 work for Post-it® — Decoding the process

Evolving Crazy 8’s role, in an innovation process like this: 

design thinking
Step 1: Write the problem or challenge statement

You write down the challenge or a problem statement, which in this case was:

products to bridge the analog to digital divide

P.S. For this solution to work, you must, absolutely must, outline the problem at the right level of abstraction. But that’s another post for another time. We’ll go with this for now.

Step 2: Diverge: Time box to get 8(x) different solves in 8(x) minutes

Once we have this statement down, we allocate eight minutes to find eight ways to solve this problem. I often encourage this step to be done alone. This comes from the design thinking toolbox of problem-solving: “together alone,” where you do certain things together, and certain things separately to drive innovation faster. The key principle is to crowdsource cross-functional ideas, even crazy ideas. If there are 4 participants, we have 32 ideas. That a lot to converge.

Step 3: Cluster ideas together using affinity mapping

We now do affinity mapping, where we cluster  ideas that are similar. Themes will emerge that bring out similarity between ideas. We label the themes using the discovered similarities. Then, reframe the themes to solution themes. Understanding perspectives and points of view is important to evolve the ideas and create net-new additions. Timeboxed show and tell demos help with that( 2-3 minutes per participant). The goal is to identify opportunities and solutions.

Step 4: Prioritize the top 2 or 3 (Time: 5 minutes)

Usually, 10-12 reframed themes emerge from an affinity mapping/reframing exercise like this. It is hard to work on 10-12 statements, so we converge to two or three ideas and move forward. Prioritization can be done using voting with play money or using a matrix of orthogonal priorities (like impact-effort).

Reverse engineering the launches that emerged from this vision sprint, it appears the following ideas were green-lit for prototypes and further testing:

  • 1. How might we enable innovators to manage their brainstorming workflow by easily converting and embedding their analog Post-it®'s to their existing workflow products?
  • 2. How might we enable Post-it® users to easily search through analog Post-it®'s?

A complete white board challenge to a solution in 60 minutes

On a realistic note, any company, especially product companies, need continuous innovation to drive growth, adoption, investment, and success. A five-day design sprint every few weeks is neither feasible nor possible. Waiting for a lightning strike of inspiration to inspire the next cycle of growth is impractical.

While heuristic solutions are great, growth will eventually stagnate without a structured, regular, and persistent approach to define hypotheses, visualize solutions, experiment, and test.

So, where do we go from here: faster innovation and using every opportunity to problem-solve as a source of new ideas that can be leveraged to grow.

Using Crazy 8, you get from a complete whiteboard challenge statement to a reframed, converged solution statement in 45-60 minutes. Asking yourself whether something is right or wrong can be counterproductive because, in reality, half the time you don’t know what is right? AirBnB’s co-founder Joe Gebbia repeatedly recounts his big 5 failed attempts before his company really took off. Most of the time, innovators are faced with ambiguous challenge statements and they want to converge and test.

Thus, give it a try and see how it works for you and your team. 

The next time you run a brainstorming/critical alignment meeting use these steps:

white board challenge

So what is your next big challenge you want to apply this technique to? Ping me if you want to discuss the technique and set up your workspace to ensure a meeting that converges to points of decision.

ZEMOSO PRODUCT STUDIO

Real Talk: Lessons learned and evolved from 3M and Post-it®’s adoption of Crazy 8 methodology

April 10, 2022
8 min read

In one of my earlier published articles: Working Backwards: Amazon's Culture of Innovation: My Notes, I briefly discussed Crazy 8’s — the design technique that UI/UX designers swear by, and a key tool in the Design Sprint toolbox. On further analysis, have we as a sprint-abiding community, restricted the true power of this particular tool by relegating it for designers’ use only? I say, Crazy 8 was meant for more than that: problem-solving, structured innovation in brainstorming sessions in a time-bound manner.

Ideation in teams is painful: Remote makes it like a trip to the dentist.

For every meme I’ve seen in the last two years about “meetings that could have been an email,” I’ve created another one in my head about “meetings that shouldn’t have resulted in a follow-up meeting.” 

No matter the task: a new product, a new process, or even a root-cause analysis of failures — productive brainstorming within teams leading to action items and solutions is elusive. 

My read is that focussed ideation is hard. In any given room, filled with knowledgeable and opinionated stakeholders, multiple people with diverging points of view come up with multiple ideas. Then that becomes hard to converge. Eventually you are left with another meeting on the books. 

How do people solve this problem today?

Imagine a Zoom call with Chief Product Officers, CEOs, developers, and entrepreneurs; everyone tries to arrive at some solution vocalizing their opinions. The result is a long-winded meeting that will spill over into another long-winded meeting.

Technically, COVID-driven boost to collaborative softwares like Miro or Mural and smarter project management tools should have made this easier. And yet, Zoom fatigue is real and conclusions remain unequivocally out-of-reach. There needs to be a better way to handle the process of getting hairy ideas to execution, within the span of one meeting.

Enter the unsung hero of design sprints: Crazy 8

In a tangential universe of UI/UX designers, Crazy 8 is essential and omnipresent. Designers use it to come up with eight screens, one minute per screen, allowing quick iterations, and getting you closer to your goal, fast.

design sprints

The double diamond design thinking methodology of diverging and converging is useful in this context. Crazy 8 speeds up the “diverge” part of the exercise by time-boxing it without limiting creativity.

As experienced innovators and top product company founders will be the first to tell you: “more is sometimes, just more, not better.” When diverging, you can do a lot with eight new ideas; you don’t need 80.

diverge - converge - design thinking methodology

Let’s say we want to create a digital calendar for artists. What a designer will do is express the challenge statement and quickly create eight different, low-fidelity screens or simple sketches. Then they will speak to their stakeholders, do a simple vote if needed, and converge into two or three top designs. These top options will be green-lit into development and testing.

low fidelity screens or simple sketches

Why is this process relevant? It connects directly to the problem at hand and then creates a fast way to move forward to testing a hypothesis in an innovation process or a meeting.

Unusual applications: Crazy 8’s, Vision Sprints, and Post-it®

During a Google Ventures Design Sprint with stakeholders from 3M (Parent company for Post-it®) — the goal was to springboard the analogous Post-it® product into the future, and bridge the digital divide for sprint hosts. What does that even look like?

When the problem statement is as large as that, what was rightly hosted was a “Vision Sprint.” While not a far cry from a design sprint— the prototypes at the end of such a sprint rarely look like an actual product. For Post-it®, it was a collection of ideas and value props that would help them transition into the future. After the sprint, two extremely successful Post-it® App launches could be directly tied back to this sprint.

How did Crazy 8 work for Post-it® — Decoding the process

Evolving Crazy 8’s role, in an innovation process like this: 

design thinking
Step 1: Write the problem or challenge statement

You write down the challenge or a problem statement, which in this case was:

products to bridge the analog to digital divide

P.S. For this solution to work, you must, absolutely must, outline the problem at the right level of abstraction. But that’s another post for another time. We’ll go with this for now.

Step 2: Diverge: Time box to get 8(x) different solves in 8(x) minutes

Once we have this statement down, we allocate eight minutes to find eight ways to solve this problem. I often encourage this step to be done alone. This comes from the design thinking toolbox of problem-solving: “together alone,” where you do certain things together, and certain things separately to drive innovation faster. The key principle is to crowdsource cross-functional ideas, even crazy ideas. If there are 4 participants, we have 32 ideas. That a lot to converge.

Step 3: Cluster ideas together using affinity mapping

We now do affinity mapping, where we cluster  ideas that are similar. Themes will emerge that bring out similarity between ideas. We label the themes using the discovered similarities. Then, reframe the themes to solution themes. Understanding perspectives and points of view is important to evolve the ideas and create net-new additions. Timeboxed show and tell demos help with that( 2-3 minutes per participant). The goal is to identify opportunities and solutions.

Step 4: Prioritize the top 2 or 3 (Time: 5 minutes)

Usually, 10-12 reframed themes emerge from an affinity mapping/reframing exercise like this. It is hard to work on 10-12 statements, so we converge to two or three ideas and move forward. Prioritization can be done using voting with play money or using a matrix of orthogonal priorities (like impact-effort).

Reverse engineering the launches that emerged from this vision sprint, it appears the following ideas were green-lit for prototypes and further testing:

  • 1. How might we enable innovators to manage their brainstorming workflow by easily converting and embedding their analog Post-it®'s to their existing workflow products?
  • 2. How might we enable Post-it® users to easily search through analog Post-it®'s?

A complete white board challenge to a solution in 60 minutes

On a realistic note, any company, especially product companies, need continuous innovation to drive growth, adoption, investment, and success. A five-day design sprint every few weeks is neither feasible nor possible. Waiting for a lightning strike of inspiration to inspire the next cycle of growth is impractical.

While heuristic solutions are great, growth will eventually stagnate without a structured, regular, and persistent approach to define hypotheses, visualize solutions, experiment, and test.

So, where do we go from here: faster innovation and using every opportunity to problem-solve as a source of new ideas that can be leveraged to grow.

Using Crazy 8, you get from a complete whiteboard challenge statement to a reframed, converged solution statement in 45-60 minutes. Asking yourself whether something is right or wrong can be counterproductive because, in reality, half the time you don’t know what is right? AirBnB’s co-founder Joe Gebbia repeatedly recounts his big 5 failed attempts before his company really took off. Most of the time, innovators are faced with ambiguous challenge statements and they want to converge and test.

Thus, give it a try and see how it works for you and your team. 

The next time you run a brainstorming/critical alignment meeting use these steps:

white board challenge

So what is your next big challenge you want to apply this technique to? Ping me if you want to discuss the technique and set up your workspace to ensure a meeting that converges to points of decision.

Recent Publications
How to remix Amazon’s Working Backwards with Google’s Venture’s User Journey: The Dr. Strange Way
How to remix Amazon’s Working Backwards with Google’s Venture’s User Journey: The Dr. Strange Way
June 14, 2022
How we built a big data platform for a futuristic AgriTech product
How we built a big data platform for a futuristic AgriTech product
June 3, 2022
Zemoso Labs starts operations in Waterloo, Canada
Zemoso Labs starts operations in Waterloo, Canada
May 25, 2022
Deconstructing Elon Musk’s dog ate my homework answer for Twitter: More validation will be asked of startups
Deconstructing Elon Musk’s dog ate my homework answer for Twitter: More validation will be asked of startups
May 20, 2022
Why Realm trumps SQLite as database of choice for complex mobile apps — Part 1
Why Realm trumps SQLite as database of choice for complex mobile apps — Part 1
February 7, 2022
Understanding dynamic multi-column search with JPA Criteria for product development
Understanding dynamic multi-column search with JPA Criteria for product development
January 2, 2022
Product engineering zeitgeist: Implement OOPs in React JS using atomic design
Product engineering zeitgeist: Implement OOPs in React JS using atomic design
July 8, 2021
Honorable mention at O’Reilly’s Architectural Katas event
Honorable mention at O’Reilly’s Architectural Katas event
May 17, 2021
Product dev with testable spring boot applications, from day one
Product dev with testable spring boot applications, from day one
May 4, 2021
When not to @Autowire in Spring or Spring Boot applications
When not to @Autowire in Spring or Spring Boot applications
May 1, 2021
Efficiently handle data and integrations in Spring Boot
Efficiently handle data and integrations in Spring Boot
January 24, 2021
Unlock the power of atomic design in React and React Native using a theming library — Part 1
Unlock the power of atomic design in React and React Native using a theming library — Part 1
November 2, 2020
Our favorite CI/CD DevOps Practice: Simplify with GitHub Actions
Our favorite CI/CD DevOps Practice: Simplify with GitHub Actions
October 25, 2020
Kubernetes — What is it, what problems does it solve, and how does it compare with alternatives?
Kubernetes — What is it, what problems does it solve, and how does it compare with alternatives?
June 21, 2019
GraphQL — Why is it essential for agile product development?
GraphQL — Why is it essential for agile product development?
April 30, 2019
Orchestrating backend services for product development with AWS Step Functions
Orchestrating backend services for product development with AWS Step Functions
April 1, 2019
How To Decide When to Use Amazon Working Backwards, Business Model Canvas and Lean Canvas
How To Decide When to Use Amazon Working Backwards, Business Model Canvas and Lean Canvas
November 30, 2018
How to validate your Innovation: Mastering Experiment Design
How to validate your Innovation: Mastering Experiment Design
November 22, 2018
Working Backwards: Amazon's Culture of Innovation: My notes
Working Backwards: Amazon's Culture of Innovation: My notes
November 19, 2018
Product developer POV: Caveats when building with Spark
Product developer POV: Caveats when building with Spark
November 5, 2018
ZEMOSO PRODUCT STUDIO
April 10, 2022
8 min read

Real Talk: Lessons learned and evolved from 3M and Post-it®’s adoption of Crazy 8 methodology

“I was leading a brainstorming session in one of my MBA classes, and it was like wading through oatmeal.”

Hal B Gregersen
MIT Sloan & best-selling author

In one of my earlier published articles: Working Backwards: Amazon's Culture of Innovation: My Notes, I briefly discussed Crazy 8’s — the design technique that UI/UX designers swear by, and a key tool in the Design Sprint toolbox. On further analysis, have we as a sprint-abiding community, restricted the true power of this particular tool by relegating it for designers’ use only? I say, Crazy 8 was meant for more than that: problem-solving, structured innovation in brainstorming sessions in a time-bound manner.

Ideation in teams is painful: Remote makes it like a trip to the dentist.

For every meme I’ve seen in the last two years about “meetings that could have been an email,” I’ve created another one in my head about “meetings that shouldn’t have resulted in a follow-up meeting.” 

No matter the task: a new product, a new process, or even a root-cause analysis of failures — productive brainstorming within teams leading to action items and solutions is elusive. 

My read is that focussed ideation is hard. In any given room, filled with knowledgeable and opinionated stakeholders, multiple people with diverging points of view come up with multiple ideas. Then that becomes hard to converge. Eventually you are left with another meeting on the books. 

How do people solve this problem today?

Imagine a Zoom call with Chief Product Officers, CEOs, developers, and entrepreneurs; everyone tries to arrive at some solution vocalizing their opinions. The result is a long-winded meeting that will spill over into another long-winded meeting.

Technically, COVID-driven boost to collaborative softwares like Miro or Mural and smarter project management tools should have made this easier. And yet, Zoom fatigue is real and conclusions remain unequivocally out-of-reach. There needs to be a better way to handle the process of getting hairy ideas to execution, within the span of one meeting.

Enter the unsung hero of design sprints: Crazy 8

In a tangential universe of UI/UX designers, Crazy 8 is essential and omnipresent. Designers use it to come up with eight screens, one minute per screen, allowing quick iterations, and getting you closer to your goal, fast.

design sprints

The double diamond design thinking methodology of diverging and converging is useful in this context. Crazy 8 speeds up the “diverge” part of the exercise by time-boxing it without limiting creativity.

As experienced innovators and top product company founders will be the first to tell you: “more is sometimes, just more, not better.” When diverging, you can do a lot with eight new ideas; you don’t need 80.

diverge - converge - design thinking methodology

Let’s say we want to create a digital calendar for artists. What a designer will do is express the challenge statement and quickly create eight different, low-fidelity screens or simple sketches. Then they will speak to their stakeholders, do a simple vote if needed, and converge into two or three top designs. These top options will be green-lit into development and testing.

low fidelity screens or simple sketches

Why is this process relevant? It connects directly to the problem at hand and then creates a fast way to move forward to testing a hypothesis in an innovation process or a meeting.

Unusual applications: Crazy 8’s, Vision Sprints, and Post-it®

During a Google Ventures Design Sprint with stakeholders from 3M (Parent company for Post-it®) — the goal was to springboard the analogous Post-it® product into the future, and bridge the digital divide for sprint hosts. What does that even look like?

When the problem statement is as large as that, what was rightly hosted was a “Vision Sprint.” While not a far cry from a design sprint— the prototypes at the end of such a sprint rarely look like an actual product. For Post-it®, it was a collection of ideas and value props that would help them transition into the future. After the sprint, two extremely successful Post-it® App launches could be directly tied back to this sprint.

How did Crazy 8 work for Post-it® — Decoding the process

Evolving Crazy 8’s role, in an innovation process like this: 

design thinking
Step 1: Write the problem or challenge statement

You write down the challenge or a problem statement, which in this case was:

products to bridge the analog to digital divide

P.S. For this solution to work, you must, absolutely must, outline the problem at the right level of abstraction. But that’s another post for another time. We’ll go with this for now.

Step 2: Diverge: Time box to get 8(x) different solves in 8(x) minutes

Once we have this statement down, we allocate eight minutes to find eight ways to solve this problem. I often encourage this step to be done alone. This comes from the design thinking toolbox of problem-solving: “together alone,” where you do certain things together, and certain things separately to drive innovation faster. The key principle is to crowdsource cross-functional ideas, even crazy ideas. If there are 4 participants, we have 32 ideas. That a lot to converge.

Step 3: Cluster ideas together using affinity mapping

We now do affinity mapping, where we cluster  ideas that are similar. Themes will emerge that bring out similarity between ideas. We label the themes using the discovered similarities. Then, reframe the themes to solution themes. Understanding perspectives and points of view is important to evolve the ideas and create net-new additions. Timeboxed show and tell demos help with that( 2-3 minutes per participant). The goal is to identify opportunities and solutions.

Step 4: Prioritize the top 2 or 3 (Time: 5 minutes)

Usually, 10-12 reframed themes emerge from an affinity mapping/reframing exercise like this. It is hard to work on 10-12 statements, so we converge to two or three ideas and move forward. Prioritization can be done using voting with play money or using a matrix of orthogonal priorities (like impact-effort).

Reverse engineering the launches that emerged from this vision sprint, it appears the following ideas were green-lit for prototypes and further testing:

  • 1. How might we enable innovators to manage their brainstorming workflow by easily converting and embedding their analog Post-it®'s to their existing workflow products?
  • 2. How might we enable Post-it® users to easily search through analog Post-it®'s?

A complete white board challenge to a solution in 60 minutes

On a realistic note, any company, especially product companies, need continuous innovation to drive growth, adoption, investment, and success. A five-day design sprint every few weeks is neither feasible nor possible. Waiting for a lightning strike of inspiration to inspire the next cycle of growth is impractical.

While heuristic solutions are great, growth will eventually stagnate without a structured, regular, and persistent approach to define hypotheses, visualize solutions, experiment, and test.

So, where do we go from here: faster innovation and using every opportunity to problem-solve as a source of new ideas that can be leveraged to grow.

Using Crazy 8, you get from a complete whiteboard challenge statement to a reframed, converged solution statement in 45-60 minutes. Asking yourself whether something is right or wrong can be counterproductive because, in reality, half the time you don’t know what is right? AirBnB’s co-founder Joe Gebbia repeatedly recounts his big 5 failed attempts before his company really took off. Most of the time, innovators are faced with ambiguous challenge statements and they want to converge and test.

Thus, give it a try and see how it works for you and your team. 

The next time you run a brainstorming/critical alignment meeting use these steps:

white board challenge

So what is your next big challenge you want to apply this technique to? Ping me if you want to discuss the technique and set up your workspace to ensure a meeting that converges to points of decision.

Recent Publications

ZEMOSO ENGINEERING STUDIO

How we built a big data platform for a futuristic AgriTech product

June 3, 2022
8 min read
ZEMOSO NEWS

Zemoso Labs starts operations in Waterloo, Canada

May 25, 2022
5 min read
ZEMOSO ENGINEERING STUDIO

Honorable mention at O’Reilly’s Architectural Katas event

May 17, 2021
5 min read
ZEMOSO ENGINEERING STUDIO

Product dev with testable spring boot applications, from day one

May 4, 2021
5 min read
ZEMOSO ENGINEERING STUDIO

When not to @Autowire in Spring or Spring Boot applications

May 1, 2021
5 min read
ZEMOSO ENGINEERING STUDIO

Efficiently handle data and integrations in Spring Boot

January 24, 2021
5 min read
ZEMOSO ENGINEERING STUDIO

Our favorite CI/CD DevOps Practice: Simplify with GitHub Actions

October 25, 2020
5 min read
ZEMOSO ENGINEERING STUDIO

GraphQL — Why is it essential for agile product development?

April 30, 2019
12 min read
ZEMOSO PRODUCT STUDIO

How to validate your Innovation: Mastering Experiment Design

November 22, 2018
8 min read
ZEMOSO PRODUCT STUDIO

Working Backwards: Amazon's Culture of Innovation: My notes

November 19, 2018
8 min read
ZEMOSO ENGINEERING STUDIO

Product developer POV: Caveats when building with Spark

November 5, 2018
2 min read

Want more best practices?

Access thought-leadership and best practice content across
the product development lifecycle

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

© 2021 Zemoso Technologies
Privacy Policy

Terms of Use
LinkedIn Page - Zemoso TechnologiesFacebook Page - Zemoso TechnologiesTwitter Account - Zemoso Technologies

© 2021 Zemoso Technologies
Privacy Policy

LinkedIn Page - Zemoso TechnologiesFacebook Page - Zemoso TechnologiesTwitter Account - Zemoso Technologies
June 7, 2022