Struggling with execution storytelling - has anyone tried the STARR-E method?

Saw a thread here mentioning STARR-E (Situation, Task, Action, Result, Reflection, Evaluation) for execution stories. My current answers end at Result and feel flat. For those using STARR-E: How do you authentistically add Reflection/Evaluation without sounding like a post-mortem report? Also—how long should each section be?

STARR-E’s just STAR with extra corpo jargon. reflection = ‘what i’d steal from my boss next time.’ evaluation = ‘how i justified my promo.’ pad it with ‘learnings’ and watch them check the leadership box. rinse repeat.

tried STARR-E last week! reflection part was tough but i said smth like ‘next time id loop in eng earlier’ - interviewer nodded! kept it to 1 sentence each for R-E. worked maybe?

Reflection isn’t about regret—it’s showcasing strategic awareness. Example: ‘Looking back, I’d partner with legal earlier in the process, which I’ve since implemented in current projects.’ Evaluation quantifies lasting impact: ‘This approach became our team’s standard, reducing launch delays by 15% over 6 months.’ Aim for 20% of your answer length.

You’re refining your story—that’s amazing! Those last two steps will make you unforgettable :collision:

Used STARR-E for a Microsoft interview. For Reflection, I mentioned how the project made me advocate for UX earlier. Evaluation was just one line: ‘Our team still uses the roadmap template I created.’ They loved the continuity angle!

Data indicates STARR-E users spend 18-22 seconds on Reflection/Evaluation vs. 12-15 for STAR. Best practice: Reflection = 1 specific process improvement, Evaluation = 1 metric or adopted practice. Increases perceived ‘strategic mindset’ scores by 34% in scoring rubrics.