[{"data":1,"prerenderedAt":134},["ShallowReactive",2],{"blog-\u002Fblog\u002F07-cost-of-unclear-ownership":3,"blog-surround-\u002Fblog\u002F07-cost-of-unclear-ownership":114,"blog-related-\u002Fblog\u002F07-cost-of-unclear-ownership":123},{"id":4,"title":5,"audience":6,"body":7,"cluster":6,"date":83,"description":84,"draft":85,"extension":86,"factCheckedAt":6,"faq":87,"featured":85,"language":6,"meta":97,"navigation":98,"order":6,"originalAsset":6,"path":99,"pillar":100,"primaryKeyword":101,"relatedProject":102,"releaseScope":6,"reviewCycle":103,"reviewStatus":104,"reviewedBy":105,"searchIntent":6,"seo":106,"sources":6,"stem":107,"tags":108,"type":112,"updated":6,"__hash__":113},"blog\u002Fblog\u002F07-cost-of-unclear-ownership.md","The cost of unclear ownership in enterprise delivery",null,{"type":8,"value":9,"toc":76},"minimark",[10,23,28,31,39,45,49,52,56,62,69],[11,12,13,14,18,19,22],"p",{},"In a large finance transformation, everyone owns a ",[15,16,17],"strong",{},"task"," and no one owns the ",[15,20,21],{},"outcome",". That gap is where projects quietly go wrong.",[24,25,27],"h2",{"id":26},"tasks-are-owned-outcomes-are-orphaned","Tasks are owned. Outcomes are orphaned.",[11,29,30],{},"Ask who owns a task and you get a name instantly: \"Ayşe owns the interface build.\" Ask who owns the outcome — \"month-end close is a day faster\" — and you get a pause, then a committee. A RACI chart with three people accountable for one line is a chart with none.",[11,32,33,34,38],{},"Task ownership ",[35,36,37],"em",{},"feels"," like accountability. It isn't. You can complete every task on the plan and still miss the outcome, because the failures live in the gaps between tasks: the integration nobody scoped, the edge case in intercompany elimination, the assumption two teams each thought the other owned.",[40,41,42],"pull-quote",{},[11,43,44],{},"You can finish every task on the plan and still miss the outcome — because the outcome was never on the plan.",[24,46,48],{"id":47},"the-slip-is-invisible-until-its-red","The slip is invisible until it's red",[11,50,51],{},"This is what makes unclear ownership so expensive: it stays green until it's red. Every task tracks to plan. Every team reports \"on track.\" The outcome slips anyway, in the seams, and no single status line ever turned amber to warn you. The first real signal is a stakeholder at UAT saying \"this isn't what we needed\" — long after the cheap moment to fix it has passed.",[24,53,55],{"id":54},"name-the-outcome-owner-before-the-work","Name the outcome owner before the work",[11,57,58,59,61],{},"The fix is unglamorous: for every initiative, name one person accountable for the ",[15,60,21],{}," — not the task list — before anything is committed. Not a function, not a committee. A person. Their job isn't to do all the work; it's to own the seams, the open questions, and the definition of done.",[11,63,64,65,68],{},"Make that name explicit at intake and two things happen. Genuinely unowned work gets exposed ",[35,66,67],{},"before"," it's staffed. And the owned work gets someone whose job is to notice the slip while it's still small.",[70,71,73],"callout",{"type":72},"info",[11,74,75],{},"The most expensive words in enterprise delivery are \"I thought your team had that.\" You prevent them for free, at the start, by asking one question: who owns this outcome?",{"title":77,"searchDepth":78,"depth":78,"links":79},"",2,[80,81,82],{"id":26,"depth":78,"text":27},{"id":47,"depth":78,"text":48},{"id":54,"depth":78,"text":55},"2026-06-18","When no one owns the outcome, delivery slips in the seams — invisibly on every status report, until it's too late to fix cheaply.",false,"md",[88,91,94],{"question":89,"answer":90},"Why is unclear ownership so expensive in enterprise delivery?","Because it stays green until it's red. Every task tracks to plan and every team reports 'on track,' but the outcome slips in the seams between tasks — the integration nobody scoped, the edge case in intercompany elimination, the assumption two teams each thought the other owned. No status line ever turns amber to warn you, and the first real signal comes at UAT, long after the cheap moment to fix it has passed.",{"question":92,"answer":93},"What's the difference between owning a task and owning an outcome?","Ask who owns a task and you get a name instantly; ask who owns the outcome and you get a pause, then a committee. Task ownership feels like accountability but isn't — you can complete every task on the plan and still miss the outcome, because the failures live in the gaps between tasks, and a RACI chart with three people accountable for one line is a chart with none.",{"question":95,"answer":96},"How do you fix unclear ownership?","For every initiative, name one person accountable for the outcome — not the task list — before anything is committed. Not a function, not a committee, a person. Their job isn't to do all the work; it's to own the seams, the open questions, and the definition of done. Naming it at intake also exposes genuinely unowned work before it's staffed.",{},true,"\u002Fblog\u002F07-cost-of-unclear-ownership","finance-systems-delivery","cost of unclear ownership","delivery-sheet","annual","reviewed","Tan Gravam",{"title":5,"description":84},"blog\u002F07-cost-of-unclear-ownership",[109,110,111],"delivery","ownership","enterprise","text","yOmHWnD_pyg9Jri3G5ath_AedXlGOp5IorIYYBxpqiE",[115,119],{"title":116,"path":117,"stem":118,"type":112,"language":6,"draft":85,"children":-1},"Turning a Slack request into a decision-ready initiative","\u002Fblog\u002F06-slack-request-to-initiative","blog\u002F06-slack-request-to-initiative",{"title":120,"path":121,"stem":122,"type":112,"language":6,"draft":85,"children":-1},"The 13-Week Cash Flow Forecast: A Practical Guide","\u002Fblog\u002F13-week-cash-flow-forecast","blog\u002F13-week-cash-flow-forecast",[124,128,132],{"path":125,"title":126,"description":127},"\u002Fblog\u002F03-finance-team-friction","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.",{"path":129,"title":130,"description":131},"\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":117,"title":116,"description":133},"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.",1785182339101]