What is a "SMART" Problem Statement at McKinsey?

Aligning on the problem statement is the first step in McKinsey's approach to structured problem solving.  It is considered best practice at the Firm for these problem statements to be "SMART".  In this post I'll explain some of the characteristics of good problem statements...

Do's and Don'ts for Being Hypothesis-Driven at McKinsey

Image from keepcalm-o-matic.co.uk

When problem solving at McKinsey, it's considered best practice to use hypotheses to guide your thinking and work.  Your McKinsey boss will often ask you to be more "hypothesis-driven".  If you are interviewing for a job at McKinsey, your interviewer will expect you to be hypothesis-driven when solving the case interview.  In this post, I'll explain what that means and also provide some tips on what to do and not do when being a hypothesis-driven consultant...

What does it mean to "Trim an Issue Tree" at McKinsey?

As covered previously, issue trees are used to solve complex problems by breaking them down into their component parts.  Your McKinsey boss might ask you to prioritize efforts by trimming an issue tree.  In this post, I'll explain what that means...

4 Reasons Issue Trees are Used for Problem Solving at McKinsey

"Issue Trees" are especially useful for solving problems - especially large, complicated ones.  In this post I'll cover what they look like and some reasons why they are the preferred problem-solving approach at McKinsey

What Does It Mean to be "MECE" at McKinsey?

Working at McKinsey (or for a McKinsey boss) often requires dealing with large amounts of information.  There is a strong preference for organizing that data in a manner that is "MECE".  Your McKinsey boss might also ask you to be "more MECE" in your problem solving approach.  If you're applying for a job at McKinsey, your interviewer will be looking for MECE frameworks during your case interview.  In this post, I'll explain what that means.

What It Means to be "Down In the Weeds" at McKinsey

Image from Flickr.com

If you've worked in the food service industry - or watched Top Chef - you're probably familiar with the term "in the weeds".  But that means something very different than the term "down in the weeds" which not a McKinsey-specific term, but one I heard used frequently at the Firm.  In this post I'll explain the difference and what you should do if your McKinsey boss asks you to not be so down in the weeds...

It's also worth nothing that McKinsey interviewers also view being down in the weeds negatively, so aspiring consultants should also be mindful of not getting down in the weeds during interviews, especially when breaking down the case.

Top-Down vs. Bottom-Up Problem Solving Approaches at McKinsey

There are typically two primary ways to approach problem-solving - "top-down" and "bottom-up".  In this post I'll explain the differences as well as why the top-down approach is preferred by McKinsey bosses and interviewers...

What Is the "Obligation to Dissent" at McKinsey?

Image from 123RF.com

If your McKinsey boss knows that you disagree with something, you will be reminded of your "obligation to dissent".  In this post, I'll explain what that means...

4 Ways to "Streamline" a PowerPoint Page or Deck at McKinsey

Image from ecomodder.com

Your McKinsey boss might give you feedback that your work needs to be "streamlined".  In this post I'll explain what that means and provide four common ways to accomplish it...

"Laundry Lists" at McKinsey and 3 Ways to Fix Them

Image from rohdesign.com

Your McKinsey boss might give you feedback that your work reads too much like a "laundry list".  This is also a common error during consulting case interviews.  In this post I'll explain what "laundry lists" are and how you can fix them in 3 easy steps...

"Levers" and What It Means to "Pull" Them at McKinsey

Your McKinsey boss might ask you what "levers" you're pursuing or seem most promising on a project or workstream.  In this post, I'll explain what "levers" are at McKinsey...

What it means to "get smart" on topics at McKinsey and 5 Key Things to Learn

Image from People.com

Has your McKinsey boss asked you to "get smart" on a topic?  In this post I'll explain what that means and highlight five subjects to focus on...

Focus on the "Critical Few" or "Vital Few" - Application of the 80/20 Rule

Your McKinsey boss might give you feedback to focus more of your effort on the "critical few" or "vital few". This is so you can achieve maximum impact for a given amount of work - it's another way of saying that your McKinsey boss wants you to apply the 80/20 rule to your work.  In this post I'll explain those terms...

What it means to "Boil the Ocean" and why it's important to avoid doing it

Image from travel.nationalgeographic.com

The term "boiling the ocean" is used to describe any task that's impossible because it has been incorrectly scoped.  In this post I'll explain what that might look like on a McKinsey engagement - or a project for a McKinsey boss - and what to do about it...

What it means to "Sanitize" a document at McKinsey

Image from Purell.com

You might hear your McKinsey boss or colleague refer to a document as "sanitized".  Or, you might be asked to "sanitize" a document.  This has nothing to do with hygiene or disinfectant.  It has everything to do with confidentiality.  In this post I'll explain what it means for a document to be sanitized....

McKinsey Presentations - Anatomy of a McKiney PowerPoint Deck Page

McKinsey consultants use PowerPoint pages and presentations (aka "decks") to communicate with clients and each other.  In this post, I'll explain the three elements of a typical McKinsey page so you can put together your own McKinsey-style deck.  This should be helpful for new McKinsey consultants and anyone working for a former McKinsey consultant...

McKinsey Interviews - October, 2013 Posts for Aspiring Consultants

To anyone NOT interviewing with McKinsey:

With apologies to folks who are already consultants or looking for tips on how to work with a current or former McKinsey consultant, the posts for the next couple of weeks will focus on getting into the Firm.  But we'll get right back to our regularly scheduled mix of programming after that!

To those of you who ARE interviewing with McKinsey:

For those of you who are Aspiring Consultants, the posts over the next couple of weeks will help you understand what to expect as you pursue a job at McKinsey and/or other top management consulting firms.

I'll try to coordinate the content across posts so I might delay putting content on the blog until other posts are completed.  But I will schedule them so they appear on the day they were originally written.  Apologies if that gets confusing for those of you who subscribe or follow this blog regularly.

McKinsey Presentation Decks - What is the Storyline and What is a "Dot-Dash"?

If you're working with a McKinsey boss to prepare a PowerPoint (PPT) presentation - known in consulting as a "deck" - you might be asked to work on a storyline and prepare a "Dot-Dash" version of that storyline.  In this post, I'll explain what those terms means and why they're important...

McKinsey Presentations - How to Apply Ghost (aka Shell and Skeleton) Decks and Pages

Image from sweetclipart.com

McKinsey consultants invest a lot of time and effort into making PowerPoint presentations (decks) and pages.  "Ghost" decks are used to align on what the end product will look like and to minimize wasted work.  In this post I'll explain what a ghost deck is and what it means to "ghost out" a deck or pages...

Asking Your McKinsey Boss for Help - Bring Solutions, Not Just Problems

Image from deviantart.com

In a previous post, I provided three ways to keep your McKinsey boss happy.  In this post, I'll explain a fourth, equally important way to stay in the good graces of your McKinsey boss:  When you're struggling with something and need help from your McKinsey boss, make sure you bring solutions, not just problems