Choose an experience with a decision to explain
A strong personal example gives you something to explain about your own judgement. The organisation's reputation or the size of the project does not establish your contribution. Choose an experience where you faced a real choice, worked through a difficulty and can describe what you did with enough detail to answer follow-up questions.
Start with the question you are being asked. A story about delivering a successful project may contain little evidence of influencing someone who disagreed. A story about conflict may show poor listening if you cannot explain the other person's concern. Keep several examples available and choose the one whose events actually address the prompt.
Meaningful examples can come from employment, research, volunteering, student activities or personal responsibilities. What matters for preparation is that you remember the situation accurately, understand your decisions and can discuss the result honestly. Avoid inventing an experience to fit a theme.
Give the listener enough context to understand the stakes
Explain the situation, your responsibility and the obstacle in plain language. The listener needs to know what you were trying to achieve and why the task was difficult. They rarely need a complete history of the organisation or a specialist explanation of every system involved.
For a fictional student event, the candidate could say, "I was responsible for volunteer scheduling for a weekend event. A week before it began, several volunteers withdrew, leaving two activity rooms without cover. We had to maintain supervision without increasing the budget." The listener knows the candidate's responsibility and why the scheduling problem was difficult. The candidate can now explain how they dealt with it.
Explain the choices inside your actions
"I communicated with stakeholders" says little about what happened. Describe whom you spoke with, what you learned, the alternative you considered and why you chose a particular action. If someone resisted, explain their concern fairly. Your answer becomes more credible when the other people in the story have understandable reasons for their behaviour.
Explaining the scheduling decisions
"I asked the room leads which activities required trained volunteers and which could move. One lead opposed combining rooms because of noise. I proposed moving the quieter session to an unused morning slot, checked the attendance impact with its organiser and revised the rota. I then contacted volunteers with specific shifts rather than sending a general appeal."
The fictional sequence explains how the candidate adjusted the schedule after learning what the room leads needed.
Use "I" for actions you owned and "we" for work the team did together. If you contributed analysis but someone else made the final decision, say so. Clear boundaries make your contribution easier to assess and give you a sound basis for detailed follow-up questions.
Distinguish a result from a claim about causation
State the result you can support. "Every room had the required cover and the event ran on the revised schedule" is an observable outcome. "My leadership increased satisfaction by 40%" requires reliable measurement and a basis for attributing the change to your actions. Use a number when it is meaningful and known; do not add one simply because interview advice says every story needs a metric.
Separate what happened, how you know and what remains uncertain. If adoption is the only observed outcome, describe adoption rather than assuming it produced savings. If the project continued after you left, explain which results you personally observed. A mixed result can still support a useful story when you take responsibility and explain what you learned.
Prepare for follow-up questions
Build a short outline and practise answering questions about it. Why did you choose that approach? What did the other person say? What alternatives did you reject? Which part was your responsibility? What would you do differently? Missing answers often reveal where a story is too vague or where you have compressed several events into a misleading sequence.
McKinsey's public guidance asks for detailed discussion of meaningful experiences, individual role and reasoning. Prepare enough detail to explain the decisions you made. Follow the current guidance for the employer and role you are applying to rather than treating one storytelling acronym as a universal script.
After a rehearsal, remove background that did not help the listener understand the decision. Add detail where your reasoning was unclear. Keep confidential names or sensitive figures out of practice notes when they are unnecessary; an accurate, general description can preserve the substance without identifying a person or project.
Practice question
Your team adopted a process you designed, but no reliable time-savings measurement exists. Which result is supportable?
Sources
The examples and exercises are written for CaseMentor. Interview-process information comes from the sources below. Check the employer's current instructions for your role.
- McKinsey personal experience interviews
Checked 14 October 2026. McKinsey asks candidates to discuss meaningful experiences in detail, their own role and their reasoning. The guidance here is CaseMentor's original teaching material, not a firm scoring rubric.