# Example — Portfolio Review Summary

## Input

> We need a portfolio review summary for next quarter. We cannot do everything. The main candidate themes are activation cleanup, AI answer quality, enterprise admin basics, growth loop experiments, collaboration depth, and analytics instrumentation. The CEO wants a stronger growth story, sales wants more enterprise credibility, and support is still overwhelmed by new-user confusion. Help me produce a recommendation leadership can align on.

## Output

# Portfolio Review Summary

## 1. Review objective

- **Period under review:** next quarter
- **Decision objective:** choose a portfolio focus that improves growth quality without overextending capacity or reinforcing current product leaks
- **Leadership context:** CEO pressure for a stronger growth story, sales pressure for enterprise credibility, support pressure from onboarding confusion

## 2. Recommended focus

### Top bets / above the line

1. **Activation cleanup**
2. **AI answer quality**
3. **Enterprise admin basics**

### Why this focus now

- Activation cleanup addresses the loudest current user friction and reduces support drag.
- AI answer quality strengthens the product’s core value; growth on a weak core will be expensive and fragile.
- Enterprise admin basics protects active sales momentum without letting enterprise expansion fully dominate the quarter.

## 3. Below-the-line decisions

### Work that should wait

- **Growth loop experiments**
  - **Why it is not top priority now:** growth amplification before activation and trust improve is likely to scale inefficiency.
  - **What would change that decision:** activation improves materially and core usage quality holds.

- **Collaboration depth**
  - **Why it is not top priority now:** strategically valuable, but less urgent than first-use conversion and product trust.
  - **What would change that decision:** core friction drops and cross-team usage emerges as the next binding constraint.

- **Analytics instrumentation expansion**
  - **Why it is not top priority now:** useful, but not the quarter’s most urgent bottleneck relative to direct user-facing issues.
  - **What would change that decision:** current signal quality becomes too weak to guide the next decision cycle.

## 4. Trade-off view

### What we are optimizing for

- Better growth readiness through stronger activation and more trustworthy core product value

### What we are deliberately not optimizing for yet

- Maximum top-of-funnel growth optics
- Broader collaboration ambition beyond the current stage goal

### Main opportunity cost

- We may delay some narrative-friendly growth features and broader collaboration expansion in exchange for a tighter core product foundation.

## 5. Resourcing and dependency implications

- **Critical capacity assumptions:** at least one frontend-heavy lane and one quality / core experience lane can run in parallel
- **Key dependencies:** onboarding changes require design + frontend coordination; enterprise admin basics may require security / backend support
- **Major delivery or coordination risks:** quarter focus could get diluted if new enterprise requests keep entering without a sharper gating rule

## 6. Business consequence

- **Expected upside if this focus is right:** higher activation efficiency, better product trust, and enough enterprise credibility to support near-term deals without breaking focus
- **Main downside if this focus is wrong:** growth narrative may feel slower in the short term and some collaboration bets may arrive later than hoped
- **Leading indicators to watch:** activation rate, first-week retention, answer quality satisfaction, support ticket volume from onboarding, deal-stage friction from enterprise gaps

## 7. Leadership ask

- **Decision needed:** confirm activation + trust as the top portfolio objective for the quarter
- **Resource / alignment needed:** hold the line against incremental growth-loop requests unless activation and trust indicators improve
- **Review date:** end of month 1 checkpoint, with quarter midpoint revalidation
