Planning Frameworks

Planwright's primitives map cleanly to OKR structure — without the grading ceremony.

In OKR terms: a Planwright Objective is the O — a clear, agent-executable outcome. An Initiative is a natural container for a cluster of Key Results, grouped by strategic theme. Strategic Focus (BUILD / GROW / TRUST / SCALE) provides the taxonomy that connects every objective to the organizational strategy without requiring manual OKR alignment sessions. What Planwright does not implement: scoring, grading, confidence ratings, or quarterly OKR reviews. Those processes are human rituals that live outside the board. Planwright tracks whether objectives were accepted or rejected, and how long they took — not whether the team gave the quarter a 0.7.

Planwright is built for outcome thinking. Every objective is an outcome statement — never a task list.

The discipline outcome-driven planning demands — write the outcome, not the solution — is enforced structurally in Planwright. Objectives are atomic outcome statements. They have no subtasks, no checklists, and no breakdown UI. If you find yourself writing subtasks inside an objective, you are writing agent instructions, not a human objective. Hand the decomposition to the agent: it posts a plan when it claims the work, and the plan lives in the audit trail, not on the board. The human stays at the outcome layer; the agent owns the how.

Planwright has no sprints, story points, or velocity math. This is a design decision, not a missing feature.

Sprint planning assumes humans break work into tasks and estimate effort. Planwright assumes agents execute and report back. The cognitive overhead of estimation disappears when an agent can claim an objective, decompose it, ship it, and request review — often in the same session. For teams who still want time-boxed delivery: set a target date on an Initiative and use the initiative as a delivery batch. The accept/reject gate at the end of each objective is a natural review point without a sprint retrospective. Teams migrating from Jira or Linear can map their epics to Initiatives and their tickets to Objectives — but should resist the urge to recreate subtask hierarchies.

No story points. No velocity. No capacity math. If you need those, Planwright is not the right tool.

Initiatives with target dates are the roadmap. Strategic Focus is the portfolio allocation view.

A Planwright roadmap is a list of Initiatives, each with a name, a description, a target date, and a set of Objectives. The Strategic Focus report shows how objectives are distributed across BUILD, GROW, TRUST, and SCALE — making underinvestment visible without a spreadsheet. Leaders who want a timeline view can read the initiative target dates directly; leaders who want a theme view can filter by Strategic Focus area. Neither view requires a dedicated roadmapping tool. What Planwright deliberately avoids: Gantt charts, dependency graphs, and capacity lanes. Those tools optimize for predictability. Planwright optimizes for shipping.