Field note

A meeting brief before the meeting.

A meeting brief before the meeting.

Sean Niklas · MarginMethods

Bring the decisions, open commitments, and changes into one brief before the conversation begins.

The friction

Meeting preparation starts long before you sit down at the table.

It starts with the email you remember seeing, the update someone sent in Teams, and the commitment buried in last week’s notes. By the time you’ve gathered everything, you’ve already spent attention the conversation needs.

In my own business, I built a workflow that brings those sources together into a brief delivered fifteen minutes before a weekly leadership meeting.

Shape the brief

The useful part is deciding what belongs in the brief. I started with one recurring meeting and asked five questions:

  • What data is needed for this meeting?

  • Which commitments need an update?

  • What changed since we last met?

  • What decisions do we need to review?

  • What decisions do we need to make?

Then, I identified the sources for each answer. This was a critical step: one canonical source of truth to avoid ambiguity and uncertainty. The brief then gets delivered to me for review.

Check the result

A missing update in the briefing should always remain visible - otherwise, a confident summary that quietly fills the gap makes preparation harder to trust.

Try the process manually for the next meeting before automating the collection. You’ll learn which information helps and which material everyone scrolls past.

Afterward, count the gathering time, the checking time, and the corrections. That gives you a useful baseline for deciding whether automation is helping.

The goal is to arrive ready to listen, make decisions, and follow through.

MarginMethods

© 2026 MarginMethods

MarginMethods

© 2026 MarginMethods