Write Useful Books: start with the reader
Consider a new manager whose meetings with team members keep turning into status updates. They have another meeting tomorrow and want it to go better. A guide to listening, trust and communication sounds relevant, but they need something they can use: how to prepare, what to ask, and how to respond when the conversation becomes difficult.
That gap between knowing a subject and helping someone use it is the concern of Rob Fitzpatrick's Write Useful Books. He proposes developing a practical book with readers from the beginning. Their experiences help shape the promise, their questions improve the teaching, and their attempts to use it reveal what the manuscript still needs.
Begin with a particular reader
A book about management could contain almost anything. Choosing a reader gives you something firmer to work with. Here, the reader already manages a small team and holds regular meetings. They need help making those conversations useful. Hiring, compensation and company strategy can belong to other books.
Fitzpatrick calls this the book's scope: its promise, intended reader, people it is not for, and subjects it will leave out. Those exclusions make the promise possible. If you try to serve an experienced director and someone supervising their first colleague in the same way, one may sit through basics while the other struggles with assumptions you never explain.
The promise might be to help a new manager prepare and lead their next individual meeting with a clearer understanding of what the other person needs. It is specific enough to discuss and question. You can ask whether that is a problem people care about, whether your advice helps, and what the reader would reasonably expect from the title.
Fitzpatrick distinguishes this kind of useful nonfiction from books whose main purpose is pleasure. A useful outcome can still be intellectual or emotional: understanding a confusing subject or seeing an experience differently can matter. His method asks you to make that intended change clear enough for someone to recognize whether the book is for them.
Learn from their last attempt
Once you have a possible reader, Fitzpatrick suggests talking about their experience before presenting your solution. Asking whether a management book sounds useful makes encouragement easy. Asking someone to walk through their last meeting gives you details you could not supply from a topic list.
What were they hoping to understand? How did they prepare? Where did the conversation become awkward? What did they try afterward? These questions can reveal a different problem from the one you expected. Suppose the manager has no trouble starting a conversation but does not know how to respond when someone mentions a concern. A longer list of opening questions would leave that difficulty untouched.
You are also learning what the reader already knows and believes. Someone who wants help with tomorrow's meeting probably needs little persuasion that listening matters. They may need an example of what listening changes in the next sentence. An expert can overlook that small step because it has become habitual.
A few relevant conversations can improve the starting point. They do not prove the whole book will work. If invitations receive little response, investigate the reader, the promise and the request itself. People may lack time or trust as well as interest. The useful question is what you can learn before spending months writing around an assumption.
Try teaching the explanation
The conversations give you a better outline. During development, Fitzpatrick wants its headings to describe what a reader will learn. A heading such as Communication leaves a lot undecided. A heading about exploring a concern before offering advice tells you what that section is trying to teach.
Then help a suitable person work through one small part. You might use an upcoming meeting and practice how the manager could respond to a concern. Notice where you need to supply an example, repeat a distinction, or change the order. Those moments show what the eventual explanation has to carry.
When you teach someone directly, you can notice confusion and respond. The finished book has to anticipate those questions. When you answer a question aloud, record what made the answer necessary. Otherwise the lesson may work because you are present while the chapter remains incomplete. Follow up after the person tries the idea; understanding it together and using it alone are different tests.
Now draft enough to deliver a substantial piece of help. Depending on the topic, that might be one chapter or several. Fitzpatrick encourages a rough first version, followed by revisions that make it coherent enough to share. Familiar tools and explaining the section as you would to a colleague can help you get started. You will have a clearer reason to revise each passage because you know what it is meant to do.
Put useful moments within reach
The manager still has that meeting tomorrow. If the first useful preparation exercise sits behind a long history of management theory, they may never reach it. Fitzpatrick describes engagement as receiving value over the time spent reading. A practical reader keeps going when the next part helps them understand or do something they wanted.
This changes where background belongs. Give enough context to make the first useful step sound, then introduce further explanation when it helps with the next difficulty. A short worked conversation could make a distinction visible before a longer discussion explains it. Essential conditions still belong beside the advice they qualify.
One editing aid is to add word counts to the detailed outline. Look for a slow opening, a long stretch without a useful takeaway, or a section whose length seems large for its contribution. The numbers identify somewhere to look; they cannot decide whether the explanation earns its space.
Cutting can help, especially when you save removed material separately. A passage can be worthwhile without belonging here. You are making the route clearer for this reader, and the saved material can find another purpose later. The book can be as long as its promise requires. Padding it, or cutting away necessary reasoning to make it short, makes the reader's task harder.
Find out what happens without you
A beta reader is someone who wants the book's help enough to try an imperfect manuscript. A supportive friend may fit, but friendship alone is not the qualification. Invite people who face the situation you are writing for, give them a coherent draft, and make it easy to comment on a particular passage.
Tell them what would help at this stage: confusion, disagreement, boredom, unanswered questions and passages that made something click. If you ask only for feedback, they may carefully correct spelling while the structure still needs to change. Detailed polish can wait until you know more about whether the teaching works.
Suppose a reader highlights the instruction to explore a concern and asks what that means in an actual conversation. You explain it in a comment, and they understand. The next reader still needs that explanation. Revise the passage itself, perhaps with a worked exchange, then let someone new try it without the history of your discussion.
Praise is useful too when it points to something specific. Fitzpatrick describes discovering how much readers valued the mock conversations in The Mom Test, then using more of them. The useful lesson is to understand what an example enabled, rather than repeat a device everywhere because someone liked it.
Pay attention to where readers stop, while leaving room for ordinary life. Silence can mean a slow section, a confusing step, a poor fit or a busy week. Look for recurring obstacles and ask what happened. Pressuring someone to finish can hide the place where the draft stopped earning their attention.
Decide when the book is ready
Fitzpatrick gathers the qualities of a useful book into DEEP: Desirable, Effective, Engaging and Polished. Readers want the promise, receive the result, find the reading worthwhile, and get a professionally presented book. The order explains why he spends so much time with readers before detailed polishing.
His readiness signals are practical: suitable readers become easier to recruit, most receive the value and reach the end, and some start bringing others. There can always be another improvement. These signals help you judge the work alongside deadlines, energy and the point where another revision adds little.
The remaining craft still matters. Strengthen the prose, proofread, and arrange expert or other specialist review where the subject needs it. Inspect the final pages and covers in the formats readers will receive. A clear editing document can still export with a stranded heading or a displaced illustration.
Taking payment adds another decision. Fitzpatrick advises waiting until later beta reading, when the structure and teaching are mostly working. A preorder promises the finished book later; early access also supplies the current draft and updates. Either asks for more confidence in delivery than inviting someone to help you improve an experiment.
Give recommendations somewhere to begin
Fitzpatrick's ambition extends beyond a successful launch. He wants a book people can recommend when someone encounters the problem it solves. Another new manager mentions that their meetings feel unhelpful. A reader who benefited has a specific reason to suggest the guide. That is the recommendation story the book's promise was designed to make possible.
The story needs initial readers. Fitzpatrick calls the work of reaching them seed marketing. You can start finding those readers before publication, alongside the final work on the book. He describes four routes: useful appearances on podcasts or online events, paid book advertising, event giveaways or bulk orders, and an audience built by sharing useful work. You can choose a route that fits your contacts, time, money and willingness to keep doing it.
A useful excerpt from the guide might explain one conversation in a community of new managers. An interview could explore the same difficulty. A training organizer might consider copies for participants. Advertising would need enough income per sale to justify its cost. Each route still has to reach people who can use the book; distributing copies alone does not establish that anyone received its value.
If people want to hear more, be clear about the invitation. Helping with a draft, receiving an update and buying a book are different commitments. Sharing parts of the work can support the manuscript and its audience together without requiring an unrelated stream of promotional material.
Time can help recommendations accumulate when the book stays relevant. Fitzpatrick favors lasting problems and explanations over dependence on temporary tools. The guide could keep its core about conversations while moving a changing software walkthrough elsewhere. Some subjects require updated editions.
Help someone choose and use the finished book
The published book needs to make the same promise recognizable. A small cover, title and store description should help a suitable reader see why it matters to them. Samples and genuine reviews can help them judge the fit. A complaint can reveal either a broken explanation or an audience mismatch, so investigate it rather than automatically defending the book.
Your own purpose affects the business choices. Royalties, a stronger professional reputation and future work with readers are different goals. Self-publishing gives an author more control and production responsibility. A publishing deal needs to be assessed through its actual terms and support. The book's rates, prices and platform instructions describe 2021 and need checking before being reused.
Pricing also affects which distribution work is affordable. Look at what remains from a sale after its costs. Extra formats, translations or teaching materials may reach people the current edition misses, but each brings work and expense. Optional resources should add help while the book remains complete on its own.
After publication, questions from readers can become clearer passages or useful resources. A reader who reaches out may show you where an explanation failed, or how they used it in a situation you had not considered. Fitzpatrick encourages giving people a reasonable way to contact you. That relationship can keep the book useful beyond the moment someone buys it.
This connects with How to Take Smart Notes, which considers how reading and connected notes help an idea develop. Fitzpatrick asks what a particular person will need to use that idea. The material you have gathered can become an explanation, and a reader can show you what that explanation still leaves out.
For a first attempt, choose one person and one difficulty your writing could help them with. Ask about their experience, try explaining a useful piece, and notice what you have to add. That small encounter gives the next draft a concrete job. You can return to it with more than a topic and the hope that the eventual book will help.
Based on Rob Fitzpatrick, Write Useful Books: A Modern Approach to Designing and Refining Recommendable Nonfiction, version 1.00, June 2021. The management guide is a hypothetical example created for this article. Commercial examples are the author's reported experience; platform details and terms require current checking.
Source
Write Useful Books: A Modern Approach to Designing and Refining Recommendable Nonfiction. Version 1.00, June 2021., Rob Fitzpatrick
Linked references
1Published notes that link to this page.