[{"data":1,"prerenderedAt":154},["ShallowReactive",2],{"blog-\u002Fblog\u002F03-finance-team-friction":3,"blog-surround-\u002Fblog\u002F03-finance-team-friction":129,"blog-related-\u002Fblog\u002F03-finance-team-friction":141},{"id":4,"title":5,"audience":6,"body":7,"cluster":6,"date":99,"description":100,"draft":101,"extension":102,"factCheckedAt":6,"faq":103,"featured":101,"language":6,"meta":113,"navigation":114,"order":6,"originalAsset":6,"path":115,"pillar":116,"primaryKeyword":117,"relatedProject":6,"releaseScope":6,"reviewCycle":118,"reviewStatus":119,"reviewedBy":120,"searchIntent":6,"seo":121,"sources":6,"stem":122,"tags":123,"type":127,"updated":6,"__hash__":128},"blog\u002Fblog\u002F03-finance-team-friction.md","The friction tax on finance teams",null,{"type":8,"value":9,"toc":93},"minimark",[10,19,25,28,33,36,64,67,71,83,90],[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 a typical month-end close, I've watched teams spend their hours like this:",[37,38,39,46,52,58],"ul",{},[40,41,42,45],"li",{},[15,43,44],{},"15%"," computing numbers",[40,47,48,51],{},[15,49,50],{},"35%"," finding the source of those numbers",[40,53,54,57],{},[15,55,56],{},"30%"," explaining variances to people who weren't in the original meeting",[40,59,60,63],{},[15,61,62],{},"20%"," waiting for approvals that aren't blocked on anything except calendar availability",[11,65,66],{},"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.",[29,68,70],{"id":69},"what-actually-helps","What actually helps",[72,73,75],"callout",{"type":74},"tip",[11,76,77,78,82],{},"The highest-leverage tool a finance team can adopt is one that makes the ",[79,80,81],"em",{},"provenance"," of a number cheap to retrieve — not one that makes the number faster to compute.",[11,84,85,86,89],{},"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 ",[79,87,88],{},"reason"," for each entry, not just the entry itself.",[11,91,92],{},"Compute is solved. Context is the bottleneck.",{"title":94,"searchDepth":95,"depth":95,"links":96},"",2,[97,98],{"id":31,"depth":95,"text":32},{"id":69,"depth":95,"text":70},"2026-05-08","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.",false,"md",[104,107,110],{"question":105,"answer":106},"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":108,"answer":109},"Where does the time go in a month-end close?","In one team's close, only about 15% went to computing numbers. The rest went to finding the source of those numbers (35%), explaining variances (30%), and waiting for calendar-bound approvals (20%). Most tools optimize only the 15% and treat the rest as 'process' that nobody owns or measures.",{"question":111,"answer":112},"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,"\u002Fblog\u002F03-finance-team-friction","finance-systems-delivery","finance team friction","annual","reviewed","Tan Gravam",{"title":5,"description":100},"blog\u002F03-finance-team-friction",[124,125,126],"finance","workflow","observation","text","r0Jf6N8shL8v2UdgpYTKbj88X06CuFKhXFAzRFX_l8o",[130,136],{"title":131,"path":132,"stem":133,"type":134,"language":135,"draft":101,"children":-1},"Joining BKPF and BSEG without losing your mind","\u002Fblog\u002F02-bkpf-bseg-join","blog\u002F02-bkpf-bseg-join","code","sql",{"title":137,"path":138,"stem":139,"type":140,"language":6,"draft":101,"children":-1},"Confirm-before-destroy without the modal","\u002Fblog\u002F04-confirm-before-destroy","blog\u002F04-confirm-before-destroy","pattern",[142,146,150],{"path":143,"title":144,"description":145},"\u002Fblog\u002F05-commit-before-clear","Why teams commit before the request is clear","The pressure that turns a one-line ask into a commitment before anyone knows the scope — and the bill that shows up weeks later.",{"path":147,"title":148,"description":149},"\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":151,"title":152,"description":153},"\u002Fblog\u002F07-cost-of-unclear-ownership","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.",1785182339101]