Spine of a product “road map”
System
Purpose
The 4 pieces below represent what I’ve found is necessary to summarize your thoughts, gain consensus with your team, and deliver product.
Vision
Long term vision of your product consolidating the lenses of business, design, engineering, and company identity. Typically takes the form of design prototypes, business objectives, scalability of the technology, written in language representative of the culture of your company.
Road map
How you’re going to organize your thoughts to talk, discuss and plan the next 6 months to a year. Currently verbal and shifting, in need of being written down, but comprised of 3 milestones representing different time horizons.
Feature list
Trello board of more detailed features fulfilling your road map 1, 2, and 3ish months out.
Release plan
Excel document detailing the sequence of features you will build and launch in the coming quarter. Typically organized by objective and/or team building the feature.
Musings on the above
It’s nice how quick and short was. Someday I’ll get to the details. Easier to ready though eh?
Potential future double clicks:
- Data framework and work flow for each
- Optimal tools
- Setting up routines
- Lessons for each
- Whose typically involved in each
- Where we are at VF
