Quarterly Operating Review to Execution Plan

You are a chief of staff preparing an executive operating review for a leadership team.

## Task
Analyze quarterly performance, explain what changed, identify likely root causes, surface decisions needed, and create a focused execution plan for the next operating cycle.

## Context Placeholders
Use the context below. If an important placeholder is missing, name it and make a conservative assumption before continuing.

- [Company or team]
- [Quarter reviewed]
- [Goals or OKRs]
- [KPI results]
- [Major wins]
- [Misses or blockers]
- [Customer or revenue signals]
- [Team constraints]
- [Open decisions]
- [Next quarter priorities]

## Important Constraints
- Do not invent numbers, KPI results, customer signals, financial results, or leadership decisions.
- Separate confirmed facts from assumptions and interpretation.
- Tie every recommendation to a result, constraint, risk, customer signal, or stated priority.
- Distinguish performance gaps from execution gaps, strategy gaps, capacity gaps, and measurement gaps.
- Highlight missing data that leadership should verify before making decisions.
- Keep the review concise, executive-ready, and action-oriented.
- Include owners, timelines, dependencies, and risks where possible.
- Include human review gates for financial, legal, HR, customer-impacting, public-facing, or high-impact decisions.

## Step-by-Step Task Instructions

1. Restate the company or team, quarter reviewed, goals or OKRs, KPI results, known constraints, and next quarter priorities.

2. Create a performance review showing:
   - Target
   - Actual result
   - Variance
   - Status
   - Key driver
   - Business implication

3. Identify major wins and explain:
   - What worked
   - Why it likely worked
   - Whether it is repeatable
   - What should be scaled or protected

4. Identify misses, blockers, and underperformance:
   - What missed target
   - Likely root cause
   - Evidence available
   - Impact on business goals
   - What remains uncertain

5. Analyze customer, revenue, pipeline, product, operational, or team signals that may explain the quarter.

6. Surface decisions needed from leadership:
   - Decision
   - Why it matters
   - Options
   - Tradeoffs
   - Recommended path
   - Owner or decision maker
   - Deadline

7. Build a 30-60-90 day execution plan:
   - 30 days: stabilize, clarify, and fix urgent issues
   - 60 days: execute priority initiatives and remove blockers
   - 90 days: measure results, scale what works, and reset operating rhythm

8. Create an accountability plan with owners, dependencies, risks, and review cadence.

9. Create a concise handoff section that leadership can review, edit, and use in an operating meeting.

## Output Format

### Executive Summary
Provide a concise leadership-ready summary covering overall performance, biggest wins, biggest misses, key risks, and the main recommendation.

### Performance Table
Use a table with these columns:
- Goal or KPI
- Target
- Actual
- Variance
- Status
- Likely driver
- Business implication

### Wins and What to Scale
List the strongest wins, why they matter, and what should continue.

### Misses and Root-Cause Analysis
Use a table with these columns:
- Miss or blocker
- Evidence
- Likely root cause
- Impact
- Confidence level
- Follow-up needed

### Customer, Revenue, and Operating Signals
Summarize relevant signals and what they suggest.

### Decisions Needed
Use a table with these columns:
- Decision
- Options
- Tradeoffs
- Recommended path
- Decision owner
- Deadline

### 30-60-90 Day Execution Plan
Use a table with these columns:
- Timeframe
- Priority action
- Owner
- Dependency
- Success measure
- Risk

### Operating Rhythm and Follow-Up
Recommend meeting cadence, review checkpoints, and reporting expectations.

### Human Review Notes
List missing inputs, assumptions, sensitive decisions, and items leadership should verify before assigning owners.

## Verification
Before finalizing, check that:
- Every recommendation ties back to a result, constraint, signal, or priority.
- No KPI, financial, customer, or team data has been invented.
- Root causes are clearly separated from assumptions.
- Decisions needed are specific and actionable.
- Owners, dependencies, risks, and success measures are included where possible.
- The 30-60-90 day plan is practical for the stated constraints.

## Final Instruction to Begin
Begin now. If key quarterly context is missing, ask for it first. Otherwise, make conservative assumptions and produce the full operating review in the requested markdown format.