portfolio-roadmapping-bets

$npx mdskill add lyndonkl/claude/portfolio-roadmapping-bets

Design strategic portfolio roadmaps with sequenced bets and risk balance.

  • Manages multiple initiatives across time horizons and resource constraints.
  • Depends on user input for strategic themes and budget limits.
  • Decides recommendations by sizing bets against core or transformational risk.
  • Delivers clear exit criteria and sequenced execution plans.

SKILL.md

.github/skills/portfolio-roadmapping-betsView on GitHub ↗
---
name: portfolio-roadmapping-bets
description: Creates strategic portfolio roadmaps that size and sequence initiative bets across time horizons (H1/H2/H3), balance risk profiles (core/adjacent/transformational), and set clear exit/scale criteria for disciplined resource allocation. Use when managing multiple initiatives across time horizons, balancing risk vs return across portfolio, sizing and sequencing bets with dependencies, setting exit/scale criteria for experiments, allocating resources across innovation types, or when user mentions portfolio planning, roadmap horizons, betting framework, initiative prioritization, innovation portfolio, or resource allocation across horizons.
---
# Portfolio Roadmapping Bets

**When NOT to use:** Single initiative with clear priority (use one-pager-prd or project-risk-register instead), purely operational prioritization without strategic horizons (use prioritization-effort-impact), or no resource constraints or trade-offs.

## Workflow

Copy this checklist and track your progress:

```
Portfolio Roadmapping Bets Progress:
- [ ] Step 1: Define portfolio theme and constraints
- [ ] Step 2: Inventory and size all bets
- [ ] Step 3: Sequence bets across horizons
- [ ] Step 4: Set exit and scale criteria
- [ ] Step 5: Balance and validate portfolio
```

**Step 1: Define portfolio theme and constraints**

Clarify the strategic theme (north star), time horizons (H1/H2/H3 definitions), resource constraints (budget, people, time), and portfolio balance targets (e.g., 70/20/10 rule). See [Portfolio Theme & Constraints](#portfolio-theme--constraints) for guidance.

**Step 2: Inventory and size all bets**

List all candidate initiatives, size each by effort (S/M/L/XL) and impact potential (1x/3x/10x), categorize by type (core/adjacent/transformational), and identify dependencies. For simple cases use [resources/template.md](resources/template.md). For complex cases with 15+ bets or multiple themes, study [resources/methodology.md](resources/methodology.md).

**Step 3: Sequence bets across horizons**

Assign each bet to H1 (now), H2 (next), or H3 (later) based on dependencies, strategic timing, learning sequencing, and capacity constraints. See [Sequencing & Dependencies](#sequencing--dependencies) for sequencing heuristics.

**Step 4: Set exit and scale criteria**

For each bet, define what success looks like (scale criteria: double down, expand scope) and what failure looks like (exit criteria: kill, deprioritize, pivot). See [Exit & Scale Criteria](#exit--scale-criteria) for examples.

**Step 5: Balance and validate portfolio**

Check portfolio balance (are we too conservative or too aggressive?), validate resource feasibility (can we actually staff this?), and self-assess using [resources/evaluators/rubric_portfolio_roadmapping_bets.json](resources/evaluators/rubric_portfolio_roadmapping_bets.json). Minimum standard: ≥3.5 average score. See [Portfolio Balance Checks](#portfolio-balance-checks).

## Common Patterns

### By Portfolio Type

**Product Portfolio** (multiple features/products):
- H1: Ship quick wins and critical bugs
- H2: Strategic features with cross-product dependencies
- H3: Platform bets and R&D exploration
- Balance: 60% incremental, 30% substantial, 10% breakthrough

**Technology Portfolio** (platform, infrastructure, tech debt):
- H1: Stability, security, performance quick wins
- H2: Major migrations and platform upgrades
- H3: Next-gen architecture and tooling
- Balance: 50% maintain, 30% improve, 20% transform

**Innovation Portfolio** (R&D, experiments, ventures):
- H1: Validated experiments ready to scale
- H2: Active experiments with checkpoints
- H3: Early-stage exploration and research
- Balance: 70% core business, 20% adjacent, 10% transformational (McKinsey Horizons)

**Marketing Portfolio** (campaigns, channels, experiments):
- H1: Proven channels with optimization
- H2: New channel experiments and tests
- H3: Brand building and long-term positioning
- Balance: 70% performance marketing, 20% growth experiments, 10% brand

### By Bet Size

**Small Bets** (1-2 weeks, 1-2 people):
- Low effort, low-to-medium impact
- Use for quick wins, experiments, bug fixes
- Example: A/B test new pricing page (2 weeks, 1.2x conversion potential)

**Medium Bets** (1-3 months, 3-5 people):
- Moderate effort, moderate-to-high impact
- Use for features, improvements, small initiatives
- Example: Build seller dashboard (2 months, 1.8x seller retention)

**Large Bets** (3-6 months, 5-10 people):
- High effort, high impact
- Use for strategic initiatives, platform work, major features
- Example: Marketplace trust & safety system (5 months, 3x GMV via reduced fraud)

**X-Large Bets** (6-12+ months, 10+ people):
- Very high effort, transformational impact potential
- Use for platform rewrites, new business lines, moonshots
- Example: AI-powered recommendation engine (9 months, 10x engagement potential)

### By Risk Profile

**Core Bets** (Low Risk, Incremental Return):
- Optimize existing products/channels
- Proven approaches with clear ROI
- Example: Improve search relevance from 65% → 75% accuracy

**Adjacent Bets** (Medium Risk, Substantial Return):
- Extend to new use cases, segments, or capabilities
- Validated approach, new application
- Example: Launch seller analytics (proven feature, new user segment)

**Transformational Bets** (High Risk, Breakthrough Return):
- New business models, technologies, or markets
- Unproven approach, high uncertainty
- Example: Blockchain-based ownership system (unproven tech, could unlock new market)

## Portfolio Theme & Constraints

Define the strategic anchor for your portfolio:

**Theme**: The overarching goal (e.g., "Grow enterprise revenue 3x", "Achieve platform parity", "Launch in APAC")

**Time Horizons**:
- **H1 (Now)**: 0-6 months - High confidence, shipping soon
- **H2 (Next)**: 6-12 months - Medium confidence, in planning/development
- **H3 (Later)**: 12-24+ months - Lower confidence, exploration/research

**Resource Constraints**:
- Budget: $X available across all initiatives
- People: Y engineers, Z designers, etc. (capacity by function)
- Time: When must key milestones be hit? (launch date, board meeting, fiscal year)

**Portfolio Balance Targets**:
- Example: 70% core / 20% adjacent / 10% transformational (McKinsey Three Horizons)
- Example: 60% product features / 30% platform / 10% R&D
- Example: 50% H1 / 30% H2 / 20% H3 (de-risk near term while investing in future)

## Sequencing & Dependencies

**Types**: Technical (infrastructure), Learning (insights), Strategic (validation), Resource (capacity)

**Heuristics**: Dependencies first, learn before scaling, quick wins early, long bets start early, hedge portfolio

## Exit & Scale Criteria

**Exit** (kill): Time-based ("90 days"), Metric ("<5% adoption"), Cost (">$X"), Strategic ("market shifts")
**Scale** (double-down): Adoption (">20%"), Engagement (">3x baseline"), Revenue (">1.5x target"), Efficiency ("<$X CAC")

**Example**: AI chatbot bet | Exit: Deflection <30% after 60d OR sentiment <-20% | Scale: Deflection >50% AND sentiment >70%

## Portfolio Balance Checks

**Risk**: ✓ ~70% core, ~20% adjacent, ~10% transformational | ❌ >80% core (too safe) or >30% transformational (too risky)
**Horizon**: ✓ ~50-60% H1, ~25-30% H2, ~15-20% H3 | ❌ >70% H1 (no future) or >40% H3 (no near-term)
**Capacity**: Effort ≤ capacity × 0.8 (20% slack) | Example: 10 eng → 48 EM/6mo → max 38 EM in H1
**Impact**: Portfolio ladders to theme (risk-adjusted) | Example: "3x revenue" → bets sum to 4.7x potential → 50% fail = 2.35x expected → add more bets

## Guardrails

**Problem Framing**:
- ❌ Vague theme like "improve product" → ✓ Specific like "Reduce churn from 5% to 2% in 12 months"
- ❌ No constraints (infinite resources) → ✓ Explicit budget, people, time limits
- ❌ Missing portfolio balance targets → ✓ Define risk tolerance (e.g., 70/20/10)

**Bet Sizing**:
- ❌ Effort in person-days without context → ✓ Use S/M/L/XL relative sizing
- ❌ Impact as vague "high/medium/low" → ✓ Use multipliers (1x/3x/10x) or concrete metrics
- ❌ All bets are "high priority" → ✓ Force-rank or categorize by type

**Sequencing**:
- ❌ No dependencies identified → ✓ Map technical, learning, strategic dependencies
- ❌ All bets in H1 (wish list) → ✓ Realistic capacity-constrained sequencing
- ❌ No rationale for sequence → ✓ Explain why A before B (dependency, learning, quick win)

**Exit & Scale Criteria**:
- ❌ No criteria (just "we'll see") → ✓ Specific metrics and timelines for kill/scale decisions
- ❌ Only exit criteria (pessimistic) → ✓ Include scale criteria (what does wild success look like?)
- ❌ Unmeasurable criteria → ✓ Use quantifiable metrics with baselines

**Portfolio Balance**:
- ❌ All core (too safe) or all transformational (too risky) → ✓ Balanced risk distribution
- ❌ Sum of efforts exceeds capacity → ✓ Effort ≤ capacity × 0.8 (20% slack for unknowns)
- ❌ Expected impact below strategic goal → ✓ Portfolio ladders up to theme with risk adjustment

## Quick Reference

**Resources**:
- [resources/template.md](resources/template.md) - Portfolio roadmap structure and bet template
- [resources/methodology.md](resources/methodology.md) - Horizon planning, bet sizing frameworks, portfolio balancing techniques
- [resources/evaluators/rubric_portfolio_roadmapping_bets.json](resources/evaluators/rubric_portfolio_roadmapping_bets.json) - Quality criteria for portfolio roadmaps

**Success Criteria**:
- ✓ Strategic theme is clear and measurable
- ✓ All bets sized by effort (S/M/L/XL) and impact (1x/3x/10x)
- ✓ Bets sequenced across H1/H2/H3 with dependency rationale
- ✓ Exit and scale criteria defined for each bet
- ✓ Portfolio balanced across risk profiles and horizons
- ✓ Total effort ≤ team capacity (with 20% slack)
- ✓ Expected portfolio impact ≥ strategic goal (risk-adjusted)

**Common Mistakes**:
- ❌ No strategic theme → roadmap becomes random wish list
- ❌ All bets sized "Large" → no useful prioritization
- ❌ No exit criteria → sunk cost fallacy, zombie projects
- ❌ Portfolio imbalanced → all quick wins (no future) or all moonshots (no near-term value)
- ❌ Dependencies ignored → H1 bets blocked by H2 infrastructure
- ❌ Over-capacity → team burns out, quality suffers
- ❌ Under-ambitious → portfolio impact below strategic goal even if everything succeeds

More from lyndonkl/claude

SkillDescription
abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".