Taking the ‘ewww’ out of Workflow Doc(ewww)mentation

Most people hate writing documentation. Sometimes it’s because we aren’t confident writers. More often in the tech world, it’s because nobody wants to spend the time going back through the project to write out all the steps for the non-techies. It’s time-consuming and boring. I get that. What I don’t understand is why we don’t make it easy on ourselves by creating the documentation during the project creation process to begin with, but then I’m one of those weird snowflakes who uses descriptive variable names and comments in the code. I like to joke that I have a mind like a steel sieve, but there’s some truth to having to take the time to remember where I was in the project and what I was thinking when it’s been on the shelf for a while. Clearly defined code helps a lot. But I digress. Did you know that OnBase Studio has a feature that generates fully formed administration and user guides for your Workflow Life Cycles?