02 COO · The commitment tracker build
Longest overdue first, with the owner on every line.
Things get decided in meetings and quietly die. Nobody tracks decision-to-done, so the same commitments get remade, the same issues get carried, and the COO becomes the company's system of record by default.
Built on the brain: it extracts commitments from meeting transcripts on its own, watches for follow-through, nags the owner (not the room), and reports the completion rate weekly. The accountability layer EOS assumes but doesn't enforce.
Commitments come out of transcripts automatically. Nobody files anything, so nothing depends on discipline surviving a busy week.
Decision-to-done, with the age on every line. Longest overdue first: the reference calls at 20 days, the revised SOW at 18. Each one carries its owner.
The band nobody else can produce: things decided out loud that entered no system at all. “Someone needs to own the onboarding doc rewrite.” Talk to: nobody. That is the finding.
One number lands weekly, and it is a failure rate, not a completion rate. “71% completed” is a report; “29% did not happen” is a finding. It was 46% at install.
In: Fireflies or Granola transcripts, ClickUp. Out: nags to owners in Slack, tasks created for the orphans, and the weekly completion rate on the scorecard.
Only possible because the brain is underneath it. Point this at a junk drawer and you've automated confusion.
Fifteen minutes, three sizing questions, an honest answer.