» It can aid a team’s progress to make lots of small bets, rather than one large one in a quarter

» Separate your outputs in a release plan from the outcomes in your product roadmap

» Parkinson’s Law: work always expands to fill the time available

» Outcome-driven product roadmaps shift the focus from building features to solving user problems

» A product roadmap is a communication tool first and foremost

» A now/next/later roadmap helps teams to focus on the bigger picture

» Delivering outcomes instead of outputs is harder, but more valuable

» Competing execs will sometimes sabotage by claiming features for their own product long before they plan to implement them

» Your product roadmap can reveal symptoms of underlying organisational dysfunctions

» We need to consciously remember that the needs of our users change over time

» Many biases are underpinned by shared psychological mechanisms, such as the desire to feel positively about ourselves

» 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