![structured problem solving mckinsey logo](https://strategyu.co/wp-content/uploads/2022/06/STRATEGYU-logo.png)
![](http://sektorel.online/777/templates/cheerup/res/banner1.gif)
McKinsey Problem Solving: Six steps to solve any problem and tell a persuasive story
The McKinsey problem solving process is a series of mindset shifts and structured approaches to thinking about and solving challenging problems. It is a useful approach for anyone working in the knowledge and information economy and needs to communicate ideas to other people.
Over the past several years of creating StrategyU, advising an undergraduates consulting group and running workshops for clients, I have found over and over again that the principles taught on this site and in this guide are a powerful way to improve the type of work and communication you do in a business setting.
When I first set out to teach these skills to the undergraduate consulting group at my alma mater, I was still working at BCG. I was spending my day building compelling presentations, yet was at a loss for how to teach these principles to the students I would talk with at night.
Through many rounds of iteration, I was able to land on a structured process and way of framing some of these principles such that people could immediately apply them to their work.
While the “official” McKinsey problem solving process is seven steps, I have outline my own spin on things – from experience at McKinsey and Boston Consulting Group. Here are six steps that will help you solve problems like a McKinsey Consultant:
Step #1: School is over, stop worrying about “what” to make and worry about the process, or the “how”
When I reflect back on my first role at McKinsey, I realize that my biggest challenge was unlearning everything I had learned over the previous 23 years. Throughout school you are asked to do specific things. For example, you are asked to write a 5 page paper on Benjamin Franklin — double spaced, 12 font and answering two or three specific questions.
In school, to be successful you follow these rules as close as you can. However, in consulting there are no rules on the “what.” Typically the problem you are asked to solve is ambiguous and complex — exactly why they hire you. In consulting, you are taught the rules around the “how” and have to then fill in the what.
The “how” can be taught and this entire site is founded on that belief. Here are some principles to get started:
Step #2: Thinking like a consultant requires a mindset shift
There are two pre-requisites to thinking like a consultant. Without these two traits you will struggle:
- A healthy obsession looking for a “better way” to do things
- Being open minded to shifting ideas and other approaches
In business school, I was sitting in one class when I noticed that all my classmates were doing the same thing — everyone was coming up with reasons why something should should not be done.
As I’ve spent more time working, I’ve realized this is a common phenomenon. The more you learn, the easier it becomes to come up with reasons to support the current state of affairs — likely driven by the status quo bias — an emotional state that favors not changing things. Even the best consultants will experience this emotion, but they are good at identifying it and pushing forward.
Key point : Creating an effective and persuasive consulting like presentation requires a comfort with uncertainty combined with a slightly delusional belief that you can figure anything out.
Step #3: Define the problem and make sure you are not solving a symptom
Before doing the work, time should be spent on defining the actual problem. Too often, people are solutions focused when they think about fixing something. Let’s say a company is struggling with profitability. Someone might define the problem as “we do not have enough growth.” This is jumping ahead to solutions — the goal may be to drive more growth, but this is not the actual issue. It is a symptom of a deeper problem.
Consider the following information:
- Costs have remained relatively constant and are actually below industry average so revenue must be the issue
- Revenue has been increasing, but at a slowing rate
- This company sells widgets and have had no slowdown on the number of units it has sold over the last five years
- However, the price per widget is actually below where it was five years ago
- There have been new entrants in the market in the last three years that have been backed by Venture Capital money and are aggressively pricing their products below costs
In a real-life project there will definitely be much more information and a team may take a full week coming up with a problem statement . Given the information above, we may come up with the following problem statement:
Problem Statement : The company is struggling to increase profitability due to decreasing prices driven by new entrants in the market. The company does not have a clear strategy to respond to the price pressure from competitors and lacks an overall product strategy to compete in this market.
Step 4: Dive in, make hypotheses and try to figure out how to “solve” the problem
Now the fun starts!
There are generally two approaches to thinking about information in a structured way and going back and forth between the two modes is what the consulting process is founded on.
First is top-down . This is what you should start with, especially for a newer “consultant.” This involves taking the problem statement and structuring an approach. This means developing multiple hypotheses — key questions you can either prove or disprove.
Given our problem statement, you may develop the following three hypotheses:
- Company X has room to improve its pricing strategy to increase profitability
- Company X can explore new market opportunities unlocked by new entrants
- Company X can explore new business models or operating models due to advances in technology
As you can see, these three statements identify different areas you can research and either prove or disprove. In a consulting team, you may have a “workstream leader” for each statement.
Once you establish the structure you you may shift to the second type of analysis: a bottom-up approach . This involves doing deep research around your problem statement, testing your hypotheses, running different analysis and continuing to ask more questions. As you do the analysis, you will begin to see different patterns that may unlock new questions, change your thinking or even confirm your existing hypotheses. You may need to tweak your hypotheses and structure as you learn new information.
A project vacillates many times between these two approaches. Here is a hypothetical timeline of a project:
![structured problem solving mckinsey Strategy consulting process](https://i0.wp.com/strategyu.co/wp-content/uploads/2017/07/Consulting-Process.png?resize=1024%2C569&ssl=1)
Step 5: Make a slides like a consultant
The next step is taking the structure and research and turning it into a slide. When people see slides from McKinsey and BCG, they see something that is compelling and unique, but don’t really understand all the work that goes into those slides. Both companies have a healthy obsession (maybe not to some people!) with how things look, how things are structured and how they are presented.
They also don’t understand how much work is spent on telling a compelling “story.” The biggest mistake people make in the business world is mistaking showing a lot of information versus telling a compelling story. This is an easy mistake to make — especially if you are the one that did hours of analysis. It may seem important, but when it comes down to making a slide and a presentation, you end up deleting more information rather than adding. You really need to remember the following:
Data matters, but stories change hearts and minds
Here are four quick ways to improve your presentations:
Tip #1 — Format, format, format
Both McKinsey and BCG had style templates that were obsessively followed. Some key rules I like to follow:
- Make sure all text within your slide body is the same font size (harder than you would think)
- Do not go outside of the margins into the white space on the side
- All titles throughout the presentation should be 2 lines or less and stay the same font size
- Each slide should typically only make one strong point
Tip #2 — Titles are the takeaway
The title of the slide should be the key insight or takeaway and the slide area should prove the point. The below slide is an oversimplification of this:
![structured problem solving mckinsey Example of a single slide](https://i0.wp.com/strategyu.co/wp-content/uploads/2017/07/square.png?resize=558%2C313&ssl=1)
Even in consulting, I found that people struggled with simplifying a message to one key theme per slide. If something is going to be presented live, the simpler the better. In reality, you are often giving someone presentations that they will read in depth and more information may make sense.
To go deeper, check out these 20 presentation and powerpoint tips .
Tip #3 — Have “MECE” Ideas for max persuasion
“MECE” means mutually exclusive, collectively exhaustive — meaning all points listed cover the entire range of ideas while also being unique and differentiated from each other.
An extreme example would be this:
- Slide title: There are seven continents
- Slide content: The seven continents are North America, South America, Europe, Africa Asia, Antarctica, Australia
The list of continents provides seven distinct points that when taken together are mutually exclusive and collectively exhaustive . The MECE principle is not perfect — it is more of an ideal to push your logic in the right direction. Use it to continually improve and refine your story.
Applying this to a profitability problem at the highest level would look like this:
Goal: Increase profitability
2nd level: We can increase revenue or decrease costs
3rd level: We can increase revenue by selling more or increasing prices
Each level is MECE. It is almost impossible to argue against any of this (unless you are willing to commit accounting fraud!).
Tip #4 — Leveraging the Pyramid Principle
The pyramid principle is an approach popularized by Barbara Minto and essential to the structured problem solving approach I learned at McKinsey. Learning this approach has changed the way I look at any presentation since.
Here is a rough outline of how you can think about the pyramid principle as a way to structure a presentation:
![structured problem solving mckinsey pyramid principle structure](https://i0.wp.com/strategyu.co/wp-content/uploads/2019/08/Pyramid.png?resize=586%2C204&ssl=1)
As you build a presentation, you may have three sections for each hypothesis. As you think about the overall story, the three hypothesis (and the supporting evidence) will build on each other as a “story” to answer the defined problem. There are two ways to think about doing this — using inductive or deductive reasoning:
![structured problem solving mckinsey deductive versus inductive reasoning in powerpoint arguments](https://i0.wp.com/cdn-images-1.medium.com/max/800/0*DjtUkjVvWJ9fWT0C.png?resize=578%2C295&ssl=1)
If we go back to our profitability example from above, you would say that increasing profitability was the core issue we developed. Lets assume that through research we found that our three hypotheses were true. Given this, you may start to build a high level presentation around the following three points:
![structured problem solving mckinsey example of hypotheses confirmed as part of consulting problem solving](https://i0.wp.com/cdn-images-1.medium.com/max/800/0*SFVWepOPhxf5xAgX.png?w=1170&ssl=1)
These three ideas not only are distinct but they also build on each other. Combined, they tell a story of what the company should do and how they should react. Each of these three “points” may be a separate section in the presentation followed by several pages of detailed analysis. There may also be a shorter executive summary version of 5–10 pages that gives the high level story without as much data and analysis.
Step 6: The only way to improve is to get feedback and continue to practice
Ultimately, this process is not something you will master overnight. I’ve been consulting, either working for a firm or on my own for more than 10 years and am still looking for ways to make better presentations, become more persuasive and get feedback on individual slides.
The process never ends.
The best way to improve fast is to be working on a great team . Look for people around you that do this well and ask them for feedback. The more feedback, the more iterations and more presentations you make, the better you will become. Good luck!
If you enjoyed this post, you’ll get a kick out of all the free lessons I’ve shared that go a bit deeper. Check them out here .
Do you have a toolkit for business problem solving? I created Think Like a Strategy Consultant as an online course to make the tools of strategy consultants accessible to driven professionals, executives, and consultants. This course teaches you how to synthesize information into compelling insights, structure your information in ways that help you solve problems, and develop presentations that resonate at the C-Level. Click here to learn more or if you are interested in getting started now, enroll in the self-paced version ($497) or hands-on coaching version ($997). Both versions include lifetime access and all future updates.
Share this:
- Click to share on Facebook (Opens in new window)
- Click to share on LinkedIn (Opens in new window)
- Click to share on Twitter (Opens in new window)
- Click to share on Pocket (Opens in new window)
- Click to share on WhatsApp (Opens in new window)
![structured problem solving mckinsey Umbrex Logo](https://umbrex.com/wp-content/uploads/2021/02/umbrex-logo.png)
Resources >
Mckinsey approach to problem solving, a guide to the 7-step mckinsey problem solving process.
McKinsey and Company is recognized for its rigorous approach to problem solving. They train their consultants on their seven-step process that anyone can learn.
This resource guides you through that process, largely informed by the McKinsey Staff Paper 66. It also includes a PowerPoint Toolkit with slide templates of each step of the process that you can download and customize for your own use.
![The McKinsey Approach to Problem Solving The McKinsey Approach to Problem Solving](https://umbrex.com/wp-content/uploads/elementor/thumbs/The-McKinsey-Approach-to-Problem-Solving-q5b1p0coc6gdggjvmrtdnmkoc6c597onvi7qhh7w68.png)
In this guide you'll learn:
Overview of the mckinsey approach to problem solving, problem solving process, problem definition.
- Problem Statement
Stakeholder Analysis Worksheet
Structure the problem, hypothesis trees, issue trees, analyses and workplan, synthesize findings, craft recommendations, communicate, distinctiveness practices, harness the power of collaboration, sources and additional reading, request the mckinsey approach to problem solving.
Problem solving — finding the optimal solution to a given business opportunity or challenge — is the very heart of how consultants create client impact, and considered the most important skill for success at McKinsey.
The characteristic “McKinsey method” of problem solving is a structured, inductive approach that can be used to solve any problem. Using this standardized process saves us from reinventing the problem-solving wheel, and allows for greater focus on distinctiveness in the solution. Every new McKinsey associate must learn this method on his or her first day with the firm.
There are four fundamental disciplines of the McKinsey method:
1. Problem definition
A thorough understanding and crisp definition of the problem.
2. The problem-solving process
Structuring the problem, prioritizing the issues, planning analyses, conducting analyses, synthesizing findings, and developing recommendations.
3. Distinctiveness practices
Constructing alternative perspectives; identifying relationships; distilling the essence of an issue, analysis, or recommendation; and staying ahead of others in the problem-solving process.
4. Collaboratio n
Actively seeking out client, customer, and supplier perspectives, as well as internal and external expert insight and knowledge.
Once the problem has been defined, the problem-solving process proceeds with a series of steps:
- Structure the problem
- Prioritize the issues
- Plan analyses
- Conduct analyses
- Synthesize findings
- Develop recommendations
Not all problems require strict adherence to the process. Some steps may be truncated, such as when specific knowledge or analogies from other industries make it possible to construct hypotheses and associated workplans earlier than their formal place in the process. Nonetheless, it remains important to be capable of executing every step in the basic process.
When confronted with a new and complex problem, this process establishes a path to defining and disaggregating the problem in a way that will allow the team to move to a solution. The process also ensures nothing is missed and concentrates efforts on the highest-impact areas. Adhering to the process gives the client clear steps to follow, building confidence, credibility, and long-term capability.
![Slide7 The McKinsey Problem Solving Process](https://umbrex.com/wp-content/uploads/2023/04/Slide7.png)
The most important step in your entire project is to first carefully define the problem. The problem definition will serve the guide all of the team’s work, so it is critical to ensure that all key stakeholders agree that it is the right problem to be solving.
The problem definition will serve the guide all of the team’s work, so it is critical to ensure that all key stakeholders agree that it is the right problem to be solving.
There are often dozens of issues that a team could focus on, and it is often not obvious how to define the problem.
In any real-life situation, there are many possible problem statements. Your choice of problem statement will serve to constrain the range of possible solutions.
Constraints can be a good thing (e.g., limit solutions to actions within the available budget.) And constraints can be a bad thing (e.g., eliminating the possibility of creative ideas.) So choose wisely.
The problem statement may ignore many issues to focus on the priority that should be addressed. The problem statement should be phrased as a question, such that the answer will be the solution.
Example scenario – A family on Friday evening :
A mother, a father, and their two teenage children have all arrived home on a Friday at 6 p.m. The family has not prepared dinner for Friday evening. The daughter has lacrosse practice on Saturday and an essay to write for English class due on Monday. The son has theatre rehearsal on both Saturday and Sunday and will need one parent to drive him to the high school both days, though he can get a ride home with a friend.
The family dog, a poodle, must be taken to the groomer on Saturday morning. The mother will need to spend time this weekend working on assignments for her finance class she is taking as part of her Executive MBA. The father plans to go on a 100-mile bike ride, which he can do either Saturday or Sunday. The family has two cars, but one is at the body shop. They are trying to save money to pay for an addition to their house.
Potential problem definitions – A family on Friday evening :
The problem definition should not be vague, without clear measures of success. Rather, it should be a SMART definition:
- Action-oriented
Given one set of facts, it is possible to come up with many possible problem statements. The choice of problem statement constrains the range of possible solutions.
Before starting to solve the problem, the family first needs to agree on what problem they want to solve.
- What should the family do for dinner on Friday night?
- How can the family schedule their activities this weekend to accomplish everything planned given that they only have one vehicle available?
- How can the family increase income or reduce expenses to allow them to save $75K over the next 12 months to pay for the planned addition to their house?
![Slide13 The McKinsey Problem Solving Process](https://umbrex.com/wp-content/uploads/2024/06/Slide13-1.png)
Problem Statement Worksheet
This is a helpful tool to use to clearly define the problem. There are often dozens of issues that a team could focus on, and it is often not obvious how to define the problem. In any real-life situation, there are many possible problem statements. Your choice of problem statement will serve to constrain the range of possible solutions.
- Use a question . The problem statement should be phrased as a question, such that the answer will be the solution. Make the question SMART: specific, measurable, action-oriented, relevant, and time-bound. Example: “How can XYZ Bank close the $100 million profitability gap in two years?”
- Context . What are the internal and external situations and complications facing the client, such as industry trends, relative position within the industry, capability gaps, financial flexibility, and so on?
- Success criteria . Understand how the client and the team define success and failure. In addition to any quantitative measures identified in the basic question, identify other important quantitative or qualitative measures of success, including timing of impact, visibility of improvement, client capability building required, necessary mindset shifts, and so on.
- Scope and constraints . Scope most commonly covers the markets or segments of interest, whereas constraints govern restrictions on the nature of solutions within those markets or segments.
- Stakeholders . Explore who really makes the decisions — who decides, who can help, and who can block.
- Key sources of insight . What best-practice expertise, knowledge, and engagement approaches already exist? What knowledge from the client, suppliers, and customers needs to be accessed? Be as specific as possible: who, what, when, how, and why.
![Slide21 The McKinsey Problem Solving Process: Problem Definition and Statement](https://umbrex.com/wp-content/uploads/2024/06/Slide21-1.png)
In completing the Problem Statement Worksheet, you are prompted to define the key stakeholders.
As you become involved in the problem-solving process, you should expand the question of key stakeholders to include what the team wants from them and what they want from the team, their values and motivations (helpful and unhelpful), and the communications mechanisms that will be most effective for each of them.
Using the Stakeholder Analysis Worksheet allows you to comprehensively identify:
- Stakeholders
- What you need from them
- Where they are
- What they need from you
![Slide24 The McKinsey Problem Solving Process: Problem Definition and Statement](https://umbrex.com/wp-content/uploads/2024/06/Slide24-2.png)
The two most helpful techniques for rigorously structuring any problem are hypothesis trees and issue trees. Each of these techniques disaggregates the primary question into a cascade of issues or hypotheses that, when addressed, will together answer the primary question.
![Slide29 The McKinsey Problem Solving Process - Structure the Problem](https://umbrex.com/wp-content/uploads/2024/06/Slide29-2.png)
A hypothesis tree might break down the same question into two or more hypotheses.
The aim at this stage is to structure the problem into discrete, mutually exclusive pieces that are small enough to yield to analysis and that, taken together, are collectively exhaustive.
Articulating the problem as hypotheses, rather than issues, is the preferred approach because it leads to a more focused analysis of the problem. Questions to ask include:
- Is it testable – can you prove or disprove it?
- It is open to debate? If it cannot be wrong, it is simply a statement of fact and unlikely to produce keen insight.
- If you reversed your hypothesis – literally, hypothesized that the exact opposite were true – would you care about the difference it would make to your overall logic?
- If you shared your hypothesis with the CEO, would it sound naive or obvious?
- Does it point directly to an action or actions that the client might take?
Quickly developing a powerful hypothesis tree enables us to develop solutions more rapidly that will have real impact. This can sometimes seem premature to clients, who might find the “solution” reached too quickly and want to see the analysis behind it.
Take care to explain the approach (most important, that a hypothesis is not an answer) and its benefits (that a good hypothesis is the basis of a proven means of successful problem solving and avoids “boiling the ocean”).
Example: Alpha Manufacturing, Inc.
Problem Statement: How can Alpha increase EBITDA by $13M (to $50M) by 2025?
The hypotheses might be:
- Alpha can add $125M revenues by expanding to new customers, adding $8M of EBITDA
- Alpha can reduce costs to improve EBITDA by $5M
These hypotheses will be further disaggregated into subsidiary hypotheses at the next level of the tree.
![Slide34 The McKinsey Problem Solving Process - Hypothesis Tree](https://umbrex.com/wp-content/uploads/2024/06/Slide34-1.png)
Often, the team has insufficient knowledge to build a complete hypothesis tree at the start of an engagement. In these cases, it is best to begin by structuring the problem using an issue tree.
An issue tree is best set out as a series of open questions in sentence form. For example, “How can the client minimize its tax burden?” is more useful than “Tax.” Open questions – those that begin with what, how, or why– produce deeper insights than closed ones. In some cases, an issue tree can be sharpened by toggling between issue and hypothesis – working forward from an issue to identify the hypothesis, and back from the hypothesis to sharpen the relevant open question.
Once the problem has been structured, the next step is to prioritize the issues or hypotheses on which the team will focus its work. When prioritizing, it is common to use a two-by-two matrix – e.g., a matrix featuring “impact” and “ease of impact” as the two axes.
Applying some of these prioritization criteria will knock out portions of the issue tree altogether. Consider testing the issues against them all, albeit quickly, to help drive the prioritization process.
Once the criteria are defined, prioritizing should be straightforward: Simply map the issues to the framework and focus on those that score highest against the criteria.
As the team conducts analysis and learns more about the problem and the potential solution, make sure to revisit the prioritization matrix so as to remain focused on the highest-priority issues.
The issues might be:
- How can Alpha increase revenue?
- How can Alpha reduce cost?
Each of these issues is then further broken down into deeper insights to solutions.
![Slide39 The McKinsey Problem Solving Process - Issue Tree](https://umbrex.com/wp-content/uploads/2024/06/Slide39-1.png)
If the prioritization has been carried out effectively, the team will have clarified the key issues or hypotheses that must be subjected to analysis. The aim of these analyses is to prove the hypotheses true or false, or to develop useful perspectives on each key issue. Now the task is to design an effective and efficient workplan for conducting the analyses.
Transforming the prioritized problem structure into a workplan involves two main tasks:
- Define the blocks of work that need to be undertaken. Articulate as clearly as possible the desired end products and the analysis necessary to produce them, and estimate the resources and time required.
- Sequence the work blocks in a way that matches the available resources to the need to deliver against key engagement milestones (e.g., important meetings, progress reviews), as well as to the overall pacing of the engagement (i.e., weekly or twice-weekly meetings, and so on).
A good workplan will detail the following for each issue or hypothesis: analyses, end products, sources, and timing and responsibility. Developing the workplan takes time; doing it well requires working through the definition of each element of the workplan in a rigorous and methodical fashion.
![Slide44 The McKinsey Problem Solving Process Plan Analysis](https://umbrex.com/wp-content/uploads/2024/06/Slide44.png)
It’s useful to match the workplan to three horizons:
- What is expected at the end of the engagement
- What is expected at key progress reviews
- What is due at daily and/or weekly team meetings
The detail in the workplan will typically be greater for the near term (the next week) than for the long term (the study horizon), especially early in a new engagement when considerable ambiguity about the end state remains.
![Slide50 The McKinsey Problem Solving Process Workplan Three Horizons](https://umbrex.com/wp-content/uploads/2024/06/Slide50.png)
Here are three different templates for a workplan:
![Slide53 The McKinsey Problem Solving Process Workplan](https://umbrex.com/wp-content/uploads/2024/06/Slide53-1.png)
This is the most difficult element of the problem-solving process. After a period of being immersed in the details, it is crucial to step back and distinguish the important from the merely interesting. Distinctive problem solvers seek the essence of the story that will underpin a crisp recommendation for action.
Although synthesis appears, formally speaking, as the penultimate step in the process, it should happen throughout. Ideally, after you have made almost any analytical progress, you should attempt to articulate the “Day 1” or “Week 1” answer. Continue to synthesize as you go along. This will remind the team of the question you are trying to answer, assist prioritization, highlight the logical links of the emerging solution, and ensure that you have a story ready to articulate at all times during the study.
McKinsey’s primary tool for synthesizing is the pyramid principle. Essentially, this principle asserts that every synthesis should explain a single concept, per the “governing thought.” The supporting ideas in the synthesis form a thought hierarchy proceeding in a logical structure from the most detailed facts to the governing thought, ruthlessly excluding the interesting but irrelevant.
While this hierarchy can be laid out as a tree (like with issue and hypothesis trees), the best problem solvers capture it by creating dot-dash storylines — the Pyramid Structure for Grouping Arguments.
Pyramid Structure for Grouping Arguments
- Focus on action. Articulate the thoughts at each level of the pyramid as declarative sentences, not as topics. For example, “expansion” is a topic; “We need to expand into the European market” is a declarative sentence.
- Use storylines. PowerPoint is poor at highlighting logical connections, therefore is not a good tool for synthesis. A storyline will clarify elements that may be ambiguous in the PowerPoint presentation.
- Keep the emerging storyline visible. Many teams find that posting the storyline or story- board on the team-room wall helps keep the thinking focused. It also helps in bringing the client along.
- Use the situation-complication-resolution structure. The situation is the reason there is action to be taken. The com- plication is why the situation needs thinking through – typically an industry or client challenge. The resolution is the answer.
- Down the pyramid: does each governing thought pose a single question that is answered completely by the group of boxes below it?
- Across: is each level within the pyramid MECE?
- Up: does each group of boxes, taken together, provide one answer – one “so what?” – that is essentially the governing thought above it?
- Test the solution. What would it mean if your hypotheses all came true?
![Attributes of pyramid structure for grouping arguments The McKinsey Problem Solving Process](https://umbrex.com/wp-content/uploads/2023/04/Attributes-of-pyramid-structure-for-grouping-arguments-1200x675.png)
It is at this point that we address the client’s questions: “What do I do, and how do I do it?” This means not offering actionable recommendations, along with a plan and client commitment for implementation.
The essence of this step is to translate the overall solution into the actions required to deliver sustained impact. A pragmatic action plan should include:
- Relevant initiatives, along with a clear sequence, timing, and mapping of activities required
- Clear owners for each initiative
- Key success factors and the challenges involved in delivering on the initiatives
Crucial questions to ask as you build recommendations for organizational change are:
- Does each person who needs to change (from the CEO to the front line) understand what he or she needs to change and why, and is he or she committed to it?
- Are key leaders and role models throughout the organization personally committed to behaving differently?
- Has the client set in place the necessary formal mechanisms to reinforce the desired change?
- Does the client have the skills and confidence to behave in the desired new way?
Once the recommendations have been crafted in the problem-solving process, it’s vital to effectively communicate those findings and recommendations.
An executive summary is a great slide to use for this. See more on executive summary slides, including 30 templates, at our Ultimate Guide to Executive Summary Slides .
![Slide62 The McKinsey Problem Solving Process Executive Summary Communication](https://umbrex.com/wp-content/uploads/2024/06/Slide62-1.png)
Great problem solvers identify unique disruptions and discontinuities, novel insights, and step-out opportunities that lead to truly distinctive impact. This is done by applying a number of practices throughout the problem-solving process to help develop these insights.
Expand: Construct multiple perspectives
Identifying alternative ways of looking at the problem expands the range of possibilities, opens you up to innovative ideas, and allows you to formulate more powerful hypotheses. Questions that help here include:
- What changes if I think from the perspective of a customer, or a supplier, or a frontline employee, or a competitor?
- How have other industries viewed and addressed this same problem?
- What would it mean if the client sought to run the company like a low-cost airline or a cosmetics manufacturer?
Link: Identify relationships
Strong problem solvers discern connections and recognize patterns in two different ways:
- They seek out the ways in which different problem elements – issues, hypotheses, analyses, work elements, findings, answers, and recommendations – relate to one another.
- They use these relationships throughout the basic problem-solving process to identify efficient problem-solving approaches, novel solutions, and more powerful syntheses.
Distill: Find the essence
Cutting through complexity to identify the heart of the problem and its solution is a critical skill.
- Identify the critical problem elements. Are there some issues, approaches, or options that can be eliminated completely because they won’t make a significant difference to the solution?
- Consider how complex the different elements are and how long it will take to complete them. Wherever possible, quickly advance simpler parts of the problem that can inform more complex or time-consuming elements.
Lead: Stay ahead/step back
Without getting ahead of the client, you cannot be distinctive. Paradoxically, to get ahead – and stay ahead – it is often necessary to step back from the problem to validate or revalidate the approach and the solution.
- Spend time thinking one or more steps ahead of the client and team.
- Constantly check and challenge the rigor of the underlying data and analysis.
- Stress-test the whole emerging recommendation
- Challenge the solution against a set of hurdles. Does it satisfy the criteria for success as set out on the Problem Statement Worksheet?
No matter how skilled, knowledgeable, or experienced you are, you will never create the most distinctive solution on your own. The best problem solvers know how to leverage the power of their team, clients, the Firm, and outside parties. Seeking the right expertise at the right time, and leveraging it in the right way, are ultimately how we bring distinctiveness to our work, how we maximize efficiency, and how we learn.
When solving a problem, it is important to ask, “Have I accessed all the sources of insight that are available?” Here are the sources you should consider:
- Your core team
- The client’s suppliers and customers
- Internal experts and knowledge
- External sources of knowledge
- Communications specialists
The key here is to think open, not closed. Opening up to varied sources of data and perspectives furthers our mission to develop truly innovative and distinctive solutions for our clients.
- McKinsey Staff Paper 66 — not published by McKinsey but possibly found through an internet search
- The McKinsey Way , 1999, by Ethan M. Rasiel
For consultants
© Copyright 2024 by Umbrex
Designed by our friends at Filez
- Privacy Policy
- Terms of Service
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_96,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fad582127-4fa0-47da-bb04-fb00b7187c89_350x350.png)
Romulus’s Substack
The mckinsey problem solving approach to consulting: a comprehensive guide, by: jason branin.
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_80,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F9d566ab8-9691-445b-8fa2-4038165a90b1_144x144.png)
In the realm of management consulting, McKinsey & Company stands out as a beacon of excellence and innovation. Since its founding in 1926 by James O. McKinsey, the firm has grown to become one of the most prestigious and influential consulting firms in the world. Central to McKinsey's success is its unique problem-solving approach, which has not only shaped the firm’s own practices but has also significantly influenced the broader consulting industry. This article delves into the intricacies of the McKinsey Problem Solving Approach, exploring its methodologies, tools, and the impact it has on delivering high-value solutions to clients.
The Essence of the McKinsey Problem Solving Approach
Thanks for reading Romulus’s Substack! Subscribe for free to receive new posts and support my work.
At its core, the McKinsey Problem Solving Approach is a structured methodology designed to tackle complex business challenges through a combination of rigorous analysis, strategic thinking, and practical recommendations. This approach is characterized by its systematic nature, emphasizing clarity, precision, and thoroughness in every step of the problem-solving process. The primary objective is to deliver actionable insights and sustainable solutions that drive tangible results for clients.
Key Components of the McKinsey Problem Solving Approach
1. Defining the Problem
The first and most crucial step in the McKinsey Problem Solving Approach is defining the problem. This involves clearly articulating the issue at hand, setting the boundaries for the analysis, and establishing the objectives of the engagement. McKinsey consultants use a structured framework known as the “problem statement” to capture the essence of the challenge. A well-defined problem statement typically includes:
- Context: The background information and relevant facts about the client and the issue.
- Objective: The desired outcome or goal of the analysis.
- Scope: The boundaries and constraints of the problem.
- Hypotheses: Initial assumptions or potential solutions that will be tested during the analysis.
By investing time and effort in defining the problem accurately, McKinsey ensures that the subsequent analysis is focused, relevant, and aligned with the client’s needs.
2. Disaggregating the Problem
Once the problem is defined, the next step is to break it down into smaller, manageable components. This process, known as disaggregation, allows consultants to tackle each part of the problem systematically. McKinsey employs the MECE (Mutually Exclusive, Collectively Exhaustive) principle to ensure that all aspects of the problem are covered without any overlap or gaps. The MECE framework helps in organizing information logically and ensures that the analysis is comprehensive.
For example, if the problem involves improving a company's profitability, McKinsey might disaggregate it into components such as revenue enhancement, cost reduction, and operational efficiency. Each of these components is then further broken down into sub-components, allowing for a detailed and focused analysis.
3. Conducting the Analysis
The analysis phase is where McKinsey's analytical rigor comes to the fore. This phase involves gathering data, testing hypotheses, and developing insights. McKinsey consultants use a variety of tools and techniques to conduct their analysis, including:
- Benchmarking: Comparing the client’s performance against industry standards or best practices.
- Financial Modeling: Building detailed models to simulate different scenarios and their financial impact.
-Root Cause Analysis: Identifying the underlying causes of the problem rather than just addressing the symptoms.
-Scenario Planning: Exploring different future scenarios to anticipate potential challenges and opportunities.
Data-driven decision-making is a hallmark of McKinsey’s approach. The firm places a strong emphasis on using quantitative data to support its findings and recommendations. This ensures that the solutions proposed are not only theoretically sound but also practically viable.
4. Synthesizing Insights
After conducting the analysis, the next step is to synthesize the insights and draw conclusions. This involves distilling the vast amount of data and information into clear, actionable insights that address the client’s problem. McKinsey consultants use the “Pyramid Principle,” a communication technique developed by Barbara Minto, a former McKinsey consultant, to present their findings. The Pyramid Principle advocates starting with the main conclusion or recommendation and then supporting it with key arguments and data.
This top-down approach ensures that the most important insights are communicated upfront, making it easier for clients to understand and act upon the recommendations. It also helps in structuring complex information in a logical and coherent manner.
5. Developing Recommendations
Based on the synthesized insights, McKinsey consultants develop specific recommendations for the client. These recommendations are not just theoretical ideas but practical, actionable steps that the client can implement to address the problem. McKinsey places a strong emphasis on creating “value-driven” recommendations that deliver measurable impact.
To ensure the recommendations are actionable, McKinsey follows a few guiding principles:
- Feasibility: Ensuring that the recommendations are realistic and can be implemented within the client’s constraints.
- Sustainability: Focusing on long-term solutions that deliver sustained benefits rather than short-term fixes.
- Client Buy-in: Engaging the client throughout the process to ensure they understand and are committed to the recommendations.
6. Implementing Solutions
The final step in the McKinsey Problem Solving Approach is implementing the solutions. McKinsey often works closely with clients to support the implementation phase, ensuring that the recommendations are executed effectively. This involves developing detailed implementation plans, setting up monitoring mechanisms, and providing ongoing support and guidance.
McKinsey’s commitment to implementation reflects its philosophy of “seeing it through.” The firm recognizes that the true value of its consulting services lies not just in developing insightful recommendations but in helping clients achieve tangible results.
Tools and Techniques in the McKinsey Problem Solving Approach
McKinsey employs a wide range of tools and techniques to support its problem-solving approach. Some of the most commonly used tools include:
1. The Issue Tree
The Issue Tree is a visual representation of the problem and its sub-components. It helps in organizing the problem into a hierarchical structure, making it easier to identify the key issues and areas of focus. The Issue Tree is typically used during the disaggregation phase to break down the problem into smaller, manageable parts.
2. The Decision Tree
The Decision Tree is a tool used to map out different decision paths and their potential outcomes. It helps in evaluating the implications of different choices and identifying the most optimal decision. The Decision Tree is particularly useful in scenarios where there are multiple possible solutions or courses of action.
3. The Hypothesis Pyramid
The Hypothesis Pyramid is a tool used to structure hypotheses in a logical manner. It helps in organizing hypotheses into a hierarchy, with the main hypothesis at the top and supporting hypotheses underneath. This tool is used to guide the analysis and ensure that all relevant hypotheses are tested systematically.
4. The MECE Framework
The MECE (Mutually Exclusive, Collectively Exhaustive) framework is a key principle in the McKinsey Problem Solving Approach. It ensures that all aspects of the problem are covered without any overlap or gaps. The MECE framework is used during the disaggregation phase to organize information logically and comprehensively.
5. The Pyramid Principle
The Pyramid Principle is a communication technique used to present findings and recommendations in a clear and structured manner. It advocates starting with the main conclusion or recommendation and then supporting it with key arguments and data. This top-down approach ensures that the most important insights are communicated upfront.
The Impact of the McKinsey Problem Solving Approach
The McKinsey Problem Solving Approach has had a profound impact on the field of management consulting and beyond. Some of the key impacts include:
1. Driving Business Success
McKinsey’s structured and rigorous approach to problem-solving has helped countless organizations achieve significant improvements in performance and profitability. By providing data-driven insights and practical recommendations, McKinsey has enabled clients to address complex challenges and capitalize on new opportunities.
2. Setting Industry Standards
McKinsey’s methodologies and best practices have set industry standards for consulting. Many of the tools and techniques developed by McKinsey, such as the MECE framework and the Pyramid Principle, have become widely adopted across the consulting industry. McKinsey’s emphasis on analytical rigor and strategic thinking has influenced the way consulting firms approach problem-solving.
3. Fostering Innovation
McKinsey’s approach to problem-solving fosters innovation by encouraging consultants to think creatively and challenge conventional wisdom. The firm’s focus on developing hypotheses and testing them systematically promotes a culture of experimentation and continuous improvement. This has led to the development of innovative solutions that drive business success.
4. Building Client Capabilities
McKinsey’s commitment to implementation and client engagement helps build the capabilities of client organizations. By working closely with clients throughout the problem-solving process, McKinsey ensures that clients not only achieve immediate results but also develop the skills and knowledge to sustain improvements over the long term.
The McKinsey Problem Solving Approach is a testament to the firm’s commitment to excellence and innovation. Its structured methodology, emphasis on analytical rigor, and focus on delivering actionable insights have made McKinsey a trusted advisor to some of the world’s most successful organizations. By continually refining its approach and embracing new tools and techniques, McKinsey remains at the forefront of the consulting industry, helping clients navigate complex challenges and achieve sustainable growth.
As businesses continue to face an ever-changing landscape, the principles and practices of the McKinsey Problem Solving Approach will remain highly relevant. Its focus on defining the problem accurately, conducting rigorous analysis, and developing practical recommendations provides a robust framework for tackling the most pressing business issues. For organizations seeking to drive performance and innovation, embracing the McKinsey Problem Solving Approach can be a powerful catalyst for success.
If you are looking to continue this conversation or are looking for some advice, please, feel free to reach out to me at [email protected].
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_64,h_64,c_fill,f_auto,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack.com%2Fimg%2Favatars%2Flogged-out.png)
Ready for more?
Spotify is currently not available in your country.
Follow us online to find out when we launch., spotify gives you instant access to millions of songs – from old favorites to the latest hits. just hit play to stream anything you like..
![structured problem solving mckinsey structured problem solving mckinsey](https://www.scdn.co/i/generic/premium-img1.jpg)
Listen everywhere
Spotify works on your computer, mobile, tablet and TV.
![structured problem solving mckinsey structured problem solving mckinsey](https://www.scdn.co/i/generic/premium-img2.jpg)
Unlimited, ad-free music
No ads. No interruptions. Just music.
![structured problem solving mckinsey structured problem solving mckinsey](https://www.scdn.co/i/generic/premium-img3.jpg)
Download music & listen offline
Keep playing, even when you don't have a connection.
![structured problem solving mckinsey structured problem solving mckinsey](https://www.scdn.co/i/generic/premium-img4.jpg)
Premium sounds better
Get ready for incredible sound quality.
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_96,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2F3ff38300-e542-47af-83e0-4635e8fdef3b_500x500.png)
Product Mindset's Newsletter
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_120,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F65f3f2b4-b9a7-43dc-82e8-5ccbd643f561_1280x720.png)
25/36 : 🛠️ McKinsey's Problem-solving Process
A problem well defined is a problem half-solved — charles kettering.
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_80,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2Ffcbdf735-04a4-4636-8c58-1c04ac288739_500x500.png)
Problem Solving for Product Managers
Product Managers excel in problem-solving by employing a strategic mix of analytical thinking, creative ideation, and data-driven insights. They keenly identify and comprehend customer needs, analyze market trends, and craft innovative solutions that enhance products' value and propel business growth. By addressing challenges, optimizing development processes, and aligning products with company objectives, they ensure customer demands are met efficiently and deliver successful outcomes.
Concept of problem-solving
Today's businesses want employees who can adapt to new situations rapidly and effectively.
The ideal employee is a master of basic skills such as reading, writing, and numeracy.
The ideal employee is also a master of learning, communication, critical thinking, creative thinking, and problem-solving.
The ideal employee can respond to a problem quickly, correctly, and with little or no supervision.
If you can solve problems, you can write your own ticket for whatever job you want.
Defining Problem-Solving
Problems can be classified into puzzle problems, well-structured problems, and ill-structured problems.
Simple Problems Many games contain puzzle problems and are not "serious" in nature, nor is there any real-life consequence for failing to solve them.
Well-structured Problems Some problems which are simple and well-defined are called well-structured problems and include a set number of possible solutions - solutions are either 100% right or 100% wrong. An example of a well-structured problem is a typical mathematical (2 + 2 = 4) question. This question has a definitive correct answer.
Ill-structured Problems In contrast to well-structured problems are ill-structured problems. In these cases, problems may have many possible answers because they are complex and poorly defined. The "best" solutions to ill-defined problems depend on the priorities underlying the situation. What is "best" today may not be "best" tomorrow. Ill-structured problems, because they are more difficult to "solve," require the development of higher-order thinking skills and the ability to construct a convincing argument for a particular solution as opposed to all other possible solutions.
To summarize ill-structured problems:
They are complex and poorly defined.
They have many possible answers.
They do not have one best answer.
Here is an example of an ill-structured problem:
The population of your community is growing. Your water supply will not support many new people.
What do you do?
This is a complex problem. It affects the people, the environment, and the quality of life itself. To arrive at a good solution, you need to use math, science, political science, psychology, and probably more!
This problem actually occurs frequently in areas with a growing population. In one community facing this problem, more than 20 possible solutions were presented to the public. A solution was then chosen upon which the majority of the public agreed. It wasn't the "right" solution because all of the 20 possible solutions had strengths and weaknesses.
The lesson here is that ill-structured problems usually have several workable solutions. Each solution has advantages and disadvantages that depend on who is affected by the solution. The solution chosen is often the one that has the best argument for it.
3 Prerequisites for a good solution
He realized there are three essential prerequisites for good solutions:
The product must be defined to allow for the development of useful solutions. The potential solution must fit the defined problem space and product scope. The product team must have understood the problem.
Understanding the problem Whether the problem comes from your users or another set of stakeholders, you need to properly understand the problem. The only way to do that is through a combination of research, and empathy. This means gathering both qualitative and quantitative data. Find out how the user/stakeholder feels about the problem, as well as how they behave in response to it.
Communicate “The Why” As a product manager, your most important why is the customer problem that your product is trying to solve. Include your team and other stakeholders in understanding the customer problem and selecting the right goal metric to grow. This way, everyone can contribute, feel ownership, and stay motivated to solve the problem even if the product changes.
First , it helps everyone internalize “the why” so they can make decisions with the same goal in mind.
Second , if people are not aligned on “the why”, they’re more likely to bring up objections if you talk about it constantly.
Keep It Simple When communicating with others, the most critical question that you need to answer is, “Do people understand?” If people don’t understand the why, they won’t be able to execute.
Keep your communication simple, short, and specific. Check to see if people understand your message by asking them to explain it back to you
Make a risk vs reward assessment Once you know what the problem is, you need to lay the groundwork for your plan on how to proceed with solving it. Analyze the potential risks and rewards of the project. So if a stakeholder is asking that a new feature be implemented, work out how much of your team’s work hours, budget, and resources will be needed to complete the project and solve the problem.
Balance this out by seeing how the best-case scenario (eg, you completely solve the problem) will benefit your product in terms of OKRs, and the bottom line.
Define Success Defining the success of a project really boils down to the final part of your risk vs reward assessment. What does the best-case scenario look like?
If the answer isn’t obvious, think about your company’s North Star metrics, or your team’s KPIs. If the project is worthwhile, its goals should align with either, if not both, or these.
I learned to approach every problem from multiple angles. It was the combination of both qualitative and quantitative insights that led us to our proposed solution. Also, a variety of perspectives are critical.
Learning to Ask the Right Questions: Define the Problem Statement
McKinsey’s Problem-solving process
McKinsey’s benchmark is the problem-solving process as practiced by McKinsey. At the most abstract level, McKinsey develops solutions to clients’ strategic problems and, possibly, aids in the implementation of those solutions
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd213923c-6f93-4799-a1ad-b3caa75c3608_958x512.png)
Business Need You can’t have problem-solving without a problem or, more broadly, a need on the part of the client. In business, those needs come in several forms: competitive, organizational, financial, and operational.
Analyzing Once your organization has identified the problem, it can begin to seek a solution, whether on its own or with the help of McKinsey (or any other outside agent). McKinsey’s fact-based, hypothesis-driven problem-solving process begins with framing the problem: defining the boundaries of the problem and breaking it down into its component elements to allow the problem-solving team to come up with an initial hypothesis as to the solution. The next step is designing the analysis, determining the analyses that must be done to prove the hypothesis, followed by gathering the data needed for the analyses. Finally comes interpreting the results of those analyses to see whether they prove or disprove the hypothesis and to develop a course of action for the client.
Presenting You may have found a solution, but it has no value until it has been communicated to and accepted by the client. For that to happen, you must structure your presentation so that it communicates your ideas clearly and concisely and generates buy-in for your solution for each individual audience to which you present.
Managing The success of the problem-solving process requires good management at several levels. The problem-solving team must be properly assembled, motivated, and developed. The client must be kept informed, involved, and inspired by both the problem-solving process and the solution. The individual team members (that’s you) must strike a balance between life and career that allows them to meet the expectations of the client and the team while not “burning out.”
Implementation Your organization may have accepted your solution, but it must still implement it. This requires the dedication of sufficient resources within the organization, the timely reaction of the organization to any stumbling blocks that may arise during implementation, and the focus of the organization on completion of the tasks necessary for full implementation. In addition, the organization must institute a process of iteration that leads to continual improvement. That process requires reassessing implementation and rededicating the organization to make additional changes identified during reassessment.
Leadership At the nexus of solution and implementation comes leadership. Those at the helm of your organization must conceive a strategic vision for the organization. They must also provide inspiration for those in the organization who will do the hands-on work of implementation. Finally, they must make the right judgments regarding the delegation of authority in overseeing implementation throughout the organization.
There is one other piece of the model: the tension between intuition and data. Problem-solving doesn’t take place in a vacuum. Even McKinsey has only so many resources to throw at a problem and a limited time in which to solve it. While we are advocates for McKinsey-style fact-based problem solving, we recognize that it’s practically impossible to have all the relevant facts before reaching a decision. Therefore, most executives make business decisions based partly on facts and partly on intuition—gut instinct tempered by experience. We will discuss the pros and cons of each element later in the book. For now, we will simply say that we think a sound decision requires a balance of both.
8 Steps to Problem-Solving from McKinsey
Solve at the first meeting with a hypothesis, intuition is as important as facts, do your research but don’t reinvent the wheel, tell the story behind the data, start with the conclusion, hit singles, respect your time.
The McKinsey problem-solving process begins with the use of structured frameworks to generate fact-based hypotheses followed by data gathering and analysis to prove or disprove the hypotheses.
Gut feeling at this stage is extremely important because we don’t have many facts yet. However, structure strengthens your thinking and ensures that your ideas will stand up. Typically, the problem-solving process would involve defining the boundaries of the problem and then breaking it down into its component elements.
The concept of MECE (pronounced “mee-see” and an acronym for Mutually Exclusive, Collectively Exhaustive), is a basic tenet of the McKinsey thought process. Being MECE in the context of problem-solving means separating your problem into distinct, non-overlapping issues while making sure that no issues relevant to your problem have been overlooked. This allows to simplify the problem and plan the work because in most cases, a complex problem can be reduced to a group of smaller, simpler problems that can be solved individually.
The most common tool McKinsey people use to break problems apart is the logic tree .
Having reduced the problem to its essential components, you are ready to embark on the next step which is framing it: forming a hypothesis as to its likely solution. By already knowing where your solution is, you eliminate a lot of paths that lead to dead ends.
Using an initial hypothesis to guide your research and analysis will increase both the efficiency and effectiveness of your decision-making because it provides you and your team with a problem-solving roadmap that will lead you to ask the right questions and perform the correct analysis to get to your answer. A good hypothesis will also save you time by pointing out potential blind alleys much more quickly and allowing you to get back to the main issues if you do go down the wrong path.
Since you should form your hypothesis at the start of the problem-solving process, you have to rely less on facts (you won’t have done most of your fact gathering yet) and more on instinct or intuition. Take what you know about the problem at hand, combine it with your gut feelings on the issue, and think about what the most likely answers are.
Executives make major strategic decisions based as much on gut instinct as on fact-based analysis.
Intuition and data complement each other. You need at least some of each to have a solid basis for your decisions. The key to striking the balance is quality over quantity.
When you form an initial hypothesis, you are “solving the problem at the first meeting.” Unfortunately, although you may think you have the answer, you have to prove it through fact-based analysis.
Your next step is to figure out which analyses you have to perform and which questions you have to ask in order to prove or disprove your hypothesis.
When your time and resources are limited, you don’t have the luxury of being able to examine every single factor in detail. Instead, when planning your analyses, figure out which factors most affect the problem and focus on those. Drill down to the core of the problem instead of picking apart each and every piece. In most situations, achieving a scientific level of exactitude for your management decisions is counterproductive.
That’s why also as one of your first steps in designing your analysis, you should figure out what not to do.
As your next step, you should decide which analyses are quick wins — easy to complete and likely to make a major contribution to proving or refuting the initial hypothesis (80/20 rule).
When doing your research, you don’t want to get as much information as possible, you want to get the most important information as quickly as possible.
With a plan of action for what to research, make sure you don’t reinvent the wheel as you start gathering your data. Whatever problem you’re facing, chances are that someone somewhere has worked on something similar. So your next step here is to look through all possible internal documents and then look externally.
Once you have your analysis finished, you need to interpret it because numbers or data don’t say anything. You have to figure out the story behind it and the message that you want to communicate.
At this stage, first comes the process of understanding the data: piecing together (in your own mind or within your team) the story the data is telling you and the steps you should take based on that story. The second comes assembling your findings into an externally directed end product: a key message that includes a course of action for your organization, ream, or client.
Your interpretation of the data leads to a story, that is, what you think the data means. You select those portions of the story that you believe your audience needs to know in order to understand your conclusion, along with the supporting evidence, and you put them together into your end product as in your presentation.
To succeed here you need to see through your client’s, executive’s or audience’s lenses and speak their language.
The key to successful presentations and getting buy-in (in order for your audience to accept your recommendations) is prewiring.
The reason behind this is because to get the buy-in you need to bridge the information and trust gaps between you and your audience. The information gap exists because you know more about your findings than your audience does. Depending on the relationship between you and your audience, the trust gap (if it exists) could take any of several forms. Your audience may think that you are too inexperienced to comment on their business, or they may mistrust you because you are an outsider, are overeducated, or not educated enough.
In its essence, prewiring means taking your audience through your findings before you give your presentation. This allows for people to trust you, ask questions you may not have thought about to avoid surprises, and then during the presentation say yes and support you among others who may be more skeptical.
Prewire everything. A good business presentation should contain no shocking revelations for the audience. Walk the relevant decision-makers in your organization through your findings before you gather them together for a dog and pony show. At a minimum, you should send out your recommendations via email to request comments from key decision-makers before the presentation if you can’t meet with those people face-to-face.
The earlier you can start the prewiring process, the better. By identifying and getting input from the relevant players early on, you allow them to put their own mark on your solution, which will make them more comfortable with it and give them a stake in the outcome.
When you begin your presentation in front of your desired audience, make sure you start with the conclusion.
Having your conclusions or recommendations upfront is sometimes known as inductive reasoning. Simply put, inductive reasoning takes the form, “We believe X because of reasons A, B, and C.” This contrasts with deductive reasoning, which can run along the lines of, “A is true, B is true, and C is true; therefore, we believe X.” Even in this simplest and most abstract example, it is obvious that inductive reasoning gets to the point a lot more quickly, takes less time to read, and packs a lot more punch.
As an additional advantage, starting with your conclusions allows you to control how far you go into detail in your presentation.
You need to explain this clearly within just 30 seconds. Almost like an elevator pitch. If you can pass this “elevator test,” then you understand what you’re doing well enough to sell your solution.
A successful presentation bridges the gap between you — the presenter — and your audience. It lets them know what you know.
It also keeps it simple for them which is why it’s important to stick to a key rule if you are using a deck: one message per slide or chart. No more. The more complex a chart/slide becomes, the less effective it is at conveying information. The meaning should be immediately obvious to the reader, so use whatever tools you need to bring it out.
If you broke out your initial hypothesis into a MECE set of issues and sub-issues (and suitably modified them according to the results of your analysis), then you have a ready-made outline for your presentation that will support your conclusion.
Remember that you have two ears and only one mouth. It’s not just what you say, it’s how you say it. Overcommunication is better than under-communication which is why prewiring as mentioned above is so important.
Finally, if you are proposing a certain solution in which you will be involved in the execution, make sure you don’t overpromise because you’re bound to under-deliver. Instead, balance the demands for the solution with your capabilities and those of your team. If more work is necessary, you can always start a second project once the first is done.
When you begin executing on the solution, aim to hit singles.
This is a metaphor from baseball. You can’t do everything, so don’t try. Just do what you’re supposed to do, and get it right. It’s impossible to do everything yourself all the time. If you do manage that feat once, you raise unrealistic expectations from those around you. Then, when you fail to meet those expectations, you’ll have difficulty regaining your credibility.
Getting on base consistently is much better than trying to hit a home run and striking out nine times out of ten.
Do few things well rather than a ton with mediocre execution or results. Stick to targeted focus rather than perfection and drilling into every little piece.
Quality over quantity. And when there’s a lot of work to be done, delegate around your limitations. Know them for what they are and respect them.
Don’t forget that work is like a gas: it expands to fill the time available.
As in the previous point, share the load by delegating and also perform sanity checks on the way to allow you to take a step back and look at the big picture.
You will also have to get others to respect your time. The better you are at your job or the higher up you go in your organization, the more everyone wants a piece of you. There’s an old saying, “Stress is the feeling you get when your gut says, ‘No,’ and your mouth says, ‘Yes, I’d be glad to.’” You have to train your mouth to say, “No.”
Once you make a commitment — “I won’t work on weekends” or “I’ll cook dinner three nights a week” — stick to it, barring life-and-death emergencies. If you seem to be having life-and-death emergencies every week (and you’re not dealing with matters of real life and death, as in a trauma ward), take a hard look at your priorities.
Share Product Mindset's Newsletter
![](http://sektorel.online/777/templates/cheerup/res/banner1.gif)
Additional Reads :
1/36 - Product Discovery Process
2/36 - Pre-discovery Phase
3/36 - PD Preparation & Frameworks
4/36 - Double Diamond Discovery
5/36 - User-Centered Design
6/36 - Managing Product Ideas for Product Discovery
7/36 - Crafting a Problem Statement
8/36 - Product Logic Model : Input, Output, Outcome
9/36 - Understanding Problem Space
10/36 - User Research 101: Navigating the Discovery Process
11/36 - User Interviews Deep Drive
12/36 - User interview analysis – turning raw data into insights effectively
13/36 : Lean Prioritization Framework
14/36 : Understanding Solution Space
15/36 : Lean Experiment & Case Study
16/36 : 📈 Discover the Power of Product Metrics
17/36 : 🚀 Minimum Viable Product Playbook
18/36 :Product Discovery - Risks & Mitigations
19/36 : 🧠 Product Discovery - Inception
20/36 : 🧠 Outcome based Product roadmaps?
21/36 : DEEP Product Backlog
22/36 : BDD, Theme, Epic, Feature & Story
23/36 : 📚 A Guide to Effective User Stories and Story Mapping and Pointing
24/36 : 🔁 Continuous discovery & Product market matrix
Product Management Reading List For 2023
![structured problem solving mckinsey structured problem solving mckinsey](https://substackcdn.com/image/fetch/w_64,h_64,c_fill,f_auto,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack.com%2Fimg%2Favatars%2Flogged-out.png)
Ready for more?
- Business & Money
- Biography & History
![structured problem solving mckinsey](https://m.media-amazon.com/images/G/01/Audible/Homestead/logo/audiblelogo._CB482869198_.png)
Sorry, there was a problem.
![structured problem solving mckinsey Kindle app logo image](https://m.media-amazon.com/images/G/01/kindle/app/kindle-app-logo._CB668847749_.png)
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required .
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
![structured problem solving mckinsey QR code to download the Kindle App](https://m.media-amazon.com/images/G/01/kindle/app/QR-store-link-kindle-app._CB626291935_.png)
Image Unavailable
![structured problem solving mckinsey The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm](https://m.media-amazon.com/images/I/51Ltb0leJLL._SY445_SX342_.jpg)
- To view this video download Flash Player
Follow the authors
![structured problem solving mckinsey Ethan M. Rasiel](https://m.media-amazon.com/images/I/01Kv-W2ysOL._SY600_.png)
The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm Hardcover – October 17, 2001
The groundbreaking follow-up to the international bestsellera hands-on guide to putting McKinsey techniques to work in your organization
McKinsey & Company is the most respected and most secretive consulting firm in the world, and business readers just can't seem to get enough of all things McKinsey. Now, hot on the heels of his acclaimed international bestseller The McKinsey Way , Ethan Rasiel brings readers a powerful new guide to putting McKinsey concepts and skills into action The McKinsey Mind . While the first book used case studies and anecdotes from former and current McKinseyites to describe how "the firm" solves the thorniest business problems of their A-list clients, The McKinsey Mind goes a giant step further. It explains, step-by-step, how to use McKinsey tools, techniques and strategies to solve an array of core business problems and to make any business venture more successful.
Designed to work as a stand-alone guide or together with The McKinsey Way , The McKinsey Mind follows the same critically acclaimed style and format as its predecessor. In this book authors Rasiel and Friga expand upon the lessons found in The McKinsey Way with real-world examples, parables, and easy-to-do exercises designed to get readers up and running.
- Print length 272 pages
- Language English
- Publisher McGraw Hill
- Publication date October 17, 2001
- Dimensions 6.3 x 1.1 x 9.3 inches
- ISBN-10 0071374299
- ISBN-13 978-0071374293
- See all details
Editorial Reviews
From the back cover.
The First Step-by-Step Manual for Achieving McKinsey-Style Solutions--and Success
International bestseller The McKinsey Way provided a through-the-keyhole look at McKinsey & Co., history's most prestigious consulting firm. Now, the follow-up implementation manual, The McKinsey Mind , reveals the hands-on secrets behind the powerhouse firm's success--and discusses how executives from any field or industry can use those tactics to be more proactive and successful in their day-to-day decision-making.
Structured around interviews and frontline anecdotes from former McKinsey consultants--as well as the authors, themselves McKinsey alumni-- The McKinsey Mind explores how McKinsey tools and techniques can be applied to virtually any business problem in any setting. Immensely valuable in today's crisis-a-minute workplace, it discusses:
- Techniques for framing problems and designing analyses
- Methods for interpreting results and presenting solutions
The ability to think in a rigorous, structured manner--a McKinsey manner--is not a birthright. It can, however, be a learned behavior. Let The McKinsey Mind show you how to approach and solve problems with the skill of a McKinsey consultant and obtain the positive results that have been delivered to McKinsey clients for over a century.
McKinsey & Co. is renowned throughout the world for its ability to arrive at sharp, insightful analyses of its clients' situations then provide solutions that are as ingenious as they are effective. McKinsey succeeds almost as well as shielding its revolutionary methods from competitors' scrutiny.
Now, The McKinsey Mind pulls back the curtain to reveal the ways in which McKinsey consultants consistently deliver their magic and how those methods can be used to achieve exceptional results in companies from 10 employees to 10,000. Packed with insights and brainstorming exercises for establishing the McKinsey mind-set, this book is an in-depth guidebook for applying McKinsey methods in any industry and organizational environment.
Taking a step-by-step approach, The McKinsey Mind looks at the McKinsey mystique from every angle. Owners, executives, consultants, and team leaders can look to this comprehensive treatment for ways to:
- Follow McKinsey's MECE (mutually exclusive, collectively exhaustive) line of attack
- Frame business problems to make them susceptible to rigorous fact-based analysis
- Use the same fact-based analysis--in conjunction with gut instinct--to make strategic decisions
- Conduct meaningful interviews and effectively summarize the content of those interviews
- Analyze the data to find out the "so what"
- Clearly communicate fact-based solutions to all pertinent decision makers
Because organizational problems rarely exist in a vacuum, The McKinsey Mind discusses these approaches and more to help you arrive at usable and sensible solutions. It goes straight to the source--former McKinsey consultants now in leadership positions in organizations throughout the world--to give you today's only implementation-based, solution-driven look at the celebrated McKinsey problem-solving method.
" The McKinsey Mind provides a fascinating peek at the tools, practices, and philosophies that have helped this much-admired firm develop generations of bright young MBAs into trusted corporate advisors. But the book's practical, down-to-earth advice is not just for consultants. The disciplined way in which McKinsey consultants frame issues, analyze problems, and present solutions offers valuable lessons for any practicing or aspiring manager." --Christopher A. Bartlett, Daewoo Professor of Business Administration, Harvard Business School
"McKinsey and Co. rescues the biggest companies from disaster by addressing every problem with its own mixture of logic-driven, hypothesis-tested analysis. The McKinsey Mind helps everyone learn how to think with the same discipline and devotion to creating business success. According to the maxim, giving a man a fish may feed him for a day, but teaching him to fish will feed him for a lifetime. Paying McKinsey to solve your problem may help you for a day, but learning how they do it should help you for a lifetime." --Peter Wayner, Author of Free For All: How Linux and the Free Software Movement Undercut The High-Tech Titans
"The McKinsey Mind unlocks the techniques of the world's preeminent consulting firm and presents them in a format that is easy to understand and even easier to implement." --Dan Nagy, Associate Dean, The Fuqua School of Business, Duke University
About the Author
Ethan M. Rasiel was a consultant in McKinsey & Co.'s New York office. His clients included major companies in finance, telecommunications, computing, and consumer goods sectors. Prior to joining McKinsey, Rasiel, who earned an MBA from the Wharton School at the University of Pennsylvania, was an equity fund manager at Mercury Asset Management in London, as well as an investment banker.
Paul N. Friga worked for McKinsey & Co. in the Pittsburgh office after receiving his MBA from the Kenan-Flagler Business School at the University of North Carolina. He has conducted consulting projects relating to international expansion, acquisition and strategic planning, education, water, and other industries. He has also consulted for Price Waterhouse. He is currently pursuing his Ph.D. in Strategy at Kenan-Flagler and is Acting Director of the North Carolina Knowledge Management Center.
Product details
- Publisher : McGraw Hill; First Edition (October 17, 2001)
- Language : English
- Hardcover : 272 pages
- ISBN-10 : 0071374299
- ISBN-13 : 978-0071374293
- Item Weight : 2.31 pounds
- Dimensions : 6.3 x 1.1 x 9.3 inches
- #111 in Consulting
- #681 in Decision-Making & Problem Solving
- #2,345 in Business Management (Books)
Videos for this product
![structured problem solving mckinsey Video Widget Card](https://m.media-amazon.com/images/I/A1GeQRnf2yL._CR2,0,1276,720_SR684,386_.png)
Click to play video
![structured problem solving mckinsey Video Widget Video Title Section](https://m.media-amazon.com/images/I/A1GeQRnf2yL._CR2,0,1276,720_SR342,193_CR0,126,342,67_.png)
The Biggest Lesson from this Book
Omar M Khateeb
About the authors
Ethan m. rasiel.
Discover more of the author’s books, see similar authors, read author blogs and more
Paul N. Friga
Customer reviews.
- 5 star 4 star 3 star 2 star 1 star 5 star 56% 24% 15% 3% 3% 56%
- 5 star 4 star 3 star 2 star 1 star 4 star 56% 24% 15% 3% 3% 24%
- 5 star 4 star 3 star 2 star 1 star 3 star 56% 24% 15% 3% 3% 15%
- 5 star 4 star 3 star 2 star 1 star 2 star 56% 24% 15% 3% 3% 3%
- 5 star 4 star 3 star 2 star 1 star 1 star 56% 24% 15% 3% 3% 3%
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Customers say
Customers find the book's content very practical, easy to learn, and supportive illustrations. They also describe it as a great book with step-by-step instructions. Readers also appreciate the writing style as well-written, simple, and actionable.
AI-generated from the text of customer reviews
Customers find the book's content very practical for consultants, leaders, and managers. They also appreciate the good illustration of problem-solving tools and the complete guide for newbies in the consulting business. Readers also mention that the book is simple, actionable, and easy to follow.
"...not go into strategy consulting, but this book has helped me sharpen my consultative skills ." Read more
"...I believe it provides a pretty good overview of how business consultants (mostly strategy) approach problems analytically...." Read more
" Very useful " Read more
"...The good thing is these are essential field manuals , so you can read and use them over and over in your practice to become a real professional and..." Read more
Customers find the book useful.
" Awesome book !Must have for anyone planning on working in either internal/external consulting or strategy in any company...." Read more
"This is a good business book ...." Read more
"It is a nice book , however, I enjoy reading Victor Cheng's blog and emails much better...." Read more
"It is a good book but there are no updated versions. Nevertheless, it is worth reading it." Read more
Customers find the writing style well written, simple, and actionable. They also appreciate the quality and detail of the product.
"A very well written book with an easy to follow flow and good illustration of problem-solving tools and how to use them within one's business or for..." Read more
"very happy with the product and the quality and detail of it . was also lucket to find it such a good price!! very happy and recommend it highly!!" Read more
"It's a quick, easy to read , yet complete guide for newbies in the consulting business.Great book!! I strongly recommend buying it." Read more
" Well written , simple, actionable...." Read more
- Sort reviews by Top reviews Most recent Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. please try again later..
![structured problem solving mckinsey structured problem solving mckinsey](https://images-na.ssl-images-amazon.com/images/S/amazon-avatars-global/default._CR0,0,1024,1024_SX48_.png)
Top reviews from other countries
![structured problem solving mckinsey structured problem solving mckinsey](https://images-eu.ssl-images-amazon.com/images/S/amazon-avatars-global/default._CR0,0,1024,1024_SX48_.png)
- About Amazon
- Investor Relations
- Amazon Devices
- Amazon Science
- Sell products on Amazon
- Sell on Amazon Business
- Sell apps on Amazon
- Become an Affiliate
- Advertise Your Products
- Self-Publish with Us
- Host an Amazon Hub
- › See More Make Money with Us
- Amazon Business Card
- Shop with Points
- Reload Your Balance
- Amazon Currency Converter
- Amazon and COVID-19
- Your Account
- Your Orders
- Shipping Rates & Policies
- Returns & Replacements
- Manage Your Content and Devices
- Conditions of Use
- Privacy Notice
- Consumer Health Data Privacy Disclosure
- Your Ads Privacy Choices
"The McKinsey Way" Book: A Comprehensive Summary
The McKinsey Way is a book by Ethan M. Rasiel , published in 1999, about what McKinsey&Company does, how McKinsey organizes and what working at McKinsey is like.
20 years after publication, the book still holds significant value, offering timeless insights into the world’s most prestigious management consulting firm: McKinsey&Company. In this article, we’ll provide a detailed summary of all the lessons and insights from The McKinsey way . We’ll re-organize the content and occasionally insert supporting insights to make it more friendly to the reader.
The McKinsey Way has 5 Parts (Sections) with 180 pages:
- Part 1: The Problem Solving Methodology of McKinsey
Part 2: Logistics of how a McKinsey project works
Part 3: insights into the actual works of consultants, part 4: how to excel as a junior consultant, part 5: exit opportunities and life after mckinsey.
Table of Contents
Part 1: The McKinsey problem-solving methodology
The McKinsey problem-solving process can be summarized in the 5 steps: define the problems, find the root cause, use “hypothesis-driven” process, analyze with “issue tree” and propose solutions.
1. Define the problem: Every consulting project revolves around a “problem”. But the “problem” is NOT always the problem!
One symptom may have different causes and we as doctors should never rely on the patient to diagnose.
So, always dig deeper. Get facts. Asks questions. Poke around. Challenge the client… until you find the real problem.
2. Find the root cause: Don’t jump straight to the solution, because you might just be fixing the symptoms. The problem will come back if the root cause is not properly dealt with.
3. Use “hypothesis-driven” process: Make educated guesses of possible root-cause A B C and test with data (a.k.a: facts). We’ll sometimes call this a fact-based process.
4. Break down and structure the analysis with the “ issue tree ” framework: A “hypothesis-driven” process may take forever as there are millions of possible root-causes. We need to test hypotheses from the top to the bottom of the issue tree – a top-down fashion. These issue trees need to be MECE.
5. Propose solutions: When the root causes are identified, consultants propose solutions targeting them directly.
A few notes when using this methodology
No.1: Don’t force the facts to say what you want.
When you propose or work extensively with a running hypothesis , it’s easy to get emotionally attached and turn the problem-solving process into a proving exercise. So keep an open mind and listen to what the data have to say.
No.2: Let the hypothesis come to you naturally.
You will not be able to form an initial hypothesis every time. The clients may not even know their problems. The scope of the project is often large and vague. So, dive in, gather facts, conduct analyses, and the hypotheses will show themselves.
No.3: Don’t reinvent the wheel.
Business problems often resemble each other more than they differ. With suitable techniques, you can apply what you and the firm learned from other projects. After all, one of the values consulting firms bring is to provide the “best practice” – what the top players in the game are doing
No.4: Make sure your solution fits your client.
The most brilliant solution is useless without proper implementation. So know your client’s weaknesses, strengths, and capabilities and tailor your solutions accordingly.
No.5: Be mindful of politics.
There are always politics in projects. Many times, McKinsey gets involved in fights between corporate factions. This creates friction that prevents you from doing your job (late data; rejected interviews, etc.).
So think about how your solutions affect the players in an organization and always build a consensus along the way. If consensus requires you to change your solution, try to compromise. It’s no good devising the ideal solution if the client refuses to accept it.
It’s highly recommended that you refer to the following video for a general view on how McKinsey organizes and a better understanding of the insights from this part.
There is a whole system behind how McKinsey solve a business problem. In this part of The McKinsey Way, Ethan Rasiel describes how the company sells their projects, builds a team and manages its hierarchy.
Selling a study/project
McKinsey typically does not sell. The firm does marketing through a constant stream of books, articles, and scholarly journals like the McKinsey Quarterly, etc. The Firm also invites organize press releases and generates quite some coverage by journalists.
These publications help McKinsey Partners build and nurture a vast network of informal contacts with potential clients. And when a problem arises, the client knows who to contact.
Assembling a team
Almost all projects need a full-time team of consultants. Typically, the process goes like this:
- The ED (a.k.a: Project Owner) signs a contract with the client
- The ED hires an EM from within the McKinsey network, from any offices (a.k.a: Project CEO)
- The EM then hires a group of staff, consisting of BAs (a.k.a: Business Analyst) and Associates.
It’s solely the EM’s responsibility to keep the team happy and functional. McKinsey projects have a few common practices to do so:
- A monthly “team-bonding”.
- A “team temperature” (a.k.a: morale) weekly survey.
The hierarchy
The chain of command in McKinsey is very clear and strict. So is the responsibility funnel. In the ED’s eyes, the EM is responsible for everything in the project. In the EM eyes, the BA is responsible for everything within the assigned workstream. Even when a BA messes things up, to the ED, it’s not the BA’s fault, but the EM.
To provide the best solution for the clients, consultants need tons of skills in preparing presentations; conducting researchs and interviews; presenting the final products in a simple structure; communicating with clients; and brainstorming.
Making presentations, a.k.a: the final deliverable documents
Most consultants spend a big portion of their time making presentations (often in PowerPoint). Utilize the support team! Keep it structured, from top to bottom, from end to end.
Note that there are diminishing marginal returns to your effort, meaning that the last miles toward perfection are always much harder than the beginning. So, resist the temptation to tweak your presentation at the last minute. Try to assess its gains vs those of a good night’s sleep for you and the supporting cast.
Visualizing data with charts and exhibits
We subconsciously admire the people who talk in sophisticated language, so we make complex charts. However, simple and easy-to-follow charts go a long way in consulting. Charts are just a means of getting your messages across, not a Ph.D. project.
Also, don’t forget to:
- Write clear chart titles
- List out units of measurement in all axes
- Mark legends and side notes
- Provide data sources
Managing internal communications
- Over-communication is always better. Keep that information flowing. Make sure that your team is up to date with at least the broad outlines of your workstream and your boss up to date with your team’s progress. There are many channels for this: email, voicemail, messaging, small talks during cigarette breaks, meetings, etc.
- Keep your communication brief, yet comprehensive and structured.
- Look over your shoulder – always. You never know who is listening. Remember that your client’s confidentiality is a must.
![structured problem solving mckinsey structured problem solving mckinsey](https://image.mconsultingprep.com/fit-in/1000x1000/case_thumb/1669045732338_new_team_members_rafiki.png)
Working with clients
This is a big one as the true hierarchy at McKinsey is “Client -> Firm -> and then You”. The client is your biggest boss.
There are many tips on client management, but the general principle is to bring the client to your side. You never win by opposing the client. Remind them about mutual benefits. Do it everyday!
Some of the client members can be “liabilities”. There are 2 types of them:
- the merely “useless”.
- the hostile ones.
With both types, the number 1 option is to subtly trade them out of your realm. When that is not possible, the next best option is to play ignorant. Leak out information only with the right “secret audience”.
No matter what, engage the client members in the process. The more they feel everybody is on the same boat, the more they would support you.
You should also get buy-ins throughout the organization along the process. Every important party has to agree with you. Ideally, the final document has already been discussed many times through many rounds with the client before the official presentation.
Doing research
Don’t reinvent the wheel! Whatever you are doing, chances are that someone, somewhere has done something similar. Building upon someone’s work is the best way to save time and energy while achieving the highest standard.
Besides, here are some research tips:
- Start with the annual report. All public companies have them available on their website.
- Look for abnormal patterns (things that are especially good or bad). That’s where all the insights lie.
- Last but not least, look for the best practice. Find out what the best performers in the field are doing and learn from them.
Conducting interviews
This is one of the most effective ways to gather qualitative facts during a project. You will find yourself interviewing multiple industry and function experts as well as key client leaders.
Here are a few tips:
- Be prepared. Know exactly what you want to get out of it. Know as much as you can about the interviewee. Writing an interview brief for yourself is not a bad idea.
- If possible, have the interviewee’s boss set up the meeting.
- Start with some general and open-ended questions then move on to specific ones. Let the content flow naturally.
- Sometimes, it’s useful to use the indirect style. Take time to make the interviewee comfortable with you and the interview process.
- Include some questions you know the answer to. This gives insights into the interviewee’s style, knowledge, and honesty.
- Don’t ask too much. Focus on what you really need (what you prioritize in the interview brief).
- Listen and let the interviewee know you are doing so.
- Paraphrase what you hear in your own words. Confirm whether you understand correctly. This also gives chances for the interviewee to add or amplify important points.
- Near the end, use this last trick to flush out any possible missing insights: “Is there anything else you would like to tell or any question I forgot to ask…?”.
- Adopt the Columbo tactic. Wait until a day or two passes, then drop by the interviewee’s office. “I was just passing by and remembered a question I forgot to ask”. This is a less threatening way to keep the conversation going.
- Lastly, always write a thank-you note. A short and sincerely one always does the work.
Brainstorming at McKinsey
In McKinsey, we often use the word “Problem-Solving” interchangeably with brainstorming sessions. It’s a very topic-focus meeting within the McKinsey team, consisting of the consultant in-charge, the EM, and sometimes even the ED and experts.
Before the session, prepare in advance as much supporting data as possible. It will come handy in the process.Inside the White room: Start with tabula rasa — a clean slate. When you get your team into the room, leave your preconceptions at the door. Bring in only the facts, and find new ways of looking at them.
Management consulting is an interesting yet challenging job. To survive and thrive at McKinsey, here are some advices for you:
Tip 1: Find your own mentor
At McKinsey, every consultant is officially assigned a mentor, who may not be in the same office. How much you benefit from the official mentor is pretty much a matter of luck. If you want great guidance, you have to go out and get your own. Get a few too, don’t stick to just one.
Tip 2: Survive the road
Business travel can be exhausting and difficult, here are some note you can take to deal with it:
- Look at business travel as an adventure.
- Do proper planning. These simple logistics can make a big difference
- Treat everyone with tremendous respect
Tip 3: Have a list of items to bring when traveling
Here is the list:
- Clothing: extra shirts or blouses, spare ties, spare shoes, casual clothes, cashmere sweaters
- Tools: writing pad, copy of whatever you send to the client, calculator
- Personal care Items
- Things to keep you organized and in touch
Tip 4: Treat your assistant well
Having a good assistant is a lifeline. Treat them well. Be clear about what you want. Give them room to grow. Take time to train them well. Answering their questions and showing them the ropes.
Tip 5: Have boundaries to keep your life balance
Since you have a large amount of work to cover as a consultant, there is almost no work-life balance. However, if you want a life, lay down some rules. For example:
- Make one day a week to be completely free of work, both physically and mentally. Tell your boss about it! He/she will respect it. And so should you.
- Don’t take work home. When you are home, you are home!
- Plan long ahead, especially when you travel.
![structured problem solving mckinsey structured problem solving mckinsey](https://image.mconsultingprep.com/fit-in/1000x1000/case_thumb/1669045907330_work_life_balance_rafiki.png)
Tip 6: The 80 / 20 Rule
80% of the wealth is owned by just 20% of the population. 80% of the output can be produced by 20% of the effort. 20% of the problems can cause 80% of the trouble.
So if you wanna save time and effort. Always try to find those 20% and act upon them!
Tip 7: Don’t try to analyze everything
If you don’t take shortcuts, there is simply too much to do. Be selective. Find the key drivers. Focus on the core problem, then apply analysis. This helps avoid going down blind alleys and boiling the ocean.
Tip 8: The Elevator Test
Concise communication is crucial in consulting. Anytime the EM asks you for your workstream status, you have to be able to give him a 30 seconds summary. Short yet insightful. This skill takes practice. Try doing it every day in various contexts!
Tip 9: Pluck the Low-Hanging Fruit
Solving only part of the problem can still mean increased profits. Those little wins help you and your customers. Try to see such opportunities and grab them first.
Tip 10: Hit singles
Get your job and only your job done, don’t try to do the work of the whole team.
It’s impossible to do everything yourself all the time. Even if you manage to pull it off once, you raise unrealistic expectations and once you fail, it is difficult to get back credibility.
Tip 11: Look at the big picture
When you are feeling swamped, take a step back, figure out what you are trying to achieve, and then look at what you are doing. “Does this really matter?”
Probably not! All of these troubles will go away!
![structured problem solving mckinsey structured problem solving mckinsey](https://image.mconsultingprep.com/fit-in/1000x1000/case_thumb/1669046096226_vision_statement_pana.png)
Tip 12: Just say “I don’t know”
The firm pounds the concept of professional integrity: Honesty. If you don’t know something, just say “I DON’T KNOW” in an empowering fashion. Admitting that is a lot less costly than bluffing.
“Leaving McKinsey is never a question of whether—it’s a question of when”
There are not many people who stay with McKinsey for their whole career life. In the last part of The McKinsey Way , Ethan Rasiel and other ex-McKinsey consultants share their valuable lessons and memories from working at the company.
- “Structure, structure, structure. MECE, MECE, MECE. Hypothesis-driven, Hypothesis-driven, Hypothesis-driven.” – Former associate in Dusseldorf and San Francisco offices
- “The quality of the people. In the corporate world, the average-caliber employee is far below McKinsey’s least intelligent.” – Wesley Sand
- “What stays with me is the rigorous standard of information and analysis, the proving and double-proving of every recommendation, combined with the high standard of communication both to clients and within the Firm.” – Former associate in the Boston and New York offices
- “When faced with an amorphous situation, apply structure to it.” – Kristin Asleson, New York office, 1990-93; now working in Silicon Valley
- “Execution and implementation are the key. A blue book is just a blue book, unless you do something with it. Getting things done is the most important thing.” – Former EM in the New York office
Scoring in the McKinsey PSG/Digital Assessment
The scoring mechanism in the McKinsey Digital Assessment
Related product
![structured problem solving mckinsey Thumbnail of McKinsey Comprehensive Package](https://image.mconsultingprep.com/fit-in/700x0/filters:blur(1)/filters:quality(75)//case_thumb/1669802837683_mc_kinsey_comprehensive_bundle.png)
McKinsey Comprehensive Package
Unlock all materials helping you land the next job in McKinsey!
Among MBB firms, people tend to say McKinsey is slightly better than the other two in three factors: prestige, people, practices, and offices
At McKinsey, the salary for entry-level consultants ranges from $90,000 to $110,000/year, while the figure for experienced Associates can go up to $233,000
McKinsey hiring process including 3 phases: resume screening, PST test, and case interview. Each candidate will have to undergo 4-6 interviews during 4-8 weeks
How to master the seven-step problem-solving process The McKinsey Podcast
Structured problem solving can help address complex business challenges.
- Episode Website
- More Episodes
- 2024 McKinsey & Company
More by McKinsey
![](http://sektorel.online/777/templates/cheerup/res/banner1.gif)
IMAGES
VIDEO
COMMENTS
In this episode of the McKinsey Podcast, Simon London speaks with Charles Conn, CEO of venture-capital firm Oxford Sciences Innovation, and McKinsey senior partner Hugo Sarrazin about the complexities of different problem-solving strategies.. Podcast transcript. Simon London: Hello, and welcome to this episode of the McKinsey Podcast, with me, Simon London.
The McKinsey problem solving process is a series of mindset shifts and structured approaches to thinking about and solving challenging problems. It is a useful approach for anyone working in the knowledge and information economy and needs to communicate ideas to other people.
McKinsey research shows that organizations that have top-quartile problem-solving capabilities earn 3.5 times higher total shareholder returns than those in the bottom quartile, according to a podcast episode featuring McKinsey's Chris Bradley and McKinsey director emeritus Rob McLean. Dive into these insights for some structured methods that ...
The McKinsey guide to problem solving. Become a better problem solver with insights and advice from leaders around the world on topics including developing a problem-solving mindset, solving problems in uncertain times, problem solving with AI, and much more.
The characteristic "McKinsey method" of problem solving is a structured, inductive approach that can be used to solve any problem. Using this standardized process saves us from reinventing the problem-solving wheel, and allows for greater focus on distinctiveness in the solution.
How to master the seven-step problem-solving process. The McKinsey Podcast. Management. Structured problem solving can help address complex business challenges. Episode Website. More Episodes. 2024 McKinsey & Company. Structured problem solving can help address complex business challenges.
McKinsey's structured and rigorous approach to problem-solving has helped countless organizations achieve significant improvements in performance and profitability. By providing data-driven insights and practical recommendations, McKinsey has enabled clients to address complex challenges and capitalize on new opportunities.
In our 2013 classic from the Quarterly, senior partner Olivier Leclerc highlights the value of taking a number of different approaches simultaneously to solve difficult problems. Read on to discover the five flexons, or problem-solving languages, that can be applied to the same problem to generate richer insights and more innovative solutions.
Listen to this episode from The McKinsey Podcast on Spotify. Read more > Listen to the podcast (duration: 24:30) > Structured problem solving can be used to address ...
The McKinsey problem-solving process begins with the use of structured frameworks to generate fact-based hypotheses followed by data gathering and analysis to prove or disprove the hypotheses. ... Well-structured Problems Some problems which are simple and well-defined are called well-structured problems and include a set number of possible ...
Structured around interviews and frontline anecdotes from former McKinsey consultants--as well as the authors, ... solution-driven look at the celebrated McKinsey problem-solving method. " The McKinsey Mind provides a fascinating peek at the tools, practices, and philosophies that have helped this much-admired firm develop generations of bright ...
The McKinsey problem-solving process can be summarized in the 5 steps: define the problems, find the root cause, use "hypothesis-driven" process, analyze with "issue tree" and propose solutions. ... Keep it structured, from top to bottom, from end to end. Note that there are diminishing marginal returns to your effort, meaning that the ...
Drawing on consulting practitioner approaches, this article presents a translation of the McKinsey approach as a six-stage structured problem-solving methodology that can be used to guide students on how to develop solutions in a systematic, logical, and evidence-based way.
That's what we've found after decades of problem solving with leaders across business, nonprofit, and policy sectors. These leaders learn to adopt a particularly open and curious mindset, and adhere to a systematic process for cracking even the most inscrutable problems. They're terrific problem solvers under any conditions.
How to master the seven-step problem-solving process. The McKinsey Podcast. Management. Structured problem solving can help address complex business challenges. Episode Website. More Episodes. 2024 McKinsey & Company. Structured problem solving can help address complex business challenges.
ships among entities. These problems are not simple, to be sure.3 But they are well-defined and structured—a fundamental requirement of problem solving. Evolutionary flexon Evolutionary algorithms have won games of chess and solved huge optimization problems that overwhelm most computational resources.
Putting flexons to work. We routinely use these five problem-solving lenses in workshops with executive teams and colleagues to analyze particularly ambiguous and complex challenges. Participants need only a basic familiarity with the different approaches to reframe problems and generate more innovative solutions.
A program that transforms the leadership and management capabilities of mid-level professionals and high-performing talent. The McKinsey Management Program equips your teams with the skills and mindsets to achieve immediate and lasting organizational impact. NT PROGRAM (MMP) for mid-level professionalsA 7 month digital foundational management ...