The friction tax on finance teams
Finance teams move slowly not because the math is hard, but because every number has to be defended. The real bottleneck is provenance, not compute.
Field Notes 1 of 4 see the reading order →
Reviewed by Tan Gravam
On this page
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 one month-end close I tracked hour by hour, well under a fifth of the team's time went to actually computing numbers. The bulk went to everything around the numbers:
- finding the source of a figure someone else had produced
- explaining variances to people who weren't in the original meeting
- waiting for approvals that weren't blocked on anything except calendar availability
One close, one team — but I've sat through enough of them to say the shape holds: the calculation is the small slice, and the defence of the calculation is the meal. 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, the same unclear-ownership tax that sinks much bigger programmes.
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. That's the thread running through everything I write on finance systems delivery: the slow part is almost never the calculation — it's the request that was never shaped into a problem in the first place.
Frequently asked questions
3
Why does finance work feel so slow?
Not because the math is hard. The actual compute — summing transactions, reconciling balances, posting accruals — is mechanical. Teams slow down because every number has to be defended: finding its source, explaining variances to people who weren't in the original meeting, and waiting on approvals all take far more time than the calculation itself.
Where does the time go in a month-end close?
In one month-end close the author tracked hour by hour, well under a fifth of the team's time went to computing numbers. The bulk went to finding the source of figures, explaining variances, and waiting for calendar-bound approvals. Most tools optimize only the computing slice and treat the rest as 'process' that nobody owns or measures.
What actually speeds up a finance team?
A tool that makes the provenance of a number cheap to retrieve, not one that makes the number faster to compute. Think a spreadsheet that links cells back to the source query, a dashboard that shows which run and filters produced a figure, or a close checklist that records the reason for each entry. Compute is solved; context is the bottleneck.