Critical note: A roadmap should be considered a ‘point in time’ artifact instead of a contract for the quarter. Things will and do change. This will be updated with living retros as touchpoints along the way. The product workstream lead will aim for biweekly, around office hours.
If the goals set up mental models, frameworks for collaboration, and an overarching portfolio of bets this proposal explains the details of them with timelines of now, next, and later.
This roadmap will also be tremendously easier to understand with framing initiatives or features as one of three things:
<aside> 📏 Now we have a formula: {the specs give the what and why[ name & business case]} + {the size of the work [rock/pebble/sand],} + {the when [now next later]} + {statuses [draft, discovery, definition, hand off/execution]} = Shipping.
</aside>
Marching towards our north stars means planning our roadmap around those three types of work and tagging them as now, next, and later. Adjusting in real time will happen every Monday, as usual.
We have bandwidth for around one big rocks running in parallel with a few pebbles, per month. We don’t want to fracture our efforts on shiny sand that take up bandwidth without results.