Short Story With Wh Questions

The Practical Approach to Writing Short Stories Around Wh- Questions

Most people learn the six Wh- words in kindergarten. Who, what, where, when, why, and sometimes how. The idea that those six words could carry an entire narrative into a coherent shape is something you usually figure out later, after you've watched too many stories fall apart on the second act. A Short Story With Wh Questions is just a story where the skeleton is built from answers to those questions rather than characters or plot beats alone. It's a constraint-based writing method, which sounds pretentious until you realize it's mostly a scaffolding exercise. You aren't doing anything magical. You're just making sure you know what you're talking about before you start typing.

Why People Actually Use This Method

I keep coming back to it because traditional story planning often skips steps. Writers get excited about a character or an image and start writing. Two thousand words in, they realize the protagonist has no motivation and the setting keeps changing without anyone noticing. A Wh- question framework forces those things into view early. You write the answers down before you write the story. Not outline them. Actually write sentences like "the character is here because they need X" or "this event happens at 3am because Y." Those bare-bones answers become the load-bearing walls of the piece.

Setting Up the Framework Without Losing the Story

Here's the process, in the order that actually works for me.

1. Grab a blank page and write each Wh- word as a heading. Don't think about the story yet. Just set up the structure. 2. Under WHO, list every person (and non-person if relevant) in the story. One line each. Give them a desire and a lie they believe. That's it. "Maria wants to leave town. She believes she'll fail if she tries." Two sentences. That's the whole character so far. 3. Under WHAT, write the central incident. Not the theme. The thing that happens. "A package arrives with a dead phone inside." Specific beats general. General beats vague.

4. Under WHERE and WHEN, lock down the setting in sensory detail. One paragraph. Include at least two details that could cause a problem later. I always add a ticking clock element here too, even if it's subtle. "July. Heat. The air conditioning hasn't worked since Tuesday." That last sentence creates a constraint the story has to deal with. 5. Under WHY, write the motivation chain. This is where most drafts fail. Not the thematic why. The causal why. "She opens the package because the return address is her mother's handwriting, and her mother has been dead for four years." That's a chain. Follow it until it runs out. 6. Under HOW, describe the resolution mechanism. What actually changes? Not the emotional arc. The concrete change. "She calls the number on the back of the package instead of opening it." See the difference? One is a feeling. The other is a decision that moves the scene forward.

The First Draft Stage

Once the framework is done, you write the story. The Wh- answers live in the margins or on a separate doc. You don't paste them into the narrative. They serve as checkpoints. If you're stuck on a scene, go back and ask which Wh- question this passage is supposed to be answering. Most of the time it's not clear to you yet, which means the scene is wandering. I ran into a specific problem with this once that I still think about. I was writing a short story using the Wh- framework, and I had answers for all six categories. Everything looked solid on paper. Then I got to the third scene and realized the "why" answer and the "how" answer were contradicting each other at a fundamental level. The character's motivation required urgency, but the resolution mechanism was built around patience. They couldn't both be true in the same story. My workaround was simple and ugly. I deleted the "how" answer entirely, rewrote it from scratch, and then scrapped forty percent of the draft I'd already written. The constraint method didn't catch the error on its own. I caught it because the framework made the contradiction visible. That's the real value. Not that it prevents mistakes, but that it surfaces them before they compound.

Common Pitfalls Beginners Miss

The biggest mistake is treating the Wh- questions as a checklist instead of a lens. You'll fill in all six boxes, feel satisfied, and then write a story that ignores three of them. The framework is useless if you abandon it during the draft. A second mistake is making the answers too abstract. "Who: someone lonely" is not an answer. That's a mood. "Who: a man who waters his neighbor's plants while they're on vacation because he doesn't want them to die and he hasn't spoken to a human in six months" is an answer. The second one writes itself into scenes. A third mistake, and this one trips up experienced writers too, is over-indexing on WHY at the expense of WHAT. You'll build a mountain of backstory motivation and then have nothing happen in the story itself. The WHAT answer should be concrete enough that you can film it. If your WHAT answer requires a voiceover to explain, it's not concrete enough.

Advanced Nuance: How Wh- Questions Interact With Each Other

When I started using this method seriously, I noticed a pattern. The WH- answers aren't independent. They push on each other. Change the WHERE and suddenly the WHY shifts. Change the WHEN and the HOW might break entirely. That's not a bug in the method. That's the feature. I once had a story where the answer to "when" was a flood season. That single change invalidated three of my other Wh- answers. The why became irrelevant because survival replaced motivation. The how changed from a decision to an accident. The who lost their agency. The story I ended up writing was different from what I'd planned, but it was stronger because the framework forced me to revise the answers rather than ignoring the consequences of the setting change. This interdependence is what separates the constraint-based approach from a basic outline. An outline sits there. A Wh- question framework reacts to changes the way a real story does.

When This Method Fails Completely

I'm going to be blunt about this because people rarely admit it. The Wh- question framework is terrible for stories that are primarily atmospheric or lyrical. If your goal is to create a mood, explore a feeling, or paint a scene without much plot driving it, the framework will make your story worse. You'll spend more time filling in boxes than writing the story, and the result will feel mechanical because it is mechanical. It's also weak for ensemble pieces with more than five major characters. The WHO section becomes a phone book and you lose signal. I've seen people try this with large casts and end up with a story that reads like a Wikipedia article for a fictional town. If your story is plot-light or character-swathe-heavy, skip the framework entirely. Try a scene-by-scene approach instead or just write the first draft and carve structure in revision. There's no shame in that.

What to Do After the Draft

Take your finished draft and highlight every paragraph that doesn't connect to at least one Wh- answer. Not all paragraphs need to. A short story can afford a breathing room. But if you find a chunk where three or more paragraphs float free of the framework, read that section carefully. It might be beautiful. It might also be unnecessary. Decide based on what the story needs, not on what you love writing. Then do the reverse check. Look at each Wh- answer and ask if the draft actually delivers on it. Writers are bad at this. You'll write something vague and convince yourself it counts as an answer to "why." It probably doesn't. If the draft betrays your framework, you have two choices: revise the draft to match the framework, or revise the framework to match what the draft actually is. Both are valid. Just pick one deliberately.

A Working Template You Can Copy

Here's a minimal version of the framework I've used for years. It's not fancy but it works.

WHO: [character name] wants [specific goal]. They believe [specific false belief]. WHAT: [concrete event that disrupts normal life]. WHERE: [specific place with one problem embedded in the description].

WHEN: [time with a constraint — deadline, season, hour]. WHY: [causal chain that connects the character's false belief to the event]. HOW: [specific decision or action that resolves the story physically, not emotionally].

That's it. Fill in those six blanks. Write the story. Check your work. Move on. The reason this persists in my workflow isn't because it makes me a better writer overnight. It's because it prevents the kind of structural collapse that wastes three weeks of revision. A Short Story With Wh Questions isn't a shortcut. It's a stress test for your premise before you invest months in it.