Somebody Wanted But So Then: How to Teach and Use This Strategy

Somebody Wanted But So Then, often shortened to SWBST, is a summarizing strategy that forces a reader to compress an entire story into five short parts: the main character (Somebody), their goal (Wanted), the obstacle standing in the way (But), the action taken in response (So), and the outcome (Then). Instead of writing a full paragraph that can wander into plot details that do not matter, the strategy limits the writer to one clause per part, which makes it obvious when a reader has not actually pinned down what the story is about.

The strategy works because summarizing a story well is harder than it looks. A student can retell a story scene by scene without ever identifying the actual goal driving the main character or the specific obstacle blocking them. SWBST removes that option. If a student cannot state the character's goal in one clause, that gap shows up immediately instead of getting buried inside a longer, vaguer summary.

It also scales well. A picture book fits in a single SWBST sentence. A longer chapter book usually needs one sentence per major event or chapter, chained together, but the five-part structure stays the same throughout.

Each letter in Somebody Wanted But So Then maps to a specific question, and answering that question with a vague word instead of a concrete detail is the most common way the strategy falls apart in practice. Treating each part as a question rather than a label keeps the answers specific.

The five parts build on each other in order, so a weak answer early on, especially for "Wanted" or "But," tends to weaken everything that follows it.

The best source for a Somebody Wanted But So Then chart is the text itself, filled in while reading or shortly after, rather than reconstructed from memory days later. Waiting too long tends to produce a summary of what the reader remembers feeling about the story instead of what actually happened in it.

For longer books, filling in one chart per chapter or per major event, then reviewing them together at the end, catches inconsistencies that a single chart for the whole book would miss, like a goal that quietly changes partway through.

Somebody Wanted But So Then shows up most often in elementary and middle school reading instruction, but the situations where it actually helps are narrower than "use it after every story." It works best as a quick, low-pressure check on comprehension, not as a replacement for deeper literary analysis once students are ready for that.

Used at the right moments, it also doubles as a scaffold for students who struggle to organize a longer written summary, since the five-part structure gives them a starting sentence to expand from rather than a blank page.

Filling in a Somebody Wanted But So Then chart by hand for every assigned reading is slow, and it is usually the first thing students skip once a class moves past the early elementary grades. Notelyn's AI summary feature reads a PDF of an assigned text, a recorded class discussion, an uploaded audio file, or typed reading notes, and pulls out the same core elements the chart is built around: the main character, their goal, the obstacle, the action taken, and the outcome.

Because the summary comes from the actual source material rather than a guess at a typical plot shape, it reflects what is really in the text, including details a rushed hand-written chart might skip. From there, structured notes built around this five-part shape are easy to turn into other study material. Notelyn's quizzes feature can generate quick recall questions straight from the goal, obstacle, and resolution, and the mind map feature can lay the same elements out visually, similar to how a story map graphic organizer breaks a narrative into labeled parts, except compressed into the shorter SWBST shape.

The generated summary still needs a quick review before it counts as finished. An AI first pass can occasionally state a goal too broadly or miss which obstacle actually blocks the character, so checking it against the source and tightening any vague part is worth the extra minute. Once the chart looks right, running it through Notelyn's AI Q&A feature is a fast way to check whether you can recall each part without looking back at the text.

A handful of habits separate a Somebody Wanted But So Then chart that actually checks comprehension from one that is just filled in to satisfy an assignment. Writing a feeling instead of a goal for "Wanted" is the most common mistake, followed by an obstacle that does not actually connect to that goal, and a "Then" that describes what happens next in the plot instead of whether the original goal was met.

The fix for all three is the same: treat every part of the chart as a specific question, not a slot to fill with whatever comes to mind first. Read each finished sentence back and check that "Wanted" and "Then" actually connect, since a resolution that does not address the stated goal usually means the goal was written wrong in the first place. Used this way, the strategy stops being a worksheet exercise and becomes a genuine check on whether a story was understood. If you want a fuller breakdown of a narrative's parts rather than a five-sentence compression of them, our guide to the story map graphic organizer covers the longer version of the same idea.