METHOD

Six weeks. Clear steps, clear asks, one clear result.

A diagnostic, not a project. Here's exactly what happens each week, what we need from your team, and what you hold at the end.

Six-stage SIGNAL method flow: data orientation, field validation, operating model reconstruction, pattern detection, value-at-stake modelling, roadmap.
01Data orientation

Map what data exists, what is missing, and what can be trusted.

OutputData spine — available data, gaps, and trust level

02Field validation

Check how work actually happens in the field before modelling begins.

OutputValidation brief

03Operating model reconstruction

Rebuild how work moves from request to resolution across systems, roles and handoffs.

OutputOperating map

04Pattern detection

Identify repeat mechanisms, instability, leakage and root-cause hypotheses.

OutputRoot-cause register

05Value-at-stake modelling

Size validated root causes under conservative, base and stretch scenarios.

OutputValue model

06Roadmap

Sequence actions, owners, dependencies and AI opportunities by value and feasibility.

OutputExecutive decision package

Week 1
What we do

Data orientation

We review your raw system exports and map what exists, what is missing, and what can be trusted.

You provide

System extracts, a data contact, and a kickoff session.

We produce

Data spine — an inventory of your data and what can be trusted.

Week 2
What we do

Field validation

We observe how work actually happens in the field — structured field walks, ride-alongs and early interviews. This grounds the diagnostic before any model is built.

You provide

Site access, selected ride-alongs or field observations, and first interviews.

We produce

A field validation brief: what is confirmed, what is unclear, and what is only internal folklore.

Week 3
What we do

Operating-model reconstruction

We rebuild how the operation runs from request to resolution, then reconcile it against roles, systems, handoffs and the validated field context.

You provide

Stakeholder interviews and any existing process documentation.

We produce

One agreed operating map.

Week 4
What we do

Pattern detection

SIGNAL reconstructs the operation event by event to identify repeat mechanisms, instability, leakage, and the root-cause hypotheses worth testing.

You provide

Access for clarification questions and operational sense-checks.

We produce

A root-cause register.

Week 5
What we do

Value-at-stake modelling

We size each validated root cause in financial and operational terms, under conservative, base and stretch scenarios.

You provide

Financial assumptions, rate cards and cost inputs.

We produce

A value model by root cause.

Week 6
What we do

Roadmap & executive decision package

We sequence the root causes by value, feasibility, dependencies and ownership. AI opportunities are ranked only where the evidence supports them.

You provide

One executive review session.

We produce

An executive decision package — yours to keep and act on.

This page shows how the six weeks run. The analysis methods behind SIGNAL remain proprietary.

What we need from your team

Typical inputs.

We start from the records, context and field reality you already have — no system integration required.

Operational records
  • Work orders
  • Service appointments
  • Asset history
  • Scheduling changes
  • Parts / readiness data
Operating network
  • Technician roster
  • Service centers
  • Territories
  • Capacity assumptions
Business context
  • Existing dashboards
  • Financial assumptions
  • Rate cards
  • Performance targets
  • Planning assumptions
Field reality
  • Selected interviews
  • Ride-alongs / field observations
  • SOPs / work instructions
  • Training materials
  • Known workarounds
How much of my team's time does this take?

Concentrated, not constant: extracts up front, 6–10 interviews across weeks 2–4, selected field access in week 2, and one executive session in week 6. Your operation keeps running.