By Arnaud, on July 29th, 2010% This entry is part of a multi-post case study.
So we’ve developed our ‘why’ tree: we’ve identified all the potential reasons why we’re having our problem and we’ve organized these reasons in such a fashion that they only appear once in the tree. Next we need to test these hypotheses. That requires you to do four things: -1- plan out how you’re going to test each hypothesis, -2- identify in which order you’ll test them, -3- conduct the actual test, and -4- conclude what are the root causes of your problem.
This is a preview of Case study: cables negotiation — part 4/8 — Test your hypotheses . Read the full post (1045 words, 2 images, estimated 4:11 mins reading time)Related Posts:
By Arnaud, on July 23rd, 2010% This entry is part of a multi-post case study.
So, we’re back to our cables negotiation. We’ve defined the problem and identified the basic framework for breaking down the key question. Next we need to build our logic tree. We’ll do that in this post.
Building the logic tree essentially means breaking the key question into parts (or issues) and breaking these parts into smaller parts (sub-issues), all the while remaining MECE in our thinking.
This is a preview of Case study: cables negotiation — part 3/8 — Build a why tree (2/2) . Read the full post (855 words, 5 images, estimated 3:25 mins reading time)Related Posts:
By Arnaud, on July 20th, 2010% This entry is part of a multi-post case study.
So, you’ve defined your problem; well done! Now you need to look for its root cause(s) by building a logic tree.
A logic tree helps you be exhaustive in your thinking process—by forcing you to not leave any possibility out—and efficient, by considering each possibility only once. So it is an essential part in the resolution of any complex problem (here is a basic explanation of logic trees).
This is a preview of Case study: cables negotiation — part 2/8 — Build a why tree (1/2) . Read the full post (565 words, 3 images, estimated 2:16 mins reading time)Related Posts:
By Arnaud, on July 19th, 2010% This entry is part of a multi-post case study.
One effective way to become better problem-solvers is to use cases, so I’ll post problems that we have solved in my class so we can criticize them (these are all real problems).
Let’s start with a first example: the case of a multinational company that has problems with sourcing cables, an essential part of its products. Here is the problem identification card (PIC).
This is a preview of Case study: cables negotiation — part 1/8 — Build a good problem identification card . Read the full post (994 words, 1 image, estimated 3:59 mins reading time)Related Posts:
By Arnaud, on July 6th, 2010% 
The thinking process for developing a logic tree is an iteration between diverging—looking for all the ways to solve your problem—and converging: focusing on the minute details of a specific solution.
We tend to be better at converging than at diverging. That’s a problem because we tend to stick to obvious solutions. Here are a few tips to help you become better at diverging thinking.
Related Posts:
By Arnaud, on July 6th, 2010% 
In a thorough problem-solving process you’ll have to build two logic trees: one “why” to find the root cause of your problem and one “how” to identify potential solutions.
Logic trees must be mutually exclusive and collectively exhaustive (MECE) and perspicacious. Building them is hard work (if it isn’t, you’re probably doing it wrong). So consider using existing frameworks wherever possible. Just make sure that the frameworks you are considering truly are MECE (they often aren’t) and useful for your problem.
Related Posts:
By Arnaud, on July 6th, 2010% 
You embarked in a problem solving process, that requires fact gathering, analysis and communication. You might not know how long it’s going to take you and how much effort will be associated but be sure of one thing: it will be messy. Asking “so what?” consistently can help you limit the messiness…
It helps you focus your thinking
At many stages of the problem solving process you’ll have to gather data. Consistently asking “so what?” helps you decide which data is relevant.
Related Posts:
By Arnaud, on July 6th, 2010% 
Avoid describing processes in “how” trees…
There are two ways to answer to a “how” question. The first is to describe one particular solution process to reply to the question (e.g. to the question “how to go from NYC to London?”, reply: first, choose an airline; second, buy a ticket; third, go to the airport; etc.). The second is to describe the various alternatives in which one can answer the question (e.g. “by plane, by helicopter, by balloon, by boat, etc.).
Related Posts:
By Arnaud, on July 4th, 2010% 
In business communication, your primary objective is to transfer information effectively. This is done best by expressing your main idea first. Here we’ll talk about presentations, but the concepts are equally applicable to emails, voicemails, memos and all other means of communication.
Related Posts:
By Arnaud, on July 4th, 2010% 
The first step in the problem solving process is to identify precisely the problem you want to solve. That entails synthesizing the relevant information. Building a problem identification card can help you do so.
We already discussed in another entry the information that you should use to define your problem. This entry clarifies how you should organize that information.
Related Posts:
|
