If simulation is optional, it does not constitute a capability. In large organisations, optional use inevitably leads to uneven standards, declining proficiency, and weak return on investment. This is not a cultural issue or a question of motivation — it is a leadership decision. When mandate and ownership are unclear, training systems become discretionary tools rather than enforced instruments of readiness. This article explores why mandatory use is a prerequisite for sustained capability, and builds on my previous post.

Capability implies obligation

A capability is not defined by ownership or availability. It is defined by expected use.

If a capability is considered essential, its use is:

• embedded in plans
• reflected in requirements
• reinforced through leadership
• monitored and evaluated over time

When simulation is left to individual preference, the organisation sends a clear signal — often unintentionally — that simulation is not essential to training effectiveness or readiness.

That signal is received quickly and acted upon accordingly.

The quiet cost of optional use

When simulation use is optional, predictable patterns emerge:

• Adoption varies widely between units
• Training outcomes become inconsistent
• Evaluation data is fragmented or unreliable
• Leaders lose visibility into training quality
• Investment decisions become harder to justify

Over time, this erodes confidence — not only in the system, but in simulation as a concept.

The irony is that many of these organisations have already invested significantly in acquiring capable systems. The shortfall is not technical. It is organisational.

Governance does not end at delivery

A common misconception is that governance primarily concerns acquisition: requirements, contracts, acceptance, and handover.

In reality, the most consequential governance decisions come after delivery:

• Who decides how the system is used?
• When is use mandatory, and when is it optional?
• How is use linked to training objectives and evaluation?
• What happens when use declines or becomes inconsistent?

If these questions are not answered explicitly, governance defaults to convenience.

Convenience is rarely aligned with long-term capability development.

Mandatory use is not rigid

Making simulation use obligatory is often perceived as inflexible or burdensome. In practice, it is the opposite.

Clear expectations:

• reduce uncertainty
• support instructors and planners
• normalise use across the organisation
• enable meaningful evaluation and improvement

Obligation does not mean uniformity. It means intentional integration — deciding where simulation adds value and ensuring it is applied there.

Capabilities must be exercised to exist

Capabilities that are not exercised degrade.

This is evident in most operational domains, yet simulation is often treated differently — as something that remains “ready” even when it is rarely used.

In reality, simulation capabilities only exist to the extent that they are:

• planned for
• trained with
• evaluated
• refined through use

Without this cycle, simulation remains a paper asset rather than a contributor to readiness.

A leadership decision, not a technical one

Whether simulation is optional or obligatory is ultimately a leadership choice.

It reflects how seriously an organisation takes:

• training outcomes
• consistency and standards
• return on investment
• long-term readiness

Technology enables simulation. But leadership determines whether it becomes a capability.

A final thought

Organisations do not get the training effect they intend. They achieve the training effect they govern.

If simulation is optional, it will be used optionally. If it is optional, it cannot be considered a capability.

Have you reflected on this topic? What do you think? Please leave a comment so we can have a conversation.