The same meeting, every week, in five tools
A leadership team running a structured weekly meeting (L10-style, EOS-style, or your own variant) usually has the same problem: the agenda lives in one tool, the KPIs in another, the to-dos in a third, the obstacles list in a fourth, and the archive of past meetings in a fifth. Every Monday someone stitches them together. The work is predictable, low-value, and easy to forget.
The pieces are all the same shape every week. Headlines: short status notes from each team. To-dos: open + closed, tracked across meetings. Obstacles and opportunities: the issues that surface during the meeting itself. Quarterly goals: the targets the team is rowing toward. KPIs: the numbers that signal whether the rowing is in the right direction. The workspace holds each as a first-class entity; the agenda assembles itself.
Meetings, headlines, to-dos, OOs, KPIs
The hub covers the canonical shape of a structured leadership meeting. A team page lists members. A headlines page lets each team area drop a one-line status before the meeting. A to-dos page tracks open and closed action items across meetings. An obstacles / opportunities page captures the issues that come up live, with thread comments for follow-up. A quarterly goals page holds the multi-month targets. A KPI page tracks the weekly numbers and rolls them up. An archive page holds past meetings for reference.
Run the meeting, post the rollup
- Set the cadence. A meeting sequence is a recurring entity — weekly, biweekly, monthly. Each meeting in the sequence inherits the agenda template.
- Each team drops a headline. Before the meeting, teams add a one-line status to the headlines page. The meeting page renders them in one view.
- Run through the agenda. Review last week’s to-dos, scan the headlines, work through obstacles and opportunities, check the KPI rollup, capture new to-dos.
- Post the KPI rollup to Slack. When the weekly rollup is finalised, the workspace posts a Slack message to the leadership channel — KPI values for the week, link back to the meeting overview. Team members not in the meeting see the numbers without opening the workspace.
- Archive the meeting. The meeting becomes an archive entry; next week’s meeting inherits the open to-dos and unresolved obstacles.
Meeting sequence, KPI list, Slack channel
- Meeting sequence — define the recurring cadence (weekly is the default; biweekly and monthly are common for leadership teams) and the participant list. Multiple sequences in one workspace if you run more than one structured meeting (e.g. one with the leadership team, one with department heads).
- Headlines structure — typically one row per team area, with the team owner attached. Edit the structure to match how your team is organised.
- KPI list — the numbers you track weekly. Each KPI has a name, an owner, and a target. Values get logged on a per-week cadence and rolled up into the Slack post.
- Slack channel — pick the leadership channel that should receive the weekly rollup post.
- To-do roll-forward rules — open to-dos inherit to the next meeting in the sequence; closed ones land in the archive. Tune the criteria for escalating long-open items.
The agenda is a property of the workspace, not a doc someone has to maintain. The meeting follows; the Slack rollup follows the meeting.
Operating rhythm built into the workspace
The shape of a structured weekly meeting is unusually stable — across teams, across industries, across years. That stability is what makes the spec approach work here: the entities (meeting, headline, to-do, obstacle, quarterly goal, KPI) match the meeting’s real structure, and once the workspace knows them, the rest follows. Change the KPI list or the headline structure by editing the spec; the meeting next Monday picks up the change.