A simpler start to meetings

At fictional Northstar Services, a project team replaced a vague agenda label with three useful prompts: the decision, the context people need, and the next step. The change helps attendees see the meeting’s purpose before they join.

A meeting room set for a handful of people

Make the purpose visible before the meeting

“Project update” had become a catch-all agenda item. People arrived unsure whether they were expected to listen, raise a concern, or make a decision. The team tried a simpler pattern: name the decision first, include only the context needed to make it, and finish with a clear next step.

The agenda stayed brief, but readers could tell why the item was on the schedule and what preparation, if any, would help. The example below shows how that changed one item.

One agenda item, made clearer

A worked example from the fictional project team.

Agenda item
Before:
Project update
After:
Choose the launch date; review the two proposed dates and the key constraint.
What attendees can tell
Before:
The topic is the project, but the meeting’s purpose is unclear.
After:
The group needs to choose a date and consider the relevant constraint.

Try the three prompts

Use these prompts when adding an item to a team meeting agenda.

  1. 1

    Name the decision

    Write the question the group needs to answer, or state plainly that the item is for information only.
  2. 2

    Share the needed context

    Include the options, background, or constraint attendees need to understand the question. Leave out details that do not help them prepare.
  3. 3

    End with an owner and next step

    Say what should happen after the discussion and identify the role responsible for moving it forward.

More from the sample newsroom

Two shorter fictional updates, included as related editorial reading.

A handoff note names the next owner

A fictional service team began ending its daily handoff with one sentence: what changed, what remains open, and which role takes the next action.
  • The note separated completed work from open questions.
  • The receiving role could identify its next action at a glance.

A project brief puts the decision first

A fictional project group moved its requested decision to the top of a one-page brief, followed by the options and the context needed to compare them.
  • Readers saw the question before the background detail.
  • The brief made the requested input explicit.

Share a story or correction

Have a useful example of a team practice that made work clearer? Contact your organization’s editorial owner through its established news or communications channel. Include the change, who it helps, what readers can try, and the role that can verify the details. Use the same route to request a correction.

No submission destination is built into this sample page; follow your organization’s established editorial contact route.