What This Template Is For
Executives do not have time to read your full analysis. They need the conclusion first, the supporting evidence second, and the ask third. Most product updates fail because the PM writes them bottom-up: context, then analysis, then findings, then conclusion. An executive reads the first two paragraphs, does not find the point, and moves on.
The BLUF (Bottom Line Up Front) format inverts this. You lead with the conclusion, follow with the evidence that supports it, and close with the specific decision or action you need. This template gives you a repeatable structure for writing executive summaries that get read, understood, and acted on.
This template is for one-off or periodic written updates. For structuring a live presentation, use the Board Deck Template. For managing ongoing stakeholder communication rhythms, the Stakeholder Communication Plan Template provides the broader system. The stakeholder management handbook covers executive communication as a core PM skill.
How to Use This Template
- Start with the Bottom Line. Write this section last if you need to, but place it first in the document. Force yourself to state the conclusion in 2-3 sentences.
- Fill in the Metrics Snapshot with the numbers that matter most. Executives pattern-match on metrics. If the numbers look good, they skim. If something is off, they dig in.
- Complete the Key Findings section with 3-5 bullet points. Each finding should be one sentence with a specific number or outcome.
- Write the Ask section. Every executive summary should end with a clear request: a decision, a resource allocation, an approval, or an acknowledgment.
- Keep the total document to one page (or the equivalent in email: under 500 words). If you cannot fit it in one page, you have not distilled enough.
The Template
Header
| Field | Details |
|---|---|
| Subject | [Product/Initiative Name]: [One-line summary of status or conclusion] |
| Date | [Date] |
| Author | [Name, Role] |
| Audience | [Who is this for: CEO, VP Product, Board, etc.] |
| Classification | FYI / Decision Needed / Approval Needed |
| Read time | [Target: 2-3 minutes] |
Bottom Line
State the conclusion first. What is the single most important thing the reader needs to know?
[2-3 sentences maximum. Be direct. Include the key metric or outcome. If you need a decision, state it here.]
Example formats:
- "Activation rate increased from 34% to 48% after the onboarding redesign. We recommend expanding the experiment to 100% of users and investing in phase 2."
- "The Q1 launch is at risk. Two of four workstreams are behind schedule, and we need a decision on scope reduction by March 15."
- "Customer churn increased 22% MoM. The primary driver is pricing sensitivity in the SMB segment. We recommend a targeted retention campaign before the annual renewal cycle."
Status Indicator
| Indicator | Meaning |
|---|---|
| On Track | Delivering as planned. No intervention needed. |
| At Risk | One or more issues could cause a miss. Mitigation in progress. |
| Off Track | Will miss the target without intervention. Decision or resource needed. |
| Complete | Delivered. Sharing results and next steps. |
Current status: [On Track / At Risk / Off Track / Complete]
Metrics Snapshot
Include 4-6 metrics. Show the trend (up/down/flat) and whether it is on target.
| Metric | Current | Target | Trend | Status |
|---|---|---|---|---|
| [Primary KPI] | [Value] | [Target] | [Direction] | On/Off Track |
| [Secondary KPI] | [Value] | [Target] | [Direction] | [Status] |
| [Leading indicator] | [Value] | [Target] | [Direction] | [Status] |
| [Lagging indicator] | [Value] | [Target] | [Direction] | [Status] |
| [Financial metric] | [Value] | [Target] | [Direction] | [Status] |
For help selecting the right metrics, the product metrics library provides definitions and calculation methods for 100+ PM metrics. The Product Analytics Handbook covers metric selection strategy.
Key Findings
3-5 bullet points. Each finding should be one sentence with a specific number or outcome.
- [Finding 1]. [One sentence with a specific metric or outcome. e.g., "Mobile conversion improved 18% after checkout redesign, exceeding the 12% target."]
- [Finding 2]. [One sentence. e.g., "Enterprise pipeline grew from $1.2M to $2.1M after the SSO launch, driven by 3 new healthcare logos."]
- [Finding 3]. [One sentence. e.g., "Support ticket volume for onboarding issues dropped 34%, suggesting the new flow is working."]
- [Finding 4]. [One sentence. e.g., "API response time increased 40ms after the new feature deployment. Engineering is investigating."]
- [Finding 5 (optional)]. [One sentence.]
What Is Working
[2-3 sentences on what is going well and why. Attribute success to specific actions or decisions, not luck.]
What Needs Attention
2-3 sentences on risks, blockers, or concerns. Be honest. Executives value early warning over false confidence. Use the [RICE framework to help prioritize which issues to highlight.]
The Ask
What do you need from this audience? Be specific.
| # | Ask | Decision Maker | Deadline | Context |
|---|---|---|---|---|
| 1 | [Specific ask: approve, decide, allocate, acknowledge] | [Name] | [Date] | [One sentence of why this is needed now] |
| 2 | [Ask] | [Name] | [Date] | [Context] |
If no decision is needed: State "This update is FYI only. No decision or action is required."
Appendix (Optional)
Link to supporting documents. Do not embed detailed analysis in the exec summary.
| Document | Purpose | Link |
|---|---|---|
| [Detailed analysis] | [What it covers] | [Link] |
| [Dashboard] | [What it shows] | [Link] |
| [Customer research] | [What it covers] | [Link] |
Filled Example: Q1 Product Quarterly Review
Header (Filled)
| Field | Details |
|---|---|
| Subject | Q1 2026 Product Review: Activation OKR on track, Enterprise pipeline exceeding target |
| Date | March 5, 2026 |
| Author | Maya Chen, VP Product |
| Audience | CEO, CFO, CTO, VP Sales, VP CS |
| Classification | Decision Needed |
| Read time | 3 minutes |
Bottom Line (Filled)
Product delivered 8 of 10 planned Q1 initiatives. Activation rate improved from 34% to 47% (target: 50%), and enterprise pipeline grew 75% to $2.1M. Two items need executive attention: (1) the mobile app launch slipped to April due to an App Store rejection, and (2) the SMB churn spike requires a decision on whether to invest in a targeted retention program or accept the loss as a pricing correction.
Current status: At Risk (2 of 10 initiatives behind schedule)
Metrics Snapshot (Filled)
| Metric | Current | Target | Trend | Status |
|---|---|---|---|---|
| Activation rate (new users, 7-day) | 47% | 50% | Up from 34% | At Risk (3% gap) |
| Enterprise pipeline | $2.1M | $1.5M | Up 75% QoQ | On Track |
| Monthly churn (SMB) | 4.8% | 3.0% | Up from 3.2% | Off Track |
| NPS (all segments) | +42 | +40 | Flat | On Track |
| Revenue (MRR) | $890K | $850K | Up 8% QoQ | On Track |
| Feature adoption (new dashboard) | 61% | 50% | Accelerating | On Track |
Key Findings (Filled)
- Onboarding redesign is working. Activation rate improved 13 percentage points (34% to 47%) after the guided onboarding flow shipped in Sprint 10. Time-to-first-value dropped from 14 minutes to 6 minutes.
- Enterprise SSO unlocked pipeline. Three new healthcare logos entered the pipeline within 2 weeks of SSO launch, representing $420K in combined ACV.
- SMB churn spiked after January pricing change. 4.8% monthly churn vs. 3.0% target. Exit surveys cite "price increase without perceived value increase" as the top reason (38% of responses).
- Mobile app launch delayed by App Store rejection. Apple flagged our in-app subscription flow. Engineering is reworking the purchase flow. Revised launch: April 8.
- New dashboard adoption exceeded target. 61% of weekly active users adopted the new dashboard within 30 days, driven by the in-app migration prompt.
What Is Working (Filled)
The onboarding redesign is the highest-impact initiative this quarter. The product-led approach (guided flow with contextual tooltips) outperformed the alternative we considered (video tutorials). The decision to invest 3 sprints in onboarding instead of new features is paying off in activation. Enterprise pipeline growth validates the SSO investment from Q4.
What Needs Attention (Filled)
SMB churn is the primary concern. The January price increase (20%) was expected to cause 1-2% incremental churn. Actual incremental churn is 1.8%, which puts Q1 net revenue retention at risk. If churn does not stabilize by April, we will miss the annual NRR target (110%). The mobile app delay is a 1-week slip with limited revenue impact but will affect the App Store feature placement we were negotiating with Apple.
The Ask (Filled)
| # | Ask | Decision Maker | Deadline | Context |
|---|---|---|---|---|
| 1 | Approve $40K budget for a targeted SMB retention campaign (personalized feature education + account reviews for at-risk accounts) | CFO | March 12 | Campaign needs to launch before April renewal cycle. Projected ROI: retain 30-40 accounts ($72K ARR). |
| 2 | Confirm whether mobile app launch date (April 8) is acceptable or whether we should fast-track with a reduced feature set by March 28 | CEO | March 10 | Apple feature placement window closes April 15. |
Appendix (Filled)
| Document | Purpose | Link |
|---|---|---|
| Q1 Product Metrics Dashboard | Full metric breakdown with daily trends | [Looker link] |
| Onboarding A/B Test Results | Detailed experiment analysis | [Notion doc] |
| SMB Churn Analysis | Exit survey data, cohort analysis, retention modeling | [Sheet link] |
| Mobile App Store Rejection Details | Apple's feedback and engineering remediation plan | [Linear issue] |
Common Mistakes to Avoid
- Burying the lead. If an executive has to scroll past three paragraphs of context to find the conclusion, they will not finish reading. Put the most important sentence first.
- Including too many metrics. More than 6 metrics in a snapshot creates noise. Choose the 4-6 that directly relate to the audience's priorities. If they want more, they can check the dashboard in the appendix.
- Presenting problems without asks. "Churn is up" is a status update. "Churn is up, and I need $40K and a decision by March 12 to address it" is an executive summary. Always end with the ask.
- Being vague about status. "Things are mostly on track with a few challenges" tells the reader nothing. Use the four-level status indicator (On Track, At Risk, Off Track, Complete) and be honest about which it is.
- Writing it for yourself instead of the audience. The exec summary is not your internal analysis notes. Strip out the methodology, the alternatives you rejected, and the nuance that matters to you but not to the reader. Link to the detailed analysis in the appendix for anyone who wants to go deeper.
Key Takeaways
- Lead with the conclusion, not the context. Use the BLUF (Bottom Line Up Front) format
- Limit the metrics snapshot to 4-6 numbers that directly relate to the audience's priorities
- Every executive summary should end with a specific ask: a decision, a resource, or an acknowledgment
- Keep the total document under 500 words. Link to detailed analysis in the appendix
- Be honest about status. Executives value early warning over false confidence
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use