Build a Story Bank: Eight Stories That Cover Most Fit Questions

Fit questions arrive in many costumes: "tell me about a time you led," "describe a disagreement with a colleague," "what is your biggest failure." The pool of experiences underneath them is small. Candidates who prepare by writing a separate answer for every question end up with thirty thin answers they cannot remember under pressure. Candidates who build a small bank of strong stories, and learn to point each one at different questions, tend to sound more natural and hold up better under follow-up.

This post covers how to choose eight stories, how to structure them, how to map them to competencies, and how to test whether they are ready. It pairs with the PEI story buckets post, which explains the three categories McKinsey's Personal Experience Interview probes. The bank below includes stories for those three and adds five more that firms commonly explore in fit conversations. Two questions sit outside the bank: "walk me through your resume" and "why consulting." Each needs its own prepared answer, and the post linked at the end covers the second.

Why eight

Eight is the target and six is the minimum. It is few enough that you can know each story deeply, with names, numbers, and the moment it got difficult. It is enough that you can avoid using one story for every question. If only six survive testing, go with six and keep looking for the other two; fewer than six leaves too many questions pointing at the same story. In a long interview day with several conversations, reusing the same story makes you look narrow, and a second story is insurance when an interviewer probes the first one to exhaustion.

The eight stories

1. The team you led through an obstacle. A time you led a team or an effort when something real got in the way. It needs specific people, a decision you made, and at least one person who disagreed.
2. The person you brought around. A time you changed someone's mind when you had no authority over them. It needs your understanding of their position, not just your argument.
3. The thing nobody asked you to start. An initiative you took without a mandate, where there was real downside if it failed. It needs something that did not exist before you.
4. The failure you own. Something that went wrong where you were responsible. It needs you to say what you got wrong and what you changed afterward.
5. The disagreement that got real. A conflict with a colleague or teammate that was not a caricature. It needs respect for the other person's view.
6. The result you helped deliver. A team outcome where you were not the leader. It needs your specific contribution and what the team needed from you.
7. The messy analytical problem. A time you reached a decision with incomplete or conflicting data. It needs the numbers, the judgment call, and what happened.
8. The line you held. A time you stuck to a principle or pushed through something hard, and it cost you something. It needs the cost.

If you are preparing for a PEI-style interview, stories one, two, and three line up with the leadership, personal impact, and entrepreneurial drive categories. The rest are stories that commonly come up in fit conversations.

A coverage map

Think of the bank as a matrix: eight stories down the side, the competencies they can serve across the top. The table below is that matrix in compact form. Each story has one lead competency and two that it can also cover.

Read the map two ways. Down the first two columns, every competency has a lead story. Across the third, most competencies also have a backup. That is the point: if you have already used story five for a conflict question earlier in the day, story two can handle the next one. Do not force a fit. If a story does not honestly answer a question, choose another.

Choosing your stories

1. Brainstorm widely. List fifteen or so moments from the last few years across work, school, volunteering, sports, a side project, or family responsibility. One line each.
2. Score them. Rate each from one to three on stakes (did something real depend on it?), your role (what did you personally do?), result (can you say what changed?), and recency. Recent stories are easier to recall, but a strong older story beats a weak recent one.
3. Fill the eight slots. Avoid using more than three from one setting, such as a single job. Avoid any story where the real work was done by someone else.
4. Be honest about the gaps. If you have no initiative story, find a small genuine one or start something real, as the PEI post suggests. Do not stretch a leadership story to fit. The failure and values stories are the usual sticking points; the next section helps with those.

Every story must be true. Interviewers probe, and a story you have embellished will break on the second or third question. A modest true story survives probing and an impressive invented one does not.

Finding the two hardest stories: failure and values

Candidates stall most often on the failure story and the values story, because the honest ones feel uncomfortable and the safe ones sound false. Mine the last year or two with specific prompts:

• For failure: a decision you would reverse, a deadline or deliverable you missed, a person you let down, or feedback that stung. Then ask what you personally did that contributed.
• For values or resilience: a time you disagreed with a plan and said so, declined a shortcut, took on something hard that nobody assigned, or kept going through a stretch that cost you sleep or standing.

A failure story is credible when it has three things: your share of the cause, stated plainly (not "the team missed it" or "I care too much"); a specific cost, such as a missed target, a client's lost trust, or a week of rework; and a changed behavior afterward that you can point to. A small real failure beats a dramatic invented one. A values story needs the same honesty: a real choice, and a cost to you that was not obviously rewarded.

Story anatomy: six beats

• Headline. One sentence that gives the answer: "I persuaded our regional manager to pilot a new scheduling process after he had turned it down twice."
• Stakes. Why it mattered, who was affected, and the scale. Keep to what is true and checkable.
• Tension. What made it hard, who disagreed, and what you tried first that did not work.
• Action. What you did, in order, using "I." This is the longest beat, because it is the one being evaluated.
• Result. What happened, with a number if a real one exists, including what did not work.
• Reflection. What you would do differently or what you now do because of it. Specific, not a slogan.

Here is what the notes for story two might look like. The details are illustrative, not a real candidate's, and the square brackets mark where your own true numbers would go.

• Headline: persuaded the regional manager to pilot a new scheduling process after he had turned it down twice.
• Stakes: weekend overtime, [number] store managers affected, staff complaining about short-notice shifts.
• Tension: he believed the current process worked and had been burned by an earlier pilot.
• Action: asked him what went wrong the first time, rebuilt the proposal as a four-week trial in two stores with an exit rule he set himself, and sent him the numbers weekly.
• Result: he approved a wider rollout; [what changed, and what the trial did not fix].
• Reflection: now starts with the objection before the proposal.

A full telling runs around three minutes. It also helps to have a short version of about a minute (headline, action, result) for questions that do not call for the full story.

Testing a story: three "and then what" probes

Tell the story to a partner, then have them ask three follow-ups of their choosing, drawn from probes like these: "And then what happened?" "What did you do, specifically, as opposed to the team?" "What did the other person say when you told them?" "How did you know it worked?" "What would you change?"

The story passes if each answer adds new specifics. These are the signs that it is not ready:

• You repeat the headline instead of adding detail.
• You slide from "I" into "we" as soon as the details matter.
• You cannot recall a number, a name, or something someone said.
• Your answer to "what would you change" is a disguised compliment, such as "I would have worked even harder."

If a story fails, go back to the memory and write down everything you can recall. If little comes, replace it. A story you cannot probe is not an asset.

Using the bank in the interview

Listen for the competency the question is really asking, pick the lead story, and fall back to the backup if you have used the lead recently. Begin with the part of the story that answers the question. The same story told for a conflict question emphasizes the disagreement; told for a leadership question, it emphasizes the decision. A short pause before you answer is fine. Resist the pull to tell your proudest story when it does not answer the question you were asked.

When you rehearse, do not rehearse each story in order. Have a partner pick random questions from a list and make you choose the story on the spot. Pivoting is the skill you need on the day, and only random questions train it.

Getting started

Block an afternoon to do the brainstorm and the scoring, and spread the testing across a couple of weeks of mock interviews. Your first draft of the bank will not be your last, and that is the point of testing it.