» When designing an experiment to test a hypothesis, ask how might it fail, and what you need to find out
» Luck and uncertainty mean that even good decisions can have a bad outcome (and vice versa)
» Framing our beliefs with a confidence percentage makes us more willing to accept contradictory evidence
» Every other team is allowed to be uncertain about the future — so should product
» There are different types of question for strategy, opportunities and interventions
» Avoid investments that are neither defense nor offense
» What people say and how they really feel can often vary
» Focus your prototyping on the moments that matter most to users
» Prototypes range in fidelity, but remain throwaway
» Prototyping brings tangibility to intangible experiences
» Be clear about what you want to learn, and what assumptions you want to test
» Design simply to deliver early and learn quickly
» Learning is more valuable than being successful and not knowing why
» You can experiment with the content and layout of any web-based product with basic skills
» The success rate of experimentation is higher if there is no penalty for failing
» “If you have a good idea on a Monday and can design, test and learn by the Friday, then innovation explodes.”
» Remove the timelines from your product roadmap
» Use roadmap themes to focus on solving user problems
» User outcomes are more important than delivering features
» Roadmaps help to make strategic decisions when there’s low certainty
» Rethinking your roadmap approach can help when managing mature products
I gave a talk recently about how I’ve been using data and analytics to guide my decisions in product management. I’ve edited the transcript a little and split it into bite-size parts for your entertainment. This final bit tells the secret behind meaningful product roadmaps.
I gave a talk recently about how I’ve been using data and analytics to guide my decisions in product management. I’ve edited the transcript a little and split it into bite-size parts for your entertainment. This bit is about how UK government digital services gather and use evidence.
This is a little post about some ways to convince a reluctant development team that experimentation is A Good Thing.
