[{"data":1,"prerenderedAt":285},["ShallowReactive",2],{"perspectives-index":3},[4,93,174,223],{"id":5,"title":6,"body":7,"category":81,"date":82,"description":83,"extension":84,"meta":85,"navigation":86,"order":87,"path":88,"seo":89,"stem":90,"summary":91,"__hash__":92},"perspectives\u002Fperspectives\u002Fhealthcare-innovation-flywheel.md","The Milligram Flywheel",{"type":8,"value":9,"toc":75},"minimark",[10,14,17,22,46,65,69,72],[11,12,13],"p",{},"Most project work is linear. A challenge arrives, a team solves it, the engagement ends, and the next one starts from zero. Nothing accumulates.",[11,15,16],{},"Improving how healthcare organizations operate works differently. Because the hard part is rarely the technology — it's understanding the operational reality behind a decision — what you learn on one challenge is exactly what makes the next one faster. That's the flywheel.",[18,19,21],"h2",{"id":20},"the-loop","The loop",[11,23,24,25,29,30,33,34,37,38,41,42,45],{},"An ",[26,27,28],"strong",{},"operational challenge"," starts the cycle. ",[26,31,32],{},"Discovery"," turns it into a clear picture of what's actually happening. ",[26,35,36],{},"Shared understanding"," aligns everyone on the real problem, and ",[26,39,40],{},"system design"," shapes a fitting response. ",[26,43,44],{},"Implementation"," puts it to work where the decisions are made.",[11,47,48,49,52,53,56,57,60,61,64],{},"Then the part that compounds: ",[26,50,51],{},"real-world learning",". Every system in use teaches something about how the work truly happens. That learning becomes ",[26,54,55],{},"reusable knowledge"," — patterns, models, and judgment that carry forward — which yields ",[26,58,59],{},"better products"," and, ultimately, ",[26,62,63],{},"better organizations",". And a stronger organization is ready to take on the next challenge from a higher starting point.",[18,66,68],{"id":67},"why-it-matters","Why it matters",[11,70,71],{},"The flywheel is why we don't measure success by projects completed. A project is one turn of the wheel. What we're really building is momentum: the more challenges we take on together, the more the accumulated knowledge does the heavy lifting.",[11,73,74],{},"It's also why the work is collaborative. The learning that powers the wheel comes from the people who live the operations every day. Their knowledge is the fuel.",{"title":76,"searchDepth":77,"depth":77,"links":78},"",2,[79,80],{"id":20,"depth":77,"text":21},{"id":67,"depth":77,"text":68},"framework",null,"The Milligram Flywheel explains how collaborative work compounds — every project teaches something, and every lesson becomes knowledge we can reuse.","md",{},true,1,"\u002Fperspectives\u002Fhealthcare-innovation-flywheel",{"title":6,"description":83},"perspectives\u002Fhealthcare-innovation-flywheel","How solving one operational challenge makes the next one easier.","BgVBznl9x52mCbehb4P5B6h0yD27g5NK5A2VE3EZAzY",{"id":94,"title":95,"body":96,"category":81,"date":82,"description":167,"extension":84,"meta":168,"navigation":86,"order":77,"path":169,"seo":170,"stem":171,"summary":172,"__hash__":173},"perspectives\u002Fperspectives\u002Fdecision-infrastructure.md","Decision Infrastructure",{"type":8,"value":97,"toc":162},[98,105,109,117,120,124,152,156,159],[11,99,100,101,104],{},"Most healthcare organizations already have the data. What they don't have is the thing that turns data into a decision someone can act on, in the moment the decision needs to be made. We call that missing thing ",[26,102,103],{},"decision infrastructure",".",[18,106,108],{"id":107},"not-a-dashboard","Not a dashboard",[11,110,111,112,116],{},"A dashboard shows you what happened. Decision infrastructure tells you what to ",[113,114,115],"em",{},"do"," — and puts that recommendation where the work actually happens, so acting on it is the path of least resistance.",[11,118,119],{},"The difference is subtle but decisive. Dashboards get built constantly, and the underlying decision stays exactly the same. Decision infrastructure is designed backwards from the decision it exists to change.",[18,121,123],{"id":122},"what-its-made-of","What it's made of",[125,126,127,134,140,146],"ul",{},[128,129,130,133],"li",{},[26,131,132],{},"A data foundation"," that connects the sources a decision actually depends on.",[128,135,136,139],{},[26,137,138],{},"Models"," — economic and analytical — that reason over that data.",[128,141,142,145],{},[26,143,144],{},"A recommended action"," that is specific and defensible, not a chart to interpret.",[128,147,148,151],{},[26,149,150],{},"Delivery into the workflow",", so the decision reaches the person who makes it.",[18,153,155],{"id":154},"why-organizations-skip-it","Why organizations skip it",[11,157,158],{},"Because it's the hard part. Building a dashboard is a technology task. Building decision infrastructure requires understanding the economics, the workflow, and the incentives around a decision well enough to change it — which is exactly the work that generic software and generic AI skip.",[11,160,161],{},"That gap is the whole opportunity. The data already exists. The decision is what never happens.",{"title":76,"searchDepth":77,"depth":77,"links":163},[164,165,166],{"id":107,"depth":77,"text":108},{"id":122,"depth":77,"text":123},{"id":154,"depth":77,"text":155},"Decision infrastructure is the system that turns data and economics into a specific action, delivered where the decision is actually made.",{},"\u002Fperspectives\u002Fdecision-infrastructure",{"title":95,"description":167},"perspectives\u002Fdecision-infrastructure","The layer between data and action that most organizations never build.","E-fjd177nlHBgBGEbF2k-Mo0GauzlEzEsSCg8-6w0HE",{"id":175,"title":176,"body":177,"category":214,"date":82,"description":215,"extension":84,"meta":216,"navigation":86,"order":217,"path":218,"seo":219,"stem":220,"summary":221,"__hash__":222},"perspectives\u002Fperspectives\u002Fwhy-healthcare-doesnt-have-an-ai-problem.md","Why Healthcare Doesn't Have an AI Problem",{"type":8,"value":178,"toc":209},[179,182,186,189,192,196,199,203,206],[11,180,181],{},"Walk into most healthcare organizations and you'll find real enthusiasm for AI, a pilot or two, and surprisingly little that changed. It's tempting to blame the models. The models are rarely the issue.",[18,183,185],{"id":184},"the-demo-that-changes-nothing","The demo that changes nothing",[11,187,188],{},"A generic model trained on the open internet doesn't understand a prior authorization queue, a formulary decision, or a reimbursement edit. It can produce something impressive in a demo and something useless in an operation — not because it's weak, but because it's aimed at the wrong target.",[11,190,191],{},"The constraint was never intelligence. It was the decision. Which decision needs to change, who makes it, what economics govern it, and what happens after — those questions decide whether anything improves. AI that never touches them just automates the part that was already working.",[18,193,195],{"id":194},"the-software-wasnt-wrong-the-workflow-was","\"The software wasn't wrong. The workflow was.\"",[11,197,198],{},"Most failed healthcare technology shares a root cause: it was designed around a capability instead of a decision. The data existed. The dashboard shipped. The decision still never happened.",[18,200,202],{"id":201},"where-ai-actually-earns-its-place","Where AI actually earns its place",[11,204,205],{},"Applied precisely — inside a stack of expertise, economics, and workflow — AI is genuinely powerful. It's an engine, not a headline. The organizations that get value from it start with the decision and reach for AI only where healthcare complexity makes it the right tool.",[11,207,208],{},"Healthcare doesn't need more AI. It needs better ways to operate. AI is one route there — one tool among many, with healthcare expertise still doing the steering.",{"title":76,"searchDepth":77,"depth":77,"links":210},[211,212,213],{"id":184,"depth":77,"text":185},{"id":194,"depth":77,"text":195},{"id":201,"depth":77,"text":202},"perspective","Most healthcare AI initiatives produce impressive demos and little value — because the technology was never the constraint.",{},6,"\u002Fperspectives\u002Fwhy-healthcare-doesnt-have-an-ai-problem",{"title":176,"description":215},"perspectives\u002Fwhy-healthcare-doesnt-have-an-ai-problem","Healthcare doesn't have an AI problem. It has a decision problem.","kN3_iZ8F3PU18jH063uBjBQMA5i-V2xFq7W9FRg5cFY",{"id":224,"title":225,"body":226,"category":214,"date":82,"description":277,"extension":84,"meta":278,"navigation":86,"order":279,"path":280,"seo":281,"stem":282,"summary":283,"__hash__":284},"perspectives\u002Fperspectives\u002Fproducts-grow-from-problems.md","Products Grow From Problems",{"type":8,"value":227,"toc":272},[228,231,235,242,251,255,258,261,265],[11,229,230],{},"There are two ways to build a healthcare product. You can imagine what the market might want and build it on speculation. Or you can solve real problems, notice which ones keep recurring, and let a product grow from the pattern. We strongly prefer the second.",[18,232,234],{"id":233},"products-are-accumulated-learning","Products are accumulated learning",[11,236,237,238,241],{},"A product, in our view, is not separate from the work of solving problems. It ",[113,239,240],{},"is"," the work — distilled. When the same operational problem shows up across a dozen pharmacies, the solution stops being a one-off and starts being infrastructure worth productizing.",[11,243,244,245,250],{},"That's how ",[246,247,249],"a",{"href":248},"\u002Fproducts","Phios"," came to exist. Not from a roadmap meeting, but from watching the same margin and workflow problems appear again and again, and building the reusable answer.",[18,252,254],{"id":253},"why-this-order-matters","Why this order matters",[11,256,257],{},"Speculative products carry a hidden tax: you're guessing at the problem and the solution at the same time. Products grown from real problems have already been validated by the work — the problem is proven before a line of product code is written.",[11,259,260],{},"It also keeps the incentives honest. A product built from real problems has to keep earning its place in a real operation. If it stops solving the problem, the operation stops using it, and we know immediately.",[18,262,264],{"id":263},"the-connection-to-the-flywheel","The connection to the flywheel",[11,266,267,268,271],{},"This is the ",[246,269,270],{"href":88},"flywheel"," again. Reusable knowledge — the operational experience that accumulates from every build — is exactly the raw material future products are made of. Solve enough real problems well, and the products emerge on their own.",{"title":76,"searchDepth":77,"depth":77,"links":273},[274,275,276],{"id":233,"depth":77,"text":234},{"id":253,"depth":77,"text":254},{"id":263,"depth":77,"text":264},"The best healthcare products aren't dreamed up in a roadmap meeting — they emerge from patterns that show up again and again in real work.",{},8,"\u002Fperspectives\u002Fproducts-grow-from-problems",{"title":225,"description":277},"perspectives\u002Fproducts-grow-from-problems","Why our products are accumulated operational experience, made repeatable.","Rw_qPBPD5KGrx6zd21w3J0IoZWx-xsSj6ADelj6PQyk",1784599853573]