Create your first initiative

Start building your roadmap with one real project, feature, or customer request. An initiative is the right shape when the work needs intent, ownership, progress tracking, and a place on the roadmap.

What an initiative is

An initiative represents larger work: a feature, product bet, engineering project, customer request, goal, or other trackable effort. Initiatives can be nested under parent initiatives so large work can be broken into smaller pieces without losing the strategic thread.

Initiatives live on the roadmap and can be filtered, grouped, ranked, assigned, and measured. In spec-driven development, the initiative also becomes the brief people and agents build from.

Replacing Aha!, Productboard, or another roadmap tool? Start with active roadmap work and current product bets. Keeping Linear, Jira, or another issue tracker? Put initiatives above synced issues so execution can stay in the source issue tracker while roadmap context lives here.

Create the first initiative

For the global Write entry point, see Create from anywhere. You can also start from the roadmap, backlog, or recap. Give the initiative a clear title and description.

After the initiative is created, the detail view shows the fields that make the first decision clear.

Set what the initiative is, who owns it, which team should see it, and how it fits the roadmap. The full initiative field model lives in Initiatives.

Draft with Writer Mode

When the brief is rough, choose Writer in the create dialog and describe the work in plain language. Writer Mode turns your answers into a draft you can save as the initiative description. Bugs do not support Writer Mode.

After the first initiative exists, invite your team so teammates join with current work already in place. For the full initiative model, continue to Initiatives.