Solution Roadmap — Transformation Blueprint

Defines the complete transformation plan AFTER scenario approval but BEFORE PoC validation. Covers transformation vision, phased execution (Foundation > Build > Integrate > Optimize > Scale), investment horizon with TCO/ROI, team ramp-up curve, estimation pivot points with PoC validation, risk management with cascade failure analysis, and governance framework.

Principio Rector

Un roadmap sin gates es un plan de esperanza. Un roadmap sin pivot points es un plan de fantasía. Este skill produce blueprints de transformación que sobreviven el contacto con la realidad: cada fase tiene criterios de go/no-go, cada estimación tiene pivot points con PoC de validación, y cada milestone tiene kill criteria. La diferencia entre un roadmap y una lista de deseos es la gobernanza.

Filosofía de Transformación

1. Fases, no big-bang. Cada fase es independientemente valiosa. Si el proyecto se detiene en Phase 2, lo construido en Phase 1 tiene valor por sí solo.
2. Estimaciones honestas. Ranges con P50/P80/P95 — nunca un número exacto. El Cone of Uncertainty se respeta.
3. Kill criteria explícitos. Cada fase tiene condiciones bajo las cuales se detiene, se re-planifica, o se pivotea. No hay "seguir adelante a toda costa."

Inputs

• $1 — Transformation duration target in months (default: 18-24)
• $2 — Budget range: under2m, 2m-5m, 5m-10m, over10m (default: 2m-5m)

Parse from $ARGUMENTS.

Parameters:

• {MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
  • piloto-auto: Auto para construcción de fases y timeline, HITL para validación de gates y kill criteria.
  • desatendido: Cero interrupciones. Roadmap completo auto-generado. Supuestos documentados.
  • supervisado: Autónomo con checkpoint en estructura de fases y antes del governance plan.
  • paso-a-paso: Confirma cada fase, cada gate, y cada pivot point.
• {FORMATO}: markdown (default) | html | dual
• {VARIANTE}: ejecutiva (~40% — S1 vision + S2 phases + S3 investment) | técnica (full 7 sections, default)

Required Inputs

• Approved scenario from scenario analysis (component breakdown, tech stack, integration points)
• Cumulative findings from prior phases (business case, current state, target scenario)
• Organization willing to commit phased transformation
• Budget authority with phased funding tolerance (+/-25%)

Assumptions & Limits

Assumptions

• Organizational change management runs parallel (not in roadmap scope).
• Executive sponsorship stable throughout transformation.
• Current team available for transition; no mass attrition mid-program.
• Cloud infrastructure available on-demand (no procurement bottlenecks).
• Partner/vendor relationships stable for transformation duration.

Estimation Confidence at This Stage

• Cost: +/-25% confidence (refines to +/-15% after PoC, +/-10% after build)
• Timeline: +/-15% confidence (refines after PoC)
• Team sizing: +/-20% variance expected from PoC learnings

Cannot Predict

Market disruptions, regulatory changes mid-transformation, organizational restructuring, key person dependencies, exact talent availability for emerging technologies.

Conditional Logic

IF transformation > 12 months:
  -> Quarterly re-calibration gates
  -> Steering committee approval for >5% scope/budget/timeline changes

IF team size (peak) > 20 people:
  -> Add team topology planning (Inverse Conway's Law)
  -> Budget 1 month in Phase 1 for org design

IF multi-region deployment required:
  -> Add rollout wave planning per region
  -> Sequence: low-risk to medium-risk to high-risk

IF budget not fully committed upfront:
  -> Phased funding model with kill points:
    Phase 1 gate: commit ~35% of 3-year TCO
    Phase 2 gate: commit ~50%
    Phase 3 gate: commit ~15%

IF PoC learnings invalidate >2 major assumptions:
  -> Pause Phase 2 for 2-week re-planning sprint
  -> Present re-scoped roadmap to steering committee

IF team resistance detected in Phase 1:
  -> Extend Phase 1 by 1 month for change management
  -> Require department head alignment before Phase 2

Edge Cases & Triggers

• Transformation >18 months: Break into 6-month waves. Each wave independently viable. Replan after Wave 1 PoC.
• Budget >$5M: Add governance layer (PMO, steering committee, investment review board). Quarterly re-calibration mandatory.
• No PMO exists: Embed PM capacity in Phase 1. Budget PM as permanent overhead.
• Legacy team resistance: Add change management track. Budget 2-3 months for people engagement before Phase 2.
• Multiple vendors: Add vendor coordination track. Lock vendor roadmaps to SLAs before Phase 1 gate. +15% on Phase 2-3 timelines.
• Regulatory deadline: Add compliance milestone track. Reserve 20% team capacity for regulatory validation.
• Key person risk: Identify single points of knowledge. Document knowledge transfer milestones. Budget redundancy for critical roles.

Trade-off Matrix

Delivery Structure

Section 1: Transformation Vision

Business objective alignment with approved scenario. Success metrics table (baseline > 18-month target > 36-month target > owner). North star metric. Strategic capabilities unlocked per phase.

Section 2: Transformation Phases

Each phase has explicit GO/NO-GO criteria. NO-GO halts downstream phases.

Per phase: team composition and roles, key deliverables with acceptance criteria, dependency map, risk table with mitigations, gate criteria with measurable thresholds.

Section 3: Investment Horizon

3-year TCO projection, year-by-year breakdown, cost categories (labor, infrastructure, licensing, training, contingency), phased funding release points, kill points, break-even timeline, ROI modeling, cost/timeline variance scenarios (optimistic/likely/pessimistic/severe).

Section 4: Team Roadmap

Month-by-month headcount, skill gap analysis (current to required), training roadmap (bootcamp to pair programming to autonomous), technology introduction sequence, knowledge transfer milestones, technical debt retirement schedule.

Section 5: Estimation Pivot Points

5+ key assumptions that drive estimates. Per assumption: current estimate impact, why it matters, PoC validation criteria (specific measurable tests), pivot options if invalidated, decision gate timing.

Pivot Decision Framework:

IF validation PASSES -> proceed with planned schedule
IF FAILS with minor issue (<4 weeks) -> evaluate Pivot A (<$150K, <4 weeks)
IF FAILS with major issue (>4 weeks) -> pause, 2-day re-plan, steering committee
IF showstopper (pivot cost >$500K) -> escalate to board for viability decision

Risk-adjusted timeline with Monte Carlo confidence intervals (P10/P50/P90) for key milestones.

Section 6: Risk Management

Risk timeline (when each risk peaks per phase), risk-by-phase breakdown tables, cascade failure chains (3+ documented), mitigation investment vs exposure analysis, early warning indicators (Green/Yellow/Red per metric per phase), kill criteria (hard stops and soft stops).

Section 7: Governance Plan

Steering committee structure and cadence, technical architecture forum, phase gate review board, risk management committee, escalation hierarchy, RACI matrix, three-tier change control process (minor/significant/major), reporting dashboard (monthly/weekly/real-time).

Output Artifact

Primary: 06_Solution_Roadmap_{project}.md (o .html si {FORMATO}=html|dual) — Transformation vision, 5-phase execution plan with gates, investment horizon with TCO/ROI, team ramp-up, estimation pivot points, risk management, governance framework.

Diagramas incluidos:

• Gantt chart: phased timeline with P50/P80/P95 markers
• Flowchart: pivot point decision tree
• Flowchart: team ramp-up/ramp-down visualization

Validation Gate

• Transformation phases defined with clear gates and success criteria per phase
• Investment horizon: 3-year TCO with phased funding model and kill points
• Estimation pivots explicit: 5+ major assumptions with PoC validation criteria
• Team ramp-up: month-by-month headcount with role introduction sequence
• Risk timeline: shows when each risk peaks with interdependencies
• Governance: steering committee, decision authority, escalation paths, kill criteria
• All estimates linked to assumptions; all assumptions linked to PoC validation
• Break-even and ROI calculated with stated assumptions
• Roadmap immediately actionable: steering committee can approve Phase 1 funding on this plan
• Sensitivity analysis covers optimistic/likely/pessimistic/severe scenarios

Output Format Protocol

Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter.

Diagrams (Mermaid)

• Gantt chart: phased timeline with P50/P80/P95 markers
• Flowchart: pivot point decision tree
• Flowchart: team ramp-up/ramp-down visualization

Casos Borde

Decisiones y Trade-offs

Knowledge Graph

graph TD
    subgraph Core["Solution Roadmap"]
        A["Transformation Vision"] --> B["5-Phase Execution Plan"]
        B --> C["Investment Horizon"]
        B --> D["Team Ramp-Up"]
        B --> E["Estimation Pivot Points"]
        E --> F["Risk Management"]
        F --> G["Governance Framework"]
    end
    subgraph Inputs["Inputs"]
        H["Approved Scenario"] --> A
        I["Budget Range"] --> C
        J["Duration Target"] --> B
    end
    subgraph Outputs["Outputs"]
        G --> K["Roadmap Document"]
        C --> L["TCO/ROI Model"]
    end
    subgraph Related["Related Skills"]
        M["scenario-analysis"] -.-> H
        N["executive-pitch"] -.-> L
        O["change-readiness-assessment"] -.-> D
    end

Output Templates

Markdown (default)

• Filename: 06_Solution_Roadmap_{cliente}_{WIP}.md
• Structure: TL;DR > Transformation Vision > Phase cards with gates > Investment Horizon tables > Team Ramp-Up curve > Pivot Points with PoC criteria > Risk Timeline > Governance RACI > Mermaid Gantt + flowcharts > ghost menu

XLSX

• Filename: 06_Solution_Roadmap_{cliente}_{WIP}.xlsx
• Structure: Sheet 1: Phase summary with gates and dates; Sheet 2: Investment horizon year-by-year; Sheet 3: Team headcount month-by-month; Sheet 4: Risk register with scores; Sheet 5: Pivot point tracker; pivot-table-ready formatting

DOCX (bajo demanda)

• Filename: {fase}_solution_roadmap_{cliente}_{WIP}.docx
• Generado con python-docx y MetodologIA Design System v5. Portada con nombre del proyecto y fecha, TOC automático, encabezados Poppins navy, cuerpo Montserrat, acentos dorados, tablas zebra. Secciones: Transformation Vision, 5-Phase Execution Plan (con gates go/no-go), Investment Horizon, Team Ramp-Up, Estimation Pivot Points, Risk Management, Governance Framework.

PPTX (bajo demanda)

• Filename: {fase}_solution_roadmap_{cliente}_{WIP}.pptx
• Generado con python-pptx y MetodologIA Design System v5. Slide master con gradiente navy, títulos Poppins, cuerpo Montserrat, acentos dorados. Máximo 20 slides (ejecutiva). Speaker notes con referencias de evidencia. Slides: Portada, Transformation Vision y north star metric, Resumen de 5 fases (tabla con gates), Investment Horizon (TCO/ROI), Team Ramp-Up curve, Estimation Pivot Points, Risk Timeline, Governance Plan, próximos pasos.

HTML (bajo demanda)

• Filename: 06_Solution_Roadmap_{cliente}_{WIP}.html
• Estructura: HTML self-contained branded (Design System MetodologIA v5). Timeline visual con las 5 fases y gates go/no-go, investment horizon chart y pivot point decision tree interactivo. WCAG AA, responsive, print-ready.

Evaluacion

Umbral minimo: 7/10 en cada dimension para considerar el skill production-ready.

Autor: Javier Montaño | Ultima actualizacion: 15 de marzo de 2026