STAR-L — Situation, Task, Action, Result, Lesson
Adding a dimension of professional maturity to STAR by showing not just what was accomplished, but what intellectual and behavioural growth the experience produced.
Showing what the experience produced, not just what was done
Why it exists. STAR shows what you did. STAR-L shows what you became. Firms hiring for talent-development roles need to know whether a candidate builds on their experience.
What it does. Turns even a failure into a demonstration of professional value.
In which interviews. Questions about failures, manager or senior consultant roles, promotion interviews, contexts where you want to show growth between two periods of your career.
The "growth mindset" at the heart of the Lesson
The Lesson activates the "growth mindset" evaluation system (Carol Dweck): people able to draw lessons from their experience are seen as more developable and more resilient.
Entry-level version
Tell the same story as STAR, but add: "and here's what I learned from it and how I've changed the way I work since."
Senior consultant version
The most valued Lesson is the one that changes collective practice: you changed a method, trained a team, documented a process. It has to be anchored in the present ("since that experience, I..." followed by a recent example).
The 5 steps of the method
- SSituation — the context, dated and bounded.
- TTask — your personal role in the project.
- AAction — your decisions, in the first person, including the ones that led to the failure or the delay.
- RResult — the real impact, owned even if imperfect.
- LLesson — specific, already applied since, and producing a collective impact.
From a budget overrun to an architecture DACI
Question: "Tell me about a project you handled badly. What did you learn?"
Situation: in 2021, leading the rollout of a SAP S/4HANA ERP for an industrial group of 800 employees. Initial schedule: 18 months, a €2.4M budget.
Task: Project Manager on the integrator side — scheduling, coordinating the technical teams, the client relationship.
Action: applied a classic waterfall methodology, underestimated resistance to change and was late to involve key users in the configuration phases. At 12 months: 3 months behind schedule and a €400K overrun.
Result: the project was delivered 5 months late and €700K over budget. The client renewed the contract, but with a penalty clause.
Lesson: this experience settled it once and for all: change management isn't optional in an ERP rollout — it's a critical deliverable. Since then, 20% of the budget is systematically set aside for change support from the scoping phase onward, with fortnightly user workshops. Of the 3 SAP projects led since, none has overrun the schedule by more than 2 weeks.
Question: "What's the technical decision you regret the most?"
Situation: in 2019, architecting the data platform for a fast-growing e-commerce marketplace — 15 million events a day.
Task: Data Architect responsible for choosing the streaming stack's technology.
Action: chose Kafka on AWS MSK over Kinesis, based mainly on past experience, underweighting the "operational complexity for a team of 4 junior Data Engineers" criterion.
Result: 8 months later, the team was spending 40% of its time on Kafka maintenance, and two Data Engineers left. Migrating to Kinesis 18 months later cost 4 person-months.
Lesson: architecture decisions don't get made in a vacuum, even with experience. Since then, a documented DACI is used for every architecture decision, with one mandatory criterion: "can our current team maintain this in 2 years?" 6 junior architects have since been trained in this method at my current firm.
Freelance variant
STAR-L is particularly powerful in a first meeting with a new client: it shows you build on lessons from one engagement to the next.
Use the Lesson to demonstrate active learning: "That experience led me to train on [technology], which I now use in my engagements."
For large clients who outsource through freelance platforms, STAR-L reassures them about your ability to grow with no hierarchical structure around you.
Common mistakes
- ✕A Lesson that's too vague: "I learned that you need to communicate well" — worthless.
- ✕A theoretical Lesson with no grounding in practice — an unapplied lesson rings hollow.
- ✕A fake failure: "We delivered a bit late but the client was happy" — not credible.
- ✕Confusing a lesson with an excuse: "I learned that clients change their minds" — that's a complaint.
- ✕An example that's too recent, with no perspective to draw a real lesson.
- ✕No "since then, I..." — a lesson with no proof of application is worthless.
Quick checklist
- ✓The Lesson is specific and actionable (not a generality).
- ✓I can prove I've applied the lesson since.
- ✓The example is honest — I own my share of the responsibility.
- ✓The full answer fits in 3-4 minutes.
- ✓The Lesson creates a bridge to my current practice.
- ✓I've prepared an answer to the follow-up question: "And since then?"
Expert advice
Practical exercise
Turning an existing STAR into a STAR-L
Take 3 of your best STAR examples and add a realistic, actionable Lesson. Ask a colleague whether the lesson sounds credible and specific.
Failure-lesson role play
In pairs, simulate a question about a failure. The interviewer challenges the Lesson: "And since then, how exactly have you applied it?" Swap roles.
STAR-L in one sentence
STAR-L = STAR + proof of maturity. The Lesson has to be specific, already applied, and produce a collective impact. It's the format for questions about failures and for promotion interviews.
Want one-to-one support to prepare for your interviews?
An outside perspective to turn your experiences, failures included, into demonstrations of professional maturity.