← The Operations Station ~ dish 04 of 10 · the operations station

Meeting Prep Packets

Before a recurring meeting, someone spends thirty minutes pulling the context. Last week's notes. Open action items. The relevant project status. Budget numbers. The meeting prep packet exists to do this without human hands touching it. The leverage is context plumbing. You have to connect the data sources.

The job

Monday morning at 9 AM, the leadership team meets to review the week ahead. Before the meeting, someone spends thirty minutes reading last week’s notes, pulling the current project status, checking the budget dashboard, and pulling the relevant Slack thread. They write a two-page brief. Fifteen minutes into the meeting, someone is reiterating what’s in the brief. Thirty minutes gone.

The dish reads last week’s meeting notes. It pulls the project tracker. It grabs the budget update. It reads the Slack thread from the past week that’s tagged #leadership. It synthesizes a brief: here’s what we decided last week, here’s what’s happened since, here’s what we need to decide today. The brief lands in the meeting organizer’s inbox an hour before the meeting starts. Everyone walks in prepared.

Plated well, this looks like: meetings start with everyone on the same page. The brief is current. It’s specific to the business. It’s written in the team’s voice. When someone says “remind me where we left things,” the answer is already documented.

The recipe

All seven ingredients still apply. The leverage is Context (Ingredient #2). The station needs to know where the data lives. Last week’s notes. The project tracker. The Slack channel. The budget sheet. Without these connections, the brief is generic.

Output Over Process (Ingredient #5) is the second lever. The destination is a two-page brief. Not “pull all the data” but “synthesize what matters into this format.” You define the output. The station figures out what to read.

Training (Ingredient #1) is consistency. Briefs are always structured the same. Decisions from last week. Updates since. Key decisions for today. Examples (Ingredient #4) are three briefs from past meetings. The station learns the voice and the structure.

How to build it

  1. Define the meeting structure. The leadership sync happens Monday at 9. What always gets covered. Pipeline. Wins from the week. Risks. Forward planning. This is the skeleton of every brief.

  2. List the data sources. Previous week’s meeting notes. Current project status from the tracker. Relevant Slack channels. Budget dashboard. For weekly meetings, these are consistent. For quarterly planning meetings, you might add competitor research or customer feedback.

  3. Define the brief structure. Three sections: what happened since we last met, what we’ve decided on so far, what we need to decide today. Each section pulls from the source data and synthesizes.

  4. Write three briefs by hand. Real briefs from past meetings. Include the messy work. The incomplete data sources. The decisions that were tricky. This trains the station on reality.

  5. Connect the data sources. If the brief needs the notes, you tell the station “read the confluence page from last week.” If it needs the project status, “query the project tracker for all items tagged #priority.” The station is not guessing where the data is.

  6. Define the output format. Is the brief a Google Doc. A markdown file. An email. A Slack message. The station delivers into the format you’ll actually use.

  7. Set the schedule. The leadership meeting is at 9 AM Monday. The brief arrives at 8:15 AM. The ops person has fifteen minutes to spot-check before the meeting starts.

  8. Measure for completeness. Is the brief covering what you actually need to know. Are the data sources being read correctly. By week two, are people commenting that the brief was helpful or that something important was missing.

What breaks it

  • Data sources are disconnected. The brief pulls the notes but can’t access the project tracker. It reads Slack but the notes are in Confluence. Incomplete data means incomplete briefs. People still spend thirty minutes gathering context.

  • The meeting is recurring but the data isn’t. The Monday 9 AM sync is the same every week. But the data sources change. One week it’s budget. One week it’s hiring. The station doesn’t know which data to prioritize. The brief feels generic.

  • Context is stale by meeting time. The station ran at 6 AM to pull the project tracker. By 9 AM there’s been an update. The brief is out of date before people read it.

  • The voice doesn’t match. The brief reads like a report, not like the team’s internal language. People skim it instead of using it because it doesn’t feel like the conversation they’re about to have.

When it’s working

By week one, the brief is landing on schedule. It’s pulling the right data. Sixty percent feels complete. Forty percent is missing nuance or context. By week two, someone is adding one or two notes before sending but the structure is solid. By week three, the brief is sent as-is. By week four, the meeting starts with everyone on the same page because they read the brief. The first fifteen minutes of the meeting, which used to be recap, now is decision-making.

The signal that the recipe is sharp: someone asks a question in the meeting and the answer is already in the brief because the station learned what questions leadership actually cares about.

Monday Move

Write the brief for next Monday’s meeting by hand. Pull the notes. Read the tracker. Check the Slack thread. Write the two-page brief. Show the station. Have it write the brief for the following Monday while you watch. Where does it match. Where’s it missing. That’s your feedback.

Dish 4 of 10 on the Operations Station. Build-note leverage: Context (Ingredient #2).