Documentation is King

Technology industry leaders know that documentation is king when it comes to the success of any technical team. If you learn something, write it down... the entire team benefits.

This is a fundamental process to our industry, so why do we still struggle with it?

The Struggle

Technical teams typically struggle with one thing... document repositories and libraries that do not operate the way that technical people think. Technical folks think in the form of workflow diagrams, a sequence of if/then that isn't always linear. They are constantly scanning long documents for relevant information, and fast forwarding videos to get to the relevant content. They find the process of documentation daunting, they can't just add a step to existing troubleshooting, It has to be a full and complete new document each time

A Lightbulb Goes On

What if we turn technical documentation and knowledgebase software on its head? Why can't our technical documentation follow a workflow path, with each workflow object being a simple troubleshooting step? Why shouldn't the information be delivered in bite-sized portions for just in time (JIT) delivery? Why can't each step of a standard procedure correspond to a task in a checklist?