Using Pytheus in quarterly planning
Drive the quarter's security roadmap from CAMP priorities, then measure the result with the next assessment.
Last updated September 22, 2026
Quarterly planning is where Pytheus stops being a report and becomes an operating tool. The priority list tells you what to work on, the roadmap shows what the work earns, and the next assessment proves whether it happened.
Anchor the plan to priority, not opinion. Priority is the gap between target and current maturity times criticality, so the top of the list is already the work with the most defensible return. Start there and move down as capacity allows.
A workable quarterly loop
Review the priorities. Pull the ranked capability gaps from your latest assessment on the Decisions surface.
Pick the quarter's targets. Choose a realistic set of capabilities to mature, weighted toward high-criticality items.
Map work to capabilities. Add the items you will act on to the roadmap so each becomes an action tied to a specific capability.
Project the effect. Use the roadmap projection to estimate how planned maturity gains move your scores.
Re-assess at quarter end. Compare actual movement to the projection and explain any gap.
Keep the plan defensible
Because every recommendation is capability-driven and deterministic, you can walk a skeptical stakeholder from a budget line straight to the gap it closes. That traceability is what survives scrutiny when priorities compete for funding.
Plan against capabilities, not tools. A tool purchase only matters if it raises a capability's maturity. Contracts track spend and renewals, but they do not move your score on their own.
Close the loop with Tracking progress over time, and package the outcome using Board reports.