A good guide removes steps, it does not add them

Most people who look for a guide are not looking for more to do. They already have the thing in front of them: the form, the decision, the phone call they have been putting off. What they want is for someone to have walked the path already and to say, plainly, here is what matters and here is what does not. A good guide removes steps. It does not add them.

Why so many guides add steps

Guides get written for reasons that have nothing to do with the reader. A guide can exist to capture an email address, to warm someone up for a sale, to look thorough, or to demonstrate that the author knows a great deal. Each of those purposes adds something between the reader and the answer: a signup, a series, a chapter of background, a reminder of what could go wrong if they do not act now.

The reader feels each addition as weight. They came in with one question and left with three, or with a login, or with a sense that the next step is bigger than they thought. The guide has done its job for the author and failed at its job for the reader.

What removing steps looks like

Start with the step the reader is actually standing on. Not the history of the topic, not the reasons it matters, not what the author wishes they had known ten years ago. The reader has a today. The guide should meet them there.

Name the terms once, in plain words, the first time they appear. A reader who has to look up a word in the middle of a guide has been handed another step.

Say what can be skipped. Many processes have optional parts that are presented as required, and readers spend their limited energy on them. A good guide is willing to say: you do not need this yet, or you may never need this at all.

End with what to do today and what to do this week. Not a list of everything that could be done, but the few actions that move the reader forward from where they are. If the situation is complicated, say so, and say where to go for help. That is not a failure of the guide. It is the guide being honest about its edges.

Calm is a design choice

Urgency is easy to manufacture and it nearly always serves the writer. A countdown, a warning, a phrase like “before it is too late” pushes the reader toward action while narrowing their ability to think. The Forward Project does not do this. Our guides are written to be read once, used immediately, and returned to whenever they are needed, without a gate, a timer, or a pitch on the last page.

The same is true of tone. A reader working through something difficult does not need to be told how difficult it is. They know. They need the path, described by someone steady.

How we decide what to write

We write what people keep asking. When the same question arrives from different directions, from clients of the studios, from friends, from strangers who find the site, it becomes a candidate. We ask whether a clear, well made answer would actually change what someone does next. If it would, we write it. If the honest answer is “it depends,” we write the guide that helps the reader find out what it depends on.

What we ask of a guide before it is published

Would a reader with no background understand every sentence. Is every step here one the reader has to take. Have we said what to skip. Does it end with today and this week. Is there anything in it, anywhere, that exists to serve us rather than them. If the last answer is yes, it comes out.

A guide is a kindness with a structure. The structure is there to make the kindness usable. When the two are in conflict, the kindness wins.