You've picked a lead magnet idea. (If you haven't, the scoring sheet in lead magnet ideas for coaches and consultants gets you there in an afternoon.) Now comes the build, which is where a lot of downloads lose their value: the guide explains the topic well, the reader agrees with every page, and they close it having done nothing.
A useful download ends with something the reader made, like an agenda, a decision or a filled-in plan. That first result is what makes your next email worth opening.
This article builds one from start to finish. You'll write the task and result, draft the instruction, example and working pages, then test the draft with a likely buyer and fix what confused them. The example is the First 1:1s Planner from Leah Morgan, an illustrative coach for new engineering managers, including an illustrative reader test that changed 4 things in it.
Jump to the free Useful Download Build Kit
How to create a downloadable guide: define the task and the finished result
Write 1 sentence naming the reader, the task and what they'll hold when they finish: "By the end, [reader] will have [finished result] ready for [moment]." Then set 3 budgets: minutes to the first result, total pages and pages of reading before the reader does anything. Every page you add later has to serve that sentence.
Write the result sentence
Leah's sentence: "By the end, a new engineering manager will have a written agenda for their first 1:1 with each direct report, ready to send the day before."
Compare 2 weaker drafts. "Learn how to run great 1:1s" describes a topic and leaves the reader with nothing to finish. "Everything new managers need to know about one-to-ones" has no edge to stop at, which is how guides reach 40 pages.
Set the budgets
| Budget | Leah's planner |
|---|---|
| Time to first result | 20 minutes for the first person |
| Total pages | 6, including the cover |
| Reading before doing | Under 1 page |
Define done
Make "done" something the reader can check. Leah's last page carries 3 boxes: agenda written for 1 person, 4 questions chosen, meeting booked. A reader who ticks all 3 got the result, whatever they thought of the design.
Build the explanation, example and working pages
A working guide needs 3 kinds of page. Instruction pages give numbered steps, an example page shows those steps finished by someone in the reader's position, and working pages give them room to do it. Keep explanation short, write each step as an action, and put the example where readers will look when they get stuck.
The page plan
| Page | Job | In Leah's planner |
|---|---|---|
| 1 | Promise and time | "Plan your first 1:1 with every person on your team. About 20 minutes for the first." |
| 2 | Steps | 4 numbered actions |
| 3 | Questions | 8 questions, each with a note on when to use it |
| 4 | Example | A manager's completed page |
| 5 | Working page | Blank fields, duplicated per person |
| 6 | Done and next | 3 checkboxes and a reply invitation |
Page 2: the steps, as first drafted
- Fill in the context box: what you know about this person and what you want from the meeting.
- Pick 4 of the 8 questions on page 3, starting with the ones you're least sure how they'll answer.
- Book 45 minutes, and send the agenda the day before.
- During the meeting, take notes on page 5 and agree 1 action for you and 1 for them, each with a date.
Page 3: the 8 questions
- What are you working on right now that you're proudest of?
- What's slowing you down that I might be able to remove?
- How do you like to get feedback: in writing, in the moment, or saved for this meeting?
- What worked about how the team ran before, and what would you change?
- Where do you want to be in 18 months?
- How would you like to use this time each week?
- Is anything worrying you about how things might change now that I'm your manager?
- What should I know about you that wouldn't show up in a performance review?
In the planner each question carries a 1-line note on when to use it. Question 7, for example, is for anyone who was a peer last month.
Page 4: the example
Ana and Raj are illustrative, like Leah. Ana was promoted 3 weeks ago and now leads the 5 engineers she used to work beside, and Raj is a senior engineer who also applied for her role.
| Field | Ana's entry |
|---|---|
| Context | 4 years on the team, leads the billing migration, applied for my role, prefers Slack to meetings. Want to know if he still wants to lead people. |
| Questions chosen | 1, 4, 5 and 7 |
| Dropped | 6, too open for a first meeting where he may be guarded |
| Agenda message | "Hi Raj, for tomorrow I'd like to cover 4 things, listed below. No prep needed beyond a quick think." |
| Actions | Ana shares the roadmap draft by Friday. Raj writes up the migration risks by next Wednesday. |
Pages 5 and 6: working pages and done
The working page repeats the example's fields, empty, with room to type in the Google Doc or write on the printed PDF. Ship both versions, and set all text as live text so readers can search it, copy it and use a screen reader.
Page 6 holds the 3 done boxes and a reply invitation: "Which of your 1:1s are you dreading? Reply to the email this came with and tell me." A reply is the first small step from audience toward the kind of community the Community Engine guide describes, and it costs the reader 1 sentence.
Test the guide with someone in the intended audience
Give the draft to 3 to 5 people who match your reader, ask each to complete the task while thinking aloud, and stay silent while they work. Time how long the first result takes and note every hesitation and skipped page. Fix the biggest problems, then test the revision with someone new.
Jakob Nielsen's case for testing with 5 users rests on a model he built with Tom Landauer from data across many projects. It estimates that 5 participants find about 85% of the usability problems, so Nielsen advises several rounds of 5 over one big study. He adds that the math holds only for comparable users: with 2 distinct reader groups, test 3 or 4 people from each.
The think-aloud method, from the same research group, has 3 parts: recruit representative users, give them representative tasks, then let them do the talking. Nielsen was writing about websites and software. I think the logic carries to a workbook, where the interface is your page order and your field labels.
Book an hour for each session
An hour is 3 times the promised 20 minutes, which leaves room for a slow first attempt and your closing questions.
- Recruit people who match the reader, ideally loose contacts who'll be honest with you.
- Open with: "I'm testing the planner, so anything confusing is its fault. Please plan a 1:1 with one of your reports and talk me through what you're thinking."
- Stay silent. When they ask you something, reply "What would you do if I weren't here?"
- Time it from opening the file to the first finished agenda.
- Close with 2 questions: "What did you expect to find that wasn't here?" and "Would you use this before your next 1:1?"
Log each problem with the page, what happened, the tester's words and a severity: blocks the task, slows it, or minor.
Leah's first test (illustrative)
Marcus, an illustrative tester, was promoted to engineering manager 6 weeks earlier and has 5 direct reports. He took 41 minutes to finish his first agenda, against a promised 20.
His log below is 1 session. In a round of 3 to 5, merge the logs and fix anything that blocks the task first, then the problems more than 1 tester hit.
| Page | What happened | His words | Severity |
|---|---|---|---|
| 2 and 5 | Wrote a mix of facts and goals in the context box | "Is this what I know about him or what I want from the meeting?" | Slows |
| 4 | Missed the example until stuck on step 2, 2 pages away | "Oh, there's an example." | Slows |
| 3 | Picked 7 of 8 questions for a 45-minute meeting | "They all look useful." | Blocks, since the agenda can't fit |
| 2 | Asked how to word the day-before message | "Do I send the questions as a list?" | Minor |
The revision
| Problem | Change |
|---|---|
| Context box read 2 ways | Split into "What I already know" and "What I want to learn" |
| Example too far from the steps | Ana's answer printed in gray under each field of the working page |
| Too many questions picked | "Pick 4" set in bold, with "about 8 minutes each" beside it |
| No wording for the agenda message | A 3-line message template added to step 3 |
A second tester, Priya (also illustrative), manages 4 people and finished in 22 minutes with the meeting booked. Her only note was that she'd print it, so the PDF stays.
Use Marcus and Priya as a model of what to record, and expect your own testers to find different problems. Theirs are the ones worth fixing.
The Useful Download Build Kit has the 6-page template, Leah's revised planner, the session script and the notes sheet.
Your next step is the result sentence. Write it today, build the 6 pages against it, and book 3 short sessions with likely buyers before you spend anything on design. Once the guide passes, the lead magnet landing page template covers the signup page and the delivery route.