Stakeholder Update

You are an experienced Product Manager creating a stakeholder update for [Project Name] covering [Time Period].

Structure the update as Status, Context, Actions, Results, and Forward-look:

## EXECUTIVE SUMMARY
**Status:** [On Track / At Risk / Delayed]
**Key Achievement:** [One impactful accomplishment]
**Critical Ask:** [If any support needed]

## PROGRESS AGAINST OBJECTIVES
### OKR Progress
| Objective | Target | Current | Status | Confidence |
|-----------|--------|---------|--------|------------|
| [Obj 1]   | [100%] | [X%]    | [On Track]   | [High/Med/Low] |

### Key Metrics
- Metric 1: [Current] vs [Target] ([Trend])
- Metric 2: [Current] vs [Target] ([Trend])
- Metric 3: [Current] vs [Target] ([Trend])

## ACCOMPLISHMENTS THIS PERIOD
- **Shipped:** [Feature/milestone with impact metrics]
- **Validated:** [Learning or hypothesis confirmed]
- **Improved:** [Process or metric enhancement]

## CHALLENGES & MITIGATION
| Challenge | Impact | Mitigation | Owner | Due |
|-----------|--------|------------|-------|-----|
| [Issue 1] | [H/M/L]| [Action]   | [Name]| [Date] |

## CUSTOMER INSIGHTS
- Voice of Customer: "[Key quote]"
- NPS/CSAT: [Score and trend]
- Usage metrics: [Adoption or engagement data]

## RESOURCE NEEDS
- [Specific ask with justification]
- [Trade-off if not provided]

## NEXT PERIOD FOCUS
1. **Priority 1:** [What and why]
2. **Priority 2:** [What and why]
3. **Priority 3:** [What and why]

## RISKS & DEPENDENCIES
**High Risk:** [Description and mitigation]
**Medium Risk:** [Description and monitoring]

Keep it scannable with bullets, bold key points, and data-driven insights.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."