My own compiled tips

  • Almost always have a What, Why (now) sections (see Software documentation). But donโ€™t call them like that, summarize the what, the why and the how in one sentence: those are the titles of the sections.
  • Always have a table of contents! Talk in lists, have sections. Itโ€™s the map of your ideas! Use outlines in order (h1, h2, h3โ€ฆ). They donโ€™t have โ€:โ€œ. Be consistent on the format (underline, no underline).
  • You know too much! Way more than the reader. Give detail, define concepts.
  • Be specific. Instead of โ€œwe had a decreaseโ€, how much decrease? How was it measured?
  • Use the active voice, simplify! Shorter sentences, no fillers.
  • Write simple. Short sentences, avoid colourful language (overdose of adjectives, adverbs), be consistent in nouns and verbs.
  • Writing is like coding, you need iterations and refactoring: first make it work, then make it right, and finally make it fast.
  • Make it easy to respond: ask explicit questions, draw attention to where you want input.

References