[{"data":1,"prerenderedAt":194},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwhy-i-built-delivery-sheet":3,"blog-related-\u002Fblog\u002Fwhy-i-built-delivery-sheet":169,"blog-surround-\u002Fblog\u002Fwhy-i-built-delivery-sheet":193},{"id":4,"title":5,"audience":6,"body":10,"cluster":134,"conversionGoal":135,"cornerstone":136,"date":137,"description":138,"draft":136,"extension":139,"factCheckedAt":135,"faq":140,"featured":136,"language":135,"meta":150,"minRead":151,"navigation":152,"order":153,"originalAsset":135,"path":154,"pillar":155,"primaryKeyword":156,"publicationOrder":157,"relatedProject":158,"releaseScope":135,"reviewCycle":159,"reviewMethod":135,"reviewStatus":160,"reviewedAt":135,"reviewedBy":161,"searchIntent":162,"seo":163,"sources":135,"stem":164,"tags":165,"type":167,"updated":137,"__hash__":168},"blog\u002Fblog\u002Fwhy-i-built-delivery-sheet.md","Why I Built Delivery Sheet",[7,8,9],"engineering-manager","product-lead","indie-founder",{"type":11,"value":12,"toc":125},"minimark",[13,32,37,45,48,52,60,63,67,85,89,92,96,103,109,112],[14,15,16,20,21,26,27,31],"p",{},[17,18,19],"strong",{},"The standard advice is to nail down requirements before you commit to a date. Everyone nods at it; almost nobody does it."," I built ",[22,23,25],"a",{"href":24},"\u002Fproducts\u002Fdelivery-sheet","Delivery Sheet"," because I spent 18 years watching the exact failure that advice is meant to prevent: a vague leadership ask became a commitment before anyone knew the scope, the owner or the outcome — and the bill arrived weeks later as rework. At some point I stopped filing it under bad luck and started filing it under missing tool. Delivery Sheet is that tool — the one I wished existed on every programme: capture a raw ask and shape it into a decision-ready one-pager before you commit a single person. It's the clearest example of my ",[22,28,30],{"href":29},"\u002Fblog\u002Fmy-product-operating-system","operating system"," in action — a real, recurring problem I'd hit hundreds of times, turned into a focused product.",[33,34,36],"h2",{"id":35},"the-problem-i-kept-hitting","The problem I kept hitting",[14,38,39,40,44],{},"It always started the same way. A leader drops a one-line ask into a channel — \"can we add exposure reporting by entity?\" — and someone answers \"sure, we can do that.\" Three weeks later that nod has hardened into a commitment: a date living in someone's head, attached to a scope nobody wrote down, owned by no one in particular. Then the real cost arrives — ",[22,41,43],{"href":42},"\u002Fblog\u002F05-commit-before-clear","rework, a scope fight, a slipped date"," — and none of it traces cleanly back to the thirty seconds where the ask was never shaped.",[14,46,47],{},"I watched it play out on programme after programme. It isn't an execution problem; it's a shaping problem, and it happens before delivery even starts.",[33,49,51],{"id":50},"the-insight","The insight",[14,53,54,55,59],{},"The cheapest, highest-leverage moment in any piece of work is the one everyone skips: ",[22,56,58],{"href":57},"\u002Fblog\u002F06-slack-request-to-initiative","shaping the ask before committing to it",". A one-liner has to become a few clear things — problem, outcome, scope, owner, open questions — before a team can honestly commit or decline. That shaping takes minutes and saves weeks. It rarely happens, because in the moment it reads as friction, and there was never a tool that made it fast.",[14,61,62],{},"That gap — a five-minute shaping step that saves a six-week wrong build, with nothing to support it — is the whole product.",[33,64,66],{"id":65},"how-it-works","How it works",[14,68,69,70,74,75,79,80,84],{},"Delivery Sheet takes a raw request and drafts it into structured fields — ",[22,71,73],{"href":72},"\u002Fblog\u002Fproject-intake-process-for-finance-and-engineering-teams","problem, outcome, scope"," — and surfaces the gaps and open questions. Then it forces one of four honest decisions: ",[22,76,78],{"href":77},"\u002Fblog\u002Fwhy-delivery-sheet-has-four-decisions","commit, shape further, pause, or decline",". The output isn't \"it's on the backlog\"; it's a decision made with eyes open. The AI does the fast drafting; the human makes the call — the ",[22,81,83],{"href":82},"\u002Fblog\u002Fhow-i-use-ai-without-letting-ai-decide","line I hold on every product",".",[33,86,88],{"id":87},"why-its-a-product-not-a-template","Why it's a product, not a template",[14,90,91],{},"Anyone can build a form with those fields. What makes it a product is that it makes the shaping fast enough to actually do in the moment — the exact point where discipline usually loses to urgency. It turns \"we'll pick it up\" from a reflex into a genuine choice, and \"no\" from something that happens by neglect into something you decide on purpose. That's the difference between a checklist people ignore and a tool they reach for.",[33,93,95],{"id":94},"who-its-for-and-why-now","Who it's for, and why now",[14,97,98,99,102],{},"It's for ",[22,100,101],{"href":24},"engineering and product leaders"," — the people standing between a vague ask and a team's committed time. And it's a product now because AI finally makes the shaping instant. Drafting a decision-ready one-pager from a raw message used to be the friction that killed the discipline; take that friction out and shaping-before-committing becomes something you'll actually do.",[14,104,105,106,84],{},"I built Delivery Sheet because I was tired of watching good teams commit to sentences and find out what they meant in production. If that's your world too, ",[22,107,108],{"href":24},"that's what it's for",[110,111],"hr",{},[14,113,114],{},[115,116,117,118,121,122,84],"em",{},"See also ",[22,119,120],{"href":72},"the project intake process"," and ",[22,123,124],{"href":29},"my product operating system",{"title":126,"searchDepth":127,"depth":127,"links":128},"",2,[129,130,131,132,133],{"id":35,"depth":127,"text":36},{"id":50,"depth":127,"text":51},{"id":65,"depth":127,"text":66},{"id":87,"depth":127,"text":88},{"id":94,"depth":127,"text":95},"case-study",null,false,"2026-07-24","Why I built Delivery Sheet: on every programme, vague leadership asks became commitments before anyone knew scope, owner or outcome. Shape before you commit.","md",[141,144,147],{"question":142,"answer":143},"What problem does Delivery Sheet solve?","Delivery Sheet solves the failure that starts most delivery problems: a vague leadership ask becomes a commitment before anyone knows the scope, the owner or what success looks like. Teams dig requirements out of scattered messages and commit to a date before the work is actually understood, and the bill arrives weeks later as rework and scope fights. Delivery Sheet takes a raw request and shapes it into a decision-ready one-pager — problem, outcome, scope, owner, open questions — so you decide with eyes open before you commit people.",{"question":145,"answer":146},"Who is Delivery Sheet for?","Engineering and product leaders — the managers and directors who receive demands, shape them into work, and report upward. Anyone who regularly gets a one-line ask ('can we add X?') and has to turn it into something a team can actually commit to, or honestly decline, without losing weeks discovering what it meant. It's built for the person standing between a vague request and a team's committed time.",{"question":148,"answer":149},"How does Delivery Sheet work?","You capture a raw request — a Slack message, an email, a hallway ask — and it drafts that into structured fields: title, problem, outcome, scope. It surfaces the gaps and open questions, so instead of committing to a sentence you shape it into a decision-ready one-pager and then make one of four honest calls: commit, shape further, pause or decline. The point is to make the shaping fast and the decision explicit, so 'yes' is a choice rather than a reflex.",{},3,true,7,"\u002Fblog\u002Fwhy-i-built-delivery-sheet","building-ai-products","why I built Delivery Sheet",99,"delivery-sheet","annual","reviewed","Tan Gravam","informational",{"title":5,"description":138},"blog\u002Fwhy-i-built-delivery-sheet",[155,134,166],"product","text","yHXiyrQhkMTxZha6vDd-hk90MLUX0HdpESHM_56ebUA",{"related":170,"prev":182,"next":185,"hasOrder":152,"place":188},[171,175,178],{"path":172,"title":173,"description":174},"\u002Fblog\u002Fwhy-i-built-yollardayiz","Why I Built Yollardayız","Why I built Yollardayız: countless families drive Europe–Turkey each summer planning border crossings on Facebook hearsay. I built the live-data answer.",{"path":77,"title":176,"description":177},"Why Delivery Sheet Has Four Decisions, Not a Backlog","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.",{"path":179,"title":180,"description":181},"\u002Fblog\u002Fwhy-yollardayiz-shows-its-sources","Why Yollardayız Shows the Source of Every Number","Every wait time in Yollardayız is labeled — official feed or traveler report, with its age. Credibility is the moat when the competition is hearsay.",{"path":183,"title":184,"type":167,"language":135},"\u002Fblog\u002Fhow-i-handle-auth-and-user-data-solo","How I Handle Auth, Security and User Data as a Solo Builder",{"path":186,"title":187,"type":167,"language":135},"\u002Fblog\u002Fwhy-i-built-listemizde-without-sponsored-rankings","Why I Built Listemizde Without Sponsored Rankings",{"label":189,"position":190,"total":191,"hub":192},"Case Study",1,5,"\u002Ftopics\u002Fbuilding-ai-products",[],1787475407259]