ZEMOSO PRODUCT STUDIO
June 5, 2022
8 min read

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

"Done correctly, working backwards is a huge amount of work. But it saves you even more work later. The Working Backwards Process is not designed to be easy, it is designed to save huge amount of work on the backend, and to make sure we are building the right thing." - Jeff Bezos

What is this about?

Hate Amazon or love it, you will be hard pressed to deny that it has delivered on disparate business models, diverse markets, customer segments, channels. If you are an entrepreneur or Product Manager you may have most likely heard of Amazon's "Working Backwards" approach. Apparently Amazon institutionalized this approach to greenlight its innovation initiatives.

When I got a chance to attend a workshop by an insider(Richard Halkett) at the lean startup conference, I did not want to miss it.

I tried to refer to my notes to come up with a summary in this post. It is hard to replicate the message of the original messenger, my views and biases may have slipped in.

The Session breakup

The session duration was 90 minutes. A short booklet was provided. Peer reviews kept the topic focussed with constructive criticism.

Working Backwards the main artifacts: Three short documents - Focus on outcome versus output

The motivation of drafting a mock press release is to focus on the customer, the problem, why existing solutions fail and why what you are doing will blow others away. These documents get refined and iterated. The language of the release should not involve geek-speak. The press release should pass the Oprah Speak Test - imagine listening to Oprah trying to explain it to her audience. While it appears you are starting with Press release, the real process starts with a sort of customer discovery. The big idea is that it is easier to iterate over these artifacts versus the product itself.

The session mainly focussed on the Press release. FAQ is the outcome of a blown up set of answers based on reviews you are getting on top of the press release document.

Some background to technique used: Crazy Eights

Crazy Eights is a technique used in UX design sprints extensively. If you are an entrepreneur, product manager or designer you may have used this. The main motivation for crazy eights is:

1. Focus on quantity (not quality).

2. Time box. The human brain is a tricky beast, it procrastinates especially when there is any planning, visualization activity. The brain's limbic system gets into a tug of war with the pre-frontal cortex. Without digressing too much, time can be a force-function in such activities.

You can google on Crazy Eights but I sketched out a brief summary for you to understand the technique since it is used extensively here.

Fig: Crazy Eights in 5 simple steps

The main elements of Working backwards

1. Start with the customer & problem (Discovery do it with Crazy Eights)

2. Ideate around solutions(Crazy Eights)

3. Pick the best solution that solves the most important problem(Prioritize)

4. Draft the press release(Time box it around 4 minutes)

5. Get it reviewed, critiqued

6. Use the critique to come up with FAQ

Start with the customer :The 5 customer questions

1. Who is the customer?

2. What is the customer problem or opportunity?

3. What is the most important customer benefit?

4. How do you know what customers want?

5. What does the customer experience look like?

The best way to do this is through a customer discovery. Many early stage ideas have several assumptions baked in, that's the nature of any innovation. The question, "How do you know what customers want?" is looking for evidence that those assumptions are right.

Who is the customer?

Start working backwards to defining the customer. You should get as specific as possible. Time box and force yourself to write 5 defining characteristics of the customer. Specificity on context is important.

For UX designers this exercise sounds similar to persona definitions - it is not. The goal is simply to get customer & problem centric when you start.

Write down 2-3 key needs/wants the customer has before you start ideating the solutions

Pick those top 2-3 needs or wants from the 8. Once you have a reasonable understanding of Customer Problem & Opportunity, the next step is to actually diverge and generate ideas

Exercise: Generate ideas

The goal is to generate 8 breakthrough ideas in 8 minutes- do it with Crazy Eights. Do not worry of being silly and audacious here. Think big. You are expected to now go silly and diverge.

Divergence to Convergence: Hunker down the big idea now

The question is now to force yourself to pick one(or two?) ideas from the 8. The blueprint we were asked to follow were based on answers to the fill in the blanks:

1. The Big Idea is ______________

2. The most important benefit to the customer is ____________

Draft The Press Release

The press release must have the following:

1. Customer quote : The quote has to be realistic, specific and credible depicting the outcome/benefit

2. Idea Summary: The idea summary should depict the 2-3 wants/needs that you are solving from the customer perspective

3. Headline: The headline of the press release should be compelling. After going through the entire session I felt the headline should be focussed on the customer. Too often we start talking of the product, company or solution.

There is more in real life to press releases, but for starters this is pretty good especially since the goal is to create an artifact to review and align. Focus on the customer benefits and put yourself in customer shoes.

Review of the press release:

You are then required to get the press release reviewed. Based on the questions you get, you move on to building FAQs, then the visuals etc.

Putting it all Together

I put up a graphic cheat sheet for my personal future reference. Hope it helps you as well:

Fig: Working backwards in one sheet

Some of the people who read this article asked for a downloadable cheat sheet. Here it is: Working Backwards cheat sheet (PDF format). I watermarked it with a link to this narrative, if you want the source files to change for your internal use send me a message and I can send it over to you.

Key Takeaways and Lessons for me

1. Time boxing is super efficient(can't get over it). 8 minutes is all it takes to move things forward.

2. Too often , companies(especially larger ones) worry about scale early in the process. Often building systems and technology with no evidence that someone wants. Technology teams start focussing on what they are best at in their previous avatars - build scalable, secure systems and components. This is ok when it comes to extensions to products or displacement products - not disruptive innovation. The working backwards process forces everyone to focus on the outcome. I have seen demo scripts being used in a similar to focus teams on customer outcomes. It is the same principle, work backwards - focus on the customer, the problem and evidence that you have the right thing to build.

ZEMOSO PRODUCT STUDIO

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

November 19, 2018
8 min read

"Done correctly, working backwards is a huge amount of work. But it saves you even more work later. The Working Backwards Process is not designed to be easy, it is designed to save huge amount of work on the backend, and to make sure we are building the right thing." - Jeff Bezos

What is this about?

Hate Amazon or love it, you will be hard pressed to deny that it has delivered on disparate business models, diverse markets, customer segments, channels. If you are an entrepreneur or Product Manager you may have most likely heard of Amazon's "Working Backwards" approach. Apparently Amazon institutionalized this approach to greenlight its innovation initiatives.

When I got a chance to attend a workshop by an insider(Richard Halkett) at the lean startup conference, I did not want to miss it.

I tried to refer to my notes to come up with a summary in this post. It is hard to replicate the message of the original messenger, my views and biases may have slipped in.

The Session breakup

The session duration was 90 minutes. A short booklet was provided. Peer reviews kept the topic focussed with constructive criticism.

Working Backwards the main artifacts: Three short documents - Focus on outcome versus output

The motivation of drafting a mock press release is to focus on the customer, the problem, why existing solutions fail and why what you are doing will blow others away. These documents get refined and iterated. The language of the release should not involve geek-speak. The press release should pass the Oprah Speak Test - imagine listening to Oprah trying to explain it to her audience. While it appears you are starting with Press release, the real process starts with a sort of customer discovery. The big idea is that it is easier to iterate over these artifacts versus the product itself.

The session mainly focussed on the Press release. FAQ is the outcome of a blown up set of answers based on reviews you are getting on top of the press release document.

Some background to technique used: Crazy Eights

Crazy Eights is a technique used in UX design sprints extensively. If you are an entrepreneur, product manager or designer you may have used this. The main motivation for crazy eights is:

1. Focus on quantity (not quality).

2. Time box. The human brain is a tricky beast, it procrastinates especially when there is any planning, visualization activity. The brain's limbic system gets into a tug of war with the pre-frontal cortex. Without digressing too much, time can be a force-function in such activities.

You can google on Crazy Eights but I sketched out a brief summary for you to understand the technique since it is used extensively here.

Fig: Crazy Eights in 5 simple steps

The main elements of Working backwards

1. Start with the customer & problem (Discovery do it with Crazy Eights)

2. Ideate around solutions(Crazy Eights)

3. Pick the best solution that solves the most important problem(Prioritize)

4. Draft the press release(Time box it around 4 minutes)

5. Get it reviewed, critiqued

6. Use the critique to come up with FAQ

Start with the customer :The 5 customer questions

1. Who is the customer?

2. What is the customer problem or opportunity?

3. What is the most important customer benefit?

4. How do you know what customers want?

5. What does the customer experience look like?

The best way to do this is through a customer discovery. Many early stage ideas have several assumptions baked in, that's the nature of any innovation. The question, "How do you know what customers want?" is looking for evidence that those assumptions are right.

Who is the customer?

Start working backwards to defining the customer. You should get as specific as possible. Time box and force yourself to write 5 defining characteristics of the customer. Specificity on context is important.

For UX designers this exercise sounds similar to persona definitions - it is not. The goal is simply to get customer & problem centric when you start.

Write down 2-3 key needs/wants the customer has before you start ideating the solutions

Pick those top 2-3 needs or wants from the 8. Once you have a reasonable understanding of Customer Problem & Opportunity, the next step is to actually diverge and generate ideas

Exercise: Generate ideas

The goal is to generate 8 breakthrough ideas in 8 minutes- do it with Crazy Eights. Do not worry of being silly and audacious here. Think big. You are expected to now go silly and diverge.

Divergence to Convergence: Hunker down the big idea now

The question is now to force yourself to pick one(or two?) ideas from the 8. The blueprint we were asked to follow were based on answers to the fill in the blanks:

1. The Big Idea is ______________

2. The most important benefit to the customer is ____________

Draft The Press Release

The press release must have the following:

1. Customer quote : The quote has to be realistic, specific and credible depicting the outcome/benefit

2. Idea Summary: The idea summary should depict the 2-3 wants/needs that you are solving from the customer perspective

3. Headline: The headline of the press release should be compelling. After going through the entire session I felt the headline should be focussed on the customer. Too often we start talking of the product, company or solution.

There is more in real life to press releases, but for starters this is pretty good especially since the goal is to create an artifact to review and align. Focus on the customer benefits and put yourself in customer shoes.

Review of the press release:

You are then required to get the press release reviewed. Based on the questions you get, you move on to building FAQs, then the visuals etc.

Putting it all Together

I put up a graphic cheat sheet for my personal future reference. Hope it helps you as well:

Fig: Working backwards in one sheet

Some of the people who read this article asked for a downloadable cheat sheet. Here it is: Working Backwards cheat sheet (PDF format). I watermarked it with a link to this narrative, if you want the source files to change for your internal use send me a message and I can send it over to you.

Key Takeaways and Lessons for me

1. Time boxing is super efficient(can't get over it). 8 minutes is all it takes to move things forward.

2. Too often , companies(especially larger ones) worry about scale early in the process. Often building systems and technology with no evidence that someone wants. Technology teams start focussing on what they are best at in their previous avatars - build scalable, secure systems and components. This is ok when it comes to extensions to products or displacement products - not disruptive innovation. The working backwards process forces everyone to focus on the outcome. I have seen demo scripts being used in a similar to focus teams on customer outcomes. It is the same principle, work backwards - focus on the customer, the problem and evidence that you have the right thing to build.

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
Real Talk: Lessons learned and evolved from 3M and Post-it®’s adoption of Crazy 8 methodology
Real Talk: Lessons learned and evolved from 3M and Post-it®’s adoption of Crazy 8 methodology
April 10, 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
Product developer POV: Caveats when building with Spark
Product developer POV: Caveats when building with Spark
November 5, 2018
ZEMOSO PRODUCT STUDIO
November 19, 2018
8 min read

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

"Done correctly, working backwards is a huge amount of work. But it saves you even more work later. The Working Backwards Process is not designed to be easy, it is designed to save huge amount of work on the backend, and to make sure we are building the right thing." - Jeff Bezos

What is this about?

Hate Amazon or love it, you will be hard pressed to deny that it has delivered on disparate business models, diverse markets, customer segments, channels. If you are an entrepreneur or Product Manager you may have most likely heard of Amazon's "Working Backwards" approach. Apparently Amazon institutionalized this approach to greenlight its innovation initiatives.

When I got a chance to attend a workshop by an insider(Richard Halkett) at the lean startup conference, I did not want to miss it.

I tried to refer to my notes to come up with a summary in this post. It is hard to replicate the message of the original messenger, my views and biases may have slipped in.

The Session breakup

The session duration was 90 minutes. A short booklet was provided. Peer reviews kept the topic focussed with constructive criticism.

Working Backwards the main artifacts: Three short documents - Focus on outcome versus output

The motivation of drafting a mock press release is to focus on the customer, the problem, why existing solutions fail and why what you are doing will blow others away. These documents get refined and iterated. The language of the release should not involve geek-speak. The press release should pass the Oprah Speak Test - imagine listening to Oprah trying to explain it to her audience. While it appears you are starting with Press release, the real process starts with a sort of customer discovery. The big idea is that it is easier to iterate over these artifacts versus the product itself.

The session mainly focussed on the Press release. FAQ is the outcome of a blown up set of answers based on reviews you are getting on top of the press release document.

Some background to technique used: Crazy Eights

Crazy Eights is a technique used in UX design sprints extensively. If you are an entrepreneur, product manager or designer you may have used this. The main motivation for crazy eights is:

1. Focus on quantity (not quality).

2. Time box. The human brain is a tricky beast, it procrastinates especially when there is any planning, visualization activity. The brain's limbic system gets into a tug of war with the pre-frontal cortex. Without digressing too much, time can be a force-function in such activities.

You can google on Crazy Eights but I sketched out a brief summary for you to understand the technique since it is used extensively here.

Fig: Crazy Eights in 5 simple steps

The main elements of Working backwards

1. Start with the customer & problem (Discovery do it with Crazy Eights)

2. Ideate around solutions(Crazy Eights)

3. Pick the best solution that solves the most important problem(Prioritize)

4. Draft the press release(Time box it around 4 minutes)

5. Get it reviewed, critiqued

6. Use the critique to come up with FAQ

Start with the customer :The 5 customer questions

1. Who is the customer?

2. What is the customer problem or opportunity?

3. What is the most important customer benefit?

4. How do you know what customers want?

5. What does the customer experience look like?

The best way to do this is through a customer discovery. Many early stage ideas have several assumptions baked in, that's the nature of any innovation. The question, "How do you know what customers want?" is looking for evidence that those assumptions are right.

Who is the customer?

Start working backwards to defining the customer. You should get as specific as possible. Time box and force yourself to write 5 defining characteristics of the customer. Specificity on context is important.

For UX designers this exercise sounds similar to persona definitions - it is not. The goal is simply to get customer & problem centric when you start.

Write down 2-3 key needs/wants the customer has before you start ideating the solutions

Pick those top 2-3 needs or wants from the 8. Once you have a reasonable understanding of Customer Problem & Opportunity, the next step is to actually diverge and generate ideas

Exercise: Generate ideas

The goal is to generate 8 breakthrough ideas in 8 minutes- do it with Crazy Eights. Do not worry of being silly and audacious here. Think big. You are expected to now go silly and diverge.

Divergence to Convergence: Hunker down the big idea now

The question is now to force yourself to pick one(or two?) ideas from the 8. The blueprint we were asked to follow were based on answers to the fill in the blanks:

1. The Big Idea is ______________

2. The most important benefit to the customer is ____________

Draft The Press Release

The press release must have the following:

1. Customer quote : The quote has to be realistic, specific and credible depicting the outcome/benefit

2. Idea Summary: The idea summary should depict the 2-3 wants/needs that you are solving from the customer perspective

3. Headline: The headline of the press release should be compelling. After going through the entire session I felt the headline should be focussed on the customer. Too often we start talking of the product, company or solution.

There is more in real life to press releases, but for starters this is pretty good especially since the goal is to create an artifact to review and align. Focus on the customer benefits and put yourself in customer shoes.

Review of the press release:

You are then required to get the press release reviewed. Based on the questions you get, you move on to building FAQs, then the visuals etc.

Putting it all Together

I put up a graphic cheat sheet for my personal future reference. Hope it helps you as well:

Fig: Working backwards in one sheet

Some of the people who read this article asked for a downloadable cheat sheet. Here it is: Working Backwards cheat sheet (PDF format). I watermarked it with a link to this narrative, if you want the source files to change for your internal use send me a message and I can send it over to you.

Key Takeaways and Lessons for me

1. Time boxing is super efficient(can't get over it). 8 minutes is all it takes to move things forward.

2. Too often , companies(especially larger ones) worry about scale early in the process. Often building systems and technology with no evidence that someone wants. Technology teams start focussing on what they are best at in their previous avatars - build scalable, secure systems and components. This is ok when it comes to extensions to products or displacement products - not disruptive innovation. The working backwards process forces everyone to focus on the outcome. I have seen demo scripts being used in a similar to focus teams on customer outcomes. It is the same principle, work backwards - focus on the customer, the problem and evidence that you have the right thing to build.

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 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