Benefits Realization Plan

TL;DR: Produces a benefits realization plan linking project deliverables to measurable business outcomes. Defines KPIs, success metrics, measurement methods, target values, and a tracking framework that extends beyond project closure to ensure the organization captures the intended value.

Principio Rector

Un proyecto exitoso no es uno que entrega a tiempo y en presupuesto — es uno que genera el valor de negocio prometido. Los beneficios no se realizan en la fecha de entrega; se realizan cuando los usuarios adoptan, los procesos mejoran, y los KPIs se mueven. El plan de beneficios es el puente entre la entrega y el valor.

Assumptions & Limits

• Assumes the project charter includes a business case with quantifiable objectives [SUPUESTO]
• Assumes baseline metrics are measurable or can be established before project execution [SUPUESTO]
• Breaks when benefits are purely intangible with no proxy metrics — requires creative KPI design
• Does not replace the financial business case — complements it with operational benefit tracking
• Post-project benefit tracking requires organizational commitment beyond the PM team [STAKEHOLDER]
• Benefit targets beyond 12 months carry increasing uncertainty — tag as [INFERENCIA]

Usage

# Create benefits realization plan from charter
/pm:benefits-realization-plan $PROJECT --type=create --source="charter"

# Define KPIs for specific benefit category
/pm:benefits-realization-plan $PROJECT --type=kpi --category="operational"

# Generate benefits tracking dashboard
/pm:benefits-realization-plan $PROJECT --type=dashboard --period="quarterly"

Parameters:

Service Type Routing

{TIPO_PROYECTO} variants:

• Agile/Kanban: Iteration-based benefit tracking, velocity as proxy
• Waterfall: Phase-gate benefit milestones, formal measurement points
• SAFe: PI-level benefits tracking, value stream metrics
• Transformation: Organizational capability maturity, adoption rates
• Recovery: Restoration metrics (schedule recovery, budget recovery rate)

Before Planning

1. Read the project charter and business case to extract expected benefits and success criteria
2. Glob skills/benefits-realization-plan/references/*.md for KPI design patterns
3. Read organizational strategic objectives (OKRs, balanced scorecard) for alignment mapping
4. Grep for existing baseline metrics in current operational reports or dashboards

Entrada (Input Requirements)

• Approved project charter with business case
• Stakeholder expectations and success criteria
• Organizational strategic objectives (OKRs, balanced scorecard)
• Current baseline metrics for comparison
• Historical benefits data from similar projects

Proceso (Protocol)

1. Identify benefits — Map each project objective to specific, measurable benefits
2. Categorize benefits — Classify as financial, operational, strategic, or compliance
3. Define KPIs — Establish Key Performance Indicators with SMART criteria
4. Set baselines — Document current state metrics for comparison
5. Set targets — Define target values with timeline (30/60/90/180 days post-delivery)
6. Assign ownership — Designate a benefits owner for each KPI (usually business stakeholder)
7. Design measurement method — Define how each KPI will be measured and data sources
8. Create tracking framework — Build benefits dashboard with measurement schedule
9. Plan sustainability — Define actions to sustain benefits beyond project closure
10. Review cadence — Establish post-project benefits review schedule

Edge Cases

1. No baseline data available: Design baseline measurement sprint before project execution. Document current state as [SUPUESTO] if measurement is impossible pre-project. [METRIC]
2. Benefits are purely intangible (morale, culture): Design proxy metrics (employee NPS, retention rate, survey scores). Never claim intangible benefits are unmeasurable. [INFERENCIA]
3. Stakeholders disagree on target values: Facilitate target-setting workshop using historical benchmarks. Document agreed targets with evidence of consensus. [STAKEHOLDER]
4. Benefits ownership rejected by business: Escalate to sponsor. Benefits without owners will not be tracked — document this risk explicitly. [STAKEHOLDER]

Example: Good vs Bad

Good Benefits Plan:

Bad Benefits Plan: A document listing "improved efficiency" and "better customer satisfaction" without KPIs, baselines, targets, or owners. No measurement method defined. No post-project tracking plan. Fails because benefits without metrics are wishes, not plans — the organization will never know if the project delivered its promised value.

Validation Gate

• Every charter objective maps to ≥1 measurable benefit with KPI
• All KPIs meet SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
• ≥75% of KPIs have baseline metrics from actual data, remainder tagged [SUPUESTO]
• Target values defined at ≥2 time horizons (e.g., 90-day and 180-day post-delivery)
• Every KPI has an assigned business stakeholder owner — no PM-only ownership
• Measurement methods specify data source, collection frequency, and responsible party
• Post-project review schedule extends ≥6 months beyond project closure
• Benefits realization risks identified (adoption failure, measurement gaps)
• Sponsors see clear value justification linked to strategic objectives [STAKEHOLDER]
• Tracking cadence aligned with delivery rhythm and governance schedule [PLAN]

Escalation Triggers

• No baseline data available for key KPIs
• Benefits ownership rejected by business stakeholders
• Target values conflict between stakeholder groups
• Measurement method requires unavailable data sources

Salida (Deliverables)

• Primary deliverable: benefits realization plan with tracking framework
• All outputs tagged with evidence markers
• Mermaid diagrams where applicable
• Executive summary for stakeholder consumption

Additional Resources

Output Configuration

• Language: Spanish (Latin American, business register)
• Evidence: [PLAN], [SCHEDULE], [METRIC], [INFERENCIA], [SUPUESTO], [STAKEHOLDER]
• Branding: #2563EB royal blue, #F59E0B amber (NEVER green), #0F172A dark

Sub-Agents

Benefit Identifier

Benefit Identifier

Core Responsibility

The Benefit Identifier agent systematically discovers, articulates, and categorizes all expected benefits from a project or program initiative. It classifies benefits into four dimensions — financial (revenue growth, cost savings, cost avoidance), operational (efficiency gains, quality improvements, cycle-time reduction), strategic (market positioning, capability building, competitive advantage), and intangible (employee satisfaction, customer loyalty, organizational morale) — ensuring no value stream is overlooked and each benefit is expressed in stakeholder-meaningful language.

Process

1. Review the project business case, charter, and stakeholder expectations to extract all stated and implied benefits.
2. Interview key stakeholders and sponsors using structured benefit elicitation questions to surface unstated or assumed benefits.
3. Classify each identified benefit into its primary dimension: financial, operational, strategic, or intangible, applying mutual exclusivity where possible.
4. Decompose compound benefits into discrete, independently measurable benefit statements with clear cause-effect linkage to project deliverables.
5. Validate each benefit against the project scope to confirm traceability — every benefit must link to at least one deliverable or capability.
6. Prioritize benefits using weighted scoring (value magnitude, certainty of realization, strategic alignment) to establish a ranked benefits register.
7. Document the complete benefits register with unique IDs, descriptions, dimensions, owning stakeholders, and preliminary realization windows.

Output Format

## Benefits Register

| Benefit ID | Benefit Statement | Dimension | Sub-Category | Linked Deliverable | Owner | Priority Score | Realization Window |
|------------|-------------------|-----------|--------------|-------------------|-------|----------------|-------------------|
| BEN-001 | ... | Financial | Cost Savings | ... | ... | ... | ... |
| BEN-002 | ... | Operational | Efficiency | ... | ... | ... | ... |

### Benefit Detail Cards

#### BEN-001: [Benefit Statement]
- **Dimension**: Financial — Cost Savings
- **Description**: [2-3 sentence elaboration]
- **Cause-Effect Chain**: [Deliverable] → [Capability] → [Benefit]
- **Owner**: [Name / Role]
- **Priority**: [Score] — [Rationale]
- **Dependencies**: [Other benefits or external factors]

Benefit Measurer

Benefit Measurer Agent

Core Responsibility

Define how each identified benefit will be measured, establishing baselines before project delivery and targets for post-delivery tracking. Every benefit must have at least one quantifiable KPI with a clear measurement method and responsible owner.

Process

1. Categorize Benefits. Classify each benefit as financial, operational, strategic, or intangible and assign appropriate measurement approaches for each category.
2. Define KPIs. For each benefit, establish 1-3 Key Performance Indicators with units of measurement, data sources, and collection frequency.
3. Establish Baselines. Measure current-state values for each KPI before project delivery begins. Document baseline date, method, and any data quality caveats.
4. Set Targets. Define target values at 6-month, 12-month, and 24-month horizons with confidence levels and assumptions documented.
5. Design Collection Methods. Specify how KPI data will be collected: automated systems, surveys, financial reports, or manual tracking with responsible parties.
6. Create Measurement Calendar. Schedule measurement points aligned with organizational reporting cycles and project milestones.
7. Produce Measurement Framework. Deliver complete benefit measurement plan with KPI definitions, baselines, targets, collection methods, and measurement calendar.

Output Format

• Benefit Measurement Matrix — Table: Benefit, KPI, Baseline Value, 6mo/12mo/24mo Targets, Collection Method, Owner.
• Measurement Calendar — Timeline of measurement points with responsible parties.
• Data Quality Assessment — Confidence level for each baseline and potential measurement risks.

Benefit Tracker

Benefit Tracker Agent

Core Responsibility

Monitor actual benefit realization against planned targets, detect early signs of benefit erosion or underperformance, and recommend corrective actions when benefits are not materializing as expected.

Process

1. Collect Actuals. Gather actual KPI values from data sources at scheduled measurement points. Validate data quality and flag any collection issues.
2. Calculate Variance. Compare actual values against planned targets: absolute variance, percentage variance, and trend direction (improving, stable, declining).
3. Assess Realization Rate. Calculate percentage of planned benefit realized at each measurement point. Compare against expected realization curve.
4. Detect Erosion Signals. Identify early warning signs: declining adoption rates, workaround usage, process reversion, or stakeholder disengagement.
5. Analyze Root Causes. For underperforming benefits, investigate root causes: incomplete adoption, environmental changes, flawed assumptions, or missing prerequisites.
6. Recommend Corrective Actions. Propose specific actions to close benefit gaps: additional training, process reinforcement, system adjustments, or target revision with justification.
7. Produce Tracking Report. Deliver benefit realization dashboard with actuals vs targets, variance analysis, erosion alerts, and corrective action recommendations.

Output Format

• Benefit Realization Dashboard — Table: Benefit, KPI, Target, Actual, Variance, Trend, RAG Status.
• Erosion Alert Report — Benefits showing declining trends with root cause analysis.
• Corrective Action Register — Actions to close benefit gaps with owners and deadlines.

Realization Timeline Mapper

Realization Timeline Mapper Agent

Core Responsibility

Map the temporal relationship between project delivery milestones and benefit realization, recognizing that most benefits lag delivery by weeks to months. Identify prerequisites, enablers, and organizational changes needed before benefits can materialize.

Process

1. Map Delivery-to-Benefit Lag. For each benefit, determine the expected lag between project deliverable completion and benefit realization (immediate, 0-3mo, 3-6mo, 6-18mo, 18mo+).
2. Identify Prerequisites. Document what must happen between delivery and realization: user adoption, process changes, data migration, training completion, or regulatory approval.
3. Sequence Benefit Chains. Identify where benefits depend on each other — e.g., efficiency gains enable cost savings which enable reinvestment benefits.
4. Create Realization Waves. Group benefits into realization waves aligned with project phases and organizational readiness milestones.
5. Map Early Wins. Identify quick-win benefits that can be realized during project execution to maintain stakeholder confidence and funding support.
6. Assess Realization Risks. For each benefit, identify factors that could delay or prevent realization: adoption resistance, competing initiatives, market changes.
7. Produce Timeline Visualization. Deliver a benefits realization timeline showing delivery milestones, prerequisites, and expected realization dates.

Output Format

• Realization Timeline — Gantt-style chart showing delivery milestones, prerequisite completion, and benefit realization windows.
• Prerequisite Tracker — Table: Benefit, Prerequisites, Owner, Target Date, Status.
• Early Wins Register — Quick-win benefits with expected realization dates and visibility plan.