HE WORLD ECONOMIC FORUM’S lists complex problem-solving as the number one skill for jobs in 2020. Organizations are looking for people that can define problems and form solid creative responses. Like leaders themselves, good problem solvers are made, not born. Yet these skills are rarely taught. That’s where comes in. McKinsey alums Charles Conn and Rob McLean teach us how to be bulletproof problem solvers using a simple 7-steps approach. The approach has its foundation in the hypothesis-driven structure of the scientific method. This process is not just applicable to business but is useful in finding solutions for personal problems as well. In the book they apply the process to individual problems such as, “Should I put solar panels on my roof?,” “What career should I choose?,” and “Is where I live affecting my health?” Business examples range from “Should my startup raise its prices?” and “Should we go to court?” to “Can obesity be reduced?” This process can be applied to nearly every problem is responds well to the systematic problem-solving method that this approach provides.
While this is presented in a linear way, the authors make a great point that you learn more about the problem as you go. You shouldn’t be so eager to get to the end that you don’t go back and refine previous steps. “While the process has a beginning and an end, we encourage you to think of problem solving as an iterative process rather than a linear one. At each stage we improve our understanding of the problem and use those greater insights to refine our earlier answers.”
Like us on and for additional leadership and personal development ideas.
Posted by Michael McKinney at 04:30 AM | ™ (1) wrote: Thanks for another great post. Thes... [ ] (1) wrote: Bonus Insight from Talent Wins: “... [ ] (1) Blake Argo wrote: I have found that my success in the... [ ] (1) wrote: This is an exceptional article outl... [ ] (1) wrote: Thanks for the reminder of principl... [ ] --> |
delivered to your inbox. | |||
© 2024 LeadershipNow™ |
Think about all the harebrained ideas and strategies that big companies pursue. Why do they make such obviously silly decisions? They don’t have a disciplined process for analyzing problems and finding good solutions.
I will delve into the famed McKinsey 7-step problem-solving process today.
Legendary management consulting firm McKinsey & Company takes problem-solving extremely seriously. They have developed and refined a structured 7-step methodology that all McKinsey consultants use to methodically work through challenges. As former McKinsey partner Charles Conn states,
“By following steps, we can more clearly understand what problem it is we’re solving, what are the components of the problem, which components are most important to pay attention to, which analytic techniques to apply, and how to synthesize learnings into a compelling solution story.”
This methodology is used by top consultants to methodically work through even the trickiest issues. While no framework is perfect, this one at least forces you to slow down and think things through deliberately.
The McKinsey 7-step problem-solving process is a methodology developed by the prestigious consulting firm McKinsey & Company. It provides a structured way to think through difficult situations and develop solutions.
The 7 steps are:
By rigorously working through each phase, you avoid missing key details or jumping to flawed conclusions. It results in more thorough and effective problem-solving.
Let’s dive into each of the 7 steps in more detail:
You can’t solve a problem until you truly understand what the heck it is. This deceptively simple first step is critical.
Ask: What is the actual problem we’re trying to solve here? What are the symptoms and effects we’re seeing? What are the goals and objectives? Get crystal clear upfront.
Many problem solving efforts fail right out of the gate because there was never precise agreement on the problem itself. Properly defining the problem ensures everyone is aligned and working towards the same endpoint.
Once you know the core problem, you need to break it down into its components. Diagram it visually using tools like issue trees and prioritization matrices.
The goal is to uncover root causes rather than just treating symptoms. Look for relationships between different factors. Structuring makes the inherent complexities more understandable.
With the problem neatly structured, identify the 2-3 main root causes to prioritize. These are the areas where focusing your efforts will have the biggest impact.
Don’t spread yourself too thin by trying to tackle everything at once. Find the highest leverage points that will drive a disproportionate amount of the solution.
Time to start formulating potential solutions! Based on your diagnosed root causes, generate hypotheses about what changes could alleviate or eliminate the core issues.
Don’t jump straight to recommending solutions yet, but form educated guesses about promising directions to explore further. Hypotheses help avoid getting anchored on any single remedy too early.
Validate your hypotheses through research, analysis, experiments, and testing. Gather data and feedback to determine which ideas have merit versus which should be discarded.
This step is all about objectively evaluating your potential solutions before committing major resources. Ruling out the bad ideas early saves immense time and effort.
Now that you’ve pressure-tested your options, you can put together a concrete plan of attack. This is where you finally propose your recommended solutions to the problem.
Based on your testing results, synthesize the optimal combination of remedies into an integrated solution roadmap. It should comprehensively address the core issues at their root.
The final step is determining how actually to implement your solutions. What resources are required? What roadblocks might you face? How will you track progress?
Build out a detailed plan for execution, including key milestones, owners, budgets, etc. Careful planning in this step paves the way for a smooth rollout.
The 7-step methodology is most valuable for complex, ambiguous problems with unclear paths. It provides a rigorous framework to impose order on messy situations.
For straightforward issues with obvious solutions, the process may be overkill. It works best when dealing with:
Whenever you’re facing a high-stakes quandary that impacts key outcomes, applying a proven process like this can mitigate risks of overlooking key factors or making rash decisions.
Like any framework, the McKinsey 7-step approach has its pros and cons:
Weaknesses:
No model is perfect, but the 7 steps at least provide guard rails for tackling thorny problem-solving challenges in a structured way.
One of the defining challenges of problem-solving in today’s ever-changing business landscape is the pervasive presence of uncertainty. Rapidly evolving markets, disruptive technologies, geopolitical instability, and a host of other factors continuously introduce new unknowns.
This makes it critical that any structured problem-solving methodology has mechanisms built in to explicitly identify, analyze, and manage uncertainties throughout the process. The McKinsey 7-step approach achieves this in multiple ways:
Step 1: Define Uncertainty in the Problem Context From the outset, a crucial part of problem definition is fleshing out the key sources and degrees of uncertainty surrounding the issue. What are the volatile factors that could significantly impact the situation? What future scenarios need to be accounted for? Explicitly calling out ambiguities upfront prevents them from being overlooked.
Step 2: Uncertainty Branches in the Structure When disaggregating the problem into structured issue trees, distinct branches can be created to separately examine different uncertain elements and scenarios. This allows for rigorous mapping of how these uncertainties could affect other components of the problem.
Step 3: Prioritize Based on Impact x Uncertainty The prioritization phase provides an opportunity to assign intentional weight and emphasis to uncertain factors based on their potential impact and likelihood. High-impact branches with large uncertainties may get prioritized over more certain but lower-impact areas.
Step 4: Design a Hedging & Learning Plan Part of the work plan development involves designing analyses and techniques to reduce key uncertainties through research, modeling, tests, and experiments. It also involves mapping out contingency plans to hedge against various possible outcomes related to uncertainties that cannot be fully resolved upfront.
Step 5: Test Assumptions & Scenarios As the kernel hypotheses around uncertain factors are pressure-tested through analysis, the team is forced to confront and revisit the validity of assumptions. Results may invalidate certain scenarios envisioned earlier while raising new potential uncertainties to consider.
Step 6: Integrate Uncertainty into the Synthesis When synthesizing the final solution and recommendations, it is imperative to attach confidence intervals, risk factors, and contingency triggers. The team should make clear which aspects of the solution are higher or lower conviction based on remaining uncertainties.
Step 7: Build Feedback Loops in the Execution Plan Dealing with uncertainty is not a one-and-done exercise. The execution plan must include mechanisms for continual monitoring of uncertain factors, course correction if needed, and a feedback loop to refine the solution as new information emerges over time.
By systematically integrating uncertainty at each phase, the McKinsey 7-step methodology imposes a disciplined process around identifying, prioritizing, analyzing, and managing ambiguities. This maximizes the robustness of solutions in our increasingly unpredictable world.
Q: Where does the McKinsey 7-step process come from? A: It was developed by the elite management consulting firm McKinsey & Company as a structured approach for their engagements.
Q: How long does it take to go through all 7 steps? A: The duration varies widely depending on the complexity of the issue and the scope involved. For a major strategic overhaul at a large company, it could take months. For a smaller operational issue, potentially just weeks.
Q: Do you have to follow the steps exactly as laid out? A: No, the 7 steps are simply a general guiding framework. Experienced practitioners will adapt and modify the process as needed for each unique situation.
Q: Is this process only for business problems? A: No, the same core principles can be applied to all kinds of problems outside of business as well, from public policy to personal goal-setting. The fundamentals of structured problem-solving translate widely.
Q: What skills are required to use this process effectively? A: Key abilities include analytical thinking, data synthesis, attention to detail, project management, and communication. Prior consulting experience isn’t necessarily required with the right training.
1. Do you define the problem clearly before brainstorming solutions?
2. Do you structure the problem by breaking it down into manageable parts?
3. Do you prioritize issues to focus on the most important aspects?
4. Do you generate a hypothesis before analyzing the problem in depth?
5. Do you rely on data and facts to validate your hypothesis?
Leave a reply cancel reply.
Save my name, email, and website in this browser for the next time I comment.
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:
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:
There are two pre-requisites to thinking like a consultant. Without these two traits you will struggle:
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.
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:
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.
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:
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:
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:
Both McKinsey and BCG had style templates that were obsessively followed. Some key rules I like to follow:
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:
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 .
“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:
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!).
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:
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:
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:
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.
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.
Learn to solve complex problems, write compellingly, and upgrade your thinking with our free mini-course.
Join 1,000+ professionals and students learning consulting skills and accelerating their careers
Discover the powerful 7-Step Problem-Solving Process to make better decisions and achieve better outcomes. Master the art of problem-solving in this comprehensive guide. Download the Free PowerPoint and PDF Template.
Introduction.
The 7-Step Problem-Solving Process involves steps that guide you through the problem-solving process. The first step is to define the problem, followed by disaggregating the problem into smaller, more manageable parts. Next, you prioritize the features and create a work plan to address each. Then, you analyze each piece, synthesize the information, and communicate your findings to others.
In this article, we'll explore each step of the 7-Step Problem-Solving Process in detail so you can start mastering this valuable skill. At the end of the blog post, you can download the process's free PowerPoint and PDF templates .
One way to define the problem is to ask the right questions. Questions like "What is the problem?" and "What are the causes of the problem?" can help. Gathering data and information about the issue to assist in the definition process is also essential.
After defining the problem, the next step in the 7-step problem-solving process is to disaggregate the problem into smaller, more manageable parts. Disaggregation helps break down the problem into smaller pieces that can be analyzed individually. This step is crucial in understanding the root cause of the problem and identifying the most effective solutions.
Disaggregation helps in breaking down complex problems into smaller, more manageable parts. It helps understand the relationships between different factors contributing to the problem and identify the most critical factors that must be addressed. By disaggregating the problem, decision-makers can focus on the most vital areas, leading to more effective solutions.
Once the issues have been prioritized, developing a plan of action to address them is essential. This involves identifying the resources required, setting timelines, and assigning responsibilities.
The work plan should include a list of tasks, deadlines, and responsibilities for each team member involved in the problem-solving process. Assigning tasks based on each team member's strengths and expertise ensures the work is completed efficiently and effectively.
Developing a work plan is a critical step in the problem-solving process. It provides a clear roadmap for solving the problem and ensures everyone involved is aligned and working towards the same goal.
Pareto analysis is another method that can be used during the analysis phase. This method involves identifying the 20% of causes responsible for 80% of the problems. By focusing on these critical causes, organizations can make significant improvements.
Once the analysis phase is complete, it is time to synthesize the information gathered to arrive at a solution. During this step, the focus is on identifying the most viable solution that addresses the problem. This involves examining and combining the analysis results for a clear and concise conclusion.
During the synthesis phase, it is vital to remain open-minded and consider all potential solutions. Involving all stakeholders in the decision-making process is essential to ensure everyone's perspectives are considered.
In addition to the report, a presentation explaining the findings is essential. The presentation should be tailored to the audience and highlight the report's key points. Visual aids such as tables, graphs, and charts can make the presentation more engaging.
The 7-step problem-solving process is a powerful tool for helping individuals and organizations make better decisions. By following these steps, individuals can identify the root cause of a problem, prioritize potential solutions, and develop a clear plan of action. This process can be applied to various scenarios, from personal challenges to complex business problems.
By mastering the 7-step problem-solving process, individuals can become more effective decision-makers and problem-solvers. This process can help individuals and organizations save time and resources while improving outcomes. With practice, individuals can develop the skills to apply this process to a wide range of scenarios and make better decisions in all areas of life.
Free powerpoint and pdf template, executive summary: the 7-step problem-solving process.
Mastering this process can improve decision-making and problem-solving capabilities, save time and resources, and improve outcomes in personal and professional contexts.
I'd appreciate your support if my templates have saved you time or helped you start a project. Buy Me a Coffee is a simple way to show your appreciation and help me continue creating high-quality templates that meet your needs.
7-step problem-solving process powerpoint template, multi-chapter growth strategy framework (free template), lidl swot analysis: free ppt template and in-depth insights.
Discover Lidl's strengths, weaknesses, opportunities, and threats with our free PowerPoint template. This in-depth SWOT analysis provides valuable insights to help you understand Lidl's market position and strategic direction.
Pestle analysis: decoding reddit's landscape (free ppt).
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 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
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.
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.
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.
Almost all projects need a full-time team of consultants. Typically, the process goes like this:
It’s solely the EM’s responsibility to keep the team happy and functional. McKinsey projects have a few common practices to do so:
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.
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.
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:
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:
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.
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:
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:
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:
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.
Business travel can be exhausting and difficult, here are some note you can take to deal with it:
Here is the list:
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.
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:
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!
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.
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!
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.
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.
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!
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.
Scoring in the McKinsey PSG/Digital Assessment
The scoring mechanism in the McKinsey Digital Assessment
Related product
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
Tiffani bova, 1 reveal: the revenue intelligence podcast, 1 the influence factor by the influencer marketing factory, the influencer marketing factory, 1 outsource accelerator podcast with derek gallimore, derek gallimore, 1 radio advisory, advisory board, 1 the entreleadership podcast, ramsey network, 1 wholesaling inc with brent daniels, find distressed properties for pennies on the dollar and turn them for huge profits, 1 the enablement edge, 1 jocko podcast, jocko defcor network, 1 knowledge at wharton, knowledge at wharton, podcasts worth a listen, the mckinsey podcast « » how to master the seven-step problem-solving process.
See www.mckinsey.com/privacy-policy for privacy information
308 episodes
The McKinsey Podcast
18,064 subscribers
published 3y ago
Welcome to player fm.
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.
The greatest CEOs are necessarily driven, decisive, and confident. But McKinsey senior partner Ramesh Srinivasan , senior partner emeritus Hans-Werner Kaas, and coauthors of their new book, The Journey of Leadership: How CEOs Can Learn to Lead from the Inside Out , say CEOs must weave in a layer of soft skills like self-awareness, humility, and compassion to inspire their workforce. On this episode of The McKinsey Podcast , Srinivasan and Kaas speak with editorial director Roberta Fusaro about taking on the challenge of reinvention for the greater good of the company.
This transcript has been edited for clarity and length.
The McKinsey Podcast is cohosted by Roberta Fusaro and Lucia Rahilly.
Roberta Fusaro: You and your coauthors just released a new book, The Journey of Leadership: How CEOs Can Learn to Lead from the Inside Out . Put simply, what is inside-out leadership?
Ramesh Srinivasan: The world is changing rapidly. The geopolitics have become quite complex, technology is having a huge impact, and climate change is here to stay. In this context, we felt the world needed a new paradigm of leadership. We call it human-centric leadership. Our belief is that leaders need to reflect on their purpose, who they are, how they show up in the world, and how they can inspire their teams and the institutions they’re leading.
Hans-Werner Kaas: Human-centric leadership provides the permanent guidepost for leaders of all backgrounds and levels. That guidepost, plus the actions leaders take to get to it, is central for colleagues and external stakeholders to look up to.
The inside-out notion means that any change starts with ourselves. We need to have the ability to be self-aware—of our words, our behaviors, and actions, and then reflect upon where our strengths and weaknesses are. You can call it self-development, which requires adopting human behaviors such as empathy , care, compassion, humility, and vulnerability—and at times, determination, confidence, and resilience. Balancing these different behavioral sets really depends on the situation you’re in as a leader.
Roberta Fusaro: Why this, why now? Ramesh, you answered it a little bit. The challenges for today’s leaders in 2024 are very different. But can you talk a little bit about what exactly has changed?
Ramesh Srinivasan: The geopolitics in the world have become much more complicated. Technology, AI, and gen AI [generative AI] are also having a huge impact. So amid all these changes, leaders need to have a sense of who they are, what their purpose is, and what motivates them. How do they show up in the world? What do they talk about? How do they understand their team members even more deeply as human beings, so they can inspire them in the spirit of their team purpose? And use all of that to inspire organizations and institutions that they’re part of.
Leaders need to have a sense of who they are, what their purpose is, and what motivates them. Ramesh Srinivasan
Roberta Fusaro: Hans-Werner, you’d mentioned that this inside-out approach is very personal. The book prompts leaders to take a closer look at their vulnerabilities, perhaps their insecurities—and that can be scary. I’m curious, how can the book help ease this process for CEOs and other leaders?
Hans-Werner Kaas: There are stories of 24 former and active CEOs in the book. They’re very personal stories, in which they reveal their insecurities, their struggles, how they’ve addressed them, and how they tried to overcome them. None of those 24 CEOs said they have achieved or reached a destination point, but all of them said they’re on a good trajectory to become more effective and more human-centric leaders.
The book also has a step-by-step “reinvention guide” that really helps you to transform yourself.
Roberta Fusaro: The book is helpfully divided into two parts: the psychological and emotional aspects of leading yourself, and then the human side of leading others. Among the chapters that talk about humility, confidence, selflessness, vulnerability, resilience, and versatility, Ramesh, is there any one of those traits or a focus area that is more important or harder to get right than the other?
Ramesh Srinivasan: We find that all of them are quite important. The one trait I want to start with is the balance between courage and curiosity. There’s the example of Stéphane Bancel , who shares in the book how, at the peak of the pandemic, he had to make a bold decision to develop and manufacture a vaccine, something that Moderna had never done before.
He had the courage to set a bold vision and inspire his team. At the same time, he brought an incredible level of curiosity because he knew there were many things they did not have capabilities for, like manufacturing a vaccine—and also a billion doses of them.
The other trait is a balance between confidence and humility. Lynn Elsenhans is another inspiring leader, who balances confidence and humility. When she was CEO, she sometimes had to be in rooms where she was the only woman, and she carried with her a sense confidence that she belonged there. As a leader, she brings amazing confidence; I’ve seen it in all my interactions with her. And yet she is extremely grounded and humble in the way she operates, and in the way she inspires her team.
Hans-Werner Kaas: Another example that comes to mind is that of Mark Fields, the former CEO of Ford Motor Company. When he became CEO of Mazda Motor Corporation, which was part of the Ford group in the year 2000, he decided it would be much better for the first six months or so to show humility. He then went on a mission to listen and be humble. He did not pretend to have all the answers, even though he did have clear views and hypotheses on the solutions for the company. He engaged in that balance of showing confidence and humility, as well as vulnerability, because he admitted that not all the answers are obvious to him, and that it would take a co-creative team effort to develop them.
One additional example is about deep learning. Admiral Eric Olson , the former head of the US Special Operations Command and a Navy SEAL, talks about the notion of fearless learning in the book. He says it’s such an important ability to not fear that your assumptions can be wrong. On the contrary, be willing to abandon your assumptions if needed. Olson says that no single plan survives the first enemy contact. In that context, he talks about how important it is that, when the terrain differs from the map, you follow the terrain. It means make a new plan, change your assumptions, so that you have a higher probability of succeeding in your mission.
Roberta Fusaro: Hans-Werner, you mentioned the notion of self-awareness is critical to succeed in this inside-out journey. But CEOs, leaders, and military leaders have such a packed agenda. How do they find the time to break from the day-to-day patterns and practice some self-awareness and reflection?
Hans-Werner Kaas: It’s very hard. We all experience it in our own roles and professions. I would point to what we describe in the book as micro practices.
As it relates to making time to be self-aware, we have to first understand our situation. Why is it so hard for us to set aside time for it? Then, consider practical things you can do. You might decide to not touch any digital device in the first hour you’re awake in the morning. Instead, you use the time to mentally go through your day and not interact with anybody. You are just alone with your thoughts, alone with your priorities. Reflect on what you have done in the recent past, the past day, the recent week, and what impact your words and behaviors had on others.
This is very important because self-awareness means you understand the implications of your words and thoughts on others. It’s fundamental in leadership . The second step is to self-reflect, which is the exercise of developing behavior practices to improve. So that’s the sequence.
Ramesh Srinivasan: I’d add one more thought. In the book, a former media company CEO talks about finding truth tellers in the organization. As you become senior, people often don’t come and tell you the truth or give you specific suggestions for how you can evolve as a leader. So putting in place a culture where people feel safe, and taking the time to meet junior people and those at the front line who meet your customers, is critical to have a pulse on what is happening in the company. And that can also be a great source for insight and subsequent self-reflection.
Roberta Fusaro: Ramesh, you mentioned gen AI as one of the bigger changes that leaders are facing nowadays, and pointed to the importance of human-centered leadership amid all the changes that are happening. Can both of you say a little bit more about this notion of leadership alongside gen AI and other technologies?
Ramesh Srinivasan: I see technology having a massive impact on the world. Yet, in all our research and our work, we feel the value of humans in the loop is not going to go away. The challenge for leaders is they need to understand how the technology is impacting themselves, their teams, and their businesses.
On how the role of the leader and the human being is evolving, Hans-Werner talks about the value of empathy, deep listening, and creativity. We don’t see those dimensions going away. So the question for leaders is, how do they bring some of those skills to bear so that the institutions they’re leading can use technology in service of society, in service of their customers, and in service of employees?
The question for leaders is, how do they bring some of those skills to bear so that the institutions they’re leading can use technology in service of society, in service of their customers, and in service of employees? Ramesh Srinivasan
Hans-Werner Kaas: As Ramesh said, in our view, there are two things gen AI will not accomplish. It cannot develop the emotional human touch. Second, gen AI can be a helpful tool to all different leaders, but leaders need to be very cognizant of where those most profound applications are, and not hype or exaggerate it, as if it’s the solution to many leadership problems. It is not.
Roberta Fusaro: Hans-Werner, another point in the book is this notion of the imperial CEO. Folks like Jack Welch and Lee Iacocca, the larger-than-life leaders, are essentially no more. When did that change and why did it change?
Hans-Werner Kaas: As Ramesh outlined at the beginning of our conversation, the forces at work, whether it’s in geopolitics, societal movements, environmental sustainability, or technology, have dramatically changed compared with where we were in the ’80s and ’90s.
The age of the imperial CEO has long passed, and it all comes back to what we said about inside-out leadership and displaying human-centric leadership. Only then will you invite stakeholders and colleagues to provide ideas in a proactive manner and be engaged, versus being in a more commanding or controlling environment, as if they are managerial subjects.
The age of the imperial CEO has long passed, and it all comes back to what we said about inside-out leadership and displaying human-centric leadership. Only then will you invite stakeholders and colleagues to provide ideas in a proactive manner and be engaged, versus being in a more commanding or controlling environment, as if they are managerial subjects. Hans-Werner Kaas
Roberta Fusaro: If you’re looking out a year, two years ahead, what impact do you hope this book will have in the business community?
Ramesh Srinivasan: Our hope is that both business leaders and social-impact leaders benefit from the ideas in the book. We hope that leaders of all genders and of all kinds will also benefit from what we have in the book. That’s our first hope.
We also want to add to the debate on leadership. We’re hoping our knowledge and research will be additional contributions. We hope to use the book as a catalyst to engage with leaders and institutions on this topic, to help them at an individual level, to help their teams, and to help institutions in the world.
Hans-Werner Kaas: Let me pick up on the third point of what Ramesh said. The aspiration is that everybody who reads the book, or even only a portion of the book, becomes more human-centric. Not only in their personal life but also in their professional life and in different sectors.
Then there is the process itself in “The Journey Never Ends,” the concluding chapter. Every reader should indeed define their own self-reflection and reinvention process and methodology. And that can happen in confidence within your family circle or with your spouse. It could be with one or two trusted individuals on your executive team, or trusted people in your organization. It can also happen with external coaches. Find your own what we call self-reflection and self-reinvention forum.
Hans-Werner Kaas is a senior partner emeritus in the Detroit office. Ramesh Srinivasan is a senior partner in McKinsey’s New York office. Lucia Rahilly is the global editorial director of McKinsey Global Publishing and is based in the New York office, and Roberta Fusaro is an editorial director in the Boston office.
Related articles.
IMAGES
VIDEO
COMMENTS
Discover the time-tested 7-step technique to problem solving that top consulting professionals employ; ... This engaging book puts together a McKinsey team's scientific seven-step approach. From taking a problem apart to rearranging its pieces, to framing it so its solution can be seen, the book presents a must-read analysis for executives and ...
To discuss the art of problem solving, I sat down in California with McKinsey senior partner Hugo Sarrazin and also with Charles Conn. Charles is a former McKinsey partner, entrepreneur, executive, and coauthor of the book Bulletproof Problem Solving: The One Skill That Changes Everything [John Wiley & Sons, 2018].
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. ... 2023 - McKinsey Global Institute director and senior ... diverse perspectives and rigorous debate are crucial to ...
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 ...
Problem solving doesn't have to be a puzzle. August 14, 2021 Knowing how to solve any problem thrown your way is a uniquely valuable skill. The good news is that it's a muscle you can develop and strengthen over time. Revisit several articles on tactics that can help you up your game, diving deeper on: Six problem-solving mindsets for very ...
Complex problem solving is the core skill for the 21st Century, the only way to keep up with rapid change. But systematic problem solving is not taught in most universities and graduate schools. The book covers the seven-step approach to creative problem solving developed in leading consulting firms. It employs a highly visual, logic-tree method that can be applied to almost any problem, from ...
Complex problem solving is the core skill for 21st Century Teams Complex problem solving is at the very top of the list of essential skills for career progression in the modern world. But how problem solving is taught in our schools, universities, businesses and organizations comes up short. In Bulletproof Problem Solving: The One Skill That Changes Everything you'll learn the seven-step ...
That is what this book is about. 7 Steps to Problem Solving. ... Charles wrote one of the early internal documents to systematic problem solving in McKinsey, and both of us have developed the approach further for application more broadly to personal, social and environmental problems at all scales in later work with the Nature Conservancy, the ...
The problem-solving technique outlined in this book is based on a highly visual, logic-tree method that can be applied to everything from everyday decisions to strategic issues in business to global social challenges. The authors, with decades of experience at McKinsey and Company, provide 30 detailed, real-world examples, so you can see ...
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 ...
The important first step is to describe the context and the boundaries of the problem that is agreed upon by those involved in making the decision. A weak problem statement is a common problem. "Rushing into analysis with a vague problem statement is a clear formula for long hours and frustrated clients.". Step Two: Disaggregate the Issues.
The 7 steps are: Define the problem. Structure the problem. Prioritize root causes. Develop initial hypotheses. Test key hypotheses. Synthesize and converge on solutions. Outline execution plan. By rigorously working through each phase, you avoid missing key details or jumping to flawed conclusions.
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.
In this episode of the Inside the Strategy Room podcast, McKinsey senior partner Chris Bradley interviews Rob McLean, McKinsey director emeritus, about applying a disciplined, comprehensive approach to problem solving. You can listen to the episode on Apple Podcasts, Spotify, or Google Podcasts.. Sean Brown: From McKinsey's Strategy and Corporate Finance Practice, I'm Sean Brown.
Step 1: Define the Problem. The first step in the problem-solving process is to define the problem. This step is crucial because finding a solution is only accessible if the problem is clearly defined. The problem must be specific, measurable, and achievable. One way to define the problem is to ask the right questions.
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!
The document provides information about McKinsey & Company, a global management consulting firm. It discusses McKinsey's presence in Greater China, with over 350 consultants and 5 offices across major cities. It also includes a brief bio of an Engagement Manager at McKinsey Hong Kong. Finally, it outlines McKinsey's 7 key steps to problem solving: define the problem, structure it, prioritize ...
Listen to How To Master The Seven-step Problem-solving Process and ninety-nine more episodes by The McKinsey Podcast, free! No signup or install needed. Will generative AI hurt middle managers—or help them?. The key to accelerating AI development? Pragmatism plus imagination.
Mckinsey Podcast - How to master the seven-step problem-solving process. A great podcast on a seven step process to problem solving. For those practicising case studies, you should listen to the emphasis put on understanding the problem before going into solving it and focussing on levers of which you can control.
Here's the simple 7-step framework we used (steal it for free) 🧵: McKinsey is paid to solve complex problems. They created a process that helps find solutions: The Hypothesis-Driven Framework. Let's dive in. 👇. Start by Gathering Facts. Most people skip this step. That's a huge mistake. Take a few hours to understand the problem.
Podcast. Enduring Ideas: The 7-S Framework. Featured in the book In Search of Excellence, by former McKinsey consultants Thomas J. Peters and Robert H. Waterman, the framework maps a constellation of interrelated factors that influence an organization's ability to change. The lack of hierarchy among these factors suggests that significant ...
An avid traveler and author who loves a good personal development book. Welcome to my Thrive With Trish Blog. A place where I share about all things related to life, career, and happiness. Archives. September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 October 2023 ...
The greatest CEOs are necessarily driven, decisive, and confident. But McKinsey senior partner Ramesh Srinivasan, senior partner emeritus Hans-Werner Kaas, and coauthors of their new book, The Journey of Leadership: How CEOs Can Learn to Lead from the Inside Out, say CEOs must weave in a layer of soft skills like self-awareness, humility, and compassion to inspire their workforce.