In behavioral answers, what does the O beat in SOAR make explicit that STAR leaves implied?

## What SOAR is SOAR is a four-beat frame: Situation, O, Action, Result. It is worth knowing that the O is read two ways in common use — **Obstacle** and **Objective** — and that both readings do the same structural job: they replace STAR's Task beat with a statement of *stakes*. If you meet the acronym in the wild, expect either reading; if you use it yourself, know which one your story needs. (An unrelated planning acronym also spells SOAR; in interview-answer context it is the story frame.) Across the frames a candidate is likely to meet, this is the one that sharpens a beat rather than adding or removing one. Reflection frames add a beat at the end; three-beat frames remove one at the front; SOAR keeps four and changes what the second one carries. ## Task versus Obstacle versus Objective - **Task** (STAR) answers: what were you on the hook for? "I owned the release candidate." - **Obstacle** (SOAR) answers: what stood in the way? "Nobody owned the nightly regression run, so a red result blocked no one and everyone had learned to scroll past it." - **Objective** (SOAR) answers: what did winning look like? "A suite the team would actually believe, before the next release candidate." The Task beat is the weakest beat of STAR in practice, because a lot of candidates fill it with a restatement of the situation in the first person. Swapping it for an obstacle or an objective forces a new fact into the answer rather than a paraphrase of one already given. ## When SOAR is the better fit Reach for it when the difficulty carries the story: - The blocker was structural — no owner, no budget, no access, conflicting priorities — and the interesting part of your answer is how you got around it rather than what you built. - Two goals were in tension and you had to pick, which is exactly what an Objective beat sets up. - The work itself was routine but the conditions were not. Without an explicit obstacle beat, that story sounds like a description of ordinary work. ## When it is the wrong fit On a straightforward achievement story there is no obstacle worth a beat, and a candidate who reaches for the frame anyway either inflates a minor annoyance into an adversary or spends a beat on scene-setting that adds nothing. Interviewers notice inflation quickly, and it costs more credibility than the structure buys. If the honest answer to "what stood in the way" is "not much, it just needed doing carefully", use a frame without that slot. SOAR also has no reflection beat, so it is a poor answer to a backward-looking prompt. If someone asks `What would you do differently?`, an obstacle-forward story that ends on an outcome answers a question they did not ask — the difficulty is not the point, the change you made afterwards is. ## A worked comparison Take the same quality-assurance story and outline the second beat three ways on one page: - *Task:* "I was responsible for getting the release candidate out." — accurate, and nearly a restatement of the setting. - *Obstacle:* "The nightly run was red often enough that red had stopped meaning anything, and no single person owned it." — a new fact, and the one that makes the rest interesting. - *Objective:* "I wanted a nightly run the team would trust enough to block a release on." — a target the Result can be measured against. Read all three aloud to a mock-interview partner and ask which version made them want to hear the Action. That is a faster way to pick a frame than reasoning about acronyms. ## The practical takeaway SOAR is not a competitor to STAR so much as a diagnostic on it. If your Task beat is not pulling its weight — if it repeats the situation or states something the listener has already assumed — try stating the obstacle or the objective there instead. You may keep calling the answer STAR; the beat will simply be doing its job.