The STAR Method, and Where It Stops

What STAR is for

STAR organizes an answer into four parts. Situation, the context you were working in. Task, what you were responsible for. Action, the steps you took. Result, how it turned out.

It is a good structure, and for a large share of interviews it is the right one. It does two things well. It forces you to ground a claim in something that actually happened, and it lands on a concrete result rather than a vague impression. For individual contributor roles and early management roles, that is exactly what the interviewer needs. They are evaluating execution. Can you take a defined problem, own it, do the work, and deliver. STAR answers that, in order, without wandering.

If that is the interview ahead of you, STAR is enough. Use it well, and use it cleanly: one situation, clearly set; your task, not the team's; the actions that were actually yours; a result with a number in it wherever a number exists. Most weak answers are not weak on method. They go soft because the speaker blurs the task, narrates the whole team's action, or finishes without a result. Tighten those four parts and you have a strong answer for an execution interview.

This is not a case against STAR. It is a case about scope. The method is matched to a question. The only thing worth checking is whether your question is still that question.

What a clean STAR answer leaves out

Run a perfect STAR answer and notice where it ends. It has told the room what the situation was, what you were asked to do, what you did, and what resulted. It has not told the room why the situation mattered, which tradeoffs you were weighing, or what the logic behind your sequence was. STAR walks the listener through events. It does not surface the judgment underneath them.

Barbara Minto, the first woman hired as a consultant at McKinsey, named this shape decades ago. Her insight, taught at the firm for half a century, is that we think from the bottom up but should present from the top down. STAR is bottom-up by design. It builds across the situation, the task, and the action, and arrives at the point only at the result, the very end. For an interviewer checking that you can execute, arriving at the end is fine. The result is the thing they came for. For an interviewer weighing how you decide, the answer reaches the interesting part last, if it reaches it at all.

Here is the same moment, two ways.

Not this

"We were behind on the migration, so I split the team into two tracks, moved our two strongest engineers onto the integration risk, and we shipped three weeks late but with no rollback."

But this

"The real risk in the migration was not the deadline, it was shipping something we could not safely reverse. So I traded three weeks of schedule for a fallback we could trust, and here is how I moved the team to buy it."

The first is a competent STAR answer. Nothing is wrong with it. The second leads with the judgment and lets the events become evidence for it. To an execution interviewer, the first is enough. To a senior interviewer, the second is the answer, and the first is raw material.

When the question changes

The shift happens because the role does. Below a certain level, the organization is buying your execution. Above it, the organization is buying your judgment, because your judgment is now the thing that scales or fails across other people's work. The interview moves with the role. The surface question still sounds operational. The question underneath it is no longer whether you can do the work. It is whether you can see what the work is really about.

Research

In a 2017 Harvard Business Review study, Thomas Wedell-Wedellsborg surveyed 106 C-suite executives across 91 companies in 17 countries. 85% agreed their organizations were bad at diagnosing problems, and 87% agreed the flaw was expensive. His conclusion is that most leaders are not poor at solving problems. They are poor at working out what the problem actually is, because a bias toward action moves them into solution mode before the problem is understood. A senior interviewer has lived inside that pattern, which is why it is the thing they probe for. The test behind the test is not whether you can answer the question on the table. It is whether you can name the question underneath it. STAR was never built to do that. It begins after the diagnosis is already made.

The same direction shows up in what executive presence has come to mean. Sylvia Ann Hewlett's 2024 research finds that gravitas still rests on confidence and decisiveness, but pedigree now counts for less, while the capacity to think clearly under pressure and say it without armouring it in jargon has become the differentiator.

STAR answers the question. Judgment answers the question behind it.

What senior interviews test instead

If the senior room is listening for judgment, the answer has to lead with judgment and let the example carry it, not the other way around. In practice that means doing three things before you ever reach the story.

Frame

First

Name what the question is really about, at the level of strategy, before you touch the events.
Risks

Second

Say what the real pressures and tradeoffs were, including the one you misjudged.
Approach

Third

Give the logic of what you did and why in that order, not just the sequence of moves.

Then tell the story. This is where STAR returns, and where it belongs. Situation, task, action, result, told tightly, now doing a different job. It is no longer the answer. It is the evidence for a conclusion you have already stated. The room heard your judgment first, and is now watching you back it with something real.

That ordering is the four-beat structure at the center of Presence: Frame, Risks, Approach, Story. STAR lives inside the final beat. The full framework, and the research behind it, is laid out in the philosophy.

Presence does not replace STAR. It places it.

Which interview are you preparing for

This is the only question that decides whether STAR is enough.

If you are interviewing for a role where the room is evaluating whether you can execute, a defined scope, a clear deliverable, a result you can point to, then STAR is the right tool and you do not need more than it. Sharpen the four parts and walk in.

If you are interviewing for a role where the room is evaluating how you think, where your judgment is the thing being bought because it now governs other people's work, then STAR is where your preparation begins, not where it ends. You need a structure that leads with judgment and uses the story as proof. That is the work Presence is built for.

Experience gets you into the room. What the room does with you depends on which question it is asking, and on whether you walked in ready for that one.