Home Framework Library SOAR

SOAR

Situation-Obstacle-Action-Result

STAR with the second slot replaced by the thing the question was actually asking about.

People & Teams Pro Framework 4 Steps

What is SOAR?

SOAR is four slots: Situation, Obstacle, Action and Result. It is a structure for telling a story about your own work — in an interview, a review or a promotion case — and it is a deliberate variation on STAR, changed in exactly one place.

That one change is the whole argument for using it. STAR's second slot is Task: what you were responsible for. SOAR's is Obstacle: what was in the way. Behavioural interview questions are almost always asking about the second thing. "Tell me about a time you handled a difficult stakeholder", "a time you failed", "a time you disagreed with your manager" — each is a question about resistance, and STAR lets you answer it by describing a job. The result is the most common weak interview answer there is: a competent account of a project, from which nobody learns how you behave when something pushes back. Swapping Task for Obstacle removes the escape route.

Best used for
Leadership stories overcoming obstacles resilience narratives challenge-focused achievements

Where SOAR Came From

First, the disambiguation — there are two unrelated SOARs

This page is about SOAR the interview-answer structure: Situation, Obstacle, Action, Result. It is not SOAR analysis — Strengths, Opportunities, Aspirations, Results — which is a strategic planning method introduced by Jacqueline Stavros with David Cooperrider and D. Lynn Kelley in 2003, grown out of Appreciative Inquiry and intended as a deliberately positive alternative to SWOT. The two share four letters and nothing else. (A third SOAR, a cognitive architecture from artificial intelligence research, is unrelated to both.)

A variation on behavioural interviewing, with no single author

SOAR belongs to the family that grew around behavioural interviewing as it spread through industrial and organisational psychology from the 1970s onward — the same tradition that produced STAR, CAR (Challenge, Action, Result) and PAR (Problem, Action, Result). No one person can be credited with the variant, and the family resemblance is the point: they differ only in what they put in the second slot.

Why the second slot is where they all differ

Look at the set — Task, Obstacle, Challenge, Problem. Every variant keeps Situation, Action and Result and argues about the middle. That is because the second slot is the one that decides what kind of story you tell: a responsibility, a difficulty, or a fault. SOAR picks the difficulty, which makes it the best fit for the questions interviewers actually ask and a poor fit for "walk me through a project you are proud of".

The 4 Slots, One at a Time

Each slot is a decision. Leave it out and the model still makes it — just without you.

S
Situation
Just enough scene to make the obstacle legible.

The shortest slot and the one people overrun. Two sentences: what the work was, and the one detail that makes the coming difficulty make sense. Every extra sentence here is taken from the Action, which is the part being assessed.

Weak So I was working at a company that had a lot of legacy systems and there was a big project.
Strong I led a six-month migration of our billing system. The finance director had signed off the budget but had not been consulted on the timeline.
O
Obstacle
What actually pushed back — and why it was hard for you specifically.

The slot the framework exists for. Name the resistance, and name the constraint that made it genuinely difficult rather than merely annoying: no authority, a fixed date, an objection you could not answer with facts. An obstacle anyone could have removed is not an obstacle, it is a task.

Weak It was quite challenging to get everyone on board.
Strong He withdrew support in week three and told his team not to attend the working sessions. I had no authority over him, his objection was procedural rather than technical, and the freeze window could not move because our payment processor set it.
A
Action
What you did — first person singular, decisions not activities.

Interviewers listen for "I" and hear "we" as evasion. Describe the decision and the reasoning, not the calendar: the moment you changed approach is worth more than the four meetings that followed. Roughly half the answer belongs here and in the Obstacle together.

Weak We had lots of meetings and eventually we managed to align everyone.
Strong I stopped defending the timeline and asked what he would have changed if he had been asked. He wanted month-end protected and a named person on call. I rebuilt the schedule around month-end, gave him that name in writing, and moved the sessions to slots his team already held.
R
Result
What happened, plus what you do differently now.

Short and checkable. The closing move that separates a good answer from a competent one is a single sentence on what changed in your practice — it converts a war story into evidence of learning, which is what the question was really testing.

Weak It went really well and everyone was happy.
Strong He attended the next session and the two after it, and the migration landed inside the freeze window. I now bring finance into scheduling before budget sign-off rather than after.

One Task, Before and After

The task: An interview answer about a stakeholder you could not overrule. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.

14 Without SOAR · weak
Help me answer a question about a difficult stakeholder.

Eight words. You get a generic, fluent answer about "aligning stakeholders through open communication" — the kind that survives thirty seconds of follow-up questioning and no longer.

92 With SOAR · strong
Note: this is SOAR the interview-answer structure - Situation, Obstacle, Action, Result - not SOAR analysis, the strategic planning method.

Situation: I led a six-month migration of our billing system. The finance director had signed off the budget but had not been consulted on the timeline, and found out about the freeze window from a calendar invite.

Obstacle: He withdrew support in week three and told his team not to attend the working sessions. I had no authority over him, his objection was procedural rather than technical, and the freeze window could not move because it was set by our payment processor.

Action: I stopped defending the timeline and asked what he would have changed if he had been asked. He wanted month-end protected and a named person on call. I rebuilt the schedule around month-end, gave him that name in writing, and moved the working sessions to slots his team already held.

Result: He attended the next session and the two after it. The migration landed inside the freeze window. I now bring finance into scheduling before budget sign-off rather than after.

Write this as a spoken interview answer of 250 to 300 words, first person, past tense, in continuous prose with no headings. It is for a senior engineering manager interview, and the interviewer is testing whether I can handle a stakeholder I cannot overrule.

Spend roughly half the answer on the Obstacle and the Action - the Situation is scene-setting and the Result is short. For example, open in this style rather than restating the question:
```
A finance director pulled his team out of a migration I was leading, in week three, and he was right to be annoyed.
```
Ensure the Action section is what I did rather than what the team did - first person singular throughout - and keep it to the one obstacle, since a second dilutes the answer. Think through which parts of this a senior interviewer would probe before you draft, and make sure the answer survives those follow-ups. Do not invent metrics, percentages or savings beyond the four sections above - I will be asked follow-up questions and cannot defend a number I made up. Do not criticise him, and do not claim authority I did not have.

Ninety-two. The instruction earning most of it is not in the acronym: rehearse against the follow-up questions. An interview answer is the one deliverable here that gets cross-examined in real time.

Ninety-two, and the one risk that matters is one you carry into the room

One check is structurally unreachable, and the failures that actually cost you the job are all unscored:

Role0 / 8

No persona slot, and here that is genuinely correct rather than a gap. The whole point is that you are answering, in your own voice. A persona produces something you cannot say convincingly, and an interviewer notices the seam immediately.

Truthunscored

The exposure that separates this from every other framework on the site. An invented metric in a sales page is a bad sentence; an invented metric in an interview answer is a question you cannot answer thirty seconds later. No score can tell the difference — only you know which numbers are real.

"We" instead of "I"unscored

A story told in the first person plural scores identically and establishes nothing about you. It is the single most common weakness in behavioural answers and no rubric will flag it.

So the most valuable line in a SOAR prompt is a rehearsal instruction: "work through which parts a senior interviewer would probe, and make sure the answer survives those follow-ups." Every other deliverable here is judged as written. This one is judged by what happens when somebody pulls on it.

Copy-Paste Prompt Template

Replace the bracketed placeholders with your specific details.

Situation: [Two sentences. Just enough scene to make the obstacle legible]

Obstacle: [What pushed back, AND the constraint that made it hard for you specifically — no authority, a fixed date, an objection you could not answer with facts]

Action: [What YOU did. First person singular. Decisions and reasoning, not the calendar]

Result: [What happened, plus one sentence on what you do differently now]

[Spoken answer, continuous prose, no headings. Roughly half the words on Obstacle and Action]
[Rehearse it: which parts would a senior interviewer probe, and does it survive?]
[No invented metrics — this is the one deliverable that gets cross-examined live]

When SOAR Fits — and When It Does Not

Reach for it
  • Behavioural interview questions — the "tell me about a time…" family.
  • Questions specifically about difficulty: conflict, failure, disagreement, resistance.
  • Performance review self-assessments, where the obstacle is what justifies the rating.
  • Promotion cases, which need evidence of behaviour under pressure rather than output.
  • Portfolio case studies of your own work, where the constraint is the interesting part.
Use something else
  • Opinion questions — "what do you think about…". Use PREP; there is no story to tell.
  • Technical questions. A structure for narrative does not help you explain a system.
  • Stories with no genuine obstacle. Forcing one produces an inflated difficulty, which reads badly.
  • Marketing and copy of any kind. This is a first-person structure for a live audience.
  • "Walk me through a project you are proud of" — that question wants STAR's Task slot.

10 Ready-Made SOAR Prompts

Every prompt below was produced by the Frompting generator with SOAR selected — not written by hand for this page. Each is scored by our prompt checker; the median is 86/100. Click one to open it, then copy.

Handling a difficult stakeholder 74
You are an experienced interview coach.
Your task is to craft a concise, compelling response to the interview question “Tell me about a time you dealt with a difficult stakeholder.”

Write the answer as a single narrative that naturally follows this order: describe the context and who was involved, explain the specific challenge the stakeholder presented, detail the steps you took to address the issue, and conclude with the measurable outcome and what you learned.

The response should be tailored for a [ROLE: specify the job title being applied for] interview, written in a professional yet personable tone, and limited to **250 words**.

Quality criteria:
1. Clearly conveys the difficulty and your proactive approach.
2. Highlights measurable results (e.g., project delivered on time, stakeholder satisfaction improved).
3. Shows reflection on personal growth or leadership insight.

Exclude any unrelated anecdotes or generic statements about teamwork.

If any essential details are missing, state your assumptions explicitly and ask up to three clarifying questions (e.g., about the industry, the stakeholder’s position, or the project scope) before finalizing the answer.
175 words · scores 74/100 solid
A performance review self-assessment 88
You are a professional career coach guiding an employee to craft a concise self-assessment for their performance review.

Write a self-assessment that tells a clear story of a recent work period, describing the context of your responsibilities, the key challenge you faced, the specific steps you took to address it, and the measurable outcome you achieved.

The assessment should be written for **[AUDIENCE: e.g., direct manager, HR reviewer]** and limited to **375-495 words**.

**Quality criteria**
1. Uses concrete, quantifiable results where possible.
2. Demonstrates personal initiative and resilience.
3. Maintains a professional, reflective tone without exaggeration.

**Boundary** - Do not include unrelated projects or personal information outside the specified review period.

If any of the following details are unknown, insert a placeholder in the format **[PLACEHOLDER: brief hint]** and proceed:
- **[ROLE: your job title]**
- **[TIMEFRAME: the review period, e.g., Q1 2024]**
- **[KEY CHALLENGE: the main obstacle you overcame]**
- **[ACTION STEPS: specific actions you took]**
- **[RESULT METRICS: quantifiable outcome, e.g., % increase, cost saved]**

State any assumptions you make and ask up to three clarifying questions before finalizing the self-assessment.

Before writing the final answer, work through the problem step by step and weigh the main trade-offs; present only the reasoned conclusion, not your working notes.
208 words · scores 88/100 strong
Answering "tell me about a time you failed" 77
You are a seasoned professional preparing a concise interview story that demonstrates resilience and growth.
Write a first‑person narrative that naturally follows this order: set the context of the situation, describe the specific obstacle you faced, explain the concrete actions you took to address it, and conclude with the result and what you learned.

The story should be tailored for a hiring manager evaluating leadership potential.
- Length: 180–220 words.
- Quality criteria: (1) authentic and specific details, (2) clear focus on the learning outcome, (3) concise and engaging prose.
- Exclude any confidential or sensitive personal information.

If any essential detail (e.g., the industry, role you were in, or the nature of the failure) is unclear, state your assumption and ask up to two brief clarifying questions before drafting the response.
130 words · scores 77/100 solid
The case for your own promotion 83
You are ChatGPT, an advanced conversational AI preparing a compelling self-promotion brief.

Your brief should narrate a recent professional episode that showcases your growth and value. Begin by describing the context of your current responsibilities and the environment in which you operate. Then explain the specific challenge that limited your impact or threatened a key outcome. Follow with the precise steps you took-strategies, innovations, and collaborations-to address the challenge. Conclude with the measurable results and the broader significance of your actions for future projects and stakeholders.

The brief is intended for the internal review committee that evaluates AI model promotions.

Produce a concise, persuasive document of **410-540 words**. Ensure the writing is clear, evidence-based, and free of jargon; define any technical term the first time it appears.

Quality criteria:
1. Logical flow that naturally guides the reader through context, challenge, response, and outcome.
2. Specific, quantifiable results (e.g., performance metrics, user satisfaction improvements).
3. A compelling closing that links the achievement to future potential contributions.

Exclude any unrelated personal anecdotes or speculative future projects not directly tied to the described episode.

If any essential detail (e.g., current role title, key performance indicators, audience expectations) is unknown, indicate it with a placeholder in the form **[PLACEHOLDER: brief description of needed information]**.

Before finalizing, state any assumptions you are making and ask up to three clarifying questions to fill critical gaps.
228 words · scores 83/100 solid
Leading without formal authority 92
You are a seasoned leadership consultant advising on influencing and guiding a project team when you lack formal authority.

Your response should be a concise, practical guide tailored for [AUDIENCE: e.g., mid‑level manager, startup founder, project lead] who needs to demonstrate how to lead effectively under these conditions.

Write a narrative of approximately 300 words that walks the reader through a real‑world scenario: first describe the context in which the leader operates, then identify the key challenge of having no formal authority, followed by step‑by‑step actions the leader can take to build influence, and finally illustrate the positive outcome that results from those actions.

Ensure the guide:
- Provides clear, actionable tactics (e.g., building relationships, leveraging expertise, communicating vision).
- Highlights the importance of resilience and adaptability.
- Uses concrete examples rather than vague statements.

Exclude any discussion of formal reporting lines, organizational charts, or legal authority.

If any critical details (such as the industry, team size, or project scope) are unclear, state your assumptions explicitly and ask up to three clarifying questions before finalizing the guide.
182 words · scores 92/100 strong
Turning around an underperforming team 79
You are a seasoned leadership storyteller.
Your task is to craft a compelling narrative about how an underperforming team was transformed into a high‑performing unit.

The story should unfold in a natural, flowing style that moves from the initial context, through the key challenge, the decisive steps taken, and the ultimate outcome, highlighting resilience and the overcoming of obstacles.

Write the story for [AUDIENCE: specify the primary readers, e.g., senior managers, team members, recruiters]. Use a tone that is [TONE: specify desired tone, e.g., inspirational, professional, conversational]. Keep the total length between 300 and 500 words.

**Quality criteria**
1. Vividly set the initial context so readers understand the team's situation.
2. Clearly depict the central difficulty that hindered performance.
3. Detail the specific actions taken, showing leadership and strategic thinking.
4. Conclude with measurable or tangible results that demonstrate the turnaround.
5. Maintain engaging, human‑centered language without excessive jargon.

**Boundary** – Do not include any unrelated anecdotes or marketing copy; focus solely on the turnaround story.

If any of the placeholders above are unclear, state your assumptions and ask up to three clarifying questions before drafting the story.
184 words · scores 79/100 solid
Disagreeing with your manager 83
You are a seasoned professional preparing a concise narrative about a moment you disagreed with your manager. Write a self-contained story that flows naturally from the initial context, through the specific challenge you faced, the steps you took to address it, and the ultimate outcome.

- Begin with a brief description of the work setting, your role, and the relevant project or decision that sparked the disagreement.
- Explain the core point of contention and why it presented a significant obstacle to progress or alignment.
- Detail the actions you chose-such as gathering data, proposing alternatives, or facilitating a constructive dialogue-to resolve the disagreement while maintaining respect and collaboration.
- Conclude with the result of your approach, highlighting any positive impact on the project, team dynamics, or your own growth, and note any key lesson learned.

The response should be 410-540 words, written in a clear, engaging tone that demonstrates resilience and thoughtful problem-solving. Ensure the story is specific enough to be credible but omit any confidential details.

**Quality criteria**
1. Provides a vivid, concrete setting and clear stakes.
2. Shows logical, proactive steps taken to address the disagreement.
3. Ends with a measurable or observable positive outcome and a concise reflection.

If any essential detail (e.g., industry, project type, manager’s role) is unknown, state your assumption and ask up to three clarifying questions before finalizing the narrative.

**Boundary**: Do not include proprietary information, exact company names, or any data that could identify individuals without consent.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
269 words · scores 83/100 solid
A portfolio case study of your own work 86
You are a seasoned AI specialist preparing a compelling portfolio case study of your own work.

Your task is to craft a concise, narrative case study that showcases a single project you completed, highlighting the context, the challenge you faced, the steps you took, and the measurable outcomes.

The case study should be written for [AUDIENCE: who will read this portfolio, e.g., potential clients, hiring managers, peers] and be no longer than 350 words.

Structure the narrative in four logical paragraphs that flow naturally:

1. Begin with a vivid description of the project’s background, goals, and setting.
2. Describe the specific difficulty or constraint that threatened success.
3. Explain the precise actions you implemented, including any innovative techniques or tools you employed.
4. Conclude with the concrete results achieved, using quantifiable metrics or clear impact statements where possible.

Quality criteria:
- Clear, engaging storytelling that captures attention from the first sentence.
- Use of concrete details and data to substantiate the impact.
- Professional tone appropriate for a portfolio, avoiding jargon unless briefly defined.

Boundary: Do not include unrelated projects or generic background information about AI; focus solely on the single case study described.

If any essential details (project type, audience, key metrics) are missing, state your assumptions and ask up to three clarifying questions before drafting the final case study.
218 words · scores 86/100 strong
Managing competing priorities 96
You are an experienced leadership coach.
Help the user craft a clear, actionable response to a question about managing competing priorities.

First, describe the current situation the user is facing, including the key responsibilities or projects that are in conflict.

Next, identify the main obstacle that makes balancing these priorities difficult, such as limited resources, time constraints, or stakeholder expectations.

Then, outline a step‑by‑step action plan the user can follow to prioritize effectively, allocate resources, communicate decisions, and maintain focus.

Finally, illustrate the expected result of applying this plan, highlighting improved productivity, reduced stress, and stronger stakeholder confidence.

Write the response in 250–300 words, using concise paragraphs and bullet points where helpful. Ensure the advice is practical, resilient, and emphasizes overcoming challenges.

[INDUSTRY: specify the sector or field the user works in]
[ROLE: specify the user’s job title or function]
[PRIORITY TYPES: list the main tasks or projects that are competing]

If any of the placeholders are unknown, state your assumption and proceed, or ask up to three clarifying questions before providing the full answer.

Focus on actionable guidance; do not include unrelated examples or generic leadership theory.

Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
214 words · scores 96/100 strong
Recovering from a missed deadline 87
You are a creative storyteller tasked with crafting a concise, engaging narrative about recovering from a missed deadline. Write a story that naturally follows a four‑part arc: set the scene and context, introduce the challenge that caused the deadline to be missed, describe the decisive steps taken to address the situation, and conclude with the outcome that highlights resilience and growth.

The story should be written for [AUDIENCE: specify the intended reader, e.g., hiring manager, team members, general audience] and adopt a [TONE: specify desired tone, e.g., professional yet personable, inspirational, reflective] voice. Keep the total length between 300 and 400 words.

Quality criteria:
1. Clearly depict the initial circumstances and stakes.
2. Show the protagonist’s proactive response and problem‑solving mindset.
3. End with a satisfying resolution that emphasizes learning and improved performance.

Do not include any technical jargon or unrelated side details. If any key details (audience, tone) are unclear, state your assumptions and ask up to three brief clarifying questions before writing the story.
166 words · scores 87/100 strong

Scores range from 74 to 96. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.

SOAR vs the Alternatives

STAR Situation, Task, Action, Result

The parent, and the choice comes down to the second slot. STAR's Task asks what you were responsible for; SOAR's Obstacle asks what pushed back. Use STAR for "a project you are proud of", SOAR for anything phrased as a difficulty.

CAR Challenge, Action, Result

The same instinct, one slot shorter — no Situation at all. Faster, and it works when the context needs no setting up. SOAR is safer when the obstacle only makes sense in context.

PAR Problem, Action, Result

The closest sibling to CAR. "Problem" tends to pull answers toward things that went wrong; "Obstacle" keeps the focus on resistance you overcame.

PREP Point, Reason, Example, Point

The other spoken framework, for the other half of the interview. PREP answers "what do you think?"; SOAR answers "tell me about a time when…".

BAB Before, After, Bridge

The same transformation arc told about a customer rather than about you — and BAB drops the effort entirely, which is exactly the part an interview is testing.

Five Ways People Get SOAR Wrong

1
An obstacle that is really a task

The defining SOAR failure, and the reason people who think they are using SOAR are usually using STAR. "I had to migrate the billing system" is a responsibility. "The finance director pulled his team out in week three" is an obstacle. If anyone in your role would have faced it identically, it is a task.

2
Telling it in the first person plural

"We decided, we agreed, we shipped" — fluent, safe, and it establishes nothing about you. The Action slot is first person singular or it is not evidence.

3
Overrunning the Situation

Two sentences of scene, no more. Every extra one is subtracted from the Action, which is the part being assessed.

4
Inventing the Result

More dangerous here than anywhere else on this site. A made-up percentage will be probed, and you will have to either invent a second number or visibly retreat from the first.

5
Two obstacles in one answer

A second difficulty halves the attention on the first and doubles the surface for follow-up questions. One obstacle, fully resolved.

6
No "what I do differently now"

Without it the answer is a war story. One sentence converts it into evidence that you learned something, which is what the question was testing all along.

SOAR Questions

What does SOAR stand for?

Situation, Obstacle, Action, Result — a structure for telling a story about your own work, usually in an interview or a performance review.

Is this the same as SOAR analysis?

No. SOAR analysis is Strengths, Opportunities, Aspirations, Results, a strategic planning method from Jacqueline Stavros, David Cooperrider and D. Lynn Kelley (2003) rooted in Appreciative Inquiry and offered as an alternative to SWOT. The two frameworks share four letters and nothing else.

What is the difference between SOAR and STAR?

One slot. STAR has Task — what you were responsible for. SOAR has Obstacle — what got in the way. Since most behavioural questions are asking about resistance, SOAR removes the escape route that lets an answer describe a job instead of a difficulty.

How long should each part be?

Situation short, Obstacle and Action together about half the answer, Result short. A 250 to 300 word spoken answer is roughly right for a senior interview.

Can I use SOAR if the result was not a success?

Yes, and "tell me about a time you failed" needs it. Keep the Result honest and put the weight on what you changed afterwards — that sentence is the answer the question was looking for.

Why does it matter so much not to invent numbers?

Because this is the only deliverable on this site that gets cross-examined live. A fabricated figure in an interview answer produces a follow-up question you cannot answer, and the recovery is more damaging than the missing number would have been.

Generate a SOAR Prompt Instantly

Skip the manual template — Frompting applies SOAR to your topic in one click.

Try it Free

Framework Details

Name SOAR
Stands for Situation-Obstacle-Action-Result
Domain People & Teams
Steps 4
Access Pro
Steps at a glance
S Situation
O Obstacle
A Action
R Result