A chief of staff's guide to tracking decisions across a fast-moving team

Why decision tracking falls to the chief of staff

A chief of staff sits across every team's decisions and owns none of the tools that record them. Sales decides pricing exceptions in a Slack DM, product decides scope in a planning meeting nobody minuted, and the exec team decides a policy change in a doc that never gets linked anywhere else. Nobody on any of those teams thinks documentation is their job, and technically none of it is. It becomes yours by default, because you are the one person expected to know the current state of everything without having been in the room for most of it.

The result is a specific, recurring failure: someone asks “didn't we already decide this?” in a meeting, everyone looks at the chief of staff, and the honest answer is often “I think so, let me check.” That gap is not a personal failing, it is what happens when decision debt accumulates across a company faster than any one person can track it from memory.

Run a weekly decision inventory, not a live dashboard

The instinct is to build a live dashboard that captures every decision the moment it happens. It fails for a structural reason: you are not in every meeting and every channel as the decision is made, so a dashboard that depends on real-time capture depends on other people remembering to feed it, which is the same compliance problem every voluntary decision log has.

The practical unit is a weekly inventory instead: a fixed thirty-minute pass, same time every week, across the channels, threads, and meeting notes where your company's decisions actually cluster. For each one you find: log the question, the decision, the owner, and the date. For each one you expected to find and did not, that is the more useful signal, since a decision that should have concluded and has not is exactly what an exec team needs flagged before it becomes a blocker nobody named out loud.

Chasing down the owner and the reasoning after the fact

Capturing after the fact has one real cost a live capture does not: the reasoning degrades fast. Ask someone why they made a call three weeks ago and you get the outcome and a shrug; ask the same day and you get the actual tradeoff, who disagreed, and what would change their mind. A weekly inventory is often three to seven days behind the decision, which is late enough to lose the reasoning but early enough to still recover it if you ask directly rather than wait for a retro that may never happen.

The question that gets a real answer is specific: “what made you land there, and did anyone push back?” not “what did you decide?”. The first surfaces the part of a decision record that actually gets consulted later, the reasoning and the dissent; the second just restates the outcome you could already see in the channel.

Catching relitigation before it happens

The chief of staff role has one genuine structural advantage in this problem: you are the one person with visibility across teams that otherwise never compare notes. That means you are often the first to notice when a question resurfacing in product this week is the same one operations settled two months ago under a different name. We wrote about why that keeps happening in why teams relitigate decisions, and the short version is that it is almost never bad faith, it is an unfindable record.

Catching it before the second debate eats a meeting requires the inventory to be searchable across teams, not filed per-team the way most Decisions channels and wiki pages end up. A cross-team archive is the difference between noticing the pattern in week two and noticing it a quarter later, after both teams have already spent real time re-arguing something that was already settled.

Where capture tooling actually helps this role

Disclosure: Withose is built partly for this exact problem, and Withose publishes this blog, so weigh this section accordingly.

The specific fit is structural, not just a feature list: the chief of staff is almost never the one making the decision, which means manual capture always means reconstructing something after the fact from a channel you were not part of. Tooling that drafts the record from the Slack or Teams conversation itself, at the moment someone captures it, removes that reconstruction step entirely, and it does not require the decision-maker to adopt a new habit beyond one mention or message action in a tool they are already using. The resulting archive is cross-team by default, searchable, and checks new decisions against old ones automatically, which is the relitigation-catching advantage above without you having to hold the whole company's decision history in your head.

You can see the flow on sample data with no account in the playground, or read the free decision log template if you want to run the manual version of the weekly inventory first and see how far it gets you before reaching for a tool.