[{"data":1,"prerenderedAt":125},["ShallowReactive",2],{"profile":3,"writing-find-the-three-workflows":14},{"name":4,"role":5,"tagline":6,"location":7,"contact":8},"Sankar Vema","AI Builder & Architect of Agentic Systems","I help enterprise leaders turn AI ambition into capability that actually ships.","India · open to global advisory engagements",{"email":9,"linkedin":10,"github":11,"blog":12,"twitter":13},"sankar.vema@gmail.com","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fsankarvema\u002F","http:\u002F\u002Fsankarvema.github.io\u002F","http:\u002F\u002Fsankarvema.blogspot.com\u002F","https:\u002F\u002Ftwitter.com\u002Fsansvema",{"id":15,"title":16,"body":17,"date":110,"description":23,"draft":111,"excerpt":112,"extension":113,"meta":114,"navigation":115,"path":116,"seo":117,"slug":118,"status":112,"stem":119,"tags":120,"__hash__":124},"writing\u002Fwriting\u002Ffind-the-three-workflows.md","Find the Three Workflows",{"type":18,"value":19,"toc":102},"minimark",[20,24,29,32,55,58,62,65,69,96,99],[21,22,23],"p",{},"Most AI strategies fail by being too ambitious. Forty initiatives, a committee, a\nplatform, and no clear first win. The teams that succeed do the opposite. They\nfind three workflows where AI moves a number the business already cares about, and\nthey do those, well, before anything else. Here is how to find your three.",[25,26,28],"h2",{"id":27},"the-filter","The filter",[21,30,31],{},"A workflow is worth doing when it scores on three things at once.",[33,34,35,43,49],"ul",{},[36,37,38,42],"li",{},[39,40,41],"strong",{},"Volume."," It happens a lot. Small improvements compound only when the base is large.",[36,44,45,48],{},[39,46,47],{},"Pain."," It is manual, slow, or error-prone today, so the improvement is felt.",[36,50,51,54],{},[39,52,53],{},"Boundedness."," The task is defined enough that a machine can do it reliably,\nwith a clear right answer or a clear place to stop and ask.",[21,56,57],{},"Miss any one and the case gets shaky. High volume but unbounded is a reliability\nnightmare. Bounded and painful but rare is not worth the build. You want all three.",[25,59,61],{"id":60},"the-number-test","The number test",[21,63,64],{},"Then apply the number test: can you name the outcome in a unit the CFO recognizes?\nHours saved, dollars, error rate, cycle time, revenue. If the best you can say is\n\"efficiency\" or \"better experience,\" it is not one of your three. Not yet.",[25,66,68],{"id":67},"the-method","The method",[70,71,72,78,84,90],"ol",{},[36,73,74,77],{},[39,75,76],{},"List your highest-volume operational processes."," Start from where the people\nand the tickets are, not from where the excitement is.",[36,79,80,83],{},[39,81,82],{},"Score each on volume, pain, and boundedness."," Be honest about boundedness.\nIt is the one teams consistently overrate.",[36,85,86,89],{},[39,87,88],{},"Attach a number to the top few."," If you cannot, dig until you can, or drop it.",[36,91,92,95],{},[39,93,94],{},"Pick three."," Not thirty. Three you can ship and prove within two quarters.",[21,97,98],{},"The point of three is focus. Three shipped, proven workflows build the\ncredibility, the platform, and the appetite for the next ten. Forty parallel\npilots build a graveyard.",[21,100,101],{},"Strategy is choosing. So which three workflows would you bet the whole AI program\non, and why not start there?",{"title":103,"searchDepth":104,"depth":104,"links":105},"",3,[106,108,109],{"id":27,"depth":107,"text":28},2,{"id":60,"depth":107,"text":61},{"id":67,"depth":107,"text":68},"2026-08-01",false,null,"md",{},true,"\u002Fwriting\u002Ffind-the-three-workflows",{"title":16,"description":23},"find-the-three-workflows","writing\u002Ffind-the-three-workflows",[121,122,123],"enterprise","adoption","method","vW31VvOZsp4RYA25kkzCbwfJ9L7llYiJcIuEnhiKRfQ",1790601541678]