Manifesto.
9 beliefs · 1 argument
Planning has not failed because planners are wrong. Planning has failed because the systems planners run on were designed for a world that no longer exists.
Variability is the signal, not the noise.
From → To · From smoothing it away to planning against it.
Traditional planning treats variability as a problem to be smoothed away — averaged into a forecast, buffered with safety stock, hidden in penalty weights. This is backwards. Variability is the most informative feature of the supply chain. The right response is not to hide it but to model it, price it, and plan against it.
A plan should ship with its risk profile attached.
From → To · From point estimates to distributions.
A point estimate without a distribution is a guess presented as a fact. Every plan VYAN produces ships as a distribution — expected value, percentile bands, tail exposure. Planners review distributions. Executives review distributions. Risk is not a side conversation; risk is in the plan.
Decisions are first-class.
From → To · From plans-as-documents to decisions-as-commitments.
Plans are documents. Decisions are commitments. Traditional planning systems emit plans and treat decisions as a downstream artifact; the most consequential moments — a supplier slip, a customer escalation, a capacity loss — happen between cycles when the planning system has nothing to say. We invert this. The decision is the unit of work. The plan is the snapshot of accumulated decisions. The engine emits decisions continuously, each one carrying its reasoning, its expected value, its confidence, its alternative options.
The right financial measure is not cost. It is EVA.
From → To · From cost minimization to value creation.
Cost minimization misses the point. A plan that minimizes cost while consuming three times the working capital it should is a worse plan than one that costs slightly more and frees the capital. — Economic Value Add, profit adjusted for the capital employed to produce it — is the right unit. We anchor the optimization on Resilient-EVA: expected EVA penalized for tail risk. The plan that maximizes Resilient-EVA is the plan that creates the most value the business is willing to defend.
Plans should be defensible.
From → To · From "the optimizer said so" to here-is-the-trade-off.
Every decision the engine produces should be interrogable. Why this supplier? Why this customer prioritization? Why this reschedule? The answer should not be "because the optimizer said so." The answer should be: here are the alternatives considered, here are the trade-offs, here is the binding constraint, here is the EVA delta to the next-best option. Trust in the system is earned by transparency, not asserted by accuracy claims.
Autonomy should be granular, not binary.
From → To · From all-manual or all-auto to policy-defined.
Planning systems today are either all-manual (planner becomes the bottleneck) or all-auto (control is lost). The middle ground — auto-commit for safe routine decisions, route to a role for material ones, block pending approval for the most consequential — requires policy infrastructure that traditional systems do not have. We built that infrastructure. Governance Policy is first-class. Autonomy is granular. The business runs leaner without losing control.
The system should learn.
From → To · From frozen artifact to learning system.
A planning system that runs the same way next quarter as it ran this quarter, regardless of what happened, is a frozen artifact. We built VYAN to learn. Every cycle, the engine compares plan to actual and recalibrates the drivers that drove the plan. Drift surfaces as a quality signal. Master data corrects itself from realized signal. The system gets more accurate the more it runs. Data quality is a function of usage, not of cleansing.
SAGE is a colleague, not an oracle.
From → To · From AI-that-replaces to AI-that-relieves.
We are not building a planning AI that replaces the planner. We are building a colleague that frees the planner from the parts of the job that should never have been the job in the first place — the schema lookups, the scenario assembly, the briefing preparation, the explanation construction. SAGE proposes; the planner decides on material moves; the engine commits on routine ones under policy authority. The planner's judgment is the constraint we want to relax, not the variable we want to remove.
Planners deserve a better job.
From → To · From system operators to decision policy architects.
The best planners in our customers' organizations are some of the most capable problem-solvers in the business. They spend their days on schema mechanics, exception triage, and slide preparation. We think this is a waste of the most expensive operational judgment the company has. The right outcome of deploying VYAN is not "we automated the planners away." The right outcome is "our planners are now decision policy architects focused on enterprise performance optimization, and they are doing the most valuable work of their careers."
What we are building toward.
A world where planning is continuous, not periodic. Where decisions are auditable, not opaque. Where variability is priced, not hidden. Where the supply chain is a learning system, not a static artifact. Where the planner is a strategic advisor, not a system operator. Where the CFO can ask the planning engine a question in their own language and get an answer in theirs.
We are early in this. The platform we have built is the foundation; the journey from foundation to ubiquity will take a decade. We are looking for the customers who want to be early with us, the partners who want to build the implementation discipline around this category, and the people who want to spend their careers building what comes after deterministic planning.
If any of this resonates, we should talk.