In the past month we’ve looked at why it’s so difficult to be outcome-led, the ugly truths about NPS in B2B companies, what it means to build a diverse product team, and much more besides. In case you’ve missed any of it, here’s the rundown on our most-read posts in April.
3 tips to ensure a flexible product roadmap
In this post Jordan Jacobi shares some tips to “help you build a roadmap that’s set up to conquer the unknown”. She advises that you prepare your post-release workflow, because mapping out potential workflows and defining priorities can help you make decisions more quickly post launch. You should also lay out your work in a visual roadmap in order to help stakeholders and prioritise outcomes over outputs, says Jordan.
Dealing with HiPPOs and big dogs in product
In this article we catch up with Randeep Sidhu, the former Head of Product for the NHS Covid 19 app, to find out what he’s doing now and hear about his strategies for being successful in companies that have little to no knowledge of product management.
How to build an MVP that matters
Author Robert Schlaff says that in his two decades as a product manager, he’s seen how much value agile tools can bring to software development. But he says they’re also often misunderstood and abused. Minimum Viable Product (MVP) is a powerful tool, driving production and cutting waste, but it’s often misinterpreted as “the lowest quality thing I can build.” In this article Robert shows us how he’s used the MVP process in his career and built MVPs that matter.
The 9 ugliest truths about NPS in B2B
Senior Product Manager Paula Stürmer shares her thoughts on product managers who regularly use NPS as a metric in their B2B practices. NPS may be a widely used measure of customer satisfaction but it has many pitfalls, particularly in B2B products, she says.
It only provides a snapshot of the moment and doesn’t paint a comprehensive picture, she says, and doesn’t give any insight into problems. There’s also a long time lag between feedback and action, and an excellent score doesn’t mean much.
10 tips for writing good product handover documentation
Abigail Lloyd has worked in product development for more than 10 years so is well placed to offer some insight on what makes good product handover documentation. Briefly, she advises you shouldn’t assume that your audience has prior knowledge of the product and that you focus on answering questions that will develop understanding. Share the good, the bad and the ugly – such as defects and known workarounds – Abigail adds. She also suggests you link to other apps where relevant, and that you share ways of working.