A Sunday leadership brief from meeting transcripts and Slack

How this helps you

In a few minutes a week you see what each team is working on and where it drifts from your priorities, with links to check.

✦ Try it

Build me a leadership Bot. Connect it to my meeting transcripts in [tool] and my team's Slack, including [channels]. Every Sunday morning, send me a short brief: what each team talked about this week, what decisions were made, and where that does or doesn't match my top priorities. My priorities are: [list]. Link the source of anything important and tell me what you couldn't read. Read only: don't post or reply anywhere.

Fill in: [tool]: where your meeting transcripts live. [channels]: the Slack channels to cover, or 'every channel you can read'. [list]: your current priorities.

What they did

Dan Martell doesn't run day-to-day operations in his companies but wants to know whether everyone is pulling in the same direction without sitting in every meeting. He asked his chief of staff to build a leadership Bot connected to meeting transcripts, team Slack and every channel. Every Sunday morning it sends him a short brief: what each team talked about that week, what decisions were made, and where that does or doesn't match his top priorities, which he gives it as a list. It links the source of anything important and tells him what it couldn't read. He says it takes him about five minutes a week to read.

Who it's for: Founders and managers who want to know what their teams are focused on without attending every meeting.

Before you start

Meeting transcripts it can read (a notes tool or recording connector).
Slack connected, with the Bot able to read the channels you want covered.
Your current top priorities written down.

How to try it

Write your top 3 to 5 priorities in one short list.
Ask your chief of staff to build the leadership Bot with the prompt below and connect transcripts and Slack.
Run it once by hand before scheduling and check the links it gives for each claim.
Ask it to schedule the brief for Sunday morning, and update the priorities list whenever they change.
Read the 'couldn't read' section each week; a missing channel or transcript means the brief has a blind spot.

What to expect

A one-screen Sunday brief grouped by team, each point linked to the meeting or thread, ending with 'off priority' items and a list of sources it couldn't open.

Common mistakes

Not giving it priorities. Without them it can only summarise, not tell you what's off track.
Skipping the 'what you couldn't read' line, so a quiet channel looks like a quiet week.
Letting it reply in Slack. 'Read only' is our addition to keep it a reporting Bot (Dan doesn't say this).

Related tips

Run a daily standup with your Bots in a group chat: Put your main Bots in one group chat and have your primary Bot ask each morning what everyone is doing today, so nothing slips.
Build a weekly before-and-after scoreboard from a Google Sheet: Point a Page at a sheet, compare baseline weeks with recent weeks, and refresh it every Monday.
Let a team Bot answer requests in Slack: Install a team Bot in Slack so colleagues tag it directly, and give it a routine to catch missed tags.