Do you know what prewiring is?
By the time you finish reading this blog post, you will.
I recently read the McKinsey Mind which is a great, quick book that offers a simple problem-solving framework and quite a few consulting techniques, proven and tested by McKinsey and its people.
We all know McKinsey so I think we can trust their expertise which is why I wanted to share with you my learnings from the book.
Some of them are simple but we don't implement them enough, others are very clever tips that can help us not just in consulting but also with stakeholder management and buy-in or teamwork.
Before I get to the tips, here's the model that McKinsey uses for problem-solving with clients:
The McKinsey Mind book covers analysing, presenting and managing problems. I took a ton of kindle notes while reading it and upon reviewing them, I put together the below 8-step framework which is a much simplified and shorter version than what the book offers.
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
#1 Solve at the first meeting with a hypothesis
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.
#2 Intuition is as important as facts
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.
#3 Do your research but don't reinvent the wheel
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.
#4 Tell the story behind the data
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 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. Second comes assembling your findings into an externally directed end product: a key message that includes a course of action for your organisation, 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 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 sceptical.
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 comment 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.
#6 Start with the conclusion
When you begin your presentation in front of your desired audience, make sure you start with the conclusion.
Having your conclusions or recommendations up front 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 undercommunication which is why prewiring as mentioned above is so important.
Finally, if you are proposing a certain solution in which you will be involved for 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.
#7 Hit singles
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.
#8 Respect your time
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.
Which of these steps stuck out to most at you and why?
Here's a detailed project management framework that allows you to execute on solutions if you are looking for one.