Adoption Diagnosis
Identify what is shaping adoption and what leadership should change next.
Latent Variables combines the adoption pattern leadership can already see with in-depth evidence from the people behind it. The diagnostic compares teams and workflows, identifies the conditions producing different adoption outcomes, and returns targeted interventions tied to the mechanisms the evidence supports.
The adoption diagnosis at a glance
The adoption diagnosis and interventions arrive within 6 days of fieldwork start.
15 minutes per person.
Conversations run in parallel across the adopting teams and workflows. A coordinated population completes fieldwork in 48 hours.
About 2 hours in total: the rollout context, the population, and the adoption pattern you can already see.
Up to 2,000 participants in a single wave.
Each conversation adapts to the participant's workflow, and the diagnosis reflects one moment in the rollout rather than a weeks-long collection window.
What the adoption diagnostic identifies
One interviewing instrument operates across the teams leadership wants to compare, so groups with different adoption outcomes are read against each other rather than in isolation. A condition that emerges in one cohort is tested with the cohorts adjacent to it.
Adoption by workflow
How the new system, process, tool, or behavior is incorporated into actual work, not only whether it is logged as used.
Differences between teams
Where the same rollout produces different operating behavior across teams, sites, or roles.
The mechanism behind the difference
The condition that best explains the pattern: awareness, knowledge, ability, workflow fit, process design, ownership, manager behavior, incentives, policy, trust in the output, verification burden, competing work, or another condition the evidence supports.
Workarounds and adaptations
What people changed around the rollout to keep their work moving.
Usage versus value
Where apparent usage is translating into the intended operating outcome, and where it is not.
Conditions affecting sustained adoption
What will determine whether current behavior persists after the initial rollout attention ends.
How the diagnosis becomes targeted interventions
Where the evidence supports it, the diagnosis converts into materials leadership can act on directly:
The diagnosis stands on its own. If leadership intervenes, a later read returns to the same cohorts with the earlier evidence preserved and shows whether the barrier changed, on the same 6-day turnaround.
What makes Latent Variables different
Explains what usage data cannot
Latent Variables shows how a rollout fits into actual work, including the workarounds, competing priorities, trust concerns, and verification burden behind the adoption pattern. It distinguishes visible usage from meaningful operational value.
Finds why adoption differs across teams
The same diagnostic runs across teams, workflows, sites, and roles. Differences between cohorts reveal whether the barrier is widespread or produced by a specific workflow, manager, policy, capability, or local condition.
Matches the intervention to the cause
Each intervention is tied to the mechanism the evidence supports. Leadership receives targeted changes to workflows, enablement, ownership, policy, or reinforcement, followed by a later read that shows whether the barrier changed.
Bring us one rollout.
We’ll describe how the diagnosis would be scoped, which cohorts it would compare, and what the intervention materials would give your team.
Diagnose adoption
Bring one transformation decision in planning or execution.
Pick a time on the rightbelow to learn more about our research and explore whether it may be relevant to your organization.
30 min
Web conferencing details provided upon confirmation.