Every product team runs some version of the Monday meeting where people take turns describing their week. It costs an hour of the whole team, everyone performs progress, and the numbers quoted are whatever someone remembered on the walk over. We replaced ours with a memo the platform writes itself. Here’s the shape, so you can steal it.
The four questions
A signal memo earns its slot by answering exactly four things, from the record:
- What shipped. Releases and the tasks behind them — not “worked on”, shipped. Pulled from delivery data, not memory.
- What customers said. New insights and feedback themes, weighted by who said them: three requests from paying accounts outrank thirty from tourists.
- What moved. The handful of metrics you’ve committed to, as deltas: activation, retention, the funnel steps that matter. Flat is a finding too.
- What’s drifting. Planned-versus-actual: features sliding past their targets, work in progress too long, promises aging. The uncomfortable section — which is why it must be automated. Machines don’t soften drift.
That’s it. If it takes longer than five minutes to read, it’s a report, not a memo.
The rule that makes it trustworthy
One design decision matters more than everything else: deterministic reads first, narration second. The queries pull the facts — release list, feedback counts, metric deltas, drift flags. Only then does a model turn the result set into readable prose. The model cannot introduce a number the queries didn’t return.
Skip that rule — just prompt an assistant with “summarize our week” — and you get confident fiction on the weeks that matter most, because those are the messy ones.
Build vs included
You can build this yourself: land shipped-work, feedback, and metrics somewhere queryable, write the four queries, schedule them, pipe the result through a narration step into email or chat. Teams with a warehouse and a data engineer do it in a week — and then discover the recurring cost is the joins, because the tracker, the feedback portal, and the analytics tool each hold a different copy of the truth that must be reconciled every single week.
That reconciliation is the actual product problem, and it’s why the memo is a built-in on AIOProductOS rather than a template: the spine already holds one joined record, so the four queries are trivial — every Monday at 06:30 UTC the memo writes itself. How we run on our own product documents the rest of our dogfooding; the live demo has a real memo you can read.
Either way: kill the meeting. The facts don’t need an hour of the whole team performing them.