Because Nobody Reads the Manual
The story of making a book instead of a user guide
Takeaway: "The best way to explain how something works is to tell the story of why it works that way."
On every pre-launch to-do list there's one strange item. It isn't code and it isn't design, yet it keeps sliding to the bottom. The manual.
If you build a service, you have to explain how to use it. Obvious. So I sat down to write the manual, and before the first sentence, a question surfaced.
Have I ever actually read a manual?
No. Almost never, to be precise. When I sign up for a new service, a "getting started" guide pops up, and I close it. When I'm curious about something, I search; when search fails, I give up. A manual is often a document that proves the maker's diligence, not one that serves the reader.
My bookmarks folder holds about 300 things saved "to read later." I have reopened 2. There's no reason to believe a manual I write would meet a different fate.
So I asked the AI a different question: "Is there a way to teach people how to use this without writing a manual?"
This time I convened a meeting. A book designer, an essayist, a SaaS planner, a marketer — four imaginary specialists, each shown the same problem, each returning their own answer. It's the privilege (and the cheat) of working alone: you can hold a meeting without a meeting room.
All four answers converged on one point. Don't explain the features. Tell the decisions.
Stacktube has a fair number of features that need explaining. Register a channel and new videos get analyzed; notes pile up; they get delivered to Obsidian or Kindle; a month's worth gets bound into a book. Write all that in feature order and you get a manual. But every one of those features carries a reason it was built that way.
Take the free plan's analysis cadence — bundled to once a week. It isn't only about cost. Notes that arrive daily eventually stop being read, and a pile of unread notes is no different from a pile of YouTube watch history. The monthly digest EPUB carries no ads and no "read more" links. At the end of a month, at least, I wanted readers to hold something that doesn't interrupt itself.
None of this fits in a feature table. But once you know it, the way you use the service changes. Instructions are memorized; reasons are understood; and what's understood isn't forgotten.
So instead of a manual, I made a book. With rules.
The unit of a chapter is not a feature but a scene. Not "How to register a channel" but "The day your first note arrives." The words "manual" and "guide" were banished from the title. The book came to be called The Stacktube Companion. Mechanical information — plan tables, setup steps — was exiled from the body into a single appendix. The body stays an essay to the last page.
Length became a discipline too: 40 to 60 pages, 4 to 6 per chapter. "A manual dies the moment it gets thick," said the AI playing book designer. I had no rebuttal.
The design wasn't created from scratch. Stacktube already publishes a monthly mook that binds your notes into an EPUB, and this book wears that design system as-is. Only the cover changed color, from amber to deep teal. So this isn't a standalone document — it's issue zero of the monthly series. A companion volume. A book dressed in the series' clothes, showing you how to read the service before the service arrives.
I made one in Korean, one in Japanese, one in English. Not translated — rewritten in each language. And all three now sit here in this workshop. You can read them without signing up.
A manual would have taken three days. The book took longer. I don't regret it, for a simple reason: nobody would have read the three-day manual, and this book has been read cover to cover by at least one person. Me. And if the person who made a document can read it to the end, there's a chance someone else can too.
🔧 Technical terms in this episode
Onboarding The process of a new user settling into a service, usually implemented as a "getting started" guide or tooltip tour. This booklet is an attempt to replace the tour with prose.
Mook Magazine + Book. A publication issued like a magazine but bound like a book. Stacktube's monthly digest EPUB follows this format.
Companion volume A supplementary book attached to a series, numbered as issue zero — the series' entrance. It must wear the same design as the main series to signal it belongs.
Transcreation Translation that rewrites for equivalent effect rather than literal accuracy. A joke in the Korean edition may become a different joke in the Japanese one.
The Stacktube Companion — 1.0