TLDR
Product Roadmaps are great or terrible in proportion to how well it does the job of communicating what those outcomes are and what our current plan is. Too many product managers and engineering teams are working without product roadmaps. Outcome based roadmaps that connect with day to day work are a better way to plan effectively. The two milestones on the bottom side of the timeline exemplify the don't do of a roadmap, namely: do not use phrases that don't clarify purpose. Do not define the feature specifications without giving context.via the TL;DR App
no story
Written by balach | Founder at https://epekworks.com - passionate about products, their users, and the makers
