McKinsey PEI: Insider Guide to All Four Dimensions (2026)

Last Updated on June 16, 2026

By Florian Smeritschnig, former McKinsey Senior Consultant · Updated June 2026

The McKinsey PEI (Personal Experience Interview) is the behavioral half of the McKinsey interview, and it counts for as much as the case. Most candidates spend 95% of their prep on the case and treat the PEI as an afterthought. That is exactly why so many strong applicants get cut here.

I spent 5 years at McKinsey as a Senior Consultant and evaluated real candidates. Since then, I have run 2,200+ mock interviews and coaching sessions and helped candidates win 700+ offers at McKinsey, BCG, and Bain. The pattern is consistent: the people who fail the PEI almost always make the same avoidable mistakes.

This StrategyCase guide shows you what McKinsey actually assesses, the framework to structure your answers, and a full set of example stories for every dimension.

Key Takeaways

• The PEI is worth as much as the McKinsey interview score, equal to the case, yet most candidates barely prepare it.
• McKinsey assesses four dimensions, all renamed in summer 2025: Leadership (was Inclusive Leadership), Connection (was Personal Impact), Growth (was Courageous Change), and Drive (was Entrepreneurial Drive).
• Problem-solving is not a PEI dimension. That is the case interview. Preparing a “problem-solving story” for the PEI wastes your time.
• Structure every answer with the SCORE framework (Situation, Complication, Outcome Expectation, Remedial Actions, End Result) and spend about 80% of your airtime on Remedial Actions.
• Prepare two distinct stories per dimension. You cannot reuse a story, and you may be asked about the same trait twice.

What is the McKinsey PEI? The Personal Experience Interview is McKinsey’s structured behavioral interview. In a 10 to 20 minute conversation, you tell real stories from your past that show four traits (Leadership, Connection, Growth, and Drive) while the interviewer digs into your actions, decisions, and motivations. It runs alongside the case interview and carries equal weight in the offer decision.

A quick note on the 2025 renaming. McKinsey rebranded all four dimensions in summer 2025: Inclusive Leadership became Leadership, Personal Impact became Connection, Courageous Change became Growth, and Entrepreneurial Drive became Drive. The labels changed; what each one tests did not. I use the current names throughout and flag the old ones so you recognize them in older prep material.

Treat this as content you prepare cold. The PEI is not where you improvise. It is where you calmly recall stories you have already built, so they land structured, specific, and aimed at the exact trait the question is testing.

The Role of the PEI in the McKinsey Interview Process

The McKinsey interview sits at the end of a longer funnel. Candidates are first screened on their resume and cover letter, then play the McKinsey Solve game, and only then reach the interviews. For the full sequence, see our McKinsey interview process guide.

Each interview is standardized and has two parts: the case interview and the PEI. They carry equal weight in the decision. A typical interview runs about 50 minutes: 10 to 20 minutes of PEI, around 25 minutes of case, and roughly 5 minutes for your questions to the interviewer.

Ace one half and bomb the other, and you do not get the offer.

Understanding the McKinsey PEI

The PEI is a tightly standardized version of the behavioral interview that every consulting firm runs. It revolves around four character traits and the stories you tell to prove you have them.

What the PEI Is Actually For

McKinsey’s logic is simple: strong problem-solving is not enough. Consultants also need drive, leadership, persuasion, and the composure to handle change. The PEI is how the firm checks for those qualities before it makes you an offer.

The format also lets interviewers compare candidates fairly. Your stories are personal, but the scoring is structured, so two interviewers in two offices can rate the same trait against the same bar. Your job is to give them clean evidence that you have it.

How the PEI Differs From the Case Interview

The case interview tests how you think: you take a business problem, structure it, run the numbers, and land a recommendation.

The PEI tests who you are: you draw on real experiences to show how you led a team, won someone over, or handled a setback. One rewards structured analysis. The other rewards honest, well-told reflection. They need separate preparation.

What Traits Does the McKinsey PEI Assess?

McKinsey looks at four traits (renamed in 2025, with the old names in brackets):

1. Leadership (Inclusive Leadership): can you lead a diverse team and get people to follow you toward a shared goal, including the hard calls and the conflicts.
2. Connection (Personal Impact): can you influence and persuade people, especially when they start out disagreeing with you.
3. Growth (Courageous Change): can you stay effective when the ground shifts, with resilience and adaptability instead of panic.
4. Drive (Entrepreneurial Drive): can you take initiative, push through obstacles, and get results without being told to.

The four McKinsey PEI dimensions (renamed in 2025)

All four are live and assessed.

We go deep on each one below, after the preparation and framework sections. Jump to a dimension: Leadership, Connection, Growth, Drive.

Is Problem Solving Part of the McKinsey PEI?

No. Problem-solving is not a PEI dimension, whatever some coaches and websites tell you.

This myth costs candidates real prep time. McKinsey tests problem-solving in the case interview, which the firm literally calls the Problem Solving Interview. The PEI is about people: how you lead them, persuade them, and respond when things go wrong. If you walk in with a “problem-solving story” for the PEI, you have prepared for a dimension that does not exist and shortchanged the four that do.

How to Prepare for the McKinsey PEI

Start early, because good PEI stories come from reflection, practice, iteration, not from a template you fill in the night before. Go through your resume and pull out the moments that genuinely show leadership, connection, growth, and drive. Those moments are your raw material.

What Makes a PEI Story Strong

Pick moments with real friction: a conflict, a setback, a person who pushed back, a deadline that looked impossible. Stakes and tension are what let you show character. And pull from across your life, not just university. A range of work, extracurricular, and personal stories signals range as a person.

Prepare Two Stories per Trait

Build two distinct stories for each trait. You need the backup because most offices will not let you reuse a story, and you may get asked about the same trait by two interviewers. For Leadership, for example, keep one story from a formal role and one where you led without the title. Either can score top marks; what matters is the impact and how you carried it.

Build a Story Matrix

The cleanest way to organize all this is a story matrix. List your experiences down the side and the four dimensions across the top, then mark which story covers which trait. You will see your coverage and your gaps at a glance.

When you choose which stories to lead with, rank them on four things, in this order:

1. Fit: the story clearly demonstrates the target dimension.
2. Impact: you overcame a real challenge and the result mattered.
3. Range: your set spans different contexts (work, extracurricular, personal).
4. Recency: prefer the last few years, so it reflects who you are now.

How Detailed and How Long

A question I get constantly: how much detail, and how long should I talk? Cover the key beats yourself, before the interviewer has to pull them out of you. The PEI rewards depth over breadth, so go deep on one or two critical moments rather than skating across many.

When you hit those moments, slow down. Walk through the specific interactions, the decisions, and what was going through your head. A story built this way gives you roughly 8 minutes of material, and the interviewer fills the rest with questions.

Expect a lot of them, and expect them to be pointed: “What exactly did you say and why?” and “How did that make you feel?” are standard.

The SCORE Framework for Structuring PEI Stories

The PEI grades two things at once: what you did, and how well you tell it. Storytelling is not a soft add-on here. Consultants at McKinsey, BCG, and Bain live or die by their ability to make a recommendation land, so the firm screens for it early.

At StrategyCase, I built the SCORE framework from years of coaching to do exactly that. It keeps your story tight and, just as important, it maps onto how McKinsey interviewers actually probe. SCORE stands for:

• Situation: the context and your specific role, in a sentence or two.
• Complication: the challenge or conflict that made this hard.
• Outcome Expectation: what would have gone wrong if you had done nothing. This is what raises the stakes.
• Remedial Actions: the specific steps you took. This is the core of your answer and deserves about 80% of your airtime.
• End Result: the outcome and what you learned.

Open With a Tight Summary

Lead with a three-sentence headline version: Situation, Complication, and how you resolved it. That gives the interviewer the shape of the story and lets them steer you toward the part they care about. You stay in control while sounding responsive.

Then Expand With SCORE

If they want more (they usually do), expand into the full SCORE structure. Here is how it looks in practice.

Full-length McKinsey PEI Story

Julia is asked to describe a time she showed leadership. Her opening summary:

At my last company, we had to present a strategy document to the board. (SITUATION) My boss got sick the day before and could not run the prep, which put my whole department at risk. (COMPLICATION) I stepped in, ran the team, and we delivered a strong presentation the next morning. (RESOLUTION)

The interviewer is now interested and asks for detail. Julia expands, keeping the spotlight on what she personally did:

The story I would use here is about stepping into a leadership role without formal authority when a cross-functional team was very close to failing in front of senior leadership.

At the time, I was one of six product managers preparing for our biannual board meeting. This meeting mattered a lot because it was the main point in the year where the board reviewed the product roadmap, assessed whether we had delivered against our previous commitments, and decided how much funding each product area would receive for the following year.

My boss, Sarah, was leading the overall preparation. She was the person who had the full picture. Each of us owned one workstream, but she was the one making sure the story came together, that the numbers were consistent, that the strategic message was sharp, and that the deck did not feel like six separate updates stitched together at the last minute.

The team itself was very capable, but also quite different in style.

There was Mark, who was analytical and very detail-oriented, but became visibly anxious under time pressure. He owned customer retention and kept worrying that if his numbers were challenged, he would not be able to defend every assumption.

Jessica was newer to the team, very smart and hard-working, but less confident in board-level discussions. She owned part of the commercial model and had done good work, but she still needed guidance on how to translate the analysis into a clear executive message.

Abdullah was the opposite. He was calm, pragmatic, and very reliable. He did not seek attention, but he was someone I trusted to take on complex pieces quietly and get them done.

Priya was creative and very customer-focused. She had strong instincts on the product narrative and user pain points, but sometimes struggled to connect that qualitative view to the financial implications the board cared about.

Cory was the most difficult personality in the group. He was experienced, smart, and very protective of his own workstream. He had strong opinions and was not afraid to challenge others, which was valuable when used constructively, but under pressure it could become combative.

Finally, Elena owned operations and implementation risks. She was very structured and realistic, but she tended to hold back in group discussions unless someone explicitly invited her in.

So it was a strong team, but not naturally aligned. Sarah had been the glue holding it together. (SITUATION)

The day before the meeting, Sarah got seriously sick and told us she would not be able to lead the final preparation or attend the board meeting the next morning. The impact was immediate. We had a deck, but it was not a board-ready deck. It was an 80% draft with six different voices, inconsistent assumptions, duplicated slides, missing transitions, and no clear top-down storyline.

The problem was not that people were not working hard. Everyone was working hard. The problem was that we had lost the person who was coordinating the whole effort, and without that coordination, the work actually started moving in different directions.

Within the first 20 minutes after the news, I could see the team fragmenting. Mark started going slide by slide through his appendix and saying, “I do not think we are ready.” Jessica was quiet and looked overwhelmed. Priya wanted to rework the customer story, which was directionally right but too big of a change for the time we had left. Cory pushed back hard and said we should not change anything anymore because “at this point, movement is risk.” Elena was trying to point out implementation gaps, but no one was really listening. (COMPLICATION)

My immediate concern was that if we presented the deck as it was, the board would not see the real progress we had made. They would see a misaligned team. And in that context, misalignment would be interpreted as weak product leadership, not as a preparation issue. That could have hurt our credibility and, more concretely, reduced our budget for the next year. (OUTCOME EXPECTATION)

I decided that someone had to step into Sarah’s role, and since I had a good grasp of both the product strategy and the commercial model, I took ownership.

The first thing I did was not to open the deck. It was to steady the team.

I said, “I know this is not ideal, but we are not starting from zero. The substance is there. What is missing is the storyline, the ownership, and the final alignment. We can fix that, but only if we stop debating everything at once.”

That helped lower the temperature a bit. Then I made the situation very explicit. I said, “For the next 24 hours, I suggest we optimize for one thing: a clear, credible board story. Not the perfect version of every workstream, but the version that gives the board confidence that we know where we are going.”

I also made clear that I was not trying to take over everyone’s content. I said, “You each still own your areas. I will take the role of stitching the story together, resolving trade-offs, and making sure we walk in with one voice.”

That distinction mattered because the team did not report to me. I needed people to follow voluntarily, not because I had authority.

After that, I asked everyone to give me 30 minutes alone. I used that time to build a simple plan. I reviewed the deck quickly and identified three issues. First, the storyline was not top-down enough. Second, the numbers were inconsistent across commercial, retention, and operations slides. Third, the speaking roles were unclear, which meant the board could easily expose gaps between us.

I then created a very simple war-room structure.

I split the remaining work into four priorities: storyline, numbers, risk narrative, and speaker preparation. I decided that I would personally own the storyline and final integration. I asked Abdullah to help Jessica take over my own workstream because I could not both lead the whole process and polish my individual section. I chose them deliberately. Abdullah was calm and could stabilize the execution. Jessica knew the commercial model and this was a chance for her to step up, but with support.

I told Jessica, “I know this is a stretch, but you understand the model better than you think. I do not need you to reinvent it. I need you to make the logic board-ready. I will give you the frame, and you can pressure-test the numbers.”

That visibly changed her energy. She went from passive to engaged because the task became concrete and because she knew she was not being left alone.

For Mark, I took a different approach. He was panicking because he felt personally exposed. I sat next to him and said, “Your work is solid. The risk is not that the board asks one detailed question. The risk is that we bury the message under too much detail. Let’s decide what you want them to remember from your section.” I cut his part from eight slides to three core slides and moved the rest into backup. That gave him more confidence because he no longer had to defend everything equally.

With Priya, I asked her to help strengthen the opening narrative. She had the best feel for the customer problem, so I said, “The board will care about the numbers, but they need to understand why this matters now. Can you help me make the first five minutes more customer-backed and less internally focused?” That gave her a clear role and made her feel included without letting the narrative drift too far away from the financial decision.

Elena was quieter, so I deliberately pulled her into the risk discussion. I said in the group, “Before we finalize this, I want Elena’s view on what could break in implementation.” She raised two important risks around capacity and launch sequencing that were not properly addressed in the deck. I added one slide that showed we had identified the risks and had mitigation actions already in motion. That slide later became one of the most important slides in the board discussion.

The hardest part was Cory.

In the first alignment session, he pushed back aggressively on several changes. He said we were weakening the message by simplifying it and that some of the commercial assumptions were “too optimistic.” The tone became tense, especially between him and Jessica, because Jessica had worked on those assumptions. I could see her shutting down.

I did not want to confront Cory publicly because that would have escalated the situation and made him more defensive. So I paused the discussion and said, “Let’s park this for ten minutes. Cory, can I quickly pressure-test something with you separately?”

In the one-on-one, I first let him speak. He explained that he was not trying to block the team, but he was worried that we were presenting a story that sounded cleaner than the underlying reality. That was a fair concern. So I acknowledged it directly. I said, “I agree with the principle. We should not over-polish the story to the point where it becomes fragile. But the current version has the opposite problem. It makes strong progress look messy. What I need from you is not resistance to the storyline. I need you to help me make the storyline defensible.”

That reframed his role. Instead of being the critic outside the process, he became the person responsible for making the story robust. I asked him to review the assumptions slide and identify the three places where the board was most likely to challenge us. He did that, and I used his input to strengthen the backup materials and adjust one claim in the main deck.

When we came back to the group, I also protected Jessica. I said, “Cory raised a good point on defensibility, and Jessica’s model gives us the right base. Let’s use both. We will keep the main message clear, but strengthen the assumptions in backup.” That helped both of them save face and re-engage.

Through the afternoon, I ran two structured alignment sessions. The first one was about content: what is the message, what are the numbers, what are the trade-offs? The second one was about delivery: who says what, what questions might come, and how do we avoid contradicting each other?

Between those sessions, I rewrote parts of the deck to make the storyline flow from market context to customer need, then product progress, then financial impact, then risks and funding request. I also created speaker notes for each presenter. I did not script people word for word because that would have sounded artificial, but I gave each person a clear message for their section, the transition into the next speaker, and the likely board questions they needed to be ready for.

That evening, I spent extra time with Jessica on the commercial model. I walked her through the logic and said, “Do not try to memorize numbers. Understand the two or three drivers behind them. If they challenge you, explain the driver, not the cell in the spreadsheet.” We practiced three likely questions, and by the end she could answer them clearly.

I also checked in with Mark again, not on the slides but on his confidence. I told him, “You are not there to prove you know every detail. You are there to give the board confidence that we understand retention and have a plan.” That helped him focus on executive communication rather than defensive detail.

By around 10 p.m., we had a much cleaner deck, but more importantly, the team had shifted emotionally. Earlier in the day, people were anxious, defensive, and working in silos. By the evening, everyone knew their role, the story was aligned, and the conflict had been converted into better preparation rather than personal tension.

The next morning, before the board meeting, I gathered the team for ten minutes. I said, “The goal today is not to pretend everything is perfect. The goal is to show that we understand the business, we know the risks, and we have a credible plan. Stay calm, answer what is asked, and if a question crosses workstreams, we support each other.” (REMEDIAL ACTIONS)

The meeting went very well. The presentation was much more coherent than the draft we had the previous day. The board did challenge us, especially on the commercial assumptions and implementation risk, but because we had prepared those points, we handled the questions cleanly. Jessica answered one of the model questions directly and confidently. Mark kept his section concise and did not get lost in detail. Cory helped defend the assumptions in a constructive way, and Elena’s risk slide gave the board confidence that we were not ignoring execution issues.

In the end, the board approved our roadmap and actually increased our budget for the following year. That was the clearest business result.

But the leadership result was just as important to me. We did not succeed because I had the best individual workstream. We succeeded because I was able to bring a diverse group of people back into alignment under pressure. I had to calm one person down, give another person confidence, channel a combative colleague into a constructive role, draw out a quieter teammate, and make the team feel that we were solving the problem together rather than protecting our individual pieces.

That evening, I took the team out for drinks. It was partly to celebrate, but also to close the loop emotionally because the previous 24 hours had been intense. I made a point of recognizing specific contributions from each person, not just saying “good job” generally. I thanked Jessica for stepping into the model, Abdullah for stabilizing the execution, Priya for sharpening the customer narrative, Elena for making the risks credible, Mark for simplifying his message, and Cory for pressure-testing the story.

For me, the main lesson was that leadership in a difficult moment is not about taking control of everything. It is about creating enough direction, trust, and emotional stability that capable people can do their best work together. In that situation, I had to be decisive, but also very tailored in how I led each person, because they each needed something different from me. (END RESULT)

This is a full-length PEI story designed to illustrate all elements of a strong Leadership narrative. For the other dimensions, I provide more concise, directional sample stories below for your reference.

Notice how little of that is about analysis and how much is about people and decisions. Also, notice the level of detail, the inclusion of names and individual examples. That is the balance and detail McKinsey wants to hear. Interviewers will still push hard (“What did this person say?”, “Why did you do it that way?”, “Why did you do that?”), so prepare a few lines for each beat.

Do that and you will sound prepared, not rehearsed.

The Four McKinsey PEI Dimensions in Depth

For each dimension below you get McKinsey’s definition, what to emphasize, the mistake that sinks most candidates, a quick SCORE sketch, and two concise example stories that you can build on. Treat the stories as scaffolding for your own, not scripts. In the room, interviewers spend 10 to 20 minutes on a single story and go far deeper.

Leadership (formerly Inclusive Leadership)

Definition. Leadership is your ability to lead a diverse group and make everyone feel valued and included. McKinsey describes it as “harnessing the power of diverse thinking to drive results” and “leading people with different backgrounds to create belonging where everyone can be at their best.” In plain terms: take a mixed group, get them aligned, and deliver a result.

You will usually be asked about “a leadership challenge you faced.” The wording varies; the trait does not. And you do not need a formal title. Informal leadership counts fully, like stepping up when a leaderless team is stalling. Here is what to show:

The mistake that sinks it. Hiding behind “we” most of the time. Occasional use of “we” is fine if it is part of the story, However, if every sentence is “we did this, we decided that,” the interviewer cannot tell what you did, which is the whole point. Name your actions. And do not forget the diverse-team angle; McKinsey renamed this dimension around inclusion deliberately, so make the makeup of your team and how you brought different people along part of the story.

Quick SCORE sketch. A college group project (Situation) where two members clashed over direction (Complication), risking a missed deadline and a poor grade for everyone (Outcome Expectation). You ran a session where both sides aired their case, found common ground, set clear owners and check-ins (Remedial Actions), and the team aligned, shipped on time, and scored well (End Result).

Leadership Example 1: Professional

I led a team of sales managers at a software company, all from different backgrounds, markets, and levels of seniority. On one high-stakes project, I needed input from all of them, but early on the discussion was dominated by the most senior and outspoken people, while others held back.

I first focused on understanding who I was dealing with. I spoke to the team as a group to surface the main issues, then had short one-on-one conversations with the quieter members to understand their perspectives, concerns, and working styles. This helped me see that some people had strong ideas but did not feel comfortable challenging the group directly.

Based on that, I adjusted how I led the team. In group sessions, I created a more structured discussion format where everyone had to contribute before we debated options. I also delegated work based on strengths and interests, not just job titles: one person with strong local market knowledge owned customer insights, another with analytical strength pressure-tested the numbers, and another who was close to the sales force gathered frontline feedback. Throughout the process, I kept collecting input, checking whether people felt heard, and making sure quieter contributions were built into the final plan.

My role was then to turn the different views into one aligned recommendation, give people credit publicly, and keep the working atmosphere constructive. We hit the goal, and the team came out tighter than it went in. The lesson stuck with me: on a mixed team, the leader’s edge is getting the quiet value out of the room, not being the loudest in it.

— Leadership story, professional context

Leadership Example 2: University

As a student, I led a project team building a marketing strategy for a local non-profit. We had people from marketing, communications, and social work, and early on the mix worked against us: no structure, no alignment, and many strong opinions about what the campaign should achieve.

I started by getting to know the team properly, not just their academic backgrounds. In our first group discussion, I asked each person what they thought the project needed to accomplish and where they felt they could contribute most. I then followed up individually with a few team members to understand what motivated them and where they were less comfortable. That helped me see that the marketing students wanted a sharper donor message, while the social work students were more concerned that the campaign would not misrepresent the community.

From there, I created a clearer working rhythm and divided responsibilities based on strengths and interests. The marketing students worked on positioning and donor messaging, the communications students shaped the campaign language, and the social work students tested whether the message felt respectful and credible for the community served. I also tailored my leadership style across the team: with some people, I had to give more structure and deadlines; with others, I had to create space and encourage them to challenge the first draft. In meetings, I made a point of asking for input before moving to decisions, so that the loudest voices did not automatically set the direction.

The hardest part was aligning the team around one message that worked for two very different audiences: donors and the community itself. By keeping the atmosphere open, mentoring people through their parts, and forcing the team to integrate the different perspectives, we produced a sharper strategy than any one subgroup would have created alone. The different backgrounds were not a box to check; they were the reason the work became good.

— Leadership story, university context

Connection (formerly Personal Impact)

Definition. Connection is your ability to influence and persuade people toward an outcome: reading where they stand, adapting how you communicate, and building enough trust to move them. The idea you are pushing can be unpopular, as long as it is right. And persuading someone does not require them to like you. When you get people genuinely on board, you build a durable way of working, not a one-time yes.

This matters in consulting more than almost anything. Consultants are not paid to hand over a slide deck; they are paid to change what a client actually does. Plenty of brilliant analyses die because no one was persuaded. For this dimension, pick a story where you won over a specific person, ideally someone senior or skeptical. Show that you:

• worked with a genuinely difficult or senior counterpart (demonstrates confidence);
• started by understanding their concerns, not by arguing;
• changed their mind with the right mix of evidence and communication for that specific person;
• built a lasting agreement, not a grudging concession.

Interviewers will press on three things: did you understand why the person felt the way they did, what exactly you did differently because of that, and how you kept your composure. Expect “why” after “why.” Remember that people are moved differently. Some want data, some want to feel respected, some just want a clear win for themselves. Reading which is the skill.

The mistake that sinks it. Turning it into a problem-solving story. If your answer is “I built a model that proved I was right,” you have failed the dimension. They do not care about the spreadsheet. They care how you understood the person and moved them.

Quick SCORE sketch. At a startup, you saw the marketing strategy was failing (Situation), which was flatlining growth (Complication) and threatening the company’s runway (Outcome Expectation). You set out to convince the CEO: you did the research, brought evidence, and, crucially, listened to their objections and pulled them into the solution instead of pushing yours (Remedial Actions). They bought in, the new strategy lifted engagement and revenue (End Result).

Connection Example 1: Business

As a consultant at an advisory firm, I worked on a project whose success depended on several senior client stakeholders backing our recommendations. The hardest was John, a senior executive with strong views and a long track record, who thought our strategy was wrong for his organization. Early on, our meetings were basically standoffs.

Instead of arguing harder, I changed approach. I first gave John room to lay out his objections fully, without interrupting or trying to win every point. I asked questions to understand not only what he disagreed with, but why it mattered so much to him. Over time, I realized his resistance was not just analytical. He was worried that our recommendation would make his previous decisions look wrong, create disruption for his team, and weaken his credibility internally.

That changed how I approached him. I stopped presenting the recommendation as “our answer” and started framing it around his priorities: protecting the organization, reducing implementation risk, and giving his team a path they could realistically support. I also used more data where he needed facts, but more empathy where the issue was trust. In private conversations, I acknowledged the validity of parts of his concern and made it clear that we wanted to build on his experience, not override it. That helped him save face and engage more openly.

From there, I made the process more collaborative. I brought him into selected working sessions, asked him where the plan would break in practice, and incorporated his strongest objections into the revised recommendation. As trust grew, the tone shifted from defensive to constructive. I ended up combining his perspective with ours into a stronger plan and implemented it together. The lesson: with a senior skeptic, listening first is not soft; it is the fastest route to yes.

— Connection story, professional context

Connection Example 2: University

In my social work graduate program, I was on a team designing a plan for a vulnerable community group. The split was sharp: our team lead, Jane, wanted immediate, direct aid, while the rest of us leaned toward a longer-term, sustainable fix. Her strong stance created real friction.

Rather than argue the point in the group, I sat down with Jane one-on-one to understand why she felt so strongly. I asked her what she was most worried would happen if we chose the longer-term approach, and it became clear that her position was driven by urgency and responsibility. She was afraid that a strategic plan would sound good on paper but leave people without help in the short term. I also noticed that she cared deeply about being taken seriously as the team lead, so pushing back too directly in front of everyone would only make her defend her position harder.

That helped me reframe the discussion. Instead of positioning it as short-term aid versus long-term sustainability, I framed it as a shared goal with two time horizons. I told her I agreed that immediate relief was necessary, but that we also had to prevent the same problem from repeating. This created a win-win: her priority became the first phase of the plan, while the rest of the team’s sustainability focus became the second phase.

In the next group session, I made the conversation collaborative rather than adversarial. I explicitly credited Jane for forcing us to consider the immediate needs more seriously, then asked the group how we could combine urgency with durability. That gave Jane a way to move toward compromise without feeling like she had lost the argument. Her urgency made the short-term piece better, and the broader structure made the solution last.

We landed on a plan everyone backed. What I took away was that persuasion is rarely about having the better argument from the start. It is about understanding what the other person is protecting, building trust, and creating an environment where they can change their mind without losing face.

— Connection story, university context

Growth (formerly Courageous Change)

Definition. Growth is how you handle change and ambiguity: do you adapt with energy and creativity, or freeze. Learning and the implementation of these learnings are core parts of this dimension. McKinsey wants a story where the ground shifted under you and you turned it into a result instead of an excuse. This dimension started life as “Courageous Change” and became “Growth” in 2025; given how fast the firm’s clients change, it is only getting more important.

What to bring out in the story:

Net: show that you adapted, found the opportunity in the mess, delivered, and brought others with you. As with every dimension, have two stories ready.

Quick SCORE sketch. You were leading a project at a large company (Situation) when you realized your initial approach was too top-down and did not reflect how the client organization actually made decisions (Complication), which risked weak buy-in and a poor implementation outcome (Outcome Expectation). Instead of pushing ahead, you took the feedback seriously, learned how decisions really moved through the organization, and adapted your approach with your team under time pressure (Remedial Actions). That learning made the revised plan much stronger, won stakeholder support, and kept the project on track (End Result).

Growth Example 1: Experienced Hire

I joined a new project in an area I had not worked in before, and I was asked to own a complex analysis under a tight deadline. At first, I approached it with the methods that had worked well for me in previous projects, but I quickly realized they were not enough for this context.

The first warning sign came when my initial output raised more questions than answers. The analysis was technically correct, but it did not isolate the real drivers of the problem. I had spent too much time building a broad, detailed view and not enough time identifying the few variables that actually mattered. It was uncomfortable because I was experienced enough to be expected to figure things out quickly, but in this case I had to admit that my usual approach was not working.

Instead of trying to polish the same analysis, I stepped back and treated the situation as a learning moment. I spoke with people who understood the topic better, reviewed prior project materials, and asked myself what decision the analysis actually needed to support. That helped me shift from trying to understand everything to finding the 20% of factors that explained most of the issue.

From there, I changed my approach. I rebuilt the analysis around the key drivers, cut out work that was interesting but not decision-critical, and focused on producing an answer that could guide action. I also started testing my logic earlier instead of waiting until the analysis felt perfect. That was a real adjustment for me, because my instinct had been to keep working until I had full confidence. In this case, the better move was to work with incomplete information, get feedback quickly, and improve the answer iteratively.

The final output was much stronger than the first version. It gave the project a clear direction and helped us focus on the actions that mattered most. The lesson for me was that growth is not just learning more content. It is recognizing when your default way of working no longer fits the situation, adapting quickly, and using the disruption to become more effective.

— Growth story, experienced hire learning under pressure

Growth Example 2: Intern or Graduate Hire

During an internship at a fast-moving startup, my main project was put on hold overnight when leadership shifted priorities. It was ambiguous and, honestly, deflating, because I had invested a lot of effort into the work.

My first reaction was frustration. I felt like the project had been taken away before I could prove myself. But I realized that staying attached to the old plan would not help me. So I tried to understand the shift instead of resisting it. I asked my manager what had changed, what leadership now cared about most, and where I could still create value.

That helped me reframe the situation. The project had not failed because the work was bad; the company simply had a more urgent priority. I learned that in a startup, priorities can change overnight, and the people who create value are not the ones who complain about ambiguity, but the ones who adapt quickly.

From there, I applied an 80/20 lens to my own work. Instead of trying to save the whole original project, I identified the few pieces that could still support the new direction. Some of the research I had done could help with the new priority, while other parts were no longer relevant. I had to let go of the sunk cost and focus my energy where it would actually move the needle.

I also used the disruption as a learning opportunity. I asked for a smaller workstream connected to the new priority, took time to understand the new business logic, and built a short update that translated my previous work into something useful for the team. I did not have complete clarity, but I learned to make a sensible next move, get feedback quickly, and adjust from there.

In the end, I became more useful to the company, not less. The lesson was that growth is not just about performing when the plan works. It is about staying positive, learning quickly, and finding a way to contribute when the plan changes.

— Growth story, intern facing an ambiguous situation

Drive (formerly Entrepreneurial Drive)

Definition. Drive is about results, initiative, and grit: spotting an opportunity, going after it, and pushing through the obstacles to get there. McKinsey cares as much about the journey as the outcome, the drive and creativity it took to turn an idea into something real. The best Drive stories show energy and ownership, ideally for something you started yourself rather than something you were assigned.

What to emphasize:

1. Initiative: you started something or spotted an opening others missed.
2. Drive: you hit setbacks and pushed through while managing multiple priorities at the same time.
3. Creativity: you solved it in a new way, not the obvious one.
4. Engagement: you are effective at getting others involved.
5. Impact: the result was real and impacted not just yourself, with numbers where you have them.

Authenticity does a lot of work here. Tell a real story, setbacks included, not a polished highlight reel. Interviewers will ask “why” repeatedly to test whether the motivation was genuinely yours, so be ready to explain your reasoning, not just your actions.

Quick SCORE sketch. You worked in your family’s small business (Situation) as it lost ground to bigger competitors (Complication), heading for more lost market share if nothing changed (Outcome Expectation). You researched the market, ran customer interviews, and launched a bolder, targeted campaign, hiring two people and building a fallback plan in case it missed (Remedial Actions). It worked, lifting recognition and sales, and taught you how to take a smart risk (End Result).

Drive Example 1: Launching a Community Initiative

I noticed that many children in my local community, especially from lower-income families, had very limited access to learning resources outside school. Their parents often could not afford private tutoring, and the schools had little capacity to provide extra support. Nobody had asked me to solve it, but I felt the gap was too visible to ignore.

The first obstacle was that I had nothing: no budget, no venue, no team, and no formal authority. I started by speaking with parents, teachers, and a few local community leaders to understand what the children actually needed. That helped me avoid building something too broad. The real need was not a full education program; it was a practical weekend format with tutoring, homework support, and basic learning materials.

From there, I pushed the idea forward step by step. I approached local businesses for small sponsorships and framed it as a concrete community investment rather than a vague charity request. I negotiated with a community center to use an empty room on Saturdays for free. To recruit volunteers, I reached out to university students and young professionals, but instead of asking for a large commitment, I created small, manageable roles: tutoring, organizing materials, helping with sign-ups, and communicating with parents. That made it easier for people to say yes.

There were several moments where the project almost stalled. Some sponsors said no, volunteer availability was inconsistent, and the first sessions were messy. I kept going by solving one bottleneck at a time. When attendance was low, I worked with teachers to identify families directly. When volunteers dropped out, I created a backup pool. When materials were missing, I asked local shops for in-kind donations instead of money. The solution became more creative because I had so few resources.

The program launched and grew to support more than 150 children over the first few months, with a volunteer base of around 20 people and donated materials from several local businesses. The impact was real, but the bigger lesson for me was personal: drive is not just working hard on something assigned to you. It is seeing an opportunity, owning it without permission, and pushing through enough practical obstacles to make the idea real.

— Drive story, community initiative context

Drive Example 2: Overcoming Product Launch Setbacks

At a startup, I was responsible for coordinating the launch of a new product feature that simplified online payments for small businesses. It was an important launch because we had already promised early customers a release window, and the feature was tied directly to our growth targets.

A few weeks before launch, we discovered a critical issue in the payment flow. In some cases, transactions appeared successful to the user but were not processed correctly in the backend. That was the worst possible type of bug: not always visible, but potentially damaging to trust. We could not ship it as it was, but delaying indefinitely would have hurt our credibility with early customers and slowed commercial momentum.

I took ownership of the problem rather than treating it as only an engineering issue. First, I worked with engineering to define the exact failure cases and separate critical launch blockers from smaller issues that could wait. That prioritization mattered because the team was under pressure, and trying to fix everything would have meant fixing nothing fast enough. I then created a daily launch war room with engineering, product, customer success, and sales, so everyone worked from the same facts and customers received one consistent message.

The creative part was the fallback plan. Instead of choosing between a risky full launch and a full delay, I proposed a phased rollout. I would first release the product to a smaller group of selected customers with close monitoring, then expand once the fix was stable. I also prepared a customer communication plan that was honest but controlled: I did not overpromise, but I showed that I was protecting their payment experience. Internally, that helped reduce panic because the team could see a path forward.

The final days were intense. I tracked open issues, escalated decisions quickly, kept stakeholders updated, and made sure the team stayed focused on the few actions that mattered for launch readiness. The bug was fixed, the phased launch went ahead, and we expanded successfully after the first monitored cohort performed well. The result was a stable release, positive feedback from early users, and preserved trust with customers. The lesson for me was that drive is not only intensity. It is ownership under pressure, creativity when the obvious path breaks, and the discipline to keep pushing until the outcome is real.

— Drive story, product launch context

If you want the different and longer versions of the McKinsey PEI plus many other fit answers, they are inside our Consulting Fit Interview Masterclass.

How to Deliver Your PEI on the Day

Good content is half the battle. Delivery is the other half, and it is very trainable.

Practice out loud with real interviewers. Run mocks with friends, mentors, or a coach, and have them interrupt and push like a real interviewer will. Reading your stories silently does almost nothing; saying them under pressure is what builds fluency. A coach who knows the McKinsey bar can also tell you exactly what to cut and what to add.

Build rapport in the first 30 seconds. Greet the interviewer warmly, make eye contact, and treat it as a conversation, not an interrogation. People score you higher when the room feels easy.

Speak with structure and conviction. Use SCORE so the interviewer can follow you without effort, cut the filler, and say things plainly. Confidence in delivery reads as competence.

Match detail to interest. Lead with the tight summary, then go deep only where the interviewer leans in. Enough detail to make it vivid, not so much that they lose the thread.

Stay composed under pressure. Expect curveballs and hard follow-ups; that is the interviewer doing their job, not a sign you are failing. Take a beat, answer honestly, and add an example if it helps. Handling the pressure well is itself evidence you can do the job.

Common PEI Mistakes (and How to Fix Them)

Most PEI failures come down to a short list of errors I saw again and again:

1. Underpreparing. Candidates pour everything into the case and wing the PEI. It shows immediately. Block real time for it.
2. Vague trait coverage. Stories that do not clearly hit a dimension leave the interviewer unable to score you. Use the story matrix to pick stories that land squarely on one trait. Compare your story with the instructions above to make sure it fits the specific McKinsey definition of each trait.
3. Telling a problem-solving story. Talk about the people, not the analysis or problem-solving: how you created the conditions for the team to win, or how you moved a person, not the model you built.
4. No structure. A rambling story buries your best moments. SCORE fixes this.
5. Too much detail. Drowning the interviewer in setup and context loses them before you reach the good part. Lead with the summary. Focus 80% of your airtime on the Remedial Actions of the SCORE.
6. No reps. Nerves and fumbling on the day almost always trace back to not practicing out loud. Do mocks.

McKinsey PEI: Frequently Asked Questions

The Bottom Line

The PEI decides half your McKinsey result, and it is the half most candidates leave to chance. It comes down to four traits: Leadership, Connection, Growth, and Drive. Prepare two real stories for each, structure them with SCORE, and keep the spotlight on what you personally did and the people involved, not the analysis. Do that and you will be in the small group that treats the PEI as seriously as the case, which is exactly the group that gets offers.

Related McKinsey Interview Guides

• The McKinsey case interview: the problem-solving half of your interview, weighted equally with the PEI.
• The McKinsey application process: the full process from resume, cover letter, and the McKinsey Solve game to the interviews.
• The McKinsey Solve Game Guide: How to ace McKinsey’s digital assessment.
• The SCORE Framework: the storytelling method behind every answer above.
• Consulting Fit Interview Masterclass: the full PEI and fit-interview prep program for McKinsey and other firms.

Master the McKinsey PEI Across All Dimensions

Strong stories are only the start. Interviewers also weigh your motivation, your judgment, and how you come across under pressure. As former McKinsey consultants, we help candidates turn real experiences into answers that hold up across all four dimensions.

Our 5-hour Consulting Fit Interview Masterclass covers the full PEI (Leadership, Connection, Growth, and Drive) and the wider fit interview. You get proven answer structures, ready-to-adapt templates, and full example stories, so you walk in prepared instead of hoping.

About the author: Florian Smeritschnig is a former McKinsey Senior Consultant and the founder of StrategyCase. He spent five years at the firm, evaluated candidates, and has since delivered 2,200+ mock interviews and coaching sessions, helping hundreds of candidates land offers at McKinsey, BCG, Bain, and other top firms. After coaching more than 200 candidates into McKinsey, he was ultimately removed from its alumni network in 2025 as a consequence.