Writing documentation is not high up the “fun ways to spend my time” list. It is however, an important part of any software package – especially if you don’t have a support team.
Generally it is good practice to have someone who is not the developer write the docs; the developer is often too close to the product and can’t see their own blind spots. Perhaps in the future I’ll decide to outsource some of the documentation, but for now I’m who I’ve got to get this done.
One of the things I’ve added throughout the docs for this release is a “how to get to this screen” explanation on every screen page. More than once I’ve sent someone a link to the “new user” screen or similar only to get a reply asking how to get to that screen. So hopefully that is one blind spot I’ve taken care of.
This post is part of the project: Tasks Pro™. View the project timeline for more context on this post.