Professional Documents
Culture Documents
Lecture Notes
Lecture Notes
The image below provides a flow of how you should approach to solve problem.
This part is about the first step to solve a problem, i.e., to understand it completely. To understand a
problem, first, you need to familiarise yourself with the company. If you are solving an internal problem, you
would already know a lot of things. However, it is still advised to verify your understanding with the
respective departments. But if it is an external client, you should spend the time to know about what the
company does, the industry it is involved in, the market it caters to, its consumers and all the information
that will help you to understand the problem better.
After you have done plenty of self-research, you need to understand the problem from the ones who are
facing it. Here comes the part which is termed as “Interviewing”. To understand a problem completely, you
will always need to interact with multiple people in the company. You need to interview people to gather
information. Different job roles will require you to interact with a different set of individuals, but the task of
interviewing will remain across all of them.
Before any interview, you should have the answers for these three questions:
• Why this interview?
• What will I do next?
• Why this person?
After self-research and interview preparation, next thing in line is the interview itself. In an interview, you
should:
• Turn off all the distractions (Mobiles, laptops, etc.) around you.
• Use pen and paper to prepare notes.
• Be patient. Don’t be anxious to reply.
• Pause. Think. Ask.
• Playback your understanding in front of the interviewee for their validation.
All the points mentioned are basic, but people often tend to ignore them when they are interviewing
someone. You should keep them in mind and practice them till they become your regular habit.
5W
This generally is a first step to as it provides the context of the problem. It is used in combination with other
frameworks to solve the problem. You just need to write down the answers for these five questions to get a
clear picture of the problem:
Fig. 3 – 5W
5 WHYs
It is a very helpful in identifying the root cause for a problem. You go on with a flow of why’s and continue
the process until you have reached a dead end. At the dead end, you would identify the root cause that has
caused the problem. The nested form of this framework helps you to cover multiple aspects of the problem
as well.
Important points to note here are that while using this framework:
• It may take time to explore multiple branches
• Include all the teams affected by the problem
• There is a risk of landing on a false root cause
5 HOWs
An extension to 5 WHYs is the 5 HOWs framework. It is a handy tool to drill down a solution that will resolve
the root cause identified using the WHYs. Once you have determined the root cause, you need to ask, “How
will we resolve the root cause?”. You will have a specific answer that the team comes up with. You drill down
into the solution with a series of HOWs until you have a set of steps that will be needed to complete the
task. An example has been attached below:
So What
This framework helps you quantify the “BAD” in the situation. Like the 5 WHYs, you create a flow by asking
“So what?” after each level. This provides you with the flow of how things are going wrong because of the
existing problem. It will help realize the problem areas in the process that the client or team is performing.
SPIN Selling
The SPIN framework is a very useful framework as it helps to understand the problem and the expectations
from the solution together. The SPIN framework starts with asking about the current situation and helps you
visualise the entire journey from when the problem exists to what will happen when the problem is solved.
Some key points should be kept in mind while using the framework:
• The result of the framework highly depends on the quality of the questions that are asked.
• Include some open-ended questions as there is a possibility that you may miss on some vital
information since you didn’t ask a question about it.
• The questions should not make the interviewee uncomfortable.
If you can identify the type of the interviewee, tailoring the conversation according to their type can result
in good information source. This is a skill that you will have to practice and develop over time.
Now, you would have a clearer idea about the way you should ask the questions in an interview. When you
understand the problem, you need to explore the reasons that may be behind it. After the interviewing
process if you think that you have identified the problem, you are mistaken. It is just one possible reason
for the problem that the company or client is facing. There can be multiple reasons for the problem.
Also, even if you believe that you found the correct reason, first you need to verify whether there is any
data that supports it and then employ your resources to solve the issue. This test is required because if
there was a different reason behind the problem, all your efforts would then go in vain.
The business model canvas is a very popular tool due to the following features:
• It covers multiple domains of the business in a simple and efficient manner. At the end of the
model, you are aware of the firm's or product's value proposition, infrastructure, customers and
finances.
• Your business understanding increases at an accelerated pace.
• This model is adaptive to all businesses.
• Finally, all you have at the end is just a piece of paper.
The model is summarised in the image below. (To read the text, you can zoom-in on the image)
Issue tree framework is one of the most effective methods to approach a problem. It works by
disintegrating the problem into sub-components. The big complex problem is continuously decomposed
into simpler issues. At last, you will end up with a bunch of hypotheses. This will be clearer with the image
below.
You should keep the following points in mind with the Issue Tree Framework:
• You should always ask the question: "How?". It helps you break the problem into simpler
components.
• You proceed from the main problem to the lower branches based on the response of the question
'How?'. You need to analyse the response at each level and keep drilling down into the problem.
• The best issue trees are mutually exclusive and collectively exhaustive (MECE). Mutually
exclusive means there is no overlap between the different branches you have broken the problem
in. Collectively exhaustive means that the sub-components of your issue tree cover all the potential
causes of the problem.
• You should always try to reach a logical hypothesis at the end of the branch. You should not use any
arbitrary assumptions during the entire process and analyse the interviewee's response to proceed
ahead.
• Always follow the practice of prioritising the hypothesis that you have at the end of the branch. It
helps you to identify the root causes that need to be dealt with first to reduce the problem. The
Pareto rule (80:20 rule) can be used to prioritise them.
• Another way to check whether the problem lies in a component is to ask for the past trend for it.
One issue with the issue tree framework is that it requires a thorough knowledge of the firm and the
industry. You need to know all the factors that can have an impact. But that may not be the case. In those
cases, you will either need domain-specific frameworks or frameworks where domain is covered. All the
frameworks covered have been summarised here for this purpose.
These frameworks should help you reach the final hypotheses at the end of the interviewing process. Apart
from these frameworks, there are other models available which you can apply according to your problem
case. So, try and explore different frameworks based on the problem you are provided.
The main aim of interviewing any person is that you have hypotheses to test at the end of the interview. As
you interact with multiple members of different teams, you will end up with multiple hypotheses for the
same problem. They will be termed as a hypothesis until you have validated them using some data.
The next step that follows the hypothesis formulation is to collect data to validate them. Once you have
validated the hypotheses, you can start working on a solution around that root cause.
• Understand all the aspects of the business using the Business Model Canvas
• Formulate hypotheses using the frameworks
Disclaimer: All content and material on the UpGrad website is copyrighted material, either belonging to UpGrad or
its bonafide contributors and is purely for the dissemination of education. You are permitted to access print and
download extracts from this site purely for your own education only and on the following basis:
● You can download this document from the website for self-use only.
● Any copies of this document, in part or full, saved to disc or to any other storage medium may only be used
for subsequent, self-viewing purposes or to print an individual extract or copy for non-commercial personal
use only.
● Any further dissemination, distribution, reproduction, copying of the content of the document herein or the
uploading thereof on other websites or use of content for any other commercial/unauthorized purposes in
any way which could infringe the intellectual property rights of UpGrad or its contributors, is strictly
prohibited.
● No graphics, images or photographs from any accompanying text in this document will be used separately
for unauthorised purposes.
● No material in this document will be modified, adapted or altered in any way.
● No part of this document or UpGrad content may be reproduced or stored in any other web site or included
in any public or private electronic retrieval system or service without UpGrad’s prior written permission.
● Any rights not expressly granted in these terms are reserved.