Project Portfolio Strategy

🧠 Free Recall ❓ Quiz 🔍 Cues 🔮 Simulation 🥷 ShadowBox 📐 Encode Cards

Anchor everything to a single portfolio‑level goal.
 Convert strategy into one quantitative North Star metric (e.g., annual net new ARR, customer NPS improvement, cost‑to‑serve reduction). All project scoring, resource allocation, and kill decisions reference this metric.
Adopt a unified scoring model.
 Score every project on the same dimensions:
Δ Value (economic or strategic impact)
Time‑criticality / Risk of Delay
Effort (person‑weeks & cash)
Option value / learning
 Weighted Shortest Job First (WSJF = Value × Urgency ÷ Effort) is a robust default; adjust weights once per year, never per project.
Enforce explicit capacity buckets.
 Split total available effort (100 %) into “Run” (keep‑the‑lights‑on), “Grow” (incremental improvements), and “Transform” (bets). Fix the percentages for a quarter; new work must fit inside a bucket or displace something already there.
Set portfolio WIP limits.
 Limit concurrent “Transform” initiatives to the number of squads you can fully staff. Nothing starts half‑staffed; nothing new starts until something finishes or is killed.
Create a two‑tier cadence.
Weekly: 15‑minute flow review—are any projects blocked? unblock or escalate.
Monthly: portfolio review—re‑score, re‑rank, and, if necessary, reallocate capacity. Data, not politics, drives changes.
Define kill‑switch thresholds up front.
 For every project: “If <metric X> isn’t ≥ Y by week Z, terminate or pivot.” Pre‑committing prevents sunk‑cost fallacy.
Weaponize shared assets.
 Centralize UX components, data pipelines, and template automations; mandate reuse before build‑new. This compounds velocity across the whole portfolio.
Keep teams liquid.
 Cross‑train to two‑skill depth and maintain a reserve bench (~10 % slack) for surge work or rescuing slipping projects.
Measure with a balanced scorecard.
Leading indicators: cycle time, escaped‑defect rate, budget burn variance.
Lagging indicators: ROI vs plan, contribution to the North Star metric.
 Display live in a single dashboard visible to all stakeholders.
Continuously harvest and recycle learnings.
 Post‑mortem every completed or killed project within one week; record one‑sentence “law” and add to a searchable playbook. Require new project charters to cite at least one prior lesson.
Follow these ten rules relentlessly and the portfolio self‑optimizes: the highest‑leverage work enters first, under‑performers exit early, capacity stays fully utilized but never over‑extended, and learning compounds across cycles.

Unstarred

Dunk (exclude from study)

I am setting up a weekly Monday cadence meeting. What actions, activities, ideas, exercises, questions, etc. do you think should be in it?

# Constructing Your Optimal Monday Cadence Meeting

Your Monday cadence meeting should serve as a precise optimization mechanism, not a wasteful status ritual. Here's the architecture that maximizes ROI on everyone's time:

## Core Components (45-60 minutes total)

### 1. North Star Alignment (5 minutes)
- Begin by displaying the single metric that drives all decisions
- Show weekly progress against quarterly targets with variance analysis
- No discussion - this is a reminder of what matters

### 2. Portfolio Performance Dashboard (10 minutes)
- Review key metrics across all workstreams:
* Planned vs. actual capacity utilization (%)
* Projects approaching kill-switch thresholds
* Cycle time trends by initiative category
* Defect escape rate

### 3. Resource Allocation Optimization (15 minutes)
- Identify capacity imbalances across buckets
- Make real-time reallocation decisions based on scoring model
- Approve/deny requests to exceed WIP limits with explicit tradeoffs

### 4. Blocker Removal Protocol (15 minutes)
- Review all tickets/issues exceeding predefined cycle time thresholds
- Assign SWAT resources from your bench capacity
- Set explicit resolution deadlines with clear ownership

### 5. Learning Amplification (10 minutes)
- Review one key learning from previous week's post-mortems
- Capture as a new "law" in your searchable playbook
- Identify which active projects must incorporate this learning

## Implementation Rules

1. Pre-distribute all data 24 hours in advance
2. No status updates or storytelling allowed
3. Record all decisions in a decision log with explicit measures of success
4. Terminate exactly on time regardless of completion
5. Rotate meeting leadership to test organizational understanding of the system

Do not allow this to devolve into a social gathering or information-sharing session. The meeting exists solely to optimize your portfolio performance against your North Star. Every minute should drive measurable impact.

Shall I elaborate on any specific component of this framework?

Continue Conversation...

Get Action Items

Project Portfolio Strategy

I am setting up a weekly Monday cadence meeting. What actions, activities, ideas, exercises, questions, etc. do you think should be in it?

Review Questions

Todos

Sensemaker