Executive Summary & Board Update

Executives Don't Want Details. They Want Decisions.

I once watched a PM present a 42-slide quarterly review to a C-suite audience. By slide 8, the CEO interrupted: "What do you need from us?" The PM stumbled. He'd spent two weeks building those slides but couldn't answer the most basic executive question in one sentence.

This happens constantly. PMs prepare for board and executive updates the same way they prepare for team meetings — with context, data, process, and narrative. Executives don't want any of that. They want three things: where are we relative to plan, what are the risks, and what decisions do you need from me?

Why Most Executive Updates Miss the Mark

According to a 2023 survey by Board Intelligence, 72% of board members say the information they receive is too detailed, too long, or not focused on the right issues. Nearly half said they struggle to identify the key decisions needed from the materials they're given.

The problem is structural. PMs are trained to show their work. In an engineering review or design critique, showing your analysis builds credibility. In a board room, it kills your momentum. An executive who reads three paragraphs of context before getting to the point has already decided you don't know what matters.

Amazon's six-page memo format works because it front-loads the conclusion. The first paragraph tells you the recommendation. Everything else is supporting evidence for people who want to dig in. Most PM executive updates do the opposite — they build to a conclusion that arrives on the last slide, by which point half the room has checked out. Andy Grove wrote about this in "High Output Management": the purpose of a management report is not to inform the reader. It's to force the writer to clarify their own thinking. If you can't summarize your product's status in three bullets, you don't understand your product's status well enough.

How This Prompt Helps

This prompt generates executive summaries and board updates in the format executives actually prefer — leading with status and decisions needed, followed by key metrics, risks, and a strategic outlook. It forces you to distill your product story into the components that matter at the leadership level: are we on track, what changed, and what do we need to decide?

The output is something you can drop into a board deck or send as a pre-read with minimal editing.

When to Reach for This

• You're preparing for a quarterly board meeting and need to translate your product progress into board-level language
• The CEO has asked for a product status update and you have 30 minutes to write it
• You're presenting at an exec team meeting and have a 5-minute slot to cover your entire product area
• Your board wants to understand a strategic pivot or major product bet you're making
• You need to communicate bad news (missed targets, delayed launches) in a way that maintains confidence

What Good Looks Like

A strong executive summary fits on one page, leads with the 2-3 most important things the reader needs to know, includes metrics with context (not just numbers but whether they're good or bad relative to plan), clearly states any decisions needed with your recommendation, and identifies the top 1-2 risks with mitigation plans. If an executive can read it in under two minutes and know exactly what's happening and what they need to do, you've nailed it.

Sources

• Board Reporting: What Directors Want — Board Intelligence
• High Output Management — Andrew Grove
• Writing for Executives: The Amazon Memo Format — Harvard Business Review