Is there such thing as too much documentation?

Being innovative requires that you think outside the box

And not overly rely on pre-conceived notions on how things ought to be

So you want to use a clean canvas

But there are benefits to using past data points as a benchmark

To understand the gap that your innovation is closing

To facilitate the test and learn phase

And clear documentation allows you to revise and refine requirements faster

Especially when team members move on

You want to be able to pick up where they left off and minimize rework

Documentation requires a lot of effort 

And it becomes outdated, if not properly maintained

But you want a balance between creating that product roadmap and creating detailed documentation to allow collaboration to take place

What’s been the right amount of documentation for you?