[{"data":1,"prerenderedAt":201},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions":3,"blog-surround-\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions":180,"blog-related-\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions":189},{"id":4,"title":5,"audience":6,"body":10,"cluster":146,"date":147,"description":148,"draft":149,"extension":150,"factCheckedAt":151,"faq":152,"featured":149,"language":151,"meta":162,"navigation":163,"order":164,"originalAsset":151,"path":165,"pillar":166,"primaryKeyword":167,"relatedProject":168,"releaseScope":151,"reviewCycle":169,"reviewStatus":170,"reviewedBy":171,"searchIntent":172,"seo":173,"sources":151,"stem":174,"tags":175,"type":178,"updated":147,"__hash__":179},"blog\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions.md","Why Delivery Sheet Has Four Decisions: Commit, Shape, Pause or Decline",[7,8,9],"engineering-manager","product-lead","indie-founder",{"type":11,"value":12,"toc":138},"minimark",[13,27,32,40,43,47,50,78,84,88,91,95,103,110,113],[14,15,16,26],"p",{},[17,18,19,20,25],"strong",{},"Ask most teams what they say to an incoming request and the honest answer is one word: yes. ",[21,22,24],"a",{"href":23},"\u002Fproducts\u002Fdelivery-sheet","Delivery Sheet"," refuses to let you stop there — every ask gets one of four answers, commit, shape further, pause, or decline — because \"yes by default, no by neglect\" is what quietly sinks delivery."," This is a product decision, not a feature list, and it's worth explaining, because those four choices are the whole philosophy of the product in one design move: replace the reflexive yes with a decision someone actually made. Everything else Delivery Sheet does exists to make those four honest and fast.",[28,29,31],"h2",{"id":30},"the-problem-with-one-answer","The problem with one answer",[14,33,34,35,39],{},"Watch how requests actually get handled. A leader asks; someone says \"sure, we can do that,\" or \"I'll add it to the backlog.\" Both are yes — one now, one deferred. There's no real mechanism for the other answers, so they never happen: nothing gets deliberately shaped, paused, or declined. The backlog swells with everything, because ",[21,36,38],{"href":37},"\u002Fblog\u002Fproject-intake-process-for-finance-and-engineering-teams","nothing was ever actually said no to",". The \"no\" turns up months later, by neglect, when the un-started work has quietly rotted — which is the most expensive moment to say it.",[14,41,42],{},"A one-answer system isn't a decision process. It's a queue that chose you.",[28,44,46],{"id":45},"the-four-honest-decisions","The four honest decisions",[14,48,49],{},"So Delivery Sheet makes you pick one, on purpose:",[51,52,53,60,66,72],"ul",{},[54,55,56,59],"li",{},[17,57,58],{},"Commit"," — it's clear, owned, and worth doing now. Commit with real scope and a real date.",[54,61,62,65],{},[17,63,64],{},"Shape further"," — it matters, but it isn't ready; some open question is big enough to change the plan.",[54,67,68,71],{},[17,69,70],{},"Pause"," — a good idea at the wrong time; park it honestly, with a date to revisit.",[54,73,74,77],{},[17,75,76],{},"Decline"," — the problem isn't real, isn't worth the cost, or belongs to someone else. Say no early, and say why.",[79,80,81],"pull-quote",{},[14,82,83],{},"The discipline isn't in the four options — anyone can list four words. It's in being made to choose one out loud, instead of defaulting to yes and finding out the cost in delivery.",[28,85,87],{"id":86},"why-four-and-not-fewer","Why four, and not fewer",[14,89,90],{},"Fewer than four and you lose an honest outcome. Drop \"shape\" and every not-yet-ready ask becomes a premature commit or a flat no. Drop \"pause\" and good-but-mistimed ideas get killed or shipped anyway. Drop \"decline\" and you're straight back to yes-by-default. Each of the four earns its place because a real, distinct thing happens to incoming work — and a tool that can't express one of them nudges the team back toward the reflex. Four is the smallest set that covers how work actually gets decided.",[28,92,94],{"id":93},"the-product-decision-behind-it","The product decision behind it",[14,96,97,98,102],{},"This is a plain example of ",[21,99,101],{"href":100},"\u002Fblog\u002Fhow-i-use-ai-without-letting-ai-decide","making the product decision yourself"," instead of defaulting to the obvious build. The obvious build is a nicer backlog — capture the requests, sort them, prioritise them. But a nicer backlog is still a yes-machine; it just arranges the yeses more tidily. What makes Delivery Sheet a product and not a tidier list is the recognition that the missing thing was never organisation — it was the decision. So the four decisions aren't a feature bolted on the side; they're the point the whole product is built around.",[14,104,105,106,109],{},"If your team commits to sentences and learns what they meant in production, the fix isn't a better backlog — it's ",[21,107,108],{"href":23},"four honest decisions, made on purpose",".",[111,112],"hr",{},[14,114,115],{},[116,117,118,119,123,124,128,129,132,133,137],"em",{},"Part of ",[21,120,122],{"href":121},"\u002Ftopics\u002Fbuilding-ai-products","Building AI Products",". See also ",[21,125,127],{"href":126},"\u002Fblog\u002Fwhy-i-built-delivery-sheet","why I built Delivery Sheet"," and ",[21,130,131],{"href":37},"the project intake process",". The ",[21,134,136],{"href":135},"\u002Fnewsletter","newsletter"," sends one practical build lesson every two weeks.",{"title":139,"searchDepth":140,"depth":140,"links":141},"",2,[142,143,144,145],{"id":30,"depth":140,"text":31},{"id":45,"depth":140,"text":46},{"id":86,"depth":140,"text":87},{"id":93,"depth":140,"text":94},"case-study","2026-07-24","Most teams answer every ask with yes. Delivery Sheet forces one of four decisions — commit, shape, pause or decline — because 'yes by default' sinks delivery.",false,"md",null,[153,156,159],{"question":154,"answer":155},"What are the four decisions in Delivery Sheet?","Commit, shape further, pause, and decline. When a request comes in, instead of the default 'sure, we can do that', Delivery Sheet forces an explicit choice: commit (it's clear, owned and worth doing now), shape further (it matters but isn't ready to commit to), pause (a good idea at the wrong time, parked with a revisit date), or decline (the problem isn't real or worth the cost — say no early, with a reason). The point is that every ask gets a deliberate decision instead of a reflexive yes.",{"question":157,"answer":158},"Why force four decisions instead of just a backlog?","Because 'add it to the backlog' is really 'yes, eventually' — a soft yes that avoids the honest decision. A backlog fills with everything because nothing was ever actually declined; 'no' happens by neglect months later instead of on purpose now. Forcing one of four explicit decisions makes the team choose deliberately: commit with real scope, shape what's not ready, park what's mistimed, or decline what shouldn't be built. It turns a queue that chose you into a roadmap you chose.",{"question":160,"answer":161},"How does this help teams deliver better?","It moves the decision to the cheapest moment — before commitment — and makes it explicit. Most delivery pain comes from committing to vague asks by reflex and discovering the cost later. Four honest decisions force clarity up front: is this clear, owned and worth doing now, or not? Saying 'shape further', 'pause' or 'decline' out loud, early, prevents the rework, scope fights and slipped dates that come from a backlog full of un-decided work.",{},true,11,"\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions","building-ai-products","Delivery Sheet four decisions","delivery-sheet","annual","reviewed","Tan Gravam","informational",{"title":5,"description":148},"blog\u002Fwhy-delivery-sheet-has-four-decisions",[166,168,146,176,177],"product","decisions","text","J_sbscRXWK-UPrfmuGRbLiz9LBYHK49cCSl8CcdK9kk",[181,185],{"title":182,"path":183,"stem":184,"type":178,"language":151,"draft":149,"children":-1},"When Does a Company Need a Treasury Management System?","\u002Fblog\u002Fwhen-do-you-need-a-treasury-management-system","blog\u002Fwhen-do-you-need-a-treasury-management-system",{"title":186,"path":187,"stem":188,"type":178,"language":151,"draft":149,"children":-1},"Why I Build in Public","\u002Fblog\u002Fwhy-i-build-in-public","blog\u002Fwhy-i-build-in-public",[190,193,197],{"path":126,"title":191,"description":192},"Why I Built Delivery Sheet","Why I built Delivery Sheet: on every programme, vague leadership asks became commitments before anyone knew scope, owner or outcome. Shape before you commit.",{"path":194,"title":195,"description":196},"\u002Fblog\u002Fwhy-i-built-listemizde-without-sponsored-rankings","Why I Built Listemizde Without Sponsored Rankings","Why I built Listemizde: local-business platforms are corrupted by paid rankings. It ranks by real community trust — one person, one vote, no sponsors.",{"path":198,"title":199,"description":200},"\u002Fblog\u002Fmy-product-operating-system","My Product Operating System for Building Multiple AI Apps","The product operating system I use to build several focused AI products solo: choosing which problem to build, shipping fast, and killing what isn't working.",1785182343479]