Categories
Agile development Product development Product documentation

The perfect product documentation

What makes a perfect product documentation? Is there any exceptional documentation example? How much effort should be put into?

What makes a perfect product documentation? Is there any exceptional documentation example? How much effort should be put into?

Product documentation is always outdated, hardly to understand and only written for the DAU or power user, and thus does not help the average user.

The fictional user

Product manual from the users perspective

Looking at the average user of a product, the typical usage pattern is: buying the product, unboxing it, starting and using the product, running into a problem and calling the support for help – of course with highest priority and requiring the solution ASAP.

The documentation, help system, manuals or operation instruction are used only by probably 30-50% of the users, depending on age, gender, background and the product itself.

In the past, the product documentation was not very “user friendly”, written with technical terms, long and hard to understand sections, screenshots and step by step instructions. It was teaching the program and application, from the creators perspective.

Looking at todays user that interacts with a new application, web page or mobile app – they only search for a help button or linked online manual in case of emergency. The product itself is expected to be simple, user-friendly and easy to grasp – even for complex tasks or features.

Reading a big book or textual folder of written pages is no longer accepted. Also big Word or PDF files with hundreds of pages are not user friendly.

Different user persona as e.g. the new user, a power user or administrator of the customers IT department need different type of documentation.

Today a multitude of application, software and apps are used together. They are running somewhere in the cloud, or are installed on-premise in the local network. Often, the products use different concepts of the user interaction and usability differs. So, the user is confronted with a set of totally different “things” to solve the tasks on hand, in a very short amount of time.

Product documentation – as seen by the producer

Todays customer is expecting regular updates of the product. The modern, agile development environment produces new product version in short frequencies – with monthly, bi-weekly and even multiple updates every day.

Keeping the documentation of a complex, advanced product up to date is very challenging. Technical writer or other experienced employees need to keep track what changed and update the manuals.

Often input and knowledge of the development, testing, sales or support teams needs to be incorporated into a well-written documentation.

For multi-language products, requiring additional translation and verification steps, the process gets more complex and delays the production of the final documentation even more.

Advanced manual incorporate screenshots, videos and other resources. Keeping them up to date with every product update is nearly impossible – especially in a multi-language application.

The manuals, onboarding resources, knowledge base and more user-product-related information can be handled by the support platforms as Zendesk or Freshdesk. They are focused on providing Q&A information, and help the customer in need. Mostly, providing product documentation is only a part of the whole support platform.

So what is the perfect product documentation?

Looking at the market, there are various product documentation products and platforms available.

This could simple as e.g. providing PDF file-based documents or even written folder.

If an online-based solution is required, a Sharepoint site or a hosted WordPress website could good enough.

For a more complex product with a bigger user base, a support platform with build-in product documentation and knowledge base could be a good fit.

A developer-centered approach as using Asciidoc-based files during the development- and QA phase is also possible.

Specific, stand-alone documentation platforms providing multi-language, versionized user manuals are on the other side of the market.

As always – there is not one perfect solution. Depending on the product, target market, the companies structure and departments a different approach is better suited.

Starting with a simple approach, targeting the customer needs and problems at hand, and improving the tooling and processes over time is often the best way to solve this problem

Leave a Reply

Your email address will not be published. Required fields are marked *