Management Cortex
The Weekly Operating Meeting, Run by the Cortex.
Issues surfaced, decisions captured, commitments extracted. The L10 — or whatever your team calls it — runs the way the framework actually describes.
What it solves
The weekly operating meeting is one of the highest-leverage cadences in any service company. When it runs well, decisions get made, issues surface, the team aligns. When it slips, the same issues recur every week without resolution.
The work that makes the meeting valuable — preparation, note-taking, decision capture, action assignment, follow-through — is real labor. Most teams skip it because nobody has time. The meeting happens, but the meeting that should happen doesn't.
A dedicated facilitator-and-note-taker would fix it. Most companies don't have the headcount.
How It Works
Before the meeting, the Cortex prepares the agenda — pulled from open commitments, last meeting's action items, drift signals from the metrics cadence, and team-submitted topics.
During the meeting, the Cortex captures decisions, surfaces issues, and extracts commitments. Voice-to-text transcript optional; structured note capture by the chair is the default.
After the meeting, the Cortex composes a one-page brief — what was decided, what was deferred, who committed to what, when each commitment is due.
The next week's agenda starts from the previous week's commitments. Recurring issues surface automatically: any issue appearing three weeks running gets flagged for structural attention.
Pre-meeting, the team sees the agenda. Post-meeting, anyone who missed the session sees the brief. The institutional memory of the meeting lives in the Cortex, not in someone's notebook.
This is the L10 — or weekly ops, or leadership review — that the operating-system frameworks always describe, finally running the way they describe it.
What You Get
- Pre-meeting agenda composed from commitments, drift signals, and team submissions
- During-meeting decision capture, issue surfacing, commitment extraction
- Post-meeting brief composed and distributed
- Recurring-issue detection across weeks
- Commitment carry-forward — last week's actions are next week's agenda starting point
- Integration with the channel your team meets in (Teams, Zoom transcripts, in-person notes)
In practice
A leadership team of six runs a weekly operating meeting every Monday morning. Before the Cortex: agendas were ad-hoc, notes were taken by whoever felt like it, decisions weren't captured, action items vanished. After: the agenda lands in the team channel Sunday evening, drawn from the previous week's open commitments and current drift signals from the metrics cadence. The chair captures decisions in shorthand; the Cortex composes the post-meeting brief by Monday afternoon. After three months, recurring issues surface that had been showing up unnoticed for years — three resolved structurally, two acknowledged as constraints to work around. The meeting that used to drift is now the highest-leverage hour in the leadership week.