How to write a how-to book
A how-to book is judged by one thing: whether a reader who follows it can do what it promised. That makes it the most testable kind of nonfiction. Define the outcome, put the steps in the order a beginner needs them, build every chapter the same way, and then watch real readers use it.
This guide covers instructional nonfiction for adults: books that teach a skill, a process or a result. If your book is mainly about personal change, see how to write a self-help book; if you are still deciding what kind of book it is, start with memoir, how-to or thought leadership.
Step 1: define the outcome
Write one sentence that finishes "By the end of this book, the reader can..." and make the end of it something a person could watch them do. "Understand marketing" fails that test. "Write and send a monthly email to past customers" passes it. The outcome tells the right reader the book is for them, tells you what to leave out, and gives you something to test in step 5. Our guide on writing your book's promise covers the before and after in more detail.
Colin Dombroski, a pedorthist, put the outcome in the title: The Plantar Fasciitis Plan. His story on scribemedia.com explains why he chose a book over other formats: "I could hand it to someone and say, 'This is how I want you to get better.'" That is a how-to book's job in one line. The story describes readers messaging him every day that they are walking with less pain after trying his methods, and lists a Keynote at the "Pedorthic Association of Canada 2020" among the results. One author's experience, not a forecast, but it shows a book doing the clinic's work for people he will never treat.
Step 2: put the steps in order
Experts skip steps because they no longer notice them. Before outlining, list everything a beginner has to know or do to reach the outcome, including the parts that feel too obvious to mention. Then sort the list so that every step depends only on the steps before it. Three checks help:
- The dependency check: for each step, ask what the reader must already know or have. If it comes later in the book, move it.
- The first-week check: can a reader do something useful after the first two or three chapters? Long theory before any action loses people.
- The size check: each step should be something a reader can finish in a sitting. Split anything bigger.
A method that already exists in another form needs the same treatment. Deneen Allen had a method long before she had a book. Her story describes it as "a 5x5 method of five steps and twenty-five workshops she first wrote down in 2019", and tells how what she had built into a 120,000-word digital program had to be distilled into a single book she could hand to someone. Moving from a program to a book means choosing what the reader needs in order, and leaving the rest for the program. The outlining guide covers turning the sorted steps into a contents page, and outline examples shows the step-by-step shape as a sample table of contents.
Step 3: use one chapter template
Readers of how-to books learn the shape of a chapter and then rely on it. Using the same five parts in every method chapter makes the book easier to use and easier to write.
| Part | What it does | How to write it |
|---|---|---|
| Goal | Tells the reader what they can do by the end of the chapter | One or two sentences, like the "thesis statement" The Scribe Method recommends for every chapter |
| Steps | The instructions themselves | A numbered list, one action per step, each starting with a verb |
| Example | Shows the steps applied to a real case | A client, student or your own case, or an illustration clearly labeled as one |
| Exercise | Has the reader do it on their own situation | A specific task with a time or quantity: "list five", "for one week" |
| Checklist | Lets the reader confirm the step is done before moving on | Three to six yes or no items they can tick |
Our own template. Thesis statement from The Scribe Method's outline chapter; step conventions from the Microsoft Writing Style Guide.
The Scribe Method's chapter on creating your book outline describes a chapter thesis statement as "a short, one-to-two sentence summary of its key takeaway". In a how-to book, the takeaway is an ability, so the goal line usually starts "By the end of this chapter you will be able to".
An example chapter
Chapter 4: Plan your first raised bed
Goal: by the end of this chapter you will have a drawn plan for one bed, with every plant placed and a planting date for each.
Steps: 1. Measure the bed and draw it to scale on squared paper. 2. Mark which end gets the most sun. 3. Choose up to five crops from the list in chapter 3. 4. Place the tallest crops on the shadiest side so they do not shade the rest. 5. Write a planting date next to each crop.
Example: the plan for a 4 by 8 foot bed in a yard that gets sun only in the afternoon, step by step.
Exercise: draw your own plan this week. If you do not have a bed yet, plan for the space you have in mind.
Checklist: the bed is drawn to scale; every crop has a place; nothing tall blocks the sun from something short; every crop has a date.
An illustrative example, not taken from a real book. Note that each step is one action, and the checklist repeats the goal as things the reader can check.
Step 4: make it usable on the page
A how-to book is used as much as it is read: open on a desk, flipped back to, followed with the reader's hands busy. Technical writers have worked out conventions for this, and they transfer well to books. The Microsoft Writing Style Guide says to "Use a numbered list" for multiple-step procedures, to "Use a separate step for each instruction", to start steps with an imperative verb, and to "Make sure that customers know where the action should take place before you describe the action." Google's developer documentation style guide adds that an optional step should begin with "Optional", and that when a step causes a result, you should "State the action first and the result second."
- Name sections after tasks. "Plan your first bed", not "Bed planning considerations". Keep the phrasing parallel so readers can scan.
- Introduce every list. Digital.gov's plain language guide on lists says lists "Help the reader understand the order in which things happen" and advises: "Always use a lead-in sentence to explain your lists."
- Put warnings before the step, never after the reader has already done it.
- Refer back rather than repeat. If a procedure appears twice, explain it once and point to it.
- Use tables and diagrams where the reader is choosing between options or needs to see a layout.
- Give the reader a way back in: a one-page summary of the steps at the end of each part, or printable checklists at the back.
For the sentences themselves, The Scribe Method's chapter on writing effective nonfiction asks for content that is "short, simple, direct, and relevant". Instructions are where that matters most.
Step 5: test it with real readers
The only proof a how-to book works is someone else doing the steps. You cannot test it yourself, because you already know what you meant. Usability research gives a useful starting size. The Nielsen Norman Group's article Why You Only Need to Test with 5 Users reports that a first study with five participants found 85% of the usability problems, and recommends several small rounds over one large one. That research was about websites, not books, but the principle carries: a handful of readers per round, then fix, then test again. Digital.gov's guide to usability testing says to find "three to five people" who match simple criteria for your intended reader.
A simple round looks like this:
- Recruit three to five people who match your reader and do not know your method. Not colleagues, and not people who have already worked with you.
- Give each one a chapter and a real task from it: "Using this chapter, plan a bed for your yard."
- Watch them work, ask them to think aloud, and do not help. Every time you want to explain, write down where.
- Afterwards, ask them to explain a key step in their own words. Digital.gov's guide to paraphrase testing describes this method: wherever participants misunderstood the message, "the content has a problem that you should fix."
- Fix every place more than one person stalled, then run the next round with new people.
Watch especially for your own jargon. The same paraphrase testing guide describes a government letter where readers said the text was clear but held several different meanings of one term, and would have acted on them. Experts are the last to notice their own terms of art.
What most people get wrong
- Teaching what they know instead of what the reader needs. Everything that does not move the reader toward the outcome belongs in another book, a talk or an appendix.
- Too much theory up front. Explain why, but get the reader doing something early.
- Steps that hide several actions. "Set up your system" is a chapter, not a step.
- Examples only from experts. Show a beginner's attempt, including what went wrong.
- Exercises nobody does. Make them specific and small, and place them where they are needed.
- Skipping the test. Every confusing step you ship becomes a reader who gives up and blames themselves.
The book idea starter asks for your reader and the change you promise, then checks that your chapter list adds up to it: a good way to test the outcome and sequence before you write the steps.
Scribe Media, which makes this site, sells book coaching and writing services, including Scribe Compass ($5,000 on scribemedia.com/pricing), in which a book coach works with you on the audience, purpose, table of contents and a chapter-by-chapter roadmap. The five steps above are ones you can work through on your own, and the testing is the part no service can do for your readers.
Common questions
How do you write a how-to book?
Write down what the reader will be able to do at the end, list every step it takes to get there, and put the steps in the order a beginner needs them. Turn the steps into chapters, each with a goal, numbered steps, an example, an exercise and a checklist. Then hand chapters to people like your reader, watch them try the steps, and fix every place they get stuck.
Is there a template for a how-to book?
A simple one works for most chapters: the goal (what the reader can do by the end), the steps (numbered, one action each), an example (the steps applied to a real or clearly labeled illustrative case), an exercise (the reader does it on their own situation) and a checklist (how they know it is done). The book as a whole adds an introduction on who it is for and a closing chapter on keeping it going.
How is a how-to book different from an instruction manual?
A manual tells you how to operate one product and is consulted, not read. A how-to book teaches a skill or a result that depends on judgment, so it explains why each step matters, shows examples and helps the reader adapt the steps to their own situation. Good how-to books borrow the manual's habits for the steps themselves: numbered lists, one action per step, plain verbs.
How do you write a guide book?
Start with the reader's task, not your knowledge. Decide what they need to find and do, organize the book around those tasks with clear headings, and write each section so it can be used on its own. Test it with readers who match your audience before you call it finished.
How do you write a step-by-step guide?
Use a numbered list, put one action in each step, start each step with a verb, and say where the action happens before saying what to do. State the result of a step after the action if the reader needs it to continue. Mark optional steps as optional, and put warnings before the step they apply to, not after.
Sources, checked October 25, 2026: Microsoft Writing Style Guide, "Writing step-by-step instructions" (learn.microsoft.com); Google developer documentation style guide, "Procedures" (developers.google.com); Digital.gov plain language guides on lists, usability testing and paraphrase testing (digital.gov); Nielsen Norman Group, "Why You Only Need to Test with 5 Users" (nngroup.com); The Scribe Method, chapters on creating your book outline and writing effective nonfiction (scribemedia.com/scribe-method-book); author stories on scribemedia.com for Colin Dombroski and Deneen Allen, linked above; scribemedia.com/pricing. Published by Scribe Media.