How can you drive the thinking on what to develop, why and how to do it — leveraging the insights from both team and stakeholders — all the way from idea to deploy?
This book tries to answer the above question. As part of our own product development at Delibr, we interviewed over 300 Product Managers to understand how they work and collaborate around feature development, what problems they face, and the many approaches to solving those problems.
"Epic alignment" describes four broad approaches that we saw help Product Managers excel.
What you'll learn
How to drive product development towards impact based on research How to use user stories as a shared language to align your entire team How to write feature documents that drive joint understanding and act as a single source of truth How to tackle the massive amounts of decisions needed for every epic
A quick read that has made me think about documentation (and especially about exposing decisions), but is ultimately a bit too basic.
My main problem is that the success of implementing Nils’ documentation approach heavily relies on using an outliner. If you’re using Confluence, Google Docs or Word, then you’re going to lose your stakeholders and engineers trying to do this. I would have liked to see some methods and strategies for overcoming ballooning documents if you don’t have an outliner, but that’s nowhere to be found.
I get why — Nils’ company delibr is an outline tool startup targeting product companies. I just feel like I’ve spent £10 on some marketing intended to make me Google ‘outliner for product managers’ and land on the delibr website.
I like that it is driven by interviews with lots of Product Managers, and I wish some more insight had been produced and visualised from that.