Minimum Viable Documentation


You're working at a startup building a "minimum viable product" -- and everything about the product is being cut down to bare minimum to reduce the risk and cost of failure. Deciding what to include in "Minimum Viable" is difficult, and the value of documentation in service of product development is often misunderstood by project managers who work in this style, who often choose to forego documentation altogether.

I will make the case for including documentation in "viable": We'll consider ways of understanding your target audience, helping introduce them to your software and getting them unstuck, and make the case for minimum-viable in-house developer documentation.