Why structuring documentation is like dating (only less awkward)
Yes, you read that right: there are some surprising similarities between these two seemingly different activities. At Flow, we specialize...
top of page
Blog
Summer’s over, yippee! Feel those first day of school vibes!
Time to sharpen those documentation skills. At Flow, we are ready to do our part with a comprehensive curriculum of technical...
The Expertise Paradox: the more you know...
As the tech world evolves, we learn as we go and we share what we learn with our peers. But at what point do we become experts in our...
The Simplicity Paradox: Easy words don't come easy
Slogans, poems, and Ikea manuals have something in common: They all look deceptively easy to create. Deceptive, because often the easier...
The Documentation Paradox: Why we love and hate documentation
Why is it that so many professionals who should write documentation, just don’t? It is the documentation paradox.
Documentatie voor ontwikkelaars: docs-as-code
Zorg met heldere documentatie voor betere code Bij software zijn niet alleen handleidingen voor gebruikers nodig, maar ook documentatie...
Simon says: Automatiseer mijn schrijfwerk
We dromen allemaal wel eens van een tool die onze gedachten leest en rechtstreeks omtovert tot een vlotte blogpost, klaar om te...
Video’s en/in documentatie: a match made in heaven?
“We zouden dat graag met een filmpje documenteren, kan dat?” "En of dat kan! We gaan daar bij Flow graag mee aan de slag." De...
Gestructureerd schrijven in een notendop
Structured writing in a nutshell
A questionnaire to help you to help them (2/3): Can your customers USE the answers?
This second group of survey questions focuses on the next step: is the answer you got correct, up-to-date and understandable?
A questionnaire to help you to help them (1/3): Can your customers FIND the answers?
In this first part we look for an answer to the questions: “Is it there?”, with subcategories: available / accessible / targeted.
bottom of page