Guide

How to write a how-to guide

Instructional writing has one measure of quality: can the reader do the thing afterwards? Everything else — style, length, structure — is downstream of that, and most of it is decided before you write a word.

Neubook Write · 11 September 2026 · 8 min read

Start with the reader’s starting point

Most bad how-to writing fails before the first step, because the author never decided who is reading. Write down three things and keep them visible while you draft:

• What the reader can already do. "Has used a spreadsheet, has never written a formula."
• What they have in front of them. Tools, budget, materials, time.
• What "done" looks like. A specific artefact or state, not a feeling. "A sourdough loaf with an open crumb" rather than "confidence in baking".

Two readers at different skill levels cannot be served by one guide. Pick the less experienced one; the expert can skim.

Task analysis before prose

Before writing, list every action the reader must take, in order, including the ones that feel too obvious to mention. The obvious ones are where beginners stop. For each action note: what they need in hand before it, what they do, how they know it worked, and what goes wrong most often.

That table is the book. Chapters are groupings of it; prose is the connective tissue.

How to write a step

1. One action per step. If the step contains "and", consider splitting it.
2. Start with the verb. "Open the file", not "You will want to open the file".
3. Put the condition first. "If the dough sticks, add flour" rather than "Add flour if the dough sticks" — the reader scanning for their situation finds it at the start of the line.
4. State the expected result. Every few steps, tell them what they should be seeing. Without checkpoints, a reader who went wrong at step four discovers it at step nineteen.
5. Attach the failure to the step. Troubleshooting sections at the back of a book are read by nobody in the moment they are needed.

Structure for a how-to book

• Chapter 1: what you will make, and what you need. Photographs or a clear description of the finished thing, plus the full list of materials or prerequisites.
• Chapter 2: the shortest possible complete run-through. A first success in one sitting, even if simplified. Momentum is everything in instruction.
• Chapters 3 onward: one stage per chapter, in order, each ending in a checkpoint.
• Penultimate chapter: when it goes wrong. Symptom, cause, fix — organised by what the reader sees, not by what is technically happening.
• Final chapter: what to do next. Variations, next skills, where to go deeper.

Where AI helps, and where it will hurt you

Instructional writing is one of the strongest uses for AI drafting and one of the most dangerous, for the same reason: the output is confident and uniform.

Verify every specific against the real thing. If the guide involves tools, chemicals, electricity, food safety, medication or money, have someone competent read it before publication — that is not a legal formality, it is how people get hurt.

Test it on a person

The only real quality check for a how-to guide is watching someone follow it without your help. Three testers in the target audience will find nearly everything. Watch for:

• Hesitation — they read a step twice. The step is ambiguous.
• Scrolling back — you introduced something out of order.
• Asking you a question — write the answer into the guide, at that step, in their words.
• Doing it differently — either your order is wrong or theirs is. Find out which.

Readers scan rather than read, especially when their hands are busy. Nielsen Norman Group's long-running work on how people read on screens applies directly: front-load the important words, keep paragraphs short, and make the structure visible without reading it.

Screenshots, diagrams and when to use them

• Use an image when the reader must recognise something — a texture, a screen, a part. Otherwise words are better: they translate, they are searchable, and they do not date.
• Annotate rather than crop. A full screen with an arrow tells them where they are; a tight crop does not.
• Describe in the caption what the image shows, so the guide still works in a black-and-white paperback or for a reader with images off.

Publishing a practical guide

Instructional books are searched by task, which makes metadata mercifully literal. Put the task in the title. Use keyword phrases that are the queries themselves — "sourdough for beginners", "bookkeeping for freelancers", "balcony vegetable garden". Google's guidance on helpful, people-first content is a decent checklist for the same material published as articles: does it demonstrate first-hand expertise, does it satisfy the reader without them going back to search.

Disclose AI assistance at upload under Amazon's content guidelines, and if the guide carries any risk, add a plain safety note in the front matter.

A one-week build

Writing for the reader who is already stuck

Most readers do not start at chapter one. They arrive mid-task, something has gone wrong, and they are scanning for the paragraph that matches their situation. Design for that reader as well as the sequential one.

• Headings that name symptoms, not topics. "The dough will not stretch without tearing" beats "About gluten development".
• Repeat essential context locally. A sentence repeated in chapter nine saves a reader from hunting back to chapter two. Instructional writing is allowed redundancy that prose is not.
• Number your steps globally so people can refer to "step 14" in a forum or a message to you.
• Put a decision table early. "If your situation is A, read chapters 2, 5 and 9" respects the reader's time more than a linear insistence.

A troubleshooting section that works

Organise by what the reader observes, never by cause. They cannot search for a cause they have not identified.

Four columns, ordered by likelihood. The "if that fails" column is what separates a guide written by someone who has taught this from one written by someone who has only done it.

Safety, and when to say "do not do this"

Instructional writing carries a duty of care that fiction does not. Where the task involves risk:

• Put the warning where the action is, not in a preface nobody reads.
• Say what the hazard is and what it does, not just "be careful". "The handle stays hot for twenty minutes and will burn through a tea towel" changes behaviour; "caution: hot" does not.
• Name the limit of the guide. "If the wiring is pre-1970 or you cannot identify the earth, stop and call an electrician." Telling readers when to stop is part of teaching them.
• Have a competent person review anything involving electricity, gas, structural work, chemicals, food safety, medication or vehicles. This is not legal cover; it is the difference between a helpful guide and a dangerous one.

Keeping it current

Instructional books decay. Software changes, prices move, regulations shift. Two structural choices slow the decay considerably:

• Separate the durable from the volatile. Principles and sequence in the book; version-specific screenshots, prices and menu paths in a companion page you control and can update.
• Date the book visibly and say what version it describes. Readers forgive age they can see and resent age they discover.

A short "what has changed since publication" page on your site, linked from the front matter, buys a practical guide two extra years of usefulness for about an hour of work a year.

From guide to product

A how-to book is often the top of a wider offering, and the transitions are natural rather than forced:

• The materials list becomes an affiliate or shop page — disclosed, always.
• The hardest stage becomes a video or a short course, sold or free.
• The template becomes the lead magnet that builds the list.
• The questions readers email you become the second edition. Keep every one; they are the most valuable research you will get.

Sources

• Nielsen Norman Group: how users read on the web
• Google Search: creating helpful, reliable, people-first content
• KDP: Keywords
• KDP: Content guidelines, including AI-generated content

Common questions