Lecture Notes - Structured Problem Solving Using Frameworks - I
Lecture Notes - Structured Problem Solving Using Frameworks - I
Business problem solving is an important skill, not only for business analysts, but also for
business leaders who have to make important decisions by doing the root cause analysis of any
organisational problem. Business problem solving in fact is determined by one of the most
important aspects of solving a problem is to understand what the business problem is. If you do
not pay attention to this aspect, then you might end up solving a business problem that was
never there in the first place. To do this efficiently, many frameworks and processes are set in
place to help the business people understand the root cause or the grass root problem in the
first place. There are many frameworks and tools that can be used to understand a business
problem. You will learn more about frameworks and types of business problems in later
sessions. As of now, let’s look at the CRISP-DM framework that essentially lists down all the
processes that are involved in an end-to-end business problem.
Sometimes, these are also subjective to the organisations methods and processes that they
have developed over the years.
In any industry, a business problem might arise at any instance. Let’s look at some instances:
"Our sales are declining. What do we do?"
"The company needs to increase its market share. How should we proceed?"
"The company is incurring huge losses. How do we cut them down?"
“The industry has a new competitor that is affecting our profits. What should we do?"
So, you cannot rely on luck while working as an employee of or a service provider for any firm.
Here is a list of all that is wrong about the approach followed above:
Company resources are not utilised optimally, as the person would try and check each phase
and department to solve one problem.
The entire process would take much longer than it should have. During that time, the company
or the client firm might incur a hefty loss due to the problem at hand.
The client might switch to a competitor seeing how unoptimised the entire process is.
The entire process of problem solving is broken down into the following steps.
Now, if it is an external client, then you should spend some time learning about the company –
what it does, the industry in which it operates, the market it caters to, its consumers – in addition
to gathering information that will help you to understand the problem better.
Now, suppose a client approaches you seeking help with planning a marketing campaign. In this
case, you should be well acquainted with the company, especially about the following:
Once you have done extensive self-research, you need to then understand the problem by
interacting with the people who are facing it. This step is what we call ‘interviewing’. To
understand a problem completely, you will always need to interact with multiple people inside a
company.
Different job roles will require you to interact with different sets of individuals, but the task of
interviewing will remain the same across all of them.
Now, even though interviewing is an important skill, it is often observed that people do not
prepare for it and end up asking random questions or missing out on crucial details.
If you have clarity on the entire scenario, then you will be more comfortable in handling the
situation that you find yourself in.
1. Turn off all the distractions (mobiles, laptops, etc.) around you.
2. Use pen and paper to prepare notes.
3. Be patient. Don’t be anxious to reply.
4. Pause. Think. Ask.
5. Playback your understanding with the interviewee for their validation.
People often tend to ignore the above when they are interviewing someone. You should keep
them in mind and practise them until they come naturally to you.
Interviewing: Frameworks - I
Now that you have learnt how to prepare for and carry yourself during an interview, in this part,
you will learn about a structured approach for interviewing any internal or external customer for
a clear understanding of the business problem.
When trying to solve a problem, you do everything possible to get a good result; you try to
gather all relevant information to solve that problem. Nevertheless, if you are not clear in your
head, then you will end up with large chunks of unwanted information.
To overcome this issue, people have developed specific patterns of asking questions, which we
call ‘frameworks’, over the years. There are multiple frameworks that are available at your
disposal, and you need to choose the one that is the most suitable for your case. As part of this
module, you will learn about some of the popular frameworks and understand how you can
apply them in different cases.
● 5 WHYs: This framework or pattern helps us ask WHY questions to the problem till we
get to the root cause we are looking for. We keep asking the WHYs till we get to the part
we are looking for or as much as we can go in-depth on the problem to solve it better.
● So what? : This framework or pattern helps us understand the implication based on the
interrogation of part 1, so what interrogation of part 2, and so on.
● 5 Ws: The 5 Ws framework or pattern often asks the following set of questions.
○ Who was involved in the problem?
○ What is the problem that is being faced?
○ Where does the problem take place?
○ When does the problem arise?
○ How does the problem affect the company or its operations?
This is quite a helpful framework when it comes to identifying the root cause of a problem. The
framework involves a sequence of ‘why’ questions, and you continue the process until you
reach a stop. This is where you identify the possible root cause of the problem. The nested form
of this framework helps you cover multiple aspects of a particular problem as well.
Now, let’s try and understand this framework through a business case. Imagine you are working
as a development manager for a leading e-commerce company like Amazon or Flipkart. The
company is facing a problem: the vendors who were selling their items through your platform
are moving to your competitor’s platform. You are asked to look into the problem and try to
solve it. You use the 5 WHYs framework to identify possible root causes of the problem. Refer
to the flow of the problem shown below, understand the WHYs asked based on the answers
found out during the interrogation process and try to think what could the answer be in the parts
1, 2 and 3 of the images.
The 5 WHYs may take some time to reach the main problem. The reasoning may branch into
multiple options (‘why else’), exploring each of which will require time.
There is always a risk of landing on a false root cause, as the branch you have explored might
digress from the main issue.
The discussion should involve people from all the teams affected by the problem. This will help
in covering all the aspects of the problem.
From the case discussed above, you must have understood that a person should be well versed
with the flow of the process and the activities surrounding the problem to create a 5 Whys
framework.
Suppose your company was losing clients and it asked you to come up with a solution to
address this issue. You started with the series of ‘Why’ questions and arrived at the root cause
behind the decline in the company’s reputation. Now, having determined the root cause, your
very first question would be “How do we resolve this issue?”. The answer to this question is:
“Improve the brand reputation”. Using the 5 Hows framework, you can break this solution down
into further steps as shown in the image given below.
As you can see in the image above, the solution has been broken down into a series of steps,
which will be required to overcome the existing problems.
This is quite a helpful framework when you are trying to evaluate the need for a business
solution. For example, consider that a client has approached you for help with finding a solution
to the shrinking customer base for its products. In this case, the ‘So what’ framework will help
you understand the implications of this problem on the business. You begin by asking the client
the following questions:
Due to the reduced customer base, the sales of the company has fallen.
“So what?”
“So what?”
“So what?”
Due to the inefficient operations, the company is losing more money and incurring greater
losses.
So, with the help of the ‘So what’ framework, you have created a map that shows how the
problems are affecting the business.
This is one of the simplest and most effective frameworks to understand the business situation
at hand. You just need to write down the answers to the following five questions to get a clear
picture of the problem:
The problem is associated with an IT consulting firm, which delivers IT solutions to its clients.
The process of client engagement is given below:
The client approaches the sales team of the company to discuss the problem that the client is
facing. (This could also be the other way around. The sales team may approach the clients as
well.)
The sales team and the technical experts of the company understand the problem of the client
and propose a solution based on the discussions with the internal teams (the testing team and
the delivery team).
The client agrees to the proposed solution and enters into an agreement with the company,
which lists the deliverables promised by the company, the timeline of the project, the payment
amount, etc.
The delivery team works on the solution and finally delivers it to the client.
After the client verifies the solution, it pays the agreed amount to the company.
In the above part, we started by asking the basic question: “Why is the percentage of revenue
returns high?”. Gradually, in this case, we concluded that “the tech stack that we equipped was
not suitable for the solution that was asked for by the clients”. (A tech stack can be considered
the base over which the tech solution is built for the client.). You have identified a possible root
cause.
However, you should not treat this as the end. It can be one of the many possible causes of the
problem. Therefore, you need to validate your cause using the data available. After the
interviewing process, you can treat this as one of the possible causes.
We started by asking the basic question: “Why was the delivery late? ” . Gradually, in this
second scenario case, we concluded that “the team skill set was under qualified or not mapped
with the skills that was required or maybe the team was not motivated ” . In this manner, we
identified the root cause of the problem.
So far, you have learnt about the process of interviewing. One important thing that should be
clear in your mind is that interviewing is a data collection process. You should not generate a
final hypothesis during one particular interview. The primary purpose of the interviewing process
is to identify the key areas where the problem might exist and then collect data concerning them
to test if the problem exists in that area or not. There are different stakeholders involved in any
problem, and each of them could have a different perspective and points to contribute. For
example, in the case above, where the company is facing the issue of revenue returns, it is
possible that either the sales team or the delivery team is responsible for the problem.
The head of the Home Loan business asked the heads of the Sales, Operations, Risk and
Analytics teams to investigate the problem and identify the root causes for the slowing growth.
A business like selling home loans can grow or shrink based on several factors. Nevertheless,
the factors analysed for the above problem are as follows:
Demand side - Are interest rates high because of which the overall demand for home loans
across all banks is low?
Demand side - Are there any macro-economic reasons, such as recession, or low salary
growth, or inflation, due to which consumers are unwilling to spend money on big-ticket items
such as real estate?
Supply side - Are new and attractive housing projects not available in the markets being
served?
Supply side - Have real-estate prices shot up, making homes unaffordable, relatively
speaking?
Competitor side - Are we losing customers to our competition? Is our competition also
experiencing slower growth?
When the teams started exploring answers to the first ‘Why’ question, they found that Bank B,
Bank A’s competitor, was witnessing robust growth in their home loan portfolio. So, the teams
decided to dive deeper into this cause.
In the second ‘WHY they analysed the competitor’s growing portfolio, and the teams conducted
investigation through various channels:
Is Bank B’s Product better? Did Bank A come up with any innovative home loan product with
an attractive EMI structure or a higher Loan-To-Value?
Is Bank B’s Selling better? Are Bank B’s sales agents better than Bank A’s? Is Bank B running a
better marketing campaign than Bank A? Does Bank B have any special tie-ups with companies
that have opened salary accounts with them?
Are Bank B’s Terms better? Was Bank B luring customers through lower processing fee or any
first-year EMI concessions?
So, in the third ‘WHY' the team found that during the document verification process and during
background checks, Bank A spent a lot of time verifying the income of an applicant. An
independent third-party agency was involved in this process, and although its process was
robust, it was time consuming and could not be modified. This was, thus, becoming a bottleneck
and was slowing down the process.
In the fourth ‘WHY, they found that when an applicant was a salaried professional, irrespective
of whether they had an account with the bank or not, the overall process followed by Bank A
was not taking longer than the time offered by Bank B. However, for the remaining three types,
the time taken was significantly longer. When the team looked at the mix of applicants for the
recent quarter, they found that the percentage of applicants who were Businessmen,
Self-Employed or Household folks had dwindled drastically compared with previous quarters.
So, ultimately, in the fifth ‘WHY' , the team detected the root cause of the problem, which was
income verification for non-salaried employees was taking a lot of time. This was identified as
the root cause of the business problem.
Demonstration: 5 WHYs - 2
Let’s understand another problem of how a leading India health insurance company found that
the profits from one of its regional markets had been hit in the latest quarter. The managing
director of the company issued a directive to the data science team to table a root cause
analysis in the next meeting, working with the Marketing, Operations, Actuarial, Underwriting,
Network and Clinical Policy teams.
In the first ‘WHY the data science team analysed the revenue stream and operational costs, and
found that they remained constant; however, when they analysed the trend for medical costs,
the team observed that there was a sharp increase in the latest quarter.
In the second ‘WHY the health insurance company broke down the medical cost into ‘Number
of Claims’ and ‘Average Cost per Claim’. When the data science team looked at the overall
trend of ‘Number of Claims’ and its components, they did not find any significant change.
In the third ‘WHY' they saw that the data science team revealed that roughly 50% of the rise in
‘Average Cost per Claim’ for the region was contributed by a rise in the cost of diagnostic
services. Although there were other service categories that had also contributed to the rise, their
contribution was in single digits.
In the fourth ‘Why’, the data science team first received the three categories of claims namely
"The types of claims", "Who files these claims", "Prices varying across geographical areas".
In the type of claims there are three categories which are as follows:
1. Inpatient Claims - Filed when a patient has to be hospitalised and are the most
expensive of all types of claims
2. Outpatient claims - Filed for visits to the outpatient department of a hospital and for
treatment without hospitalisation. These visits could be for checkups, simple procedures
or for visiting multiple specialists.
3. Doctor claims - These are claims that are filed when a patient visits a doctor for a
consultation or a check-up
When we look at "Who files these claims" , a health insurance company’s relationship with
doctors & hospitals is of two types: with whom the insurer has a contract to provide treatment to
its customers (In Network) and with whom it doesn’t (Out Of Network).
When they looked at "Prices varying across geographical areas" they understood that a health
insurance company has to pay different prices for various services separated by Geographical
Region, as prices vary from one part of the country to another.
The data science team found that the diagnostic services conducted in an Outpatient setting
were expensive for the three main districts in the region, which accounted for 75% of the claims,
for both In Network and Out of Network participants.
So, in this part, you saw how a leading health insurance company identified the root cause of
the business problem using the 5 Why framework.
Situatio Questions about the customer’s Seller understands the Used more in calls
n current processes and buyer’s context, but the that fail; overused
situations buyer is monotonous by inexperienced
here. people
Problem Questions about the customer’s Seller reveals buyer’s Strongly linked to
problems problems; the buyer is success in smaller
interested in discussing sales
the problems
Following are some key points that you should keep in mind while using the SPIN selling
framework:
● The result of the framework is highly dependent upon the quality of the questions that
are asked. If you are not asking the correct questions, then you will end up with a large
chunk of useless information. This can go in the opposite direction as well. You might
even miss out on some vital information by not asking a question. Hence, you should
always include questions from all four categories (SPIN), by maintaining a balance
among all of them.
● The questions asked should not make the interviewee uncomfortable. You should be
careful while framing the questions, so that the interviewee feels free to share relevant
information.
● You should do your own share of research before asking the ‘Situation’ and ‘Problem’
questions, so that you have some context when the interviewee is providing you with
information about the process or the company. It will help you prepare for the
‘Implication’ and ‘Need-payoff’ questions based on what solution can be provided in
those problem scenarios.
Implication and need-payoff should not trigger any unrealistic targets for the people facing the
problem. It is a possible scenario, because the client or the internal team may expect you to
solve all the problems and address the implications arising from them.
One major challenge associated with the framework is to correctly identify the category to which
a question belongs. The major confusion lies between ‘Situation’ and ‘Problem’ questions. You
should always remember that if the question that you are about to ask is trying to gather
information about a process or an activity, then it will be a ‘Situation’ question. And if it is meant
to reveal the problems that the company might face, then it is an Implication question. Now, let’s
try and understand this with an example:
The problem is associated with an IT consulting firm, for which you developed the following 5W
and 5 WHYs:
There are two scenarios for which we developed the 5WHY Framework. The following image
shows the 5WHY framework application:
One benefit that this framework has over others is that it also helps both the problem solver and
the client understand the benefits and the expectations from the solution. These include the
following:
If you are solving the problem, then you get answers to all the questions that you have in mind
and have clarity on what your client or the team expects.
The client can visualise that the solution will solve several of their problems that were discussed
under ‘Implication’ questions and provide the benefits that are conferred under the ‘Need-payoff’
category. They would be even more willing to give you all the information and resources if they
realise how useful the solution would be.
The team from ABC Consulting understood the revenue situation of the bank. They gathered
information on the following aspects by using the 5Ws framework (used in understanding the
business problem):
1. Data - Baselining the data. What was the revenue trend like for the past few years?
What is it like this year?
2. Targets - Who owns the revenue targets? How are the revenue targets arrived at for
each business team? What percentage of the overall target do they own?
3. Products - What are the products that the business teams want to sell in order to realise
the targets? How are the products designed? What are the strengths and weaknesses of
the products? What is the revenue model for each of the products that they want to sell?
4. Salesperson - Who sells the products? How are they hired? How are they trained? What
targets do they get? What is the incentive mechanism in place for them?
5. Customer - Who do they sell the products to? How are customers identified?
6. Selling process - How do they sell the products? Where does the sale take place? What
are the products that see higher sales? When do they see higher sales? Where are
higher sales seen?
ABC Consulting did as much research as it could by itself or with the help of junior interviewees
to answer these questions so that it did not overwhelm the various team leads or the Head of
Marketing with the ‘Situation’ questions. ‘Situation’ questions benefit the Consultant more than
the Problem Owner(s), and are likely to routine the latter.
There was a conversation between Bank XYZ and ABC Consulting company. The consulting
company was asking Bank XYZ various questions to analyse the problem that it was facing.
After the conversation, the team from ABC Consulting finds out what probably is the biggest
reason for the lack of revenue growth of Bank XYZ: the bank has to transform from being
product-centric to being customer-centric. The team from ABC Consulting, however, uses the
SPIN selling framework to build the implications of the problem, instead of trying to jump to a
solution straightway.
The following conversation highlights the discussions between the two teams for the problem
based questions, implications based questions and the need payoff questions.
During the conversation, it was found out that since Product teams may not be in favour of
moving to a customer-centric model, as they may lose ‘status’ and ‘precedence’ in the
organisation, the team from ABC Consulting ventures into building the implications of the
product-centric mindset of Bank XYZ with the Head of Marketing, who may, in turn, use the
same points during internal discussions to advocate for a customer-centric model.
Team ABC: “We’d like to delve deeper into the product-centric mindset that seems to
prevail at your bank. How does this impact your customers? Judging from the Voice Of
The Customer exercise, we conducted, your customers are not happy with it.”
XYZ M.H.: “No, they are not. If I have the highest premium credit card of our bank but
just thousands in my savings account, when I go to a bank branch to withdraw money, I
have to stand in a queue for a while before I can transact. However, if I call up our credit
card call center and complain about late fees being charged, they treat me like a king
and waive the charge off. Feedback from our customers, especially those who hold
multiple products, is that they receive very inconsistent treatment from us, depending on
the specific product sub-type they hold.”
Team ABC: “Aside from lower customer satisfaction scores, which obviously explains
your higher customer churn, doesn’t that also affect your branding and the effort it takes
to attract new customers? We noticed that although you’re able to generate good
revenues from your new customers, your new customer acquisition costs are among the
highest in the industry.”
XYZ M.H.: “Definitely. We’re not perceived as a premium brand in the market, in fact
people think we’re extremely transactional and don’t have a relationship-based
approach to banking. Which also means that we have to spend more on marketing,
advertising, sales incentives to bring in new customers.”
Team ABC: “So your product-centric mindset is not only affecting your revenues through
low cross-sell conversion, but is also affecting customer experience, customer
satisfaction scores, customer churn, branding and new customer acquisition costs?”
XYZ M.H.: “That is true .. Enough to make anyone feel miserable.”
Team ABC: “If we flip from your customers to your sales employees across branches and
call centers, how does the product-centric mindset affect them? Aren’t they not finding
that it makes their jobs difficult?”
XYZ M.H.: “For sure, yes. Our employee satisfaction scores are the lowest among our
sales staff. They feel that their targets are stiff on one hand and the leads they receive
are not of good quality on the other hand.”
Team ABC: “And that seems to contribute to your higher employee attrition levels as
well?”
In the conversation shown above, the team from ABC Consulting points out the implications that
show that the product-centric mindset is not just a problem for the company's revenue growth,
but it also has a significant impact on its customers, the sales team and the product team.
Team ABC: “We could help you move to a more customer-centric way of working. This
would involve a few things. Firstly, using our data management capabilities, we’ll pull
data from all the product data warehouses to build a 360 degree view of your
customers, which will give you all the relationships that a customer has or had with your
bank. Would that be helpful?”
XYZ M.H.: “Oh yes. We would definitely find that very helpful. If I know all the
relationships that a customer has with us and how they transact, it will help us at least
find out what products they are likely to prefer and more importantly, what they don’t
need.”
Team ABC: “And that should help refine your cross-sell methods, right?”
XYZ M.H.: “Yes, it should improve our cross-sell penetration.”
Team ABC: “Next, we will develop a formula to come up with a single number for each
customer that will represent their Pan Bank Relationship Value (PBRV), across all the
products that they own from your bank. Is that something that will be useful?”
XYZ M.H.: “Yes, at the very least, we can use that value to make sure our customers are
treated the same by our call centers and the various teams in the bank branch,
regardless of their product holding.”
Team ABC: “And that kind of consistent treatment could have an impact on customer
experience?”
XYZ M.H.: “Yes, our customer satisfaction scores should improve. Consequently, we
could potentially see lower attrition rates. Our brand perception should also improve
leading to lower new customer acquisition costs.”
Team ABC: “Lastly, we want to use the PBRV to segment your customer base so that you
move from product-based segmentation to total-relationship-based segmentation. What
benefits do you see from having such segmentation?”
XYZ M.H.: “Lovely. That will mean I can train and organize my sales teams to sell to a
particular customer segment rather than a particular product. I can also use the
So, in the part, you see how the team from XYZ Consultancy puts forward various suggestions,
which are as follows:
1. Data consolidation - Created a 360-degree view of all the customers, giving insights into
all the relationships with a customer, past as well as present
2. Pan Bank Relationship Value (PBRV) - Developed a formula that took into account all
the relationships that a customer had with Bank XYZ and quantified them through a
numerical value
3. Customer partition - Instead of parting customers for each product based on the product
subtype, customers could be parted just once, using the PBRV and other inputs
4. Branch–Call Centre–Website Transformation - Based on the new customer partition,
customers of a certain part, regardless of their product holding, would go to that specific
part of the branch, which is reserved for their part, dial just one call centre number for
their part, and also see a different kind of website that is customised to the needs of their
part.
Marketing and sales efforts became the responsibilities of the Customer part teams, rather than
the Product teams. These new Customer part teams endeavoured to sell the right product to the
right customer at the right time through the right channel.
1. You should have a skeptical mindset when you are listening to the interviewee. You
should not have any preconceived notions or prejudices before entering the room. This
will hinder your ability to ask the right questions and is highly unrecommended.
2. You should keep on probing into the interviewee’s statements. This will help you gather
more information and validate the points made.
3. While probing, you should always be careful when dealing with sensitive topics. You
should always make the interviewee comfortable, because they may carry the thought
that there could be some future consequences if they revealed their shortcomings.
4. Always try to ensure that the interviewee replies with information that can be tested or
verified. It is always advisable to have some supporting data for it. You should also
compare the responses of people from the same team and check whether there is a
huge difference between their answers.
So far, you have received pointers on how you should behave in an interview. In the real world,
you will come across people with different traits, and the same approach will not work for all of
them.
Among the four types, the best type of interviewee is the ‘I Know It All’ type. They believe that
they have all the answers and are willing to share their knowledge without any hesitation. The
toughest type of interviewee would be ‘The Stone Face’ type. You would need to put in more
effort into getting information from these interviewees.
If you are able to identify the type of the interviewee, then tailoring the conversation accordingly
can result in a good information source. This is a skill that you will have to practise and develop
over time.
● 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.