3 min read
Intuitive Stack
Rabbit Holes vs. Rescue Ropes: Designing for Reader Intent
A Wikipedia reader and a support agent or service technician are in two different worlds. One is following curiosity; the other is fighting a fire. Here is how to know when a sub-topic needs to stand on its own.
Key Takeaways
- A Wikipedia visitor might be down a rabbit hole in browsing mode; a documentation user is in task mode and needs rescue ropes.
- Use the One-Question Test to decide when to split a topic: does it answer a distinct question, and can someone arrive cold and leave with what they need?
- Splitting on logical separability, not word count, is what lets search engines and AI systems surface the exact answer instead of an entire page.
As a technical writer, I’d get requests to “add just one more thing” to a section of documentation. For some topics, that meant it just grew out of control, until a single topic was pages and pages long.
Intuitively, I knew none of that could stay consumable or skimmable for a novice or even an intermediate user. It was content really designed for the expert, and that always made me uneasy: content added for the expert made things worse for the novice.
So I was often hunting for a place to put the “expert stuff,” cleaving off bits and pieces to stash elsewhere, wherever elsewhere was. I needed a framework for deciding when something had gotten too big and needed to be reshaped.
Wikipedia is a standard reference for “Every Page Is Page One”-style content. Its articles are designed for browsing mode, where readers often follow “rabbit holes.” Because of this, Wikipedia’s size guidelines prioritize logical separability—the moment a sub-topic is distinct enough to stand alone, it gets its own page.
It was a logical separability framework that I needed.
Why documentation readers need a rescue rope, not a rabbit hole
Documentation readers are almost always in task mode. They aren’t usually following curiosity about your product (although sometimes they do); they are looking for a rescue rope. When a user is on the clock, their ability to filter out “interesting but irrelevant” context diminishes.
When should you split a topic? The One-Question Test
Writers often ask me how to handle a topic that keeps attracting new material. The temptation is to let it grow, but length is merely a symptom; separability is the real question.
If you are wondering whether to split a topic, apply the One-Question Test:
Does this section answer a distinct, specific question? If yes, it likely belongs in its own topic.
Can a reader arrive here cold and leave successful? If the section requires the context of the entire page to make sense, it is a fragment. If it stands alone, it should be its own addressable unit.
Is it a “distinct topic” or a sub-step? Wikipedia editors ask if content is complete enough to stand as a distinct topic or if it properly belongs inside a larger one. In user assistance, if a sub-section is a destination for a search result, it needs to be a separate page.
How splitting topics helps search engines and AI find the right answer
A person reading documentation has a specific work problem and wants an answer quickly. Applying the One-Question Test consistently means search engines and AI systems surface the “rescue rope” directly, rather than forcing the user to hunt through a “rabbit hole” of tangentially related info.
If your team is struggling to define where one topic ends and the next begins, schedule a conversation to refine your editorial standards.
