[{"data":1,"prerenderedAt":142},["ShallowReactive",2],{"blog-\u002Fblog\u002F05-commit-before-clear":3,"blog-surround-\u002Fblog\u002F05-commit-before-clear":121,"blog-related-\u002Fblog\u002F05-commit-before-clear":131},{"id":4,"title":5,"audience":6,"body":7,"cluster":6,"date":90,"description":91,"draft":92,"extension":93,"factCheckedAt":6,"faq":94,"featured":92,"language":6,"meta":104,"navigation":105,"order":6,"originalAsset":6,"path":106,"pillar":107,"primaryKeyword":108,"relatedProject":109,"releaseScope":6,"reviewCycle":110,"reviewStatus":111,"reviewedBy":112,"searchIntent":6,"seo":113,"sources":6,"stem":114,"tags":115,"type":119,"updated":6,"__hash__":120},"blog\u002Fblog\u002F05-commit-before-clear.md","Why teams commit before the request is clear",null,{"type":8,"value":9,"toc":82},"minimark",[10,14,17,23,28,36,39,43,46,54,58,61,65,72,79],[11,12,13],"p",{},"Most delivery problems don't start in delivery. They start in the thirty seconds after a request lands — when someone says \"sure, we can do that\" before anyone knows what \"that\" is.",[11,15,16],{},"It isn't carelessness. It's structure.",[18,19,20],"pull-quote",{},[11,21,22],{},"A vague request doesn't get clearer while it waits. It gets committed to.",[24,25,27],"h2",{"id":26},"saying-yes-is-the-cheap-answer","Saying yes is the cheap answer",[11,29,30,31,35],{},"When a leader drops an ask into a channel, the socially cheap response is agreement. \"We'll pick it up.\" \"Should be doable.\" Asking the real questions — what problem is this solving, who owns the outcome, what does done look like — reads as friction, or as not being a team player. So the ask gets a nod. And a nod, three weeks later, is remembered as a ",[32,33,34],"strong",{},"commitment",".",[11,37,38],{},"By then the date is already in someone's head, and nobody wrote down the scope it was attached to.",[24,40,42],{"id":41},"nobody-owns-the-request-yet","Nobody owns the request yet",[11,44,45],{},"Early on, a request belongs to no one. The person who sent it assumes it's understood. The people who received it assume someone else will shape it. In that gap, no one is accountable for turning a sentence into a scope — so it stays a sentence, and the team builds against its best guess.",[11,47,48,49,53],{},"I've watched \"can we add a revaluation report?\" turn into a three-month argument, because ",[50,51,52],"em",{},"revaluation"," meant month-end FX to finance and intercompany netting to the team that built it. Nobody caught it early, because catching it was nobody's job.",[24,55,57],{"id":56},"the-bill-arrives-late-in-disguise","The bill arrives late, in disguise",[11,59,60],{},"The cost of an unclear commitment surfaces weeks later as something else: rework, a scope fight, a slipped date, a stakeholder who \"didn't ask for this.\" None of it traces cleanly back to that first thirty seconds — so the pattern survives to the next request, and the one after that.",[24,62,64],{"id":63},"the-fix-isnt-a-heavier-process","The fix isn't a heavier process",[11,66,67,68,71],{},"You don't need a thirty-field intake form. You need to make shaping ",[32,69,70],{},"fast and visible",": capture the raw ask and force four questions to the surface before anyone commits — what problem, whose outcome, what's in scope, how we'll know it worked.",[73,74,76],"callout",{"type":75},"info",[11,77,78],{},"If those four can't be answered yet, that isn't a delay. It's the most useful thing you learned all week.",[11,80,81],{},"Commit to clarity first. The delivery date can wait thirty more seconds.",{"title":83,"searchDepth":84,"depth":84,"links":85},"",2,[86,87,88,89],{"id":26,"depth":84,"text":27},{"id":41,"depth":84,"text":42},{"id":56,"depth":84,"text":57},{"id":63,"depth":84,"text":64},"2026-05-20","The pressure that turns a one-line ask into a commitment before anyone knows the scope — and the bill that shows up weeks later.",false,"md",[95,98,101],{"question":96,"answer":97},"Why do teams commit to work before the request is clear?","It's structure, not carelessness. When a leader drops an ask into a channel, the socially cheap response is agreement — asking what problem it solves or what done looks like reads as friction or as not being a team player. So the ask gets a nod, and weeks later that nod is remembered as a commitment, with a date in someone's head but no written scope.",{"question":99,"answer":100},"Why is unclear scope so hard to trace back?","The cost of an unclear commitment surfaces weeks later disguised as something else: rework, a scope fight, a slipped date, or a stakeholder who 'didn't ask for this.' None of it traces cleanly back to the first thirty seconds after the request landed — so the pattern survives to the next request, and the one after that.",{"question":102,"answer":103},"How do you stop committing to vague requests?","Not with a heavier process or a thirty-field intake form. Make shaping fast and visible: capture the raw ask and force four questions to the surface before anyone commits — what problem, whose outcome, what's in scope, and how you'll know it worked. If those four can't be answered yet, that isn't a delay; it's the most useful thing you learned all week.",{},true,"\u002Fblog\u002F05-commit-before-clear","finance-systems-delivery","committing before the request is clear","delivery-sheet","annual","reviewed","Tan Gravam",{"title":5,"description":91},"blog\u002F05-commit-before-clear",[116,117,118],"delivery","leadership","product","text","SPagKKzJNbsMRkepvme4oDZABbGrfZqIBehtYSNjwxw",[122,127],{"title":123,"path":124,"stem":125,"type":126,"language":6,"draft":92,"children":-1},"Confirm-before-destroy without the modal","\u002Fblog\u002F04-confirm-before-destroy","blog\u002F04-confirm-before-destroy","pattern",{"title":128,"path":129,"stem":130,"type":119,"language":6,"draft":92,"children":-1},"Turning a Slack request into a decision-ready initiative","\u002Fblog\u002F06-slack-request-to-initiative","blog\u002F06-slack-request-to-initiative",[132,136,138],{"path":133,"title":134,"description":135},"\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":128,"description":137},"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":139,"title":140,"description":141},"\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]