[{"data":1,"prerenderedAt":159},["ShallowReactive",2],{"blog-\u002Fblog\u002F03-finance-team-friction":3,"blog-related-\u002Fblog\u002F03-finance-team-friction":135,"blog-surround-\u002Fblog\u002F03-finance-team-friction":158},{"id":4,"title":5,"audience":6,"body":7,"cluster":100,"conversionGoal":101,"cornerstone":102,"date":103,"description":104,"draft":102,"extension":105,"factCheckedAt":6,"faq":106,"featured":102,"language":6,"meta":116,"minRead":96,"navigation":117,"order":118,"originalAsset":6,"path":119,"pillar":120,"primaryKeyword":121,"publicationOrder":122,"relatedProject":6,"releaseScope":6,"reviewCycle":123,"reviewMethod":6,"reviewStatus":124,"reviewedAt":6,"reviewedBy":125,"searchIntent":126,"seo":127,"sources":6,"stem":128,"tags":129,"type":132,"updated":133,"__hash__":134},"blog\u002Fblog\u002F03-finance-team-friction.md","The friction tax on finance teams",null,{"type":8,"value":9,"toc":94},"minimark",[10,19,25,28,33,36,49,58,62,74,81],[11,12,13,14,18],"p",{},"Finance teams don't move slowly because the math is hard. They move slowly because every number has to be ",[15,16,17],"strong",{},"defended",".",[20,21,22],"pull-quote",{},[11,23,24],{},"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.",[11,26,27],{},"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.",[29,30,32],"h2",{"id":31},"where-the-time-really-goes","Where the time really goes",[11,34,35],{},"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:",[37,38,39,43,46],"ul",{},[40,41,42],"li",{},"finding the source of a figure someone else had produced",[40,44,45],{},"explaining variances to people who weren't in the original meeting",[40,47,48],{},"waiting for approvals that weren't blocked on anything except calendar availability",[11,50,51,52,57],{},"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 ",[53,54,56],"a",{"href":55},"\u002Fblog\u002F07-cost-of-unclear-ownership","unclear-ownership tax"," that sinks much bigger programmes.",[29,59,61],{"id":60},"what-actually-helps","What actually helps",[63,64,66],"callout",{"type":65},"tip",[11,67,68,69,73],{},"The highest-leverage tool a finance team can adopt is one that makes the ",[70,71,72],"em",{},"provenance"," of a number cheap to retrieve — not one that makes the number faster to compute.",[11,75,76,77,80],{},"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 ",[70,78,79],{},"reason"," for each entry, not just the entry itself.",[11,82,83,84,88,89,93],{},"Compute is solved. Context is the bottleneck. That's the thread running through everything I write on ",[53,85,87],{"href":86},"\u002Ftopics\u002Ffinance-systems-delivery","finance systems delivery",": the slow part is almost never the calculation — it's the ",[53,90,92],{"href":91},"\u002Fblog\u002Fproblem-statements-vs-solution-requests","request that was never shaped into a problem"," in the first place.",{"title":95,"searchDepth":96,"depth":96,"links":97},"",2,[98,99],{"id":31,"depth":96,"text":32},{"id":60,"depth":96,"text":61},"field-notes","intake-tool",false,"2026-05-13","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.","md",[107,110,113],{"question":108,"answer":109},"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.",{"question":111,"answer":112},"Where does the time go in a month-end close?","This is one observation, not a benchmark: in a single month-end close I 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.",{"question":114,"answer":115},"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.",{},true,11,"\u002Fblog\u002F03-finance-team-friction","finance-systems-delivery","finance team friction",3,"annual","reviewed","Tan Gravam","informational",{"title":5,"description":104},"blog\u002F03-finance-team-friction",[130,131],"finance-systems","process","text","2026-07-29","NU85V4DfiIZKPBMdA3_fl1MzxES9M4D8UXBC4_niROk",{"related":136,"prev":148,"next":151,"hasOrder":117,"place":154},[137,141,144],{"path":138,"title":139,"description":140},"\u002Fblog\u002F06-slack-request-to-initiative","Turning a Slack request into a decision-ready initiative","How to take a one-line ask and shape it into something a team can commit to (or decline) in a few minutes, not a few meetings.",{"path":55,"title":142,"description":143},"The cost of unclear ownership in enterprise delivery","When no one owns the outcome, delivery slips in the seams — invisibly on every status report, until it's too late to fix cheaply.",{"path":145,"title":146,"description":147},"\u002Fblog\u002Fraid-log-risks-assumptions-issues-dependencies","RAID Logs: Risks, Assumptions, Issues and Dependencies","A RAID log tracks a programme's risks, assumptions, issues and dependencies — and works only when you actually mitigate and chase them, not file them.",{"path":149,"title":150,"type":132,"language":6},"\u002Fblog\u002Fgovernance-and-steering-for-finance-programmes","Governance and Steering for Finance Programmes",{"path":152,"title":153,"type":132,"language":6},"\u002Fblog\u002F05-commit-before-clear","Why teams commit before the request is clear",{"label":155,"position":156,"total":157,"hub":86},"Field Notes",1,4,[],1787475400139]