Roadmaps & initiatives

Cycles answer 'what are we doing this week'. Roadmaps and initiatives answer 'what are we doing this quarter, and why'. They sit above day-to-day execution and roll progress up from the issues underneath.

Projects

A project is a scoped body of work with a start, a target, and an owner — a launch, a migration, a redesign. Issues belong to a project; the project's progress is derived from the state of those issues, so the roll-up is always live rather than a number someone updates by hand.

Initiatives

An initiative groups projects — often across teams — under a single strategic theme. This is how you express 'Reliability', 'Enterprise readiness', or 'Q3 growth' as something you can actually track rather than a slide. Progress rolls up from projects to initiatives the same way it rolls up from issues to projects.

The roadmap view

The roadmap lays initiatives and projects on a timeline so stakeholders can see what is in flight and what is next. Because it reads the same rows as the boards, there is no separate planning artifact to keep in sync — the roadmap is just another lens on the work.