Fourteen concepts for understanding enterprise decisions. Diagrams, shapes and numbers are illustrative; they are not product screenshots or measured client results.
01 · Where VYAN sits
A decision layer above the systems you already run.
Use on Home, Platform and Architecture. It says VYAN adds to the stack and replaces nothing, which removes the first objection a CIO raises.
Safe to show: a generic three-layer stack. Not shown: how VYAN connects, stores or computes.
The decision layer connects commitments to the systems that record and plan them. ERP and planning remain in place; integration scope is agreed for the evaluation.
02 · Ranges, not single numbers
Represent uncertainty as ranges. Most plans use one number from it.
Use on Home, Learn and Resilient planning. The dashed line is the number a conventional plan types in; the shape is what the business actually lives with.
Safe to show: that drivers have shapes. Not shown: how shapes are learned or fitted.
An average can hide the width and shape of variation. Preserve the relevant ranges until you evaluate the commitment, with business assumptions visible where evidence is missing.
03 · Sense and shape
Sense what you cannot control. Shape what you can.
Use on Why VYAN, Decision Policy and industry pages. Swap the labels per industry: crop yield and acreage for food, load and turbines for utilities.
Distinguish what the business observes from what it can choose. Demand and yields may be uncertain; sourcing, timing and protection are decisions, subject to the levers supported by the model.
04 · Four reference plans
Judge every plan in the same futures before you commit to one.
Use on Home and Cost of resilience. It shows that the single-forecast plan and the protect-everything plan both leave value on the table, and the resilient plan buys protection balanced against cost and service.
Illustrative comparison, not measured product results. Perfect information is an optimistic reference; maximum protection can still fail.
Reference plans help interpret an answer. Perfect information is an optimistic bound, a deterministic plan uses a central forecast, and full protection explores the allowed upper end. None is a guaranteed real-world outcome.
05 · Both tails
Give up a little in the middle to protect the bad years.
Use on Resilient planning and the food and utility pages. A plan tuned to one forecast earns most when that forecast comes true and loses badly when the driver lands short or long. The resilient plan earns a little less in the middle and far more in both tails.
Protection can trade some favorable-case value for a better downside. The curve illustrates that idea; whether the trade pays is a question for a scoped evaluation.
06 · Protection as a portfolio
Buy the protection that pays. Skip the rest.
Use on Cost of resilience and services. Each lever is weighed by what it costs against the loss it avoids, so leadership buys resilience deliberately.
Each protection has a price and a potential benefit. Compare material, time and capacity choices on consistent economics, and report only benefits the run actually measures.
07 · Autonomy within bounds
Small changes are absorbed. Material ones reach the owner.
Use on Event response and the contrast with automated single-number plans, which react to every signal.
A useful operating rule distinguishes variation the current plan can absorb from change that deserves review. Configured approvals are current; automatic event-triggered reassessment is product direction.
Product direction · Roadmap concepts are illustrated here, not presented as shipped capabilities.
08 · Two clocks
Wait while learning pays. Commit before the options expire.
Use on Learn, the POV pages and Decision memory. It is the executive timing question every long-lead commitment carries.
The chance to learn and the chance to act expire at different times. The concept is to weigh waiting against committing; automatic timing recommendations remain roadmap.
Product direction · Roadmap concepts are illustrated here, not presented as shipped capabilities.
09 · Futures from today
Test today's commitment down many possible paths.
Use on Learn and the POV pages. Commitments made today bind the choices available later.
A commitment made today shapes the choices available later. Future playback can test a supported controller using the information available at each point. The diagram is conceptual, not a count of tested outcomes.
10 · A decision that reopens
Every assumption stayed in range. The decision still came back.
Use on Decision memory. Combined economics, not any single threshold, decide when a commitment returns to the agenda.
Several modest changes can jointly alter the economics enough to warrant review. Monitoring that automatically reopens a commitment on that basis is product direction.
Product direction · Roadmap concepts are illustrated here, not presented as shipped capabilities.
11 · One currency
Every operating measure traced to economic profit.
Use on Integrated, Value and scorecard and the CFO story. Service, freight and inventory stop being separate arguments.
Revenue, operating cost and the capital charge create a shared economic view. Service and other non-negotiable obligations remain constraints rather than disappearing into the objective.
12 · Compounding
Decisions that remember why get better.
Use on Decision memory and About. Shows direction of travel; keep roadmap claims in the future tense.
Run versions, inputs and outputs provide history today. Fuller memory of alternatives, reasoning, overrides and outcomes is roadmap. The improvement curve is illustrative, not a measured result.
Product direction · Roadmap concepts are illustrated here, not presented as shipped capabilities.
13 · One governed flow
Engines, partners and people in one flow.
Configured flows connect supported engine steps, partner responses and human approvals. Validate the information and authority available to each participant.
14 · Where value leaked
Learn where value was lost, without assigning blame.
Use on Decision memory and the POV pages. It replaces the functional post-mortem with one enterprise view of what was believed, what was committed and what happened.
Separate changed assumptions, execution and accepted risk when reviewing an outcome. Automated attribution of value leakage and learning from overrides are product direction.
Product direction · Roadmap concepts are illustrated here, not presented as shipped capabilities.
