Framework · Presence & career · 2 min read
STAR method
Situation, Task, Action, Result (+ Learning): a structure for telling leadership stories clearly in promotion cases, performance reviews, stakeholder updates and hiring conversations.
- SSituation
The context in one sentence: where, when, what problem.
"Three apps, four filter patterns." - TTask
What you were responsible for.
"Get one standard agreed." - AAction
What you did, step by step. Use "I". This is most of the story.
"I pre-met the strongest critic." - RResult
What changed. Quantify only what is true.
"All three teams adopted it." - LLearning
What you learned or would do differently.
"Now I pre-meet for every decision."
Use it when
- You write a promotion case or prepare for a performance review.
- You give a stakeholder update and want one concrete example instead of a list of activities.
- You prepare for a hiring conversation, or coach a designer to prepare for their own review.
How to use it
- Pick one specific episode. One real situation with real details, not "I usually…". Your Leadership log is the best place to find candidates. Output: one episode, with a rough date.
- Set the Situation and Task in two sentences. Where were you, what was the problem, and what were you responsible for? Keep it short; the listener only needs enough context. Output: two sentences of context.
- Tell the Action in detail. Say what you did, step by step, using "I", not "we". Include the hard part: who disagreed and how you handled it. Output: 3–5 concrete actions you took.
- State the Result, and add the Learning. What changed, for users, the team or the business? Quantify only what is true. Then add what you learned or would do differently. Output: one result and one learning.
- Build a small story bank. Keep a handful of STAR stories ready for different themes: influence, conflict, coaching, delivery. Coach your designers to do the same for their own reviews. Output: a list of stories, each a few lines long.
Worked example
A UX lead on an internal operations platform with 6 product teams prepares a story for a promotion case.
| Part | Story |
|---|---|
| Situation | Three apps used four different table filter patterns. Users who switched between apps made errors. |
| Task | I was asked to get one standard agreed across product teams. |
| Action | I collected examples from all three apps and showed them in a cross-team critique. I set up a DACI with myself as Approver and a design-system designer as Driver. I pre-met the product manager who disagreed most and changed the proposal to include her bulk-edit case. |
| Result | All three teams adopted one filter pattern for new screens within two quarters. Support questions about filtering went down. |
| Learning | Pre-meeting the strongest critic early saved a round of debate. I now do it for every cross-team decision. |
Watch out for
- "We" all the way through. The listener can't tell what you did. Say "I" for your own actions, and credit the team for theirs.
- A long Situation. If the context takes half the story, the Action gets lost. Two sentences are enough.
- Invented or inflated numbers. If you don't have a real number, describe the change in words. A wrong number destroys the story.
- A general story. "I always align stakeholders" is a claim, not a story. Tell one specific time.
Template
Copy this into your story bank and fill one block per story.
Theme (influence / conflict / coaching / delivery / ...):
Situation (1 sentence):
Task, my responsibility (1 sentence):
Action, what I did (3-5 points, use "I"):
-
-
-
Result (true numbers only):
Learning:
Source entry in my leadership log (date):
Saved only on this device.