technical-roadmap-planning

Technical Roadmap Planning Skill

Step 1 — Gather Inputs

Before defining initiatives, collect:

• Business objectives for the period (OKRs, product strategy, growth targets).
• Tech debt inventory — known architectural problems, reliability gaps, security risks.
• Reliability data — incident history, SLA breaches, on-call burden.
• Team capacity — headcount, planned leave, hiring timeline.
• Dependencies — migrations, third-party deprecations, compliance deadlines.

Ask the user to provide or confirm these inputs before proceeding.

Step 2 — Define Initiatives

For each initiative, capture:

Initiative: <name>
Problem:    <what is broken or missing — one sentence>
Metric:     <how success is measured — must be quantifiable>
Effort:     <S | M | L | XL>  (S=days, M=weeks, L=1-2 months, XL=quarter+)
Impact:     <Low | Medium | High | Critical>
Dependencies: <other initiatives or teams this blocks or is blocked by>

Example:

Initiative: Database connection pooling
Problem:    Under peak load, the API exhausts the DB connection limit, causing 503s.
Metric:     Zero connection-limit errors in staging load test at 2× current peak traffic.
Effort:     S
Impact:     High
Dependencies: None

Step 3 — Prioritise (Impact / Effort Matrix)

Plot each initiative on a 2×2 grid and apply the priority rules:

Impact
  High │ Quick Wins ★ │ Strategic Bets ◆
       │ (do now)     │ (plan carefully)
       ├──────────────┼──────────────────
  Low  │ Fill-ins     │ Avoid / defer
       │ (if capacity)│
       └──────────────┴────────────────
          Low Effort      High Effort

Priority	Quadrant	Action
1	High Impact + Low Effort	Schedule immediately
2	High Impact + High Effort	Plan with milestones
3	Low Impact + Low Effort	Fill between larger items
4	Low Impact + High Effort	Defer or remove

Mark compliance/security items as non-negotiable regardless of quadrant.