Systems Over Sentences
Not tips. Not listicles. Writing for DevTools and SaaS founders on the architecture, ownership, and craft underneath good technical documentation.
Latest: Part 06
Most writing problems are not writing problems. They are structure problems that writing cannot fix. Structured writing is the practice of separating what you know from how you present it, so the same content can serve any reader, any channel, and any future version of your product.
“Structure is not a constraint on good writing. It is the condition that makes good writing possible at scale.”
From Part 06 of Systems Over Sentences
A complete series for technical writers and the founders who work with them. Start from Part 01 or jump to wherever you are.
Three elements separate documentation that works from documentation that merely exists. They show up in the same places every time.
Same information, completely different job. Here’s what that distinction actually means in practice, and why getting it wrong costs more than you’d think.
Documentation doesn’t break at the writing stage. It breaks when no one clearly owns what happens next.
You can’t control which page your reader lands on first. What you can control is whether every page has windows that connect them to what they need next.
Most people think technical writing is about writing. The real job is designing how information works. Here’s the distinction that changes everything.
Most writing problems are not writing problems. They are structure problems. Here is the framework that separates content that scales from content that stalls.
Subscribe by email or follow on LinkedIn to get the next part when it publishes.
I’m Douglas Ebhoman, a documentation systems specialist based in Prague. I came to this work through creative writing, which means I arrived already knowing that the hardest part of any document is not what you write. It’s understanding what the reader is carrying before you ask them to carry something new.
This blog is where I think out loud about the systems problem underneath documentation. Not tips. Not trends. The structural decisions that determine whether a documentation system holds up or slowly becomes a liability.
If your product is scaling and your docs are not, the Documentation Audit is where we start.
Douglas Ebhoman
Documentation Systems Specialist · Prague
“Narrative is infrastructure. I treat it that way.”