The difference between a good design doc and a great one is usually clarity.
Technical writing should be crisp and to the point. So, it is always better to treat every sentence like it has a cost. After writing, cut aggressively. Remove extra words. Then check if a line can go. Sometimes even a full paragraph is unnecessary.
One thing I always do is to start the doc with the conclusion; this way, the reader/reviewer knows where we are heading.
This is contrary to how most engineers write docs - listing every approach first and only concluding at the end. That slows readers down. I avoid this because long explanations make people lose track; most readers want the conclusion quickly.
So, always start with the answer and why it matters. Then add details and alternatives below for those who want depth.
A habit that helps is a quick editing pass like this:
- Remove filler words and repeated ideas.
- Break long sentences into smaller ones.
- Prefer bullets when listing options or steps.
- Check if the first section clearly states the outcome.
- Add a link or short explanation where a reader may pause.
Empathy matters more than most people realize. Try to read your document as someone new to the topic. Ask yourself what might confuse them. Add the missing context. Add the helpful link. Let the ideas evolve naturally from problem to solution. This skill develops over time.
Use simple language and fewer buzzwords. The goal is to communicate, not impress. Simple documents get read more. More readers means better alignment and better visibility for the work.
Finally, always provide enough context. A short setup about the problem, constraints, and prior decisions goes a long way. It helps readers understand why the decision exists, and, of course, it prevents unnecessary back and forth later.