AXIS PLAN
Contact

Field Note / Planning Practice

A Working Guide to
Planning Under Constraint

A useful plan does more than produce an answer. It shows people what shaped that answer, what could change it and where judgement still matters.

A planning team reviewing operational constraints around a shared table
Shared planning begins by making operating conditions visible.

Complex operations rarely fail because teams lack data. More often, the conditions that matter are scattered across systems, conversations and lived experience. Capacity may look available on paper while a maintenance window, a handover or a safety requirement makes it unusable in practice.

AXIS PLAN treats these conditions as part of the decision itself. The aim is not to replace judgement, but to give judgement a clear structure.

Start with the decision,
not the dataset.

Before choosing a method or building a model, define the decision that must be made. Who needs to act? What changes if the decision is delayed? Which outcomes matter, and which conditions cannot be negotiated?

This framing separates useful evidence from available information. It also gives operators, planners and leaders one question they can examine together.

Make constraints readable.

Constraints should not disappear inside a score. Teams need to see the limiting resource, the time window, the dependency and the consequence of moving it. A readable constraint can be challenged; a hidden one can only be trusted.

We organize constraints into a small working map: fixed boundaries, adjustable choices, uncertain signals and human review points. That map becomes the common language for comparing options.

Operational planning interface connecting demand, capacity and timing
Alternatives stay useful when teams can trace the conditions behind them.

Compare alternatives,
then record the trade-off.

A single recommendation creates false certainty. A small set of feasible alternatives gives decision-makers something more valuable: a view of the trade-offs between service, cost, workload, resilience and room to adapt.

The chosen option should retain its reasoning. Record what was prioritized, what was accepted and which signal should trigger a review. This decision history helps the next planning cycle begin with knowledge instead of starting again.

Keep people inside
the learning loop.

Implementation is not the end of planning. Actual outcomes reveal which assumptions were accurate, which constraints changed and where the operating model needs to learn. Reviewing those differences turns a plan into a reusable decision system.

The result is practical: teams move faster because they can understand the plan, question it and improve it together.

Three practices

A plan people can use.

  1. 01

    Frame the decision

    Define the action, value and non-negotiable conditions before modeling.

  2. 02

    Expose the trade-off

    Compare feasible alternatives without hiding the limits that shaped them.

  3. 03

    Review the outcome

    Use operational evidence to improve the next decision cycle.

Back to AXIS PLAN