This is a ship story, not a framework. For one quarter I changed how my product leadership team met, measured what happened, kept some of it, and threw some of it out.
The meeting I was tired of
The weekly product staff meeting started the way most do. Round the table, each leader narrates what their team did this week. Thirty minutes, sometimes more. The people whose updates were not being given half-listened and triaged their inboxes. The updates were performances of competence: confident, smooth, light on the awkward parts. And reliably, nothing was decided in that first half hour. I had run this meeting for most of my career, and sat in the equivalent at Salesforce, at Smartcat, and at a couple of startups. The format was inherited, not designed. So I stopped inheriting it.
What I built
The premise was simple. Status does not require a meeting; status requires a place to look. Decisions require a meeting. So a small set of agents assembled a dashboard before each weekly meeting, pulling from the systems we already used, and put five things on one screen: what shipped since last week, what outcome actually moved, current eval scores for production AI features with thirty-day trend lines, cost per outcome by workflow, and a flagged list of anything off track, drifting, or underwater. The rule was that everyone read it before the meeting, and the meeting was not allowed to start with status. It started with the flagged list and the decisions those flags demanded.
What it killed and what it surfaced
It killed the thirty-minute narration immediately and permanently, and nobody missed it. It killed the performance of "we are on track," because you cannot narrate a declining eval score into sounding fine when everyone is looking at the red line. And it killed the meeting as a place to look busy.
The surfacing was the real payoff. A quietly drifting eval score on one AI feature became a red trend line we caught early. Two workflow costs turned out to be persistently underwater because nobody had ever looked. The team's relationship to the numbers changed: when you know the dashboard is coming and everyone will see it, you start owning your numbers upstream instead of preparing a narrative about them.
The plain version
Status does not need a meeting. Decisions do. Moving reporting into an agent-refreshed dashboard turned the staff meeting from narration into triage. The one trap is density: keep it to the few numbers that change decisions. If your staff meeting opens with a lap around the table of what everyone shipped, try this for one month. Move that into a doc or dashboard people read beforehand, start the live meeting at the first hard decision, and watch how much of the old meeting turns out to have been theater.