Exec updates and 1-pager · Sergey Sukharevsky

A good management update shortens the path from fact to decision. He does not retell the work of the team, but answers four questions: what has changed, why it matters, what will happen next and what decision or help is needed from the recipient.

Definitions and differences

Exec update is a short update for the top guide on key product issues. It does not include details: only basic facts, conclusions and solutions are needed. It is a direct communication tool between the product team and the executive level.

1-pager is a one-page document with the same meaning: on its basis, the leader understands what is happening and what is required in a minute. Often 1-pager is used for one-time updates and start discussions.

What is different from regular food distribution

The usual updates go into details: metrics, results of experiments, plans. Exec update and 1-pager are built differently – only briefly, structurally and on a case-by-case basis. You can’t forget that the time of the leader is always counted.

Example: the manager does not need to see the statistics of small features, but it is important to know how retention has changed, where risk is maturing, whether a supporting resource is needed.

Why do we need such updates?

Meeting expectations

Top management and stakeholders – stakeholders – make decisions and adjust the course, based on fresh and structured data. If the update is blurred, there will be misunderstandings, resource losses and mistrust.

Example: the launch of a new feature is delayed, the team is silent. Stakeholders themselves make guesses and climb with questions. One clear exec update solves three tasks: relieves panic, sets expectations and shows control.

Acceleration of decision-making

A good 1-pager or exec update allows you to quickly hold a meeting and immediately solve critical issues, without wasting time discussing unimportant details. This is especially important for distributed teams and fast-paced markets.

Basic structure

Context - what kind of product, stage, key question.
2-4 main facts or results (metrics, status of the task, risk).
The next steps are suggestions/requests to the management or necessary solutions.
Attachments – if details are required, they are placed in the second line, not in the body of the message.

An example of a 1-pager structure for working on retention in a B2B service:

Context: personalization improvements, the goal is to retain new customers.
The main thing is that the N metric changed by X% after the release; there was a bug in the integration.
You need to approve the increase in the budget for servers and approve the focus of the team on the bug.

How to write: requirements for tone and content

Write simply and without unnecessary terms. Don’t give grades. Avoid excuses and excessive details. If something is wrong, point out the problem and the solution.

Anti-pattern: A long lyrical update with the story of how the mistake came about and who was at fault. It’s not read or respected.

Key Mistakes and Anti-Patterns

Detail overload

Often there is an attempt to put all the details of the work. This kills the main thing - the speed of understanding and decision-making. Think not about the team, but about the user of the update – here they are C-level or Board.

Blurred statuses

Wordings like work, in the process, thinking about it does not work. If the task is stalling, indicate the specific reason and your plan, do not wait for questions.

For example, instead of the integration process, it is better to write Now the integration is delayed due to a problem with the client’s API, we plan to solve it by June 10. We need support from the client’s IT unit.

When and how often to update exec

Regularity and triggers

The exact frequency is determined by the culture of the company. Usually divided into regular (once a week, a month, by sprint / quarter) and situational (with blockers, changes in direction, crisis).

Example: When a major update is released, the management receives a 1-pager status every Friday. Outside of that, only if the risk changes or support is needed.

Who to send?

Exec updates are often sent not only to their boss, but also to key stakeholders: techdir, head of sales, owner. It is important to agree on the list in advance.

Examples, templates and best practices

Product: CRM widget Context: Release of new email templates, expect NPS growth Results: Testing completed, bug rate deviation normal, NPS growth +2% Risks: Infrastructure update required, delay possible up to 3 days Solutions: Approve DevOps server time allocation

Where to get templates

FAQ

What is the optimal amount for exec update?

Normally, no more than one page: 300-500 words or a short presentation on one slide.

What to do if there are no new advances, but the update still needs to be sent?

Write the real state of affairs, progress, plan, risk. The main thing is the lack of surprises for the leadership.

Only key ones that are tracked by C-levels. For example: MAU/DAU, total revenue, major bugs, MVP delays.

How often do I send exec updates?

Regularity depends on the company’s policies, but most often once a week or at the end of a key stage.

How do you make sure the update is really useful?

Check by feedback: ask fewer clarifying questions, whether decisions are made quickly after your update.

Nope. 1-pager - for management and stakeholders. For the team make separate, more detailed updates.

What is Exec Update and 1-pager?