So, you want to write a story.

Where Do Ideas Come From?

People ask this like there's a vending machine somewhere. There isn't. Ideas come from paying attention to your own life — the boring parts too. The argument you overheard at the bus stop. The thing your auntie said that made the whole table go quiet. The smell of your grandmother's kitchen that you'd recognize blindfolded. That's the vending machine. You've been standing in front of it your whole life.

The "What If" Trick

Most stories start with a question, not an answer. Take something true and ask "what if" until it turns into fiction:

• What if that argument at the bus stop had happened twenty years earlier — or twenty years later?
• What if the thing your auntie said was actually a secret she'd been holding for thirty years?
• What if your grandmother's kitchen was the last place that still felt like home, after everything else changed?

You're not making things up out of nothing. You're taking something real and turning the dial.

Build an Idea Catcher

You will lose a good idea if you don't write it down. Not "might" — will. Keep a notes app, a small notebook, whatever. The goal isn't to write full scenes. It's to catch the spark before it gets away:

• A line of dialogue you overheard that stuck with you
• A "what if" question, even an unfinished one
• A character who showed up in your head fully formed, with no story yet
• A feeling you want a reader to feel, even before you know the plot
• A place — real or imagined — that you can picture clearly

Some of these will sit in your idea catcher for years before they're useful. That's fine. They're not going anywhere.

Research Before You Write (Yes, Even for Fiction)

Here's the thing nobody tells beginning writers: fiction still has to be true. Not factually true — your characters can do things that never happened to real people. But the details have to hold up, or readers who know better will stop trusting you on page one. And once a reader stops trusting you, they stop believing the emotional stuff too.

What Actually Needs Checking

You don't need a PhD before you write a sentence. But a fast check on these things will save you from small mistakes that pull readers right out of the story:

• Time and place details. If your story is set in 1985, your character can't text anyone. If it's set in St. Kitts, your character isn't seeing snow.
• How things actually work. How long does it really take to drive from one place to another? What does a real classroom, kitchen, courtroom, or hospital actually sound and smell like?
• Cultural and historical accuracy. If you're writing about a community, era, or experience that isn't your own, a little research is the difference between "this writer did their homework" and "this writer guessed."
• Sensory specifics. What does sugar cane smell like when it's burning in the field? What does the inside of a conch shell actually feel like? Specific beats vague, every time.

The second version took maybe two minutes of "let me picture this / let me look this up" — and it does ten times more work.

How to Research Without Falling Into a Hole

Research can eat your whole afternoon if you let it. Here's how to keep it from becoming procrastination wearing a productivity costume:

• Write first, flag questions as you go (drop a placeholder like [CHECK: bus routes in 1980s Basseterre] and keep moving)
• Batch your research — go back later and look up everything you flagged at once
• Use real sources: oral histories, documentaries, people who lived it, reputable archives — not just the first blog post that pops up
• When writing about real cultures, places, or historical events, ask: would someone from this place or time read this and feel respected, or feel like a costume?
• Give yourself a time limit. Twenty minutes of research, then back to the page.

Write What You Know

"Write what you know" gets a bad reputation because people hear it as "only write your autobiography" — which is not what it means. It means: your specific, lived experience is material nobody else has. Your neighborhood. Your church. Your family's particular way of arguing, loving, eating, grieving. That specificity is what makes fiction feel real, even when the plot is completely made up.

What "Knowing" Actually Includes

• Places you've lived or visited — the actual texture of them, not the postcard version
• How people around you talk — the rhythm, the phrases, the things that get said and the things that get left unsaid
• Emotions you've felt — even if the situation in your story never happened to you, the feeling underneath it probably has
• Small, specific rituals — how your family does Sunday dinner, what happens at a wake, how a classroom actually feels at 2:45 on a Friday

You don't have to have lived through exactly what your character lives through. You just have to know what fear, hope, embarrassment, or love feel like in your own body — and then put your character's body through it.

Writing Outside Your Own Experience

Sometimes the story needs you to write about something — a place, a time period, an experience — that you haven't personally lived. That's where chapter two comes back in. Research it, talk to people who have lived it if you can, and write it with care rather than assumptions. The goal is always the same: specific over generic, true over guessed.

Write What You Want to Read

This is the flip side of "write what you know," and honestly, it might matter even more. Think about the book you wished existed when you were younger — the one with a character who looked like you, talked like your family, lived somewhere that felt like home instead of somewhere you only saw on TV. If that book didn't exist, you get to be the person who writes it.

This isn't about being selfish with your story. It's about trusting that if you wanted this story, somebody else out there has been wanting it too — they just didn't know how to ask for it.

Questions to Find Your "Want to Read"

• What book did you read over and over as a kid — and what did you love about it?
• What's a story you've read that almost got it right, but you wish had gone differently?
• What kind of character do you wish you saw more of — not as a sidekick, but as the lead?
• What setting feels like home to you that you rarely see in books?
• What would make you, specifically, pick this book up off a shelf?

If you can answer even one of these honestly, you've got the seed of a story that has your fingerprints on it — which is the only kind of story worth spending months (or years) writing.

Make It Look, Sound, Feel, Smell, and Taste Real

Here's a test: read back over your last paragraph and ask, "could a reader picture exactly where they are right now?" If the answer is "sort of, I guess," that's where the senses come in. A reader can't see inside your head. They only get what's on the page — so the page has to do the work your imagination is already doing for free.

You don't need to hit all five senses in every paragraph (please don't — that gets exhausting fast). But most beginning writers lean on sight only, and forget the other four exist. Here's what each one can do for your writing:

From Generic to Specific

Notice the second version isn't longer for no reason — every detail is doing something. It's placing us in time (radio, signal cutting out), in feeling (the sting of the sand), and in a specific place rather than "generic beach."

One Sense, On Purpose

A quick exercise: take a scene you've already written and add one sensory detail that isn't sight. Just one. Smell is usually the most powerful, because it's the sense most directly wired to memory and emotion. Watch what it does to the whole paragraph.

Figurative Language (Without the Cringe)

Similes and metaphors are tools for making the unfamiliar familiar, or the familiar feel new again. Used well, they make a reader go "oh, I know exactly what that's like" — even about something they've never experienced. Used badly, they make a reader stop and think about the writer instead of the story. That's the line we're trying to stay on the right side of.

The Cringe Zone (And How to Avoid It)

• Mixed metaphors. "Her heart was a rollercoaster, sinking like a stone into deep water." Pick one image and stay in it.
• Clichés dressed up as fresh. "Her eyes were like pools" has been written approximately one billion times. If a comparison feels familiar to you, it'll feel familiar to your reader too.
• Comparisons that don't fit the character or scene. A twelve-year-old probably isn't thinking "the silence was a held breath, pregnant with possibility." A twelve-year-old is thinking "the room got weird, fast."
• Too many, too close together. One strong image lands. Three in a row starts to feel like you're trying too hard.

Where Good Figurative Language Comes From

The best comparisons usually come from your character's world, not yours. A fisherman's kid is going to describe fear differently than a kid who grew up in an apartment in the city. Let your characters' backgrounds shape their metaphors:

The second version isn't just less of a cliché — it tells us something about where this character is from, for free.

A Simple Test

Before you keep a simile or metaphor, ask:

• Have I read this exact comparison before, in roughly this form?
• Does this image come from my character's world, or just from "writing voice" in general?
• Am I using this because it's the truest way to say this — or because it sounds "writerly"?
• Could I cut this and lose nothing?

If a comparison fails that test, it's okay to just say the plain thing. "She was scared" is not a failure. Sometimes plain is exactly right, and saving your one big image for the moment that really needs it makes that moment hit harder.

Get Into Your Character's Head

This is the part that separates "a story happened" from "I felt like I was right there with them." Your reader needs to know not just what your character does, but why — what they're thinking, what they're scared to say out loud, what they notice that other characters wouldn't.

The Cover Test

Here's a quick gut-check for dialogue: cover up the names and dialogue tags ("she said," "he asked") in a scene with two or more characters talking. Can you still tell who's speaking? If every character sounds the same, that's a sign their voices need more distinction.

What Makes a Voice Distinct?

• Word choice. Does this character use big words to sound smart, or short ones because that's just how they talk? Do they curse? Do they use slang, patois, or specific phrases from their family or culture?
• Sentence length and rhythm. Some characters talk in short bursts. Some ramble. Some never finish a sentence because someone always cuts them off.
• What they notice. An artist character might describe a room by its colors. A character who grew up with not enough might notice food first — how much there is, whether there's enough to go around.
• What they don't say. Sometimes the most character-revealing thing is what a character avoids talking about, or how they change the subject.

How Would THIS Character Respond?

When you're stuck on how a character should react to something, don't ask "what would I do?" Ask "what would THEY do, based on everything I know about them?" A character who's used to being the responsible one might respond to bad news by immediately making a plan — even if inside, they're falling apart. A character who's used to being dismissed might get loud, because quiet has never worked for them before.

Same situation, three completely different reactions — and a reader who knows these characters would recognize each one without being told who's speaking.

Interiority: The Thoughts Behind the Words

Dialogue is only half of what makes a character feel real. The other half is what's happening inside — the thought right before they speak, the thing they wanted to say but didn't, the way their body reacts before their brain catches up. Give your reader access to that, even briefly, and the character stops being a puppet and starts being a person.

Dialogue & Word Choice

If you've written more than a page of dialogue, you've hit this problem: "...he said. ...she said. ...he said again." It starts to feel like a tennis match where someone's narrating every hit. So you go looking for fancier words — "she exclaimed," "he interjected," "she pontificated" — and now it feels worse, just in a different way. Let's actually fix this.

The Truth About "Said"

Here's the thing almost nobody tells beginning writers: "said" is supposed to be invisible. Stephen King has called it the best dialogue tag precisely because readers' eyes slide right over it — it does its job (telling you who's talking) without asking for attention. When you swap it for "she expostulated" or "he ejaculated" (a real one, and yes, it means what you're now thinking — it used to just mean "exclaimed"), the tag stops being invisible. Now the reader is thinking about your word choice instead of the conversation.

So if "said" is fine... why does dialogue still feel repetitive? Usually it's not the word "said" that's the problem. It's that every line has a tag at all. That's the real fix.

Two Tools: Tags vs. Action Beats

You have two ways to show who's talking and how. Most beginning writers only reach for one of them.

The action beat does everything the tag did — we know Maya's speaking, and we get a sense of her mood — but it also gives the reader something to picture. It moves the scene. And it means you never have to think of a new word for "said," because there's no tag to replace.

A good rule of thumb: in a back-and-forth conversation between two people, once the reader knows who's talking, you often don't need a tag or a beat for every line. Drop them out entirely for a few lines and let the dialogue breathe.

When You DO Need a Tag

Tags aren't banned — they're just a tool for specific jobs. Reach for a tag (beyond plain "said" or "asked") when the way something is said genuinely isn't clear from the words themselves or the scene:

Word Choice Beyond Dialogue

The same "is this doing real work, or just dressing up?" question applies to your narration too. A thesaurus is a tool, not a personality transplant for your sentence. If a simpler word says the same thing just as clearly, use the simpler word — save the unusual one for when it's the truest word, not just the fanciest.

• Read the sentence with the simple word, then with the fancy word. Does the fancy one actually change the meaning, or just the vibe?
• Would your character actually think or say this word? A character who left school at 14 probably doesn't think "the ambiance was oppressive."
• Are you reaching for a bigger word because it's true, or because you're worried "small" words make the writing look unimpressive? (They don't.)

Getting From Here to There: Transitions

This is one of those things you don't notice until it's missing. Your character is in the kitchen. Next paragraph, they're at school. How did they get there? Did time pass? How much? If the reader has to stop and figure that out, you've just lost them — even if only for a second, and even if the scene itself is great.

The Two Kinds of Gaps

Every transition is bridging one of two things: space (where we are) or time (how long has passed). Sometimes both at once. The fix for both is the same: give the reader a quick anchor before you move on.

That's it. One sentence — "the bell rang" — and the reader knows class ended, time passed, and we're moving locations. No need to narrate every step in between.

Transition Tools

• Time markers: "The next morning," "Three days later," "By the time she got home." Simple, and readers are used to them — don't be afraid of being direct.
• A change in scene, set off clearly: a line break, a new chapter, or a clear paragraph shift that signals "we've jumped." Don't make a reader guess whether they missed something.
• A small action that bridges the gap: "She grabbed her bag and headed out the door" can carry us from one room to the next without slowing down.
• An emotional through-line: sometimes the smoothest transition isn't about place or time at all — it's a feeling or thought that carries from the end of one scene into the start of the next, so the reader's mind doesn't have to "reset."

The "How Did We Get Here?" Test

When you're revising, try this: at every scene break or location change, ask out loud — "how did my character physically get from where they were to where they are now, and how much time did that take?" If you can't answer that in one sentence, your reader probably can't either, and that's worth a quick fix.

This matters even more for big jumps — across town, across years, across the impossible distances in something like time travel. The bigger the jump, the more the reader needs that one clear anchor sentence to land safely on the other side.

Keeping It Straight: Consistency

Readers remember things. Not everything — but the things that matter to them, they remember, and they will absolutely notice if your character's eyes change color on page 80, or if it was Tuesday in chapter two and somehow still Tuesday forty pages and three "next mornings" later. These slips don't ruin a story by themselves, but they chip away at the reader's trust — the same trust we talked about back in the research chapter.

What to Track

You don't need fancy software. A simple document or even a physical notebook works. Here's what's worth keeping a running list of as you write:

• Physical details: eye color, height, scars, hairstyles, what characters are wearing if it matters to a scene
• Names — and spelling of names: easy to vary by accident, especially with names that have multiple common spellings
• Timeline: what day is it, how much time has passed since the last chapter, how old are characters at each point in the story
• Relationships and what characters know: who knows what secret, and when did they find out — this one creates plot holes fast (more on that next chapter)
• World rules: if your story has any rules about how something works (time travel, magic, technology, even just "how this family's traditions work"), write the rule down so you don't accidentally break it later

Character Consistency Is Different From Character Repetition

There's an important distinction here: a character should be consistent — recognizable as themselves from scene to scene — without being repetitive, doing the exact same thing every time. Consistency is about their core: what they value, how they generally handle stress, what they're afraid of. Within that, they can still surprise you (and the reader) — people are consistent in their core and still capable of growth, bad days, and out-of-character moments that have a reason behind them.

The second version is actually a bigger moment, because it's a change we understand. That's character development. The first version just feels like a mistake.

A Simple Tracking Sheet

For a short story, you might not need much more than a sticky note. For a novel, consider a simple running document with a few columns: Chapter, Day/Date in story, Who's there, What changed, New facts established. Update it as you write — future you, deep in chapter 19, will thank present you.

Spotting Plot Holes

A plot hole is any moment where a reader stops and thinks, "wait... why did that happen?" or "wait... didn't they already know that?" — and the story doesn't have an answer. The frustrating part is that plot holes are almost invisible to you, because you know the answer. It's in your head. It's just not on the page.

Why You Can't See Your Own Plot Holes (Yet)

You're too close to the story right now. You know why the character did that thing — you've been living with this story for weeks or months. But your reader is meeting it for the first time, with none of that context. The single most effective tool for spotting plot holes is something we already covered: distance. Put the draft away for a few days or weeks. Come back and read it like a reader, not like the person who wrote it.

The "So What" and "Wait, Why" Tests

As you reread, watch for two kinds of moments:

• "So what?" — A scene or detail happens, but it doesn't connect to anything else. If you can cut it and the story doesn't change, ask whether it's pulling its weight, or whether it's setting up something that never pays off.
• "Wait, why?" — A character does something that doesn't match what we know about them, or knows something they shouldn't yet, or a problem gets solved a little too conveniently. These are the moments readers circle back to and go "...hold on."

The Most Common Plot Holes (and How to Catch Them)

• Characters know things they shouldn't. Did your character find out that secret on the page, or did you just forget to write the scene where they learn it?
• Timeline math doesn't work. If it's a five-hour drive and your characters left at noon, they can't arrive for dinner the same night. (This is where your consistency tracker from the last chapter earns its keep.)
• A problem gets solved too easily. If your character has spent the whole story unable to do something, and suddenly they can — was that set up, or did it just happen because the plot needed it to?
• Out-of-character actions with no explanation. We covered this in the last chapter — if a character does something that doesn't fit them, the story needs to acknowledge it, even briefly.
• World rules get bent. If you established that something is impossible, dangerous, or against the rules in chapter 3, chapter 15 can't quietly ignore that unless the story addresses it.

Mapping It Out

For longer stories, it can help to physically map your plot — even just a simple list of "what happens, in order, and what each event causes." If you can draw a line from event to event and the line makes sense, you're probably fine. If you get to an event and can't draw a line backward to what caused it, that's your plot hole.

Short Story or Novel? What Actually Changes

Good news: everything in this guide so far applies to both. Where ideas come from, research, sensory detail, figurative language, character voice — none of that changes based on length. What does change is scope, pacing, and how much you can (or should) try to fit in.

Starting Small Isn't a Downgrade

If a novel feels overwhelming, write the short story version of your idea first. Take one scene — the moment your "what if" is at its most intense — and write just that, as a complete, focused piece. You'll learn a huge amount about your characters and your world, and you might discover the short story is the story, or that it's actually chapter one of something bigger.

One Draft to the Next

Finishing a first draft is huge — genuinely, most people who say "I'm writing a book" never get here. But a finished first draft is not a finished book. It's the block of marble. Revision is the sculpting. And just like sculpting, you don't start with the fine details — you start with the big shapes and work inward.

Don't Edit and Write at the Same Time

This might be the single most important piece of advice in this whole guide: finish the draft before you start fixing it. If you stop after every chapter to perfect it before moving on, you'll spend most of your energy polishing a beginning that might change completely by the end — and you risk never finishing at all. Write the whole thing, messy as it is, start to finish. Then go back.

The Big-to-Small Order

When you do start revising, work in passes — big issues first, small issues last. Fixing typos in a scene you're about to cut is wasted effort.

• Pass 1 — Big picture: Does the story work? Are there plot holes (chapter eleven)? Does every major scene earn its place? Is the ending the right ending? This pass might involve cutting or rewriting whole scenes — even whole chapters.
• Pass 2 — Character and consistency: Do characters stay consistent (chapter ten)? Does dialogue sound like each specific person? Are there moments where someone's reaction doesn't fit who they are?
• Pass 3 — Scene-level craft: Transitions (chapter nine), pacing, sensory detail (chapter five), figurative language (chapter six) — does each scene do its job, and does it feel like the reader is there?
• Pass 4 — Line edits: Word choice, repetitive phrases, dialogue tags vs. action beats (chapter eight), grammar, typos. This is the last pass, not the first.

Keep a "Boneyard"

When you cut something — a scene, a character, a subplot — don't delete it. Move it to a separate document. You're not throwing it away; you're putting it in storage. Sometimes a cut scene from one project becomes the seed of something else entirely. And it's a lot easier to cut boldly when you know "delete" doesn't mean "gone forever."

The Power of Putting It Down

Between finishing your draft and starting Pass 1, take a break — a few days at minimum, a few weeks if you can manage it. This is the same distance that helps with spotting plot holes, and it works for the whole manuscript too. You'll come back able to read your own story almost like a stranger would, which is exactly the perspective revision needs.

Letting Someone Read It

At some point, you have to hand your story to another human being and let them read it. This is, for most writers, terrifying — somewhere between "asking someone to read your diary" and "asking them to grade your soul." It's also necessary. You are too close to your story to see it the way a reader will. Other people are your distance, the same way time is.

When to Share It (Not Too Early, Not Too Late)

Don't share your first draft the day you finish it — give yourself the break from chapter thirteen first, and ideally do at least one revision pass yourself. You want feedback on a story that's trying to work, not a pile of raw material. At the same time, don't wait until it's "perfect" — remember chapter fifteen. A good moment to share is after your big-picture and character passes, when the bones are solid but you're not sure about the details.

Choosing Your Readers

Not everyone who loves you is a good first reader for your story — and that's okay. Look for:

• Someone who reads the kind of thing you wrote. A reader of romance might not be the best fit for a horror story, and vice versa — not because they're wrong, but because they don't know what that genre's readers expect.
• Someone who can be honest without being cruel. You need real reactions, not just "it's great!" — but you also don't need someone tearing it apart line by line on a first read.
• A few different readers, if you can. One person's feedback is one opinion. Three people independently noticing the same thing is a pattern worth paying attention to.

Asking the Right Questions

"What did you think?" tends to get you "I liked it!" — true, friendly, and not very useful. Try giving readers more specific things to notice:

• "Where did you get bored, or want to skip ahead?"
• "Was there any point where you got confused about what was happening, or who was talking?"
• "Did any character's actions surprise you in a way that didn't feel earned?"
• "Did the ending feel like it belonged to this story?"
• "What do you remember most, a day after reading it?"

Receiving Feedback Without Spiraling

Some feedback will sting. That's normal, and it doesn't mean the feedback is wrong or right — it just means you care about this story. A few things that help:

• Read all the feedback once, then put it away for a day before deciding what to do with it.
• You don't have to act on every note. If something doesn't ring true to your vision for the story, you're allowed to set it aside — but be honest with yourself about why you're setting it aside.
• Patterns matter more than single comments. If three readers all stumbled at the same spot, that spot probably needs attention, even if you don't agree with each reader's specific suggestion for fixing it.

It Won't Be Perfect. That's the Point.

I'm going to say something that might sound like it contradicts everything above: none of this matters on your first draft. Not the sensory detail, not the figurative language, not the perfectly distinct character voices. Your first draft's only job is to exist. That's it. That's the whole job.

Here's what tends to happen instead: a writer sits down, writes one paragraph, reads it back, decides it's bad, and either deletes it or never writes the second paragraph. Multiply that by every paragraph in a story, and you understand why so many stories never get finished. Perfectionism isn't a high standard — it's a way of never finding out if you can actually do this.

What First Drafts Are Actually For

• Figuring out what your story is actually about (often different from what you thought going in)
• Getting to know your characters by watching them make decisions
• Finding the scenes that matter and the ones that don't
• Building momentum — a finished messy draft beats an unfinished perfect paragraph, every time

Everything in this guide — the senses, the figurative language, the character voices — that's revision work. That's the second draft's job, and the third, and sometimes the tenth. You're allowed to write "she felt sad" in a first draft and come back later to figure out what "sad" actually looks, sounds, and feels like for this specific character in this specific moment.

Permission Slip

Consider this your official permission to:

• Write a first draft that's "too long," "too short," "all over the place," or "kind of bad in the middle"
• Skip a scene you're not ready to write yet and come back to it later
• Use placeholder language ("INSERT BETTER DESCRIPTION HERE") and move on
• Finish something imperfect instead of polishing something forever

Your Next Step

You don't need all nine chapters memorized before you start. Pick one thing from this guide and do it today:

• Start your idea catcher — even if it's just a note titled "story stuff" on your phone
• Write down one "what if" question and one place from your own life it could be set
• Take something you've already written and add one sensory detail that isn't sight
• Write one paragraph of dialogue between two characters, then cover the names and see if you can tell who's talking
• Open a blank document, write the worst possible first sentence on purpose — just to prove the page doesn't bite

That's it. That's the whole assignment. Everything else — the structure, the polish, the figuring-out-what-it's-really-about — comes from doing the work, not from being ready first. You're ready. Go write something.