Planning

Planning turns defined work into a current plan: what happens next, who owns it, and where progress is tracked.

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.

When the team needs to move work through status, open Boards. When work is missing a clear person, team, reviewer, or escalation path, open Ownership.

Choose roadmap or board

The Roadmap is for initiatives and ongoing work that should stay visible beyond today. Boards are for scanning planned work by status and moving it forward.

Keep blockers visible

Blocked work should show why it is stuck and who can help. Keep blockers attached to the initiative, bug, issue, pull request, or todo so Daily recap, standups, and boards all point to the same problem.

When the plan is ready, move into Deliver Work so building, review, comments, pull requests, and AI handoff stay tied to the work item.