Planning
Use Planning to decide what happens next, who owns it, and where the team will track it.
Planning starts after work has enough shape to act on. Use Initiatives for planned work, Bugs for defects or incidents, and Ongoing Work for recurring streams that need owners, status, and reporting.
Planning can run in two modes. If this is the primary work system, plan native initiatives, bugs, and ongoing work here. Using Linear, Jira, or another issue tracker? Plan across synced issues, pull requests, meetings, and roadmap records without forcing every user to change their issue workflow on day one.
Assign work
Assign ownership where the next action is clear. The owner is accountable for moving the record forward. Assignees are the people doing the work. Teams decide where the work appears in team planning, standups, reports, and analytics.
Use Boards when you need to move work through Planned, In progress, and Done. The Blockers column appears when work is blocked. Use Ownership when work is missing a clear person, team, reviewer, or escalation path.
Choose the planning surface
Use the planning surface that matches the decision in front of the team.
| Surface | Use it for |
|---|---|
| Boards | Track and move work across people and statuses in a personal or team board. |
| Roadmap | Plan initiatives, ongoing work, hierarchy, taxonomy, owners, and teams. |
| Triage | Review incoming or in-review work before execution. |
| Backlog | Hold initiatives, bugs, and ideas before they are scheduled. |
| Priorities | Decide what deserves attention before something else. |
| Stack Ranking | Give planned initiatives an explicit order. |
| Blockers | Keep dependencies, missing input, and stalled work visible. |
Keep the plan current
A plan is useful when status, team, owner, assignees, priority, parent initiative, taxonomy, and blockers are current. For spec-driven development, those fields make the work safe to hand to a person, coding tool, or agent. For native work, update those fields here. For synced issues, update only the fields the integration supports and respect the source app's workflow.
When the plan is ready, move into Deliver Work so building, review, comments, pull requests, and AI handoff stay tied to the source work.