Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
At the end of the day, roadmaps are a communication tool. To figure out which ones are right for your company, think about your audience and what they need to know: Product development teams: These are generally highly detailed, require commitments from engineering by quarter, discovery and delivery status, and are usually a quarter in length. Sales teams: Sales teams need fewer details. They need bigger-picture items that address problems and rough timeline on releases (either quarterly or half year). This is where the narrative/value proposition for each feature to customers is important to include as well. Leadership: These roadmaps focus on the “initiative to strategic intent” layer. They’re used to talking about dependencies and capacity planning, and follow quarterly timelines.
Product Operations
Melissa Perri and Denise Tilles
I often look at the Objective and see if there are words that could be quantified. In the example above, “love” becomes NPS4 and “sales” becomes referrals. Both are measurable outcomes.
Radical Focus SECOND EDITION
Christina Wodtke
For this reason we built the Tabbed Inbox through a series of build-measure-learn loops, which are called Steps in GIST. There were usability tests, longitudinal studies, fishfood and dogfood, labs, and partial launches. Each step generated a more complete version of the product, but also gave us new evidence, which helped build our confidence in the idea and get more funding. We used what we learned in each step to course-correct and improve the idea. The feature we eventually launched was profoundly better than the one we started with.
Evidence-Guided
Itamar Gilad
...catch up on these, and many more highlights
Readwise