ITquette Framework Series · Framework #2

The Scenario Intelligence
Framework™

How operational events become safety learning.

Organisations often say they learn from incidents. But learning doesn't happen simply because an event occurred. It happens when events are understood, connected, and transformed into actionable knowledge — and that transformation is far from automatic.


As autonomous systems expand into increasingly complex operating environments, the ability to learn from operational experience may matter just as much as the ability to operate autonomously.

Yet most organisations treat these two capabilities very differently. They invest heavily in operational performance and relatively little in the systems that convert operational experience into safety intelligence.

Many organisations collect events. Far fewer create scenario intelligence. The difference between the two may ultimately determine how fast — and how verifiably — safety improves.

This is the basis of the Scenario Intelligence Framework™.


The difference between capturing an event and capturing a scenario

Consider two organisations experiencing the same event. An autonomous vehicle hesitates while making an unprotected left turn.

Organisation A records
Vehicle hesitation event.
Organisation B records
Unprotected left turn →
dense cross-traffic →
partial vehicle occlusion →
excessive yield behaviour.

Both organisations captured the event. Only one captured the scenario.

The difference seems small. Over time it determines whether operational experience becomes organisational learning — or simply accumulates as a log of things that happened.


Six stages. One pipeline.

The Scenario Intelligence Framework™ describes how a raw operational event becomes a meaningful contribution to safety improvement. Each stage builds on the last — and skipping any one of them limits what can be learned.

The Scenario Intelligence Framework™ — Pipeline
STAGE 01 Operational Event STAGE 02 Event Classification STAGE 03 Scenario Definition STAGE 04 Pattern Recognition STAGE 05 Risk Understanding STAGE 06 Safety Improvement Something happened Intelligence begins here The goal
01
Entry point
Operational Event
An event occurs. At this point the organisation knows one thing: something happened. Whether it is important, insignificant, or a symptom of a larger issue remains unknown.
What happened?
02
Initial triage
Event Classification
The event receives a category: safety-critical, operational, perception, planning, control, human interaction. Classification prioritises attention — but it does not yet explain what occurred.
How serious is this?
03
Where intelligence begins
Scenario Definition
The question shifts from what happened to what situation was the system facing. The event is now described as a reusable scenario — comparable, searchable, connectable to others like it.
What was the system dealing with?
04
Signal from noise
Pattern Recognition
With consistent scenario definition, the organisation can ask: have we seen this before? One event may be noise. Ten similar events may be a trend. A hundred may indicate a systemic issue.
Have we seen this before?
05
Context creates meaning
Risk Understanding
Patterns reveal underlying risk. The focus shifts from explaining a single incident to understanding a class of problems — the recurring conditions that generate similar events across the fleet.
What underlying risk is emerging?
06
The goal
Safety Improvement
Only once a risk is understood can meaningful improvement occur. Engineering, operations, safety, and leadership teams can now act in a targeted rather than reactive way.
How do we reduce it?

What scenario intelligence makes possible

Events are isolated observations. Scenario intelligence creates relationships between events. Those relationships are what ultimately support the work that matters:

Operational learning
Risk management
Corrective action prioritisation
Safety validation
Regulatory confidence

Most importantly, scenario intelligence creates the foundation for demonstrating improvement over time — not just claiming it.


Connecting back to Framework #1

The thread between frameworks

Framework #1 introduced the Safety Evidence Gap — the observation that operators, regulators, insurers, and the public all rely on different forms of evidence when evaluating whether a system is safe.

That raises a natural question: where does safety evidence come from?

The answer begins with operational events. But events alone are not evidence. They must first become intelligence — classified, contextualised, connected, and understood. Only then can they support meaningful safety claims across all four stakeholder groups.

This is why the Scenario Intelligence Framework™ is not simply an operational tool. It is also an evidence-building discipline. The organisations that learn fastest from their operational experience are likely to be the same organisations best positioned to demonstrate safety improvement to the stakeholders who need to trust it.

Questions worth holding
  1. If two organisations experience the same event but classify, interpret, and learn from it differently, are they improving safety at the same rate?

  2. At what point does an organisation's ability to learn from operational experience become a competitive and regulatory differentiator?

  3. As autonomous systems scale, will the organisations that develop the deepest scenario intelligence ultimately become the safest — and the most trusted?

The answers will likely become clearer as autonomous mobility matures — and as the gap between organisations that collect events and those that build intelligence becomes harder to ignore.

Scenario intelligence Incident management Safety learning Operational resilience Safety lifecycle AV safety Framework series
← Previous · Framework #1
The Safety Evidence Gap Framework™
Next · Framework #3 →
The Incident-to-Improvement Framework™

Follow the research on LinkedIn.

New frameworks published regularly. If something connects with a challenge you are working through, reach out.

Get in touch →