Table of Contents
This October marks a year since my switch from working on client software to working on the unified Microsoft documentation experience. Throughout the past year I had to learn a tremendous amount of absolutely new (to me, at least) things that totally changed my perception of what the importance of documentation is.
Building Documentation Systems is Not Easy #
I like to think that this is what I looked like when I was first coming in, thinking “well of course, publishing systems - we’ll get this done”:
Here is me a month in, realizing the sheer amount of complexity involved both in the publishing process as well as in getting a balance between the internal and external needs:
When it comes to documentation, it’s often not as simple as “spin up a new website and just start hosting it there”. There are requirements and expectations from the user - how they want to see content organized, structured and presented. The needs also vary between users who are using Platform X vs. users who are used Platform Y. That translates into systems that need to abstract out a lot of those under the hood of a unified experience. That is both time and resource consuming.
And now take all of the above and apply them to the Microsoft scale, where we work on tens of thousands of pieces of content. And a lot of them are generated from automated code-scanning tools.
Code Comments are Never Enough #
While at first glance, “never” might seem like an exaggeration, I learned first hand that it isn’t. You want detailed docs. You want docs that tell you why you are doing certain things and not just how. After writing several tools, setting up several dev environments for a number of other tools - no, comments are never enough. Even two months in, sometimes I would look back and realize that I have no idea what I was doing. Hours later, the realization comes: “Oh yeah, I forgot there is a parameter somewhere that is forced in a certain value so now I have to re-define it within the extension”.
Not something that you want to write an essay within your code, and guaranteed you are not the first and last to stumble over a certain issue - so spend an hour writing a doc that outlines how something works.
Writing Documentation Helps You #
That is, regardless of whether you are a developer, writer, manager or marketing person. In my own position, as a PM, I strongly believe that a great PM knows how to write great copy. And for that to happen, you need practice. Practice in making your documentation more accessible, more engaging and covering the customer needs.
You want to be able to put together coherent, thought-through pieces that make the user both delighted with the quality, but also with the ability to finish the needed task from A-Z.
The above will benefit you long-term and way beyond just your career.
Documentation is Not “Write and Forget” #
More often than not, you and your users will refer to the same piece of documentation over and over, over the span of weeks, months and even years. Maintenance here is never an after-thought but an expected part of the lifecycle (speaking of which, do take a break and listen to this Freakonomics podcast - “In Praise of Maintenance”).
As you plan investment into your docs, account for the fact that you will need to make changes, additions and remove obsolete parts of those. Documentation is not a blog post (and I see the irony here) where it attracts attention for a couple of days and then dies down. It’s an evergreen organism that people rely on in business and personal life.
Documentation is also a Product #
Too often I hear that documentation is something that compliments a product, but is not the product itself. The reality is - documentation for a tool or service is just as important as the product itself. It is important to always collect, assess and react to customer feedback, it is important to keep it updated and it’s even more important to write it.
Don’t assume that users will figure things out, and for new problems that they will encounter docs will be written. Taking that path will lead you down the road you don’t want to go.
Documentation Goes Beyond Technical Writing #
Think about the last time you used a developer doc. What went into it? Depending on the product or language that you were looking at, you will realize that the doc contained some code samples, screenshots, animations, links to a videos (or any combination of thereof).
All that is key to creating great documentation, just as much as it is key to be writing great content. Make your documentation engaging by providing multiple ways for your users to consume it. Enable your users to download a sample and execute it to see how the app works, enable them to watch an interactive video that shows step-by-step how things work.
Personally, I am not a fan of walls of text - what if what I am reading is not even relevant to me? In what ways can one show appreciation for users’ time and effort put towards learning your tool/language/product? By having them actually see that the things they need are the things you are offering vs. making them sift through mountains of articles only to realize that what you described isn’t even covering their scenario.
In Conclusion #
I am sure that as months and years go by, more lessons will be learned, more caveats will be discovered to everything I wrote above, and even more documentation will be written. The one important lesson that stuck with me, though, is this - it’s never as easy as “write and click Publish”.