Documentation

Contents

What is documentation?
Examples of product documentation

Join 6000+ product leaders

What is documentation?

💬

Definition of documentation

Documentation can relate to two different types: products and processes. Product documentation describes the product under development and provides guidelines on how to execute actions with it. Process documentation, on the other hand, relates to all the material created during development.

Examples of product documentation

Product documentation tends to include requirements, technical specifications, commercial rationale, and product manuals. In contrast, process documentation includes aspects like obligatory standards, material outlining the wider project, plans, test itineraries, general reports, and even generic notes. Broadly, the difference between the two is that product documentation details an object (be it tangible or digital), and process documentation details the timeline of creation.

Get our Mastering Prioritization eBook

Learn how to prioritize by making it a simple process, to build products that stand out. Learn more about how to source insight, choose the right prioritization framework and much more.

Get the eBook

General FAQ

What is the main purpose of documentation?

Documentation’s main goal is to keep product developers and stakeholders on-track, helping to hit the targets considered essential for a project’s success. There are different types of documentation — products, and processes — with their own specific criteria.

How do you write product documentation?

Product documentation includes multiple elements. The writers will cover the roles of a project’s participants and their responsibilities, establish the goals for different teams or individuals, user stories, acceptance criteria, and questions that should be answered along the way.

Who is responsible for product documentation?

Product teams are generally responsible for product documentation, with the core developers being accountable for the more complex aspects. Ownership should be established as soon as possible, to avoid confusion or wasted time that may disrupt the product team’s efficiency.

Building better products
starts here

Join thousands of product managers and makers who already enjoy our newsletter. Get free tips and resources delivered directly to your inbox.