Welcome back!



Forgot password?

Don’t have an account? Subscribe now

This is the feedback a reader sent in just 5 hours ago after his first of three interviews with a McKinsey partner. The problems experienced by the candidate in his McKinsey partner interview are surprisingly common.

We have noticed this pattern before, especially if you watch Alice and Michael in Season 2 of The Consulting Offer. When I was a principal, I also noticed this. I think the problem has become much worse with the large amount of poor advice on the Internet.

Interview with a McKinsey partner

“Hi Michael,

I just came back from one of my 3 final round interviews.

The remaining two are on Sunday.

The McKinsey partner was aggressive, which I had anticipated, but there was something that felt strange, it felt like he was trying to stop my progress. I got feedback right after the interview and I was very confused by it.

Two parts of the interview and feedback really confused me:

1. During the interview he asked me “How do you influence people?”.

He kept insisting that I should be theoretical, and not go into specific examples. When I tried to give him examples he said: “I don’t want to know details. I just want to know how you influence people”.

He actively stopped me from giving examples.

2. He gave me the case, which was a profitability problem for a bank. I proceeded to make an issue tree, which was broken down into customer types, product lines, and finally revenue streams and cost structure for each one of these branches.

I started walking him through the different parts of my tree when he interrupted me and moved me onto the next part of the case.

So I assumed that this was all part of a stress interview and that I had at least handled him properly.

Immediately after I left the office, the HR lady called me and gave me the feedback:

1. I did not give examples for how I influence people.

2. I did not cover enough issues in my issue tree.

HE STOPPED ME FROM COMPLETING BOTH! How on earth is this proper feedback?

He actively stopped me from completing my discussion of the issue tree and then he said that I didn’t complete it. I told the HR lady that if you look at my notes that I left behind they would see a COMPLETE AND 100% MECE issue tree.

I have two more interviews on Sunday and I am concerned that there is not much that I can do, even though my first round feedback was excellent.

What do I do?”

Feedback in three parts: PEI, case and feedback call

I am going to split my feedback into three parts: 1) The PEI, 2) the case and 3) the feedback call.

McKinsey PEI

With regards to the HR lady stating you did not provide examples, I think she meant examples of the influence framework you apply in your mind. She was not referring to examples where you applied that framework. That is what you are misunderstanding.

The way the McKinsey partner used the word example is different from the way the HR person is using it. You can have examples of frameworks and examples where you applied the framework. They are mutually exclusive.

The McKinsey partner wanted examples of the leadership framework you use, and it sounds like you did not provide these. He was not asking for examples of how you applied the framework.

This misunderstanding aside, the main mistake the candidate is making here is very obvious.

He is ignoring the McKinsey partner, and quite blatantly at that. The McKinsey partner is being very specific in that he does not want to hear examples of applying the framework, but the candidate is ignoring that request and insisting on providing examples of the application.

An example of the application and an explanation of the framework are very different.

Mercury, Venus, Earth and Mars are examples of planets.

The theoretical definition of a planet is a body of matter, which orbits a star without orbiting another body of matter. Our moon, for example, can orbit both Earth, a planet, and ultimately go around the Sun with the Earth.

Other scientists could have a different theoretical construct to define a planet and that is all fine and well.

Do you notice how different these answers are?

Typically, candidates give examples of the application when they cannot explain their underlying reasoning. This McKinsey partner is being specific in testing whether or not the candidate understands why he approaches these leadership moments as he does.

It is much more difficult to explain the reasoning behind something without application examples, and I would argue that most candidates struggle to do that.

Was this McKinsey partner being tough or placing the candidate under stress? I do not think so. The reason I think not is because this candidate obviously misjudged a fairly direct question from the interviewer. So I do wonder if the candidate’s judgment on the interviewers manner was equally misplaced.

I have seen this often where a candidate will ignore the question asked by an interviewer and follow advice offered in a blog. Blogs are usually written by associates and recruiters. Associates do not make decisions on interview offers. Partners make them. Period.

Why would you ignore the McKinsey partner, who makes the decision, to listen to an associate, who does not make the hiring decision?

Full McKinsey Case

I do not have sufficient information here, but I can still see where you are likely making a mistake. The McKinsey partner did not say your framework is incorrect. Frankly, as a partner, we do not care about frameworks as much as you would think.

Associate and engagement managers do, because in the rounds when they interview, they need to check if you hit on the issues that the recommended solution asks for.

When you get to interviews with partners, they are more interested in your reasoning, logic and ability to make sound inferences from the data.

So, you are confusing the feedback to assume he is saying your framework was insufficient. You point out he moved your analyses to another area of the case. That is completely normal. I do that all the time. He is not stopping you or hindering you, he is helping you focus on the main area of analyses.

I believe that when he pointed you to the main area of analyses you did not identify all the issues that needed to be analyzed there.

So do not confuse framework with issues.

The feedback call

While your feedback demonstrated significant improvement areas, you compounded your mistakes enormously in the feedback call.

Never ever imply the partner is wrong.

What did you think was going to happen? A recruiter from human resources was going to go back to McKinsey partner and ask him to change his feedback because your structure was complete and MECE?

You do realize a recruiter is a junior person? They have zero influence on the hiring decision. If you go on the Internet, blogs, forums etc., you will find plenty of ex-McKinsey and ex-BCG calling themselves recruiters. That position means nothing since it has no power to grant you the offer.

A recruiter is a consultant who sifts through resumes using a formula to sort out likely candidates. In other words they are glorified assistants. It is a term ex-consultants use to sound important when it is not.

Your reaction in this call indicated to the HR manager that you are not open to feedback. While she may not have influence on the hiring decision, she could let the McKinsey partner interviewing next know about your response.

I am going to respond to each of your points below for clarity:

“HE STOPPED ME FROM COMPLETING BOTH!”

He did not stop you. In the first PEI you were not answering his question. That is your mistake and he was trying to help you by restating the question. In the situation with him changing the analyses area of the case, he also did not stop you, but moved you to one area for discussion.

You assumed being MECE and having a pretty structure was enough. It is not. You need to focus on the areas the partner wants to analyze.

“How on earth is this proper feedback?”

It is clear and direct feedback. You need to listen to partners and not assume having a framework is enough in a case. You seem to have failed to outline the issues in the area he was looking for.

I also suspect you were not prioritizing your analyses. You appear to have wanted to explain each part, and maybe, eventually you would have raised the issue he wanted to discuss.

Always prioritize and analyze the area he wants you to analyze. It takes far too long for you to work your way through a tree, and it is better to use hypotheses if your tree is too big.

The big lesson here for you is a lack of prioritization.

“He actively stopped me from completing my discussion of the issue tree and then he said that I didn’t complete it.”

He did not say that.

He said that you did not raise the issues he wanted to discuss in the area he wanted analyzed. You assume you would have raised the issues if you completed your tree. That is a big assumption and even if it is true, then why were you not able to raise the issues when he pointed you to the prioritized area?

If you knew the issues, you should have been able to discuss them.

Therefore, the McKinsey partner is correct. He pointed out an area for discussion and you did not raise the issues in that discussion.

“I told the HR lady that if you look at my notes that I left behind they would see a COMPLETE AND 100% MECE issue tree.”

This, could come back to hurt you. It also shows me that you need to understand cases have little to do with structures. There are lots of partner cases where we do not even use structures. 50% of McKinsey final round cases cannot be solved with a structure. That is a scary but true statistic.

You can do a whole lot more based on my comments above. Your first round was not with partners. You are now in a whole new ball game. Raise your standards and look at how Kevin and I do cases. You will need to bring more than a structure/framework that is MECE, and you will especially need to tackle cases where frameworks cannot be used.

I would honestly watch Season 1 and 2 more carefully to watch how partners conduct cases. It is not like what you read on the Internet.

The singular piece of advice: listen to the partner and answer his question – not the question you think he should be asking.

Michael

Image from Jon Herbert under cc.

I recently had a coaching session with a client who could become a McKinsey Principal in about 12 to 24 months. He is currently a McKinsey Associate Principal and has been a long-time client of FIRMSconsulting.

He joined our coaching program when he was at Harvard completing an MBA and we helped him join McKinsey as an associate. This is my 7th year of coaching him and he is a wonderful young man.

I feel confident we can get him to the equity partnership, a McKinsey Director and ultimately to become a senior partner. I see all three steps happening within about 8 years. That is below the average time.

I am going to summarize some critical advice I offered him, and other McKinsey Principal-level coaching clients, about moving from associate principal to becoming a McKinsey Principal and, thereafter, McKinsey Director.

He found it incredibly useful so I am going to share it with the broader community. I did make a comment in the coaching call that all of the advice I am offering is already covered in a program we have. In this article, like the call with the client, I want to zoom in on just a small part of that program.

 

Mckinsey Principal

 

A McKinsey Principal within the Partnership

 

The first thing to understand is how a partnership is structured within McKinsey, and this would apply to any partnership at any elite firm. To know how a firm works you need to ignore the values, slogans, structure, and statements and look at the incentive/compensation structure.

The best way to think about a partnership is to think of the mafia or organized mob. I am using this analogy purely for the structure and incentives and not the unsavory and illegal parts. I am not making that implication at all.

The mafia is made up of families.

Different families control different parts of the trade or different regions of the same trade.

They all agree to work together and pool resources since it is better to fight in numbers as a unit versus the cost of fighting each other.

They transfer best-practices, use the same brand, ask for help etc.

Yet, they remain distinctive and different families who work together.

They may look and act similar but they are different.

Here is a very important point. You never join the mafia.

You first need to join a family that is a part of that mafia. That family trains you and mentors you until you reach a certain level of status and then they nominate you to represent them in the overall organization among many families. Around that table, controlling that Mafia, are the heads of each family. The heads of each family come together to agree on profit sharing percentages and make collective management decisions.

The head of a family is like a senior partner within McKinsey or any other elite firm.

This is how a McKinsey or any other partnership is structured. I will make this more clear shortly, but not understanding this is the main reason so many McKinsey associates don’t make a transition to the partnership.

 

A McKinsey Principal within the ‘Mafia’

 

When you join McKinsey as an associate or business analyst you are joining McKinsey the overall firm, and not just one part of McKinsey.

McKinsey is essentially a group of senior partners who have revenue-generating relationships with clients and decide it is better to work together under one brand, share resources, pool ideas and lower the risk of operating independently. McKinsey is effectively a collection of smaller consulting firms each headed by a senior partner. They share a common brand and agree to work in roughly the same way worldwide. But like all collectives, there are differences and disagreements.

Sometimes a senior partner can choose to leave McKinsey and take their entire book of business with them. They can go to Bain, BCG or even set up their own firm. This is actually very common in the legal profession.

When you join McKinsey the firm, you immediately begin auditioning to join one of the smaller consulting firms headed by a senior partner. That smaller consulting firm has not yet selected you.

However, to become a McKinsey Principal or McKinsey Director, a smaller consulting firm must select you to groom you. There is no other route to the partnership.

Kevin and I both explain these concepts in more detail but with different approaches in our programs on sales.

Let’s look at your very first engagement.

Let’s assume your first engagement as an associate is a pricing study for a tech company.

That engagement is overall headed by a senior partner who manages that relationship.

If you do well as an associate, the senior partners’ team is happy since you are helping them preserve the relationship and protect the revenue stream.

They want you to stay with them and develop you to the engagement manager level and so on.

Again, if you do that well and help them protect the revenue stream, they keep pushing you up their mini-organization.

 

Understanding your role on the path to becoming a McKinsey Principal

 

Now, you have to understand your role within McKinsey as you progress, from the perspective of what the senior partner wants relative to the revenue he is bringing in.

McKinsey partners and most partners of other firms do not talk about revenue but Kevin makes an exception as he builds his program around understanding the sales side. I also do the same since the partnership of any elite organization is about revenue.

As a senior partner in the London office once said.

We charge an awful lot of money all for the privilege of never having to discuss money, to the point that people forget we are an immensefully profitable business.

Let’s break down each level from a revenue perspective.

McKinsey Business Analyst: Do not rock the boat aka don’t do anything that upsets the client.

McKinsey Associate: Help the engagement manager protect the revenue stream

McKinsey Engagement Manager: Coordinate the team to deliver the work to protect the revenue stream

McKinsey Associate Principal: Begin managing parts of the client relationship to protect the revenue stream and free up the Principals’ time.

McKinsey Principal (non-equity partner): Find ways to grow the existing revenue stream at one or more existing clients within the senior partners’ consulting practice and/or find new revenue streams at one or more existing clients within the senior partners’ consulting practice

McKinsey Director (equity partner): Take on overall management of one or more clients to grow existing revenue streams or find new sources of revenue, such that the senior partner need only manage the relationship should a problem occur. Ideally, the senior partner simply has a relationship and all the work is led by the director.

It’s important to understand that the most brilliant McKinsey consultant who cannot grow or find new revenue streams for a senior partners’ consulting practice will struggle to become an equity partner.

There may be exceptions, but largely speaking they will find it difficult make it to senior partner. They will be stuck at the principal level.

 

A McKinsey Principal is not nominated by McKinsey

 

There is a strong myth about the way the partnership works at most firms, including McKinsey. McKinsey is not the Borg. McKinsey does not do anything. It is a brand and incorporation. Only people within McKinsey can do things and there is never going to be 100% consensus.

McKinsey does nothing as a collective because some McKinsey partners choose to take an action even if many other McKinsey partners disagree. For example, when McKinsey bought a design firm, there were definitely some partners who disagreed. However, enough partners supported the purchase for it to happen.

Whenever you see McKinsey doing something, it is not a uniform decision.

McKinsey does not nominate anyone to the McKinsey partnership: be it McKinsey Principal or Director. Let’s break that down because it is important.

When we say, McKinsey, we mean the McKinsey Partnership Committee. They do not nominate anyone because their job is to select someone nominated to them, and then they review that nomination made to them and place it for a vote.

So how does this work?

Senior Partner Steven looks at his mini-consulting practice within McKinsey. He believes that moving Sheila from Associate Principal to Principal will help him, Steven, build his small consulting practice within McKinsey for several reasons.

Sheila has a good relationship with the client and by promoting her, Steven can spend less time at the client and have one of his partners spend less time at the client.

Steven and his other partner can spend that saved time finding new clients

Sheila is also developing great skills in organizational design and Steven believes most clients in the sector he serves will be undergoing some form of reorganization in the next 2 years.

So Steven sits down with his team and makes sure they like working with Sheila. Even if Steven likes Sheila, his team must like working with her since Steven will not be the person working with her directly.

If they all agree promoting Sheila to Principal helps their small consulting outfit generate more revenue and profits, they will put forward her nomination and vigorously promote her.

The McKinsey Partnership Committee reviews these nominations and does its own checks and then submits a final list.

McKinsey did not nominate a McKinsey Principal. McKinsey selected a McKinsey Principal nominated to them.

Even if you are on a first name basis and great friends with all the partnership committee members, unless some smaller consulting team head by a senior partner strongly nominates and supports you, you cannot become a McKinsey Principal.

To say otherwise is to say that a group of partnership committee members who have never/rarely worked with Sheila and do not have a role for Sheila within the organization, are going to make Sheila a partner when Sheila has no mechanism to generate revenue, and then force Sheila into a senior partners’ smaller consulting practice.

That cannot make sense.

 

From McKinsey Associate Principal to McKinsey Principal

 

So this is the plan my client, Kalan, wanted to follow to become a McKinsey Principal within about 18 to 24 months.

(1) The senior partner has a core team that he takes to every new client or new initiative within the client. Kalan wants to be part of that team so he gets into the inner circle.

(2) Spend as much time learning from the senior partner.

(3) Try to find new sales opportunities with the existing clients where Kalan works.

(4) Gain some broader exposure at other industries/clients to gain a diverse exposure that McKinsey seeks in principals

(5) Publish articles to gain credibility with clients.

All of this is a bad idea and I will explain why below, linking the explanation to each of the 5-points Kalan wants to follow.

My overall sentiment is Kalan must have been raised by so involved helicoptering parents that his hair must look like a Beatles haircut from the downward push of the air from the helicopter blades. This list is all about what he wants when he should be treating the senior partner as his client.

To be promoted Kalan must do what the senior partner wants and needs. I will treat each of Kalan’s priorities as myths. Which is what they are.

 

McKinsey Principal Myth #1

 

The senior partner does not want to travel to clients with you. He does not want an entourage.

He is not Jay Z.

To always be in the same room as the senior partner implies that Kalan cannot do what is needed and the senior partner needs to be there to do it for Kalan.

The senior partner wants his senior team to be able to operate independently. He wants to know that his principal, Kalan is managing his client so well that he/she, the senior partner, only needs to show up when he/she, the senior partner, chooses to show up.

Kalan’s strategy should be to avoid the entourage and go off and protect one of the senior partners’ clients and do such a great job, that the account grows and the senior partner can spend time on other things. Kalan is doing well when the senior partner does need to spend time with Kalan and can just trust him to get the job done.

That is essentially how I became a partner. I was sent by the senior partner to manage problems on his behalf. If he needed to travel with me, it meant I could not do the work. I only attended one CEO meeting with the senior partner who backed my nomination. Just one.

 

McKinsey Principal Myth #2

 

Again, this must be from helicopter parents who drove him around from piano to football to clarinet to playdates to learn.

Somehow in the last 20 years, the vernacular of wanting to learn became a strength. Sounds like weakness to me. Kalan has been at McKinsey for 5 years. It’s time to shift from learning to learning-by-doing.

The senior partner does not want Kalan to learn from him. He does not want Kalan to shadow him like the paparazzi. Again, he is not Jay-Z.

The senior partner needs Kalan to help the partners who work in the senior partners’ consulting practice do their jobs well. Kalan’s goal should be to help them succeed at whatever they need to protect and grow the revenue stream, and Kalan will learn as he is doing that.

 

McKinsey Principal Myth #3

 

Kalan should not pursue sales unless the opportunity comes to him. Doing so means working independently of Kalan’s team for his sole benefit. What Kalan does must be for their benefit. If they can sell and have been selling, is it not better for that mafia family if Kalan helps them sell rather than stumbling and inefficiently trying to sell by himself? Which is better for the family?

Kalan needs to do what is good for the family. No one is going to reward Kalan for a sale that could have been done faster, better and delivered in a superior way. Kalan eats when the family eats. Kalan should not go out hunting by himself when the family hunts better together.

This is not about Kalan’s needs.

A senior partner and his senior team are not your work mummies and work nannies. They are not there to drive you to a play date with a potential client and help you close the deal.

 

McKinsey Principal Myth #4

 

The first rule of the family is you do not leave the family. Ever. They have spent years grooming and training Kalan and now Kalan wants to take all those skills to another family just so that he, Kalan, is better off. Where is the loyalty?

In the Mob this is what they do to betrayal.

In McKinsey, the senior partner effectively kneecaps your career by withdrawing his nomination for you.

If Kalan did this he would have lost the trust of the senior partner and his team and that would end his career. Period. And there is virtually no hope of resuscitating his career.

It does not help the senior partner and his consulting practice for Kalan to do this.

In fact, most senior partners are worried about their relationships and clients being hijacked by partners within the firm, or by defecting colleagues to other firms. It is easy to say the senior partner must do what is best for the client and McKinsey. Yet, who decides this? If the client wants to change the relationship that is fine, but how can another partner at McKinsey decide they are better at managing an existing relationship that works just fine.

Kalan can gain a diversity of experiences within the same client and the same sector. That is what a broad range of experiences means. It does not mean new clients and sectors.

What possible value would Kalan bring to both a new senior partners’ team and new sector?

Why would those clients of the senior partner just accept him?

Why would the senior team of the new senior partner allow an ‘outsider’ to swoop in to be next in line for a partnership nomination?

Why would a senior partner trust and let Kalan into his team when Kalan left the team that groomed him?

If Kalan was “raised” in the auto sector would he bring much value in the tech sector?

McKinsey is not a uniform drone organization. How would Kalan seamlessly fit into the new teams’ work style and approach?

 

McKinsey Principal Myth #5

 

Kalan does not need to write articles. Unless his team needs this. Again, he needs to put his team first.

The most powerful partners at McKinsey are not the partners who write books and articles. The most powerful partners are the partners who manage important client relationships.

To sell, Kalan can use articles, or Kalan can simply discuss issues with clients. Some partners have powerful client relationships and write, and they are rare. Yet, Kalan does not need articles to sell and Kalan should not be writing articles if the sole purpose is to sell since that may not be what his team wants of him.

 

The McKinsey Principal

 

If you look at this advice, it is different because most people are wired to think that becoming a McKinsey Principal or McKinsey Director is about their success as an individual trying to prove their worth at sales and insights with clients. It is also different because partners rarely discuss the inner workings of the elite firms. We are different and believe our clients should know these things.

Insights do not lead to sales but that is for another piece.

To become a McKinsey Principal or McKinsey Director is about finding a home within a senior partner’s family and helping that senior partner grow his business. It is about the family and not about you.

We speak about sales a lot here even though I do not like the word. Yet, it is word everyone understands and even though we do not focus on this in this article, the work should be exceptional, the client should be better off after you finish the work and you should never sell a client what they do not need.

Finally, this advice applies to any partnership. Whether it is Bain, BCG, Deloitte S&O, PwC Audit, law firms etc.

You are welcome to post any comments and questions below. As you can imagine we receive many requests for help and as much as we would like to respond to them all, we just do not have the time. To ensure our responses reach as many readers as possible, questions will only be answered in our iTunes podcasts. This allows us to offer both thoughtful and meaningful answers that help improve your career. If you ask a question please offer as many details as possible. It is difficult to offer customized and valuable feedback if the details are vague or missing. It helps to provide more facts and leave out your interpretation of what happened. It is better to write “Duke MBA, graduated 2 years ago and working in Wells Fargo Technology Support,” than “a Top-10 MBA, recent graduate working for a large bank’s internal technology team.” The advice we offer would be very different for each and we would select the first type of question to answer.

Many experienced-hires wrote to us about our recent piece on becoming a McKinsey Principal. While they may appear to be the same, becoming a McKinsey Director requires different skills from becoming a McKinsey Principal. This article will unpack those differences using the example below.

Let’s assume the regional CEO of a major auto company is being interviewed for the position of McKinsey Director in the Automotive & Manufacturing Practice.

Auto CEO to McKinsey Director

This regional CEO runs a region with an R&D center, manufacturing sites, and a large consumer market. In many countries, regional CEOs simply run a sales organization. This person is that rare regional leader of a Fortune 100 company who understood the entire value chain of the business and ran parts across the entire value chain.

For a variety of reasons, he wanted to do something different and given his profile, intellect, presence, and his vast network, he was being considered for a McKinsey Director position.

He was clearly smart and could command attention. He could rivet the attention of senior decision makers. McKinsey Directors need to be able to generate a book of business. If he was just smart, let’s assume very smart, but was unable to build that book of business he would be a McKinsey Principal or an expert track leader.

Stefan, let’s assume that was his name, believed he had access to a network of auto leaders that could allow him to build a practice. Let’s assume he did have access to this network. Stefan believed that by working with another McKinsey Director, they could create a significant increase in revenue for the practice and branch into new areas.

Assuming he was right, why was Stefan not hired as a McKinsey Director?

A network does not equal a McKinsey Director

Stefan makes a mistake that is common to most senior industry leaders trying to become a McKinsey Director, or even a BCG or Bain director.

Stefan confused a McKinsey Director role with a Consigliere role. A consigliere is a counselor who guides the more senior person. In the consulting world, they are used when a firm enters a new market or region and needs help to understand the local issues and especially, need introductions to the key industry and government leaders.

McKinsey, Bain etc. used them in the 1970s and 1980s as they expanded into Japan and Europe.

In this model, this is what happens:

A consigliere is valuable because they know 20 of the most powerful business leaders in India, for example.

They set up the meetings for McKinsey Director X.

They will likely attend the meetings and counsel McKinsey Director X.

McKinsey Director X explains how McKinsey works, gains the trust of a business leader, discusses the leaders’ issues etc. which ultimately leads to an engagement.

McKinsey Director X inherits the relationship with the industry leader when he gains the leaders’ trust.

As these meetings continue, there is no longer a need for the consigliere.

Once all the relationships are transferred the skill/asset the consigliere possessed is no longer useful to McKinsey.

Differences between a McKinsey Director and McKinsey Consigliere.

A McKinsey Consigliere has access to a network but cannot gain their trust to perform engagements.

A McKinsey Director can convert a relationship into revenue. That is crude but let’s call a spade a spade.

A McKinsey Consigliere only keeps his network because he is not asking much of them. He just knows them and hangs out with them.

A McKinsey Director is able to build a relationship where the firm is doing work for the client, and, this is important, the relationship does not end when the work is done.

A McKinsey Consigliere gets a finders fee. Not a share of the profits.

A McKinsey Director gains a share of the firms’ profit percentage distribution.

Once the relationships transfer to the McKinsey Director, a McKinsey Consigliere has almost no value. This scene from the Godfather captures it perfectly.

Senior vs. Junior McKinsey Director

Junior McKinsey Directors operate more like McKinsey Principals. They help a Senior McKinsey Director manage, maintain and grow his $10MM-$30MM mini-consulting business within McKinsey.

A Junior McKinsey Director is closer to the action and the teams on a consulting engagement. This means they need to understand to some degree how engagements are run, issues are structured and problems are solved.

So while it is relatively easier to become a Junior McKinsey Director, that is only true in relation to the reduced stress of sales. The stress will be high if you are interviewing for the position but either do not know how studies are conducted or the Senior McKinsey Director who is considering you for his team thinks you cannot learn enough to manage the engagement teams in an appropriate time period.

A Senior McKinsey Director is generally so far removed from the operating details of the team that they will not be assessed for this skill.

The firm will look to see if they can maintain relationships, convert those relationships to sales without alienating clients and create sales that meet the quality and style of the firm.

Does a McKinsey Director need a Consigliere?

The short answer is usually no.

There was a time when the foreign world was this tantalizing and mysterious place. It was usually an American or European going off to some land like Japan etc., to build a business. The world has opened up significantly since then.

One does not need a consigliere to navigate new countries or dark alleyways in new countries. Google Maps and Uber work just fine.

McKinsey can often send a Polish Director with Polish consultants to open the Warsaw office. I would presume they would know whom to meet, how to meet them and which alleyways of Warsaw to avoid.

In most cases, a McKinsey Director marries a foreign person (for example), eats foreign food for 10 years of the marriage, moves to his partners’ foreign country for 5 years and calls himself an expert of the country. And people believe him.  When I moved to Canada, ate Canadian food for a decade and served the top leaders, no one called me a Canadian expert. Apparently, I still needed to assimilate. This must only work when you move from the West to Everywhere Else.

Or maybe I should have married a Canadian as well.

I wonder if it is an intellectual appropriation to assume to be an expert in a country just because you served some of the business leaders? Just know when the New York Times appropriates this phrase, you heard it here first.

Generally, spouses are the new consiglieres. They may not have access to top decision makers but having a spouse from the region where you are trying to build a business is seen as an easier way to integrate.

There are very few places where McKinsey needs consiglieres these days. Maybe to meet certain government leaders or in very closed economies, but there are fewer and fewer of those.

Why was this auto CEO not appointed a McKinsey Director?

The primary reason is that he saw his main value as having access to a network versus him developing that networks into clients for the firm. He was also not such a valuable gatekeeper since the firm had other ways to reach those leaders. And even if he did have access the firm could not attain by himself, he was positioning himself to be a consigliere.

He firmly believed that he would pair up with a McKinsey Director, his work wife/husband, and they would build a happy family serving clients in the auto sector. He would go out in the morning and hunt for the prize and his work wife/husband would convert it into something worthwhile.

He wanted to be a McKinsey Director but he did not understand what the role involved. And because he could not understand there was a difference, there was no point in hiring him. It would have been a case of mismatched expectations.

You are welcome to post any comments and questions below. As you can imagine we receive many requests for help and as much as we would like to respond to them all, we just do not have the time. To ensure our responses reach as many readers/listeners as possible, questions will only be answered in our iTunes podcasts. This allows us to offer both thoughtful and meaningful answers that help improve your career. If you ask a question please offer as many details as possible. It is difficult to offer customized and valuable feedback if the details are vague or missing. It helps to provide more facts and leave out your interpretation of what happened. It is better to write “Duke MBA, graduated 2 years ago and working in Wells Fargo Technology Support,” than “a Top-10 MBA, recent graduate working for a large bank’s internal technology team.” The advice we offer would be very different for each and we would select the first type of question to answer.

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.