The friction tax on finance teams
Why finance work feels heavy even when the numbers are simple.
Finance teams don't move slowly because the math is hard. They move slowly because every number has to be defended.
A finance team's velocity is set by how quickly they can answer "where did this come from?", not by how quickly they can compute the number itself.
The actual work — summing transactions, reconciling balances, posting accruals — is mechanical. What takes the time is the layer underneath: the audit trail, the source-of-truth lookup, the explanation for why this period looks different from last.
Where the time really goes
In a typical month-end close, I've watched teams spend their hours like this:
- 15% computing numbers
- 35% finding the source of those numbers
- 30% explaining variances to people who weren't in the original meeting
- 20% waiting for approvals that aren't blocked on anything except calendar availability
The compute step is the only part most tools optimize for. The rest is treated as "process" — meaning nobody owns it and nobody measures it.
What actually helps
A spreadsheet that links cells back to the source query. A dashboard that shows which run, on which date, with which filters. A close checklist that includes the reason for each entry, not just the entry itself.
Compute is solved. Context is the bottleneck.