Insights · Blog
Blog
Short, practical write-ups from the work we're doing — 2 a week.
The Confidence Interval as a First-Class Output
A forecast that says "440 units" is a different claim than one that says "440 units, plausibly anywhere from 310 to 590." Most decision systems we inherit only ever emit the first one.
Outcomes Over Activities: What Boards Are Starting to Ask For
A board member recently asked a program team not how many workshops ran this quarter, but what changed for the people who attended, and how the team knows. The silence that followed is becoming a pattern.
Demand Sensing in a Six-Plant Network: What We Learned Re-baselining Nightly
We pitched nightly re-baselining as a modeling upgrade. It turned out to be a data-plumbing project wearing a forecasting project's clothes, and the difference cost us a month we hadn't planned for.
Ninety Days to Unify Five Legacy Systems: A Sequencing Note
The original plan had us designing the unified data model for six weeks before touching anything live. We scrapped it in the first planning meeting, and that turned out to be the right call.
Designing for Safe Degradation
Under uncertainty, most autonomous systems do one of two things: keep going as if nothing changed, or stop entirely. Both are the wrong default. The right one is a known, deliberately narrower mode the system falls into on purpose.
Glass-Box Explainability That Holds Up at Audit
We walked into a model review with a beautiful SHAP dashboard and walked out with homework. Here's what the risk committee actually wanted, and why our first answer wasn't it.
Escalation by Consequence: A Threshold Design Note
Six weeks after launch, our override rate quietly hit zero. We treated that as good news for about a week before we realized what it actually meant.
What-If as a System, Not a Workshop
Ask most operations teams when they last ran a what-if scenario and they'll point to a planning offsite months ago. Ask what changed about how they handle an actual demand shock next Tuesday, and the honest answer is usually nothing.
Responsible Prediction in Education: What We Refuse to Build
Most vendor conversations about responsible AI in education stay abstract on purpose. Ours doesn't — here are the specific things institutions have asked us to build that we've turned down, and why.
The Reconciliation Problem That Eats Optimization Budgets
Ask most supply chain optimization projects what they actually spent their first six months on, and it wasn't optimization. It was getting the ERP, the WMS, and the TMS to stop disagreeing about what's true.
The Cost of the Unreconciled Inventory Number
The MES says 4,200 units. The ERP says 3,850. The shift lead's spreadsheet says 4,000 even, because that's what it said yesterday and nobody's corrected it since. All three numbers are 'the inventory position.' None of them are wrong, exactly — that's the actual problem.
Agent FinOps: A Runtime Concern, Not a Procurement One
A signed enterprise agreement with better per-token pricing feels like the finish line on agent cost control. It's the easiest 20% of the problem, and the 20% procurement is already equipped to solve.
The Hidden Cost of the Queue: Where Compliance Exceptions Actually Live
The automation rate everyone reports is the wrong number. The number that actually determines your compliance cost is how long an item sits in the exception queue before a human looks at it.
Three Reasons Manufacturing AI Projects Stall After Pilot
The pilot works. Everyone claps. Then eleven months pass and the model is still running on one line, in one plant, watched by the two engineers who built it. Here's where that gap actually comes from.
Field Data Capture in Low-Connectivity Environments
\"Offline mode\" is the wrong mental model for field data capture where connectivity is the exception, not the fallback. A system designed around that reality looks different from one that's merely offline-capable.
The Week-Six Signal: Why Most Interventions Arrive Too Late
Midterm-based early warning systems are accurate and almost useless, because by the time they fire, most of the semester's runway for changing a student's trajectory is already gone.
Why Most Funder Reports Take Weeks (and What to Do About It)
A funder report is not hard to write. It is hard to assemble — and the assembly is where three weeks go, quarter after quarter, no matter how good the program was.
The Control Surface Inventory: A Starter Method
Most compliance teams can name their controls but not the systems those controls actually touch. That gap is where the surprises live, and it's fixable in a quarter with a method this plain.