[{"data":1,"prerenderedAt":201},["ShallowReactive",2],{"blog-\u002Fblog\u002F06-slack-request-to-initiative":3,"blog-related-\u002Fblog\u002F06-slack-request-to-initiative":177,"blog-surround-\u002Fblog\u002F06-slack-request-to-initiative":200},{"id":4,"title":5,"audience":6,"body":7,"cluster":140,"conversionGoal":141,"cornerstone":142,"date":143,"description":144,"draft":142,"extension":145,"factCheckedAt":6,"faq":146,"featured":142,"language":6,"meta":156,"minRead":135,"navigation":157,"order":158,"originalAsset":6,"path":159,"pillar":160,"primaryKeyword":161,"publicationOrder":162,"relatedProject":163,"releaseScope":6,"reviewCycle":164,"reviewMethod":6,"reviewStatus":165,"reviewedAt":6,"reviewedBy":166,"searchIntent":167,"seo":168,"sources":6,"stem":169,"tags":170,"type":174,"updated":175,"__hash__":176},"blog\u002Fblog\u002F06-slack-request-to-initiative.md","Turning a Slack request into a decision-ready initiative",null,{"type":8,"value":9,"toc":133},"minimark",[10,14,20,28,36,41,44,89,93,100,111,115],[11,12,13],"p",{},"Here's a real shape of request, lightly disguised:",[15,16,17],"blockquote",{},[11,18,19],{},"can we add a report that shows treasury exposure by entity? finance keeps asking",[11,21,22,23,27],{},"That's the whole thing. It ",[24,25,26],"em",{},"feels"," actionable: there's a noun (\"report\"), a subject (\"exposure by entity\"), a hint of urgency (\"keeps asking\"). So a team picks it up and starts building a report. Six weeks later it's the wrong report.",[11,29,30,31,35],{},"The problem isn't the request. It's that a one-liner has to be ",[32,33,34],"strong",{},"shaped"," before it can be committed to, and most teams skip straight to building.",[37,38,40],"h2",{"id":39},"five-fields-make-an-ask-decision-ready","Five fields make an ask decision-ready",[11,42,43],{},"You don't need thirty fields. You need five, and you need to actually fill them:",[45,46,47,65,71,77,83],"ol",{},[48,49,50,53,54,59,60,64],"li",{},[32,51,52],{},"Problem:"," what's broken today? \"Treasury rebuilds exposure by hand in Excel every month-end and it's error-prone\": the ",[55,56,58],"a",{"href":57},"\u002Fblog\u002F03-finance-team-friction","friction tax finance teams quietly pay",". Not \"we need a report\"; that's the difference between a ",[55,61,63],{"href":62},"\u002Fblog\u002Fproblem-statements-vs-solution-requests","problem statement and a solution request",".",[48,66,67,70],{},[32,68,69],{},"Outcome:"," what's true when this is done? \"Treasury sees exposure by entity without touching a spreadsheet.\" Now you can tell when you've succeeded.",[48,72,73,76],{},[32,74,75],{},"Owner:"," whose outcome is this? One name. If it's \"finance,\" it's no one.",[48,78,79,82],{},[32,80,81],{},"Scope:"," what's explicitly in, and just as importantly, out. \"By entity, yes. By counterparty, later. Real-time, no.\"",[48,84,85,88],{},[32,86,87],{},"Open questions:"," the things you don't know yet. This field is the point. A request with no open questions usually means you haven't looked hard enough.",[37,90,92],{"id":91},"fill-them-with-the-person-who-asked","Fill them with the person who asked",[11,94,95,96,99],{},"The leverage isn't in the fields; it's in filling them ",[32,97,98],{},"out loud, with the requester, before committing",". Half the time the exercise changes the request: \"oh, they don't need a report, they need the month-end exposure number to stop being wrong.\" The other half it surfaces an open question big enough to change the plan, the kind that's cheap to answer now and expensive to discover in UAT.",[101,102,104],"callout",{"type":103},"info",[11,105,106,107,110],{},"Shaping isn't overhead you add before the work. It ",[24,108,109],{},"is"," the work — the cheapest, highest-leverage part of it.",[37,112,114],{"id":113},"then-decide-on-purpose","Then decide, on purpose",[11,116,117,118,122,123,127,128,132],{},"Once the five fields exist, the decision is easy and honest: commit it, shape it further, park it, or say no. What you never do again is commit to a sentence and find out what it meant in production. This shaping step is the heart of a proper ",[55,119,121],{"href":120},"\u002Fblog\u002Fproject-intake-process-for-finance-and-engineering-teams","intake process",", and the habit that fixes more of ",[55,124,126],{"href":125},"\u002Ftopics\u002Ffinance-systems-delivery","finance systems delivery"," than any methodology I've used. If you want the five fields on one page as you go, the free ",[55,129,131],{"href":130},"\u002Ftools\u002Fproject-intake-one-pager","intake one-pager generator"," builds it as you type — nothing you enter leaves your browser.",{"title":134,"searchDepth":135,"depth":135,"links":136},"",2,[137,138,139],{"id":39,"depth":135,"text":40},{"id":91,"depth":135,"text":92},{"id":113,"depth":135,"text":114},"field-notes","intake-tool",false,"2026-06-03","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.","md",[147,150,153],{"question":148,"answer":149},"How do you turn a Slack request into a decision-ready initiative?","Shape the one-liner into five fields before committing: the problem, the outcome, the owner, the scope (what's explicitly in and out), and the open questions. You don't need thirty fields; you need five, actually filled in. Only once they exist can a team honestly commit to it, shape it further, park it, or say no.",{"question":151,"answer":152},"Why fill out the fields with the person who asked?","The leverage isn't in the fields; it's in filling them out loud with the requester before committing. Half the time the exercise changes the request entirely: they don't need a report, they need a number to stop being wrong. The other half it surfaces an open question big enough to change the plan, one that's cheap to answer now and expensive to discover in UAT.",{"question":154,"answer":155},"What's the point of the 'open questions' field?","It's the most important of the five. A request with no open questions usually means you haven't looked hard enough. Surfacing what you don't know yet is what stops a one-line ask from being committed to and then discovered — the wrong way — in production.",{},true,11.4,"\u002Fblog\u002F06-slack-request-to-initiative","finance-systems-delivery","turning a request into an initiative",6,"delivery-sheet","annual","reviewed","Tan Gravam","informational",{"title":5,"description":144},"blog\u002F06-slack-request-to-initiative",[171,172,173],"delivery","process","product","text","2026-07-29","-X6UmA6EfnWMTg5WhXV5el46o3Ke3UBZkYsgPBFrC64",{"related":178,"prev":190,"next":193,"hasOrder":157,"place":196},[179,182,186],{"path":57,"title":180,"description":181},"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":183,"title":184,"description":185},"\u002Fblog\u002Fgovernance-and-steering-for-finance-programmes","Governance and Steering for Finance Programmes","Programme governance steers a large finance-systems programme — the decision structure, cadence and escalation. Good governance keeps a big programme unblocked.",{"path":187,"title":188,"description":189},"\u002Fblog\u002Fraid-log-risks-assumptions-issues-dependencies","RAID Logs: Risks, Assumptions, Issues and Dependencies","A RAID log tracks a programme's risks, assumptions, issues and dependencies — and works only when you actually mitigate and chase them, not file them.",{"path":191,"title":192,"type":174,"language":6},"\u002Fblog\u002F05-commit-before-clear","Why teams commit before the request is clear",{"path":194,"title":195,"type":174,"language":6},"\u002Fblog\u002F07-cost-of-unclear-ownership","The cost of unclear ownership in enterprise delivery",{"label":197,"position":198,"total":199,"hub":125},"Field Notes",3,4,[],1787475400139]