SHARE: organize presentations with clarity

Situation, Hindrance, Action, Result, Evaluation: a story answer that ends with your judgment of it.

Last updated Oct 8, 2026

What & why

What it is

SHARE tells an experience and evaluates it in five parts. It suits interview answers, team reviews, and everyday reflection: Situation (the context), Hindrance (the obstacle that made it hard), Action (what you did), Result (what happened), and Evaluation (your judgment of it: what worked and why, what it showed you, or what you would change). The Hindrance beat names the difficulty explicitly, and the Evaluation beat adds reflection that most frameworks omit. This makes it well suited to questions that ask what you learned, what you would change or why something worked, including questions about failure, and to roles where judgment matters as much as the result.

Why it works

Separating the Result from the Evaluation helps listeners distinguish what happened from your judgment of it. Naming the hindrance makes your response easier to assess, and grounding the evaluation in a detail of the story shows how you reached it. A partial or unsuccessful result can still support a useful evaluation; reflection does not require a success story.

Before & after

These are fictional teaching examples, not accounts of real events.

Before

“The project was successful. I learned a lot from it.”

After

“We were opening our first shop in a new city (Situation) with nobody on the team who knew the area (Hindrance). I hired two local staff before opening and planned the first month's events with them (Action). We reached our first-year sales target in nine months (Result). Local staff knew which events would draw people, so hiring them before opening was the right call, and I now bring local staff into planning from the start (Evaluation).”

See it in action

An original teaching example. The situations and results are fictional.

Tell me about a time you learned from organizing something.

Situation

I arranged a beginner photography walk. I had picked three locations because each offered a different kind of light, and I thought the variety would keep people interested.

Hindrance

My route left little time for people to stop and practice. At the first stop, several people were still trying a technique when I was ready to move on.

Action

I dropped the final location and spent longer at the first two, so people had time to compare shots and try again after feedback.

Result

Everyone tried the planned exercises, but we covered less ground.

Evaluation

Cutting a stop was the right trade-off: for this group, time to practice mattered more than variety. I would plan fewer stops from the start.

How the answer works

Situation: Set the scene for the experience.
Hindrance: Make the barrier or difficulty explicit.
Action: Describe the response to that hindrance.
Result: Report what actually happened.
Evaluation: Interpret the experience: what worked, what did not, or what to change.

Why it works: The Evaluation judges the decision by what the result showed, then says what to change.

Start lesson See all examples

When you’ll use it

Senior-level and executive interviews

Leadership and management position interviews

Questions about failures and lessons learned

Behavioral questions requiring reflection and growth

Reflecting with a team on what worked, what failed, and what to change

Pro tip

Set the scene, name the barrier, say what you did and what happened, then judge it.

Questions & answers

When should I use SHARE instead of STAR?

Use SHARE when the question asks for your judgment: what you learned, what you would change or why something worked. Roles that value reflection, such as leadership, teaching or care, ask for this often. When nobody asks for a judgment, STAR, SOAR or CAR is enough.

What makes a good evaluation in SHARE?

A good evaluation grows out of your story: what worked and why, what the experience showed you, or what you would do differently. It does not need to start with 'I learned'. Keep it in proportion to what happened, and avoid generic lines like 'I learned teamwork is important.'

Is SHARE too long for most interview answers?

SHARE can run longer, so be concise in each section. The evaluation can be brief: even one sentence shows reflection. If time is short, shorten the setup rather than dropping the evaluation.