guide-writing

Guide writing (Write Useful Books method)

When to use

Use when structuring long-form educational content as a product with a promise: scoping it, ordering its contents, testing it on real readers, and planning its launch. This skill covers structure and product design of the content — voice and prose style are a separate concern, out of scope here. Only for problem-solvers (content promising an outcome); if the work is narrative, artistic, or entertainment-first, this method is explicitly the wrong advice.

The procedure

Phase 1 — Scope the promise (before writing anything)

1. Write the scope in one block: Promise + Reader profile + Who it's NOT for + What it won't cover. The promise is what's different in the reader's life afterwards, stated clearly enough that the wrong reader can decide they don't need it.
2. Sharpen by deletion, not addition. Ask: "What does my ideal reader already know and believe?" — everything they already believe gets cut. This kills introductory throat-clearing.
3. Write the recommendation loop as a literal story: one stranger, in a specific moment of pain, complains to someone — who names your thing. If no plausible story exists, adjust the promise or reader until one does. No plausible story = the growth plan is "hope."
4. Check longevity: is the promise relevant 5+ years out? Move datable tactics (tools, prices, platform mechanics) into an updatable channel (web page, appendix, changelog), not the core artifact.
5. Validate desirability by talking, not pitching: run listening conversations about the reader's life — what they tried, where they searched, what blocked them. Never ask for opinions ("asking for opinions is just fishing for compliments"). If you can't find even one interested reader now, you won't find thousands later — fix the scope today.

Phase 2 — Design the ToC for the reader

1. Every title is a takeaway, not a topic: "Good sales is about asking good questions", not "Sales 101". If a section has multiple learning outcomes, keep the category title and add takeaway subsections.
2. Test the structure by teaching it live before drafting: walk a target reader through one or two chapters' worth of value in conversation. Every improvisation, repeat, or rephrase is a ToC bug — fix the structure, then teach again.
3. Order content around the learner's goals, not the teacher's convenience. Theory is a value enabler, not value: interleave small doses of it between early wins instead of front-loading it ("let's get the theory out of the way" is the classic reader-experience killer).