Design planning process

Design Planning Process

Purpose

Help teams design a lightweight, repeatable planning process that creates consistent strategic alignment from annual goals down to sprint-level execution.

Skill type

Conceptual skill

Use this skill when

• Planning cycles exist but feel chaotic or disconnected from strategy
• A new product team is establishing its planning rhythm
• Planning produces roadmaps that change too frequently without strategic rationale
• Cross-team planning is misaligned and causes coordination failures

Do not use this skill when

• The goal is operating cadence (recurring meeting rhythms — use design-operating-cadence)
• The goal is sprint-level delivery planning (use plan-delivery-collaboration)

Required inputs

• Team size and structure
• Planning horizon (annual, quarterly, 6-week cycles)

Optional inputs

• Current planning process and pain points
• Company-level planning calendar
• OKR or goal-setting framework in use
• Cross-team dependencies

Upstream context

Works best when:

• Company strategic goals or OKRs are defined
• Operating cadence is designed or in progress

Downstream handoff

Output can feed:

• design-operating-cadence (planning process defines key cadence events)
• set-goals-okrs-kpis (planning process includes goal-setting)
• build-roadmap-prioritization (planning cycle produces the roadmap)

Instructions

1. Define the planning levels: annual / quarterly / cycle / sprint.
2. For each level: define inputs, outputs, participants, timeline, and decision rights.
3. Design the cascade: how do annual goals become quarterly priorities, then cycle deliverables?
4. Identify the key planning events and their sequence.
5. Define how strategy changes between cycles are handled.
6. Define what documentation is produced at each level.

Output

Provide:

• Planning levels and their purposes
• Each level: inputs, outputs, participants, timeline, decision rights
• Planning cascade design
• Key planning events calendar
• Strategy change protocol
• Documentation artifacts per level

Risks / caveats

• Planning overhead that exceeds the value of the plan creates resentment — keep it lightweight
• Planning without decision rights is theater — define who can say yes/no at each level
• Plans must be reviewed mid-cycle, not only at the end