Seven reasons a STAR answer still does not work.

1. The context takes over the answer

The interviewer needs enough background to understand the stakes, not the history of the company. Keep Situation and Task concise so the evidence sits where it belongs: in your actions and decisions.

2. “We” hides your contribution

Give the team credit, but make your own role assessable. Replace a sequence of “we did” statements with the decisions you owned, the people you influenced and the work you personally drove.

3. Action becomes a task list

A list of meetings and deliverables says little about how you think. Explain what you noticed, which options you considered, why you chose one route and how you handled resistance or risk.

4. The result is vague

“The project was successful” is a conclusion, not evidence. Use an honest business, customer, quality, speed or stakeholder signal. If no clean metric exists, describe the observable change without inventing a number.

5. Every story ends perfectly

A credible portfolio includes setbacks, conflict and imperfect outcomes. Interviewers often learn more from the correction you made and the lesson you applied later than from another uncomplicated win.

6. The story answers a different question

Do not select a favourite story and force it into every prompt. Listen for the competency being tested, then change either the story or the emphasis so the answer addresses the actual question.

7. The delivery sounds memorised

Prepare the logic and key evidence, not every sentence. Practise with changing follow-up questions so you can retrieve the story naturally rather than recite it.

A quick STAR answer checklist

1. Can the context be understood in two or three sentences?
2. Is your individual responsibility explicit?
3. Does the Action section explain decisions and trade-offs?
4. Is the result supported by credible evidence?
5. Can you answer likely follow-up questions?
6. Does the example answer the question asked?