Quarterly Enablement Planner

Turn quarterly priorities into a realistic enablement calendar with owners and checkpoints.

Confirm Inputs First

Confirm:

• Quarter and planning horizon
• Revenue priorities and major initiatives
• Teams and roles covered
• Known launch dates and immovable events
• Capacity constraints
• Whether a current context artifact from revenue-enablement-context exists

If inputs are partial, ask for missing blockers or proceed with assumptions labeled by confidence.

Read The Right Reference

Read references/quarterly-plan-template.md before building the plan.

Default Workflow

1. Reuse current revenue-enablement-context if available; otherwise label context assumptions.
2. Translate business priorities into enablement objectives.
3. List all candidate initiatives and classify them by impact and effort.
4. Build an explicit must do, should do, and stop/defer stack.
5. Sequence work to avoid collisions with launches and peak selling periods.
6. Assign owners, milestones, and handoff dependencies.
7. Add reinforcement and manager cadence checkpoints.
8. Define monthly review moments and change-control rules.
9. Produce a quarter calendar plus a short execution brief.

What To Avoid

• Quarter plans that exceed real capacity.
• Prioritizing visible activity over high-impact initiatives.
• Omitting explicit stop/defer calls, which creates hidden scope creep.
• Failing to define re-plan triggers when launches or priorities shift.

Tool Notes

• Keep planning format tool-agnostic.
• If requested, map deliverables into the user's existing calendar, project tracker, or wiki.

Output Contract

Default output includes:

• Quarterly enablement calendar
• Initiative priority stack with rationale
• Stop/defer list with rationale and re-entry conditions
• Owner and milestone matrix
• Monthly review cadence
• Risk and dependency notes

Quality Bar

• Calendar is achievable with available capacity.
• High-impact initiatives are prioritized ahead of low-value activity.
• Reinforcement and inspection are built into the quarter.
• Stop/defer decisions are explicit enough to prevent hidden overcommitment.
• Plan is clear enough for cross-functional alignment.