Write a How to Guide
A how to guide helps readers complete a specific task. Start with the result, show the steps in a workable order and explain how to tell whether each step succeeded. Put the finished result in the first paragraphs, in words the reader would use. Then show the first step from the place they actually are, not from an ideal setup. A how to guide earns trust when an early step can be checked with the eyes, not only believed.
Start your book, freeWhat is a how to guide eBook?
A how to guide is an instructional book organized around doing something: setting up a process, learning a practical skill or completing a project. Each chapter should move the reader closer to the promised result. Background belongs where it helps a decision, and troubleshooting belongs near the step where a reader may get stuck. Tell the reader what they will hold at the end, what they need before they start, and how they will know a step worked. A how to guide that buries the result under background makes people read three pages before they can act, and many of them stop.
How should a how to guide organize its steps?
A how to guide should put actions in the order the reader must perform them. State the starting conditions, describe the action and show how to check its result. Number a multi-step sequence so readers can keep their place.
“A procedure is a sequence of numbered steps for accomplishing a task.”
- Google’s procedure guidance uses a sentence and bullet for a one-step procedure, rather than a numbered list containing only 1.
- For a procedure with two or more actions, distinguish the sequence from an unordered list of materials or options.
- In this Bookeen workshop example, use three checkpoints: confirm the audience, approve the session plan and check the materials. The number belongs to this example, not every how to guide.
Use Bookeen to develop the chapter sequence from your process notes. Then perform the instructions yourself or ask a suitable reader to try them; clear-looking numbered steps are not evidence that the procedure works.
Source checked .
When to choose this book type
- Choose a how to guide when the reader needs a repeatable sequence. The reader should be able to tell where they are in the sequence and what finished looks like. If the book is mostly reflection with no checkable step, a different kind of book fits better.
- Define what the reader already knows and what they need before starting. Name the tools, access, and vocabulary they already have. A guide written for everyone explains terms the real reader knows and skips the exact mistake they came to avoid.
- Use a workbook instead when exercises and written responses carry most of the value. A small exercise can sit beside a step. If most of the value is the reader filling, deciding, and looking back, let that book lead and keep this one for the sequence.
A practical outline
- Describe the result and the starting conditions. Put the finished result in the reader's words, then the place they are actually starting from. An ideal setup that does not match their desk makes the first step feel impossible.
- Gather materials, information or prerequisites. List only what the steps use. A long shopping list of optional gear hides the two things the reader must have before they begin.
- Work through the steps with a continuous example. Carry one example from the first step to the last so the reader can see the work change. A new example in every chapter forces them to relearn the situation instead of the skill.
- Check the result, troubleshoot and plan the next action. Tell them what they will see if a step failed and the one change to try next. A troubleshooting chapter at the back is where those warnings go to be missed.
A guide to planning a first community workshop
Follow one organizer from a rough topic to a workable session plan. A chapter about the audience identifies who should attend. The next chapter turns that audience into a learning objective, then a schedule and a materials list. Readers can compare their own decisions with the running example instead of starting from scratch in every chapter. Keep one organizer in view from the first choice to the last checklist, and let later chapters refer to decisions that organizer already made. Readers learn the sequence by watching one case change, instead of meeting a new hypothetical every time the topic shifts.
Who should a how to guide address?
A how to guide should address one defined reader at a clear starting point. Define the reader before drafting. Explain specialist terms at the point of use and avoid adding chapters simply because you know the subject well. Name what the reader has already tried and what they are afraid of getting wrong. A guide written for everyone explains terms the real reader knows and skips the exact mistake they came to avoid.
- State prerequisites early. Say what they need before the first action, in the same words the later steps will use. A synonym in the question often looks like a new idea.
- Separate required steps from optional improvements. Required steps change the result. Optional improvements can be labeled as such. If everything looks mandatory, readers stall on work that does not move the outcome.
- Make the outcome observable. A result the reader can see, count, or compare is a check. A result that only says they will understand the topic is a hope, and the guide cannot be tested against it.
Test the instructions
A guide can sound clear while leaving out a crucial action. Work through the sequence as a reader would. Check dependencies, examples and any references to tools or screens against their current behavior. Do the steps yourself from the draft, with only the materials the chapter lists. Every time you rely on a habit the chapter never mentioned, add that habit to the page or the reader will stall where you sailed through.
- Use consistent names for the same action.
- Add checkpoints after meaningful steps.
- Explain common mistakes and recovery options.
Build a draft in Bookeen
Give Bookeen your audience, outcome and process notes. Use those inputs to develop an outline, then inspect each chapter for missing steps. Your experience and verification make the instructions useful. Bring one real attempt, including the point where you usually hesitate. Ask for the next step and the check that tells you it worked. Then try that check before you accept the wording.
- Keep one example running through the guide.
- Replace generic advice with decisions and actions.
- Review the complete sequence before preparing reader files.
Compare book types
Lead Management eBooks for a Shared Process
A Lead Management eBook turns your approach to prospective customers into a guide people can use. Define the audience, explain the next action at each stage and give readers examples they can adapt. Open with the decision a reader will face this week, not with a history of the market. Then show the next action and the fact that would make them wait. People keep a handbook they can use on the next inquiry, and they skip one that only renames stages they already know.
Workbook eBooks for Practice
A workbook eBook turns reading into practice. Give each exercise a purpose, a clear instruction and enough space for the reader to respond, reflect or make a decision. Open on the task, not on a lecture. Tell the reader what to produce, how long it should take, and what a finished response looks like. A workbook eBook that withholds the point until the second page loses the people who came ready to practice.
Course Companion eBooks between Lessons
A course companion eBook gives learners something they can return to between lessons. Connect summaries, examples and exercises to the course so the book is easy to navigate when a question comes up. Open where the learner is: the lesson they just left, and the step they cannot remember. A course companion eBook that begins with the history of the subject makes them hunt for the one procedure they came back to find.
Readers, files and next steps
Explore a related writing situation, then choose an edition that suits your readers.
Explore the Bookeen book creatorWrite a How to Guide: questions answered
How is a how to guide different from a workbook?
A how to guide explains a process. A workbook gives readers space and prompts to apply it. The two can be combined, but one should lead the structure so the reader knows whether to follow instructions or complete exercises. If the reader mostly follows instructions, you are writing a how to guide. If they mostly fill, decide, and look back at what they wrote, the center of gravity is a workbook. You can include a small exercise either way, but one of those jobs should lead.
Does every chapter need the same length?
No. Give each step enough explanation to be usable. A complex decision may need alternatives and an example; a simple action may need only a short instruction and a check. A step that takes a minute should stay short. A step where people usually fail deserves the example and the check. Equal chapter length is a design habit, not a service to the reader.
Should a how to guide include troubleshooting?
Yes, where you can identify real failure points. Explain the symptom, likely cause and next action near the relevant step. Avoid inventing problems just to make a chapter longer. Yes, beside the step where the trouble appears. Tell the reader what they will see if the step failed and the one change to try next. A troubleshooting chapter at the back is where those warnings go to be missed.
Can I turn existing articles into a guide?
Yes, but revise them into one sequence. Remove repeated introductions, fill gaps between steps and keep terminology consistent. A useful guide needs a continuous reader journey, not just a collection of articles. Only after you cut the pieces that do not help this reader reach this result. Articles written for different occasions leave gaps and repeats. Give the combined draft one starting point and one way to check the ending.
Which file format should I choose?
EPUB works well for text that readers resize on different screens. PDF preserves a specific layout. Keep an editable manuscript while revising, and inspect the exported edition before sharing it. Choose the file that matches how the reader will use the steps. Flowing text suits a guide they read on a phone. A page that must keep a diagram next to a checklist wants a fixed layout. Make that choice after the steps are clear, and review the actual file.