Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
1K views

Chapter One: Learn The Bulletproof Problem Solving Approach

The document summarizes the bulletproof problem solving approach which involves a cyclical process of defining the problem, disaggregating it, prioritizing parts, and testing hypotheses. It discusses establishing SMART problem statements focused on outcomes and at the highest level. Design thinking is presented as complementary, starting with user empathy and iterating prototypes based on testing. Logic trees are used to visualize problem elements from general to specific hypotheses that can be tested, with the goal of finding levers to solve the problem.

Uploaded by

QTKD-2K-18 La Thanh Thuy
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views

Chapter One: Learn The Bulletproof Problem Solving Approach

The document summarizes the bulletproof problem solving approach which involves a cyclical process of defining the problem, disaggregating it, prioritizing parts, and testing hypotheses. It discusses establishing SMART problem statements focused on outcomes and at the highest level. Design thinking is presented as complementary, starting with user empathy and iterating prototypes based on testing. Logic trees are used to visualize problem elements from general to specific hypotheses that can be tested, with the goal of finding levers to solve the problem.

Uploaded by

QTKD-2K-18 La Thanh Thuy
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Chapter One: Learn the Bulletproof Problem Solving Approach

1. The Bulletproof Problem Solving Cycle


- The bulletproof problem solving process is both a complete process and an iterative cycle. This cycle can be
completed over any timeframe with the information at hand.

- Once you reach a preliminary end point, you can repeat the process to draw out more insight for deeper
understanding
Chapter Two: Define the Problem
1. Define the problem
- Good problem statements have a number of
characteristics. They are:

+ Outcomes focused: A clear statement of the


problem to be solved, expressed in outcomes, not
activities or intermediate outputs.
+ Specific and measurable wherever possible.
Clearly time‐bound.
+ Designed to explicitly address decision‐maker
values and boundaries, including the accuracy
needed and the scale of aspirations.
+ Structured to allow sufficient scope for
creativity and unexpected results—too narrowly
scoped problems can artificially constrain solutions.
+ Solved at the highest level possible, meaning
for the organization as a whole, not just optimized
for a part or a partial solution.
 Teams we worked with sometimes used a
mnemonic—SMART—to remember these characteristics: whether the problem statement was specific,
measurable, action oriented, relevant, and timely. SMART
covers most but not all of these factors—make sure to have an outcomes focus and work at the highest level.
- Example: p72

2. Design thinking
- Design thinking sits in relation to our seven‐steps analytic problem solving process. We believe it is both
consistent and complementary, especially in cases where an understanding of the user experience is
essential.

- Different stages: empathize, define, ideate, build, test, and deliver. The steps are usually not linear—they
can happen in parallel and steps can be iterated and repeated as insight grows.

+ The empathize and define steps correspond closely to


the problem statement approach;

+ The ideate step is akin to our process to break


down a problem around hypotheses and then test;
+ The build and deliver steps correspond to our
work planning and analysis steps.
 As in our approach, design thinking is highly
iterative, revisiting earlier stages as knowledge
accumulates.

- Design thinking allows teams to use the creative


problem solving process to find innovative solutions.

- A user‐centered approach is fundamental to this kind of


problem solving, where a significant amount of time is
spent empathizing with and understanding the user and
their “pain points.”
+ Design thinking usually starts with understanding the potential user's needs.
+ Thus, the first step of the design thinking methodology is empathizing with the people you want to serve,
learning what their needs are, recognizing why the product or solution could be relevant,
and how it will be used within their everyday life.

+ The cycle to empathize and then build‐test‐redefine, and build‐test‐redefine again, is based on an
idea that you don't have to make decisions based on historical data and instinct. Rather, decisions can
evolve, based on evidence from users' reactions to successful or failed prototypes.

+ Design thinking methodology that focuses on user understanding, research, and iterating with prototypes,
is a powerful tool to use in conjunction with the seven‐steps problem solving approach, especially in the
consumer/product space.

Chapter Three: Problem Disaggregation and Prioritization


1. Types of Logic Trees: Getting Started
- Logic trees are really just structures for seeing the elements of a problem in a clear way, and keeping track
of different levels of the problem, which we liken to trunks, branches, twigs, and leaves.
+ You can arrange them from left to right, right to left, or top to bottom— whatever makes the elements
easier for you to visualize.
+ There are lots of ways to do it; in fact, we almost always try two or three alternative disaggregations to
discover which yields the most insights.
- Component or factor trees, and often work inductively (learning from specific cases that illuminate
general principles later), to help us define basic problem structure.
- Later, after some iterations with data and analysis, we usually move to hypothesis trees, deductive
logic trees, or decision trees, depending on the nature of the problem.
- The only rule here is to move when you can from trees with general problem elements to trees that state
clear hypotheses to test; vague labels do not drive analysis or action—which is the whole point.
- Goal in building logic trees is to find the levers that help us crack our problem, starting with the
components that can help focus data gathering and eventually move us toward good hypotheses that can
be tested.

You might also like