Inertia Audit™Behavioral Intelligence
Sign in

Diagnostic Engine

Run an Audit

Brief the model on your transformation. The Inertia Audit engine returns a composite risk score and a streaming consulting-grade synthesis.

Sign in to save
1

Context

Tell the engine who the client is and what they're trying to change.

The client company you're auditing. Used only to personalize the report.

Sector context. Regulated industries face higher baseline inertia.

5,000 employees

Headcount touched by the change. Larger orgs amplify coordination cost.

The change program in one line — what's being replaced or introduced.

The intended outcome and rough timeline. Be concrete — the AI grounds its synthesis here.

2

Inertia signals

Four sliders that capture why people resist change. Each one has a 'How to measure' guide — quick interview questions and observations you can run before scoring.

Field method (≈ 60 min)

Talk to 3–5 people who actually use the old system daily (not just managers). Ask the prompts under each signal, listen for the tells, then score. Trust the pattern, not a single quote.

70 / 100

How deeply daily work relies on the old system — spreadsheets, integrations, undocumented workarounds people built around it.

Standalone, easy to swapEmbedded in every workflow
How to measure this in the field▾

Ask 3–5 people

  • Walk me through your last Monday morning — which tools did you open first?
  • What breaks if this system is down for a day?
  • How many spreadsheets or scripts feed into or out of it?

Observe

  • Count integrations and downstream reports that read from it.
  • Look for 'shadow' Excel/Access tools built around the system.
  • Check how many teams touch its data weekly.

Translate to a score

0–30 used by one team. 40–60 cross-team. 70–100 it's the spine of operations.

60 / 100

How much the day-to-day workflow itself has to change: new steps, new tools, new approvals, new handoffs.

Same process, new interfaceEntire workflow redesigned
How to measure this in the field▾

Ask 3–5 people

  • Map the current workflow in 5 steps. Now map the future-state in 5 steps. How many steps actually change?
  • Who has to approve or hand off something differently?
  • What does an average task look like before vs. after?

Observe

  • Diff the two workflows side-by-side; count changed/added/removed steps.
  • Note new roles or owners introduced.
  • Watch for changes in cadence (daily → weekly, batch → real-time).

Translate to a score

0–30 cosmetic UI change. 40–60 several steps reshuffle. 70–100 fundamentally new way of working.

50 / 100

How much the change threatens people's sense of expertise, role or seniority. 'I was the expert on the old system' is a classic high-identity signal.

No role or status shiftRedefines who is valuable
How to measure this in the field▾

Ask 3–5 people

  • Who is the go-to person when the old system misbehaves? What happens to their role after?
  • Does anyone's title, span of control, or career path change?
  • Which skills that used to be prized become less valuable?

Observe

  • Listen for 'I built this' / 'I'm the only one who knows…'.
  • Map informal experts — they often lose status silently.
  • Check if new tooling shifts decision rights upward or downward.

Translate to a score

0–30 nobody's role shifts. 40–60 some experts lose ground. 70–100 the new system redefines who's valuable.

40 / 100

How clearly leadership has communicated what replaces the old way — the new process, owner and success criteria. Low clarity is the #1 silent killer of adoption.

Nobody knows the new wayCrystal clear, documented, owned
How to measure this in the field▾

Ask 3–5 people

  • In one sentence: what's the new way of doing X, and who owns it?
  • What does 'done well' look like in 90 days?
  • Where is this written down? Can you show me?

Observe

  • Ask three people the same question. Do you get the same answer?
  • Check for a published target operating model, RACI, or playbook.
  • Look for a named owner per workflow — not 'the transformation team'.

Translate to a score

0–30 vague vision deck only. 40–60 leadership aligned, frontline isn't. 70–100 documented, owned, repeatable.

Method · ISI v1.0 · Lovable AI · streaming

Adoption Risk Score

—/100

ISI

—

Readiness

—

Resistance prob.

—

Clarity gap

—

Diagnostic radar

AI Diagnostic Engine · Executive Synthesis

Submit the brief to generate a consulting-grade synthesis. The engine references module thresholds and the variables contributing most to your composite risk.