Methodfield now includes a complete English and Russian ADKAR learning-and-practice package. It treats adoption as a set of distinct, evidence-backed outcomes—not as a campaign metric or a label applied to people who disagree.
Start with the barrier, not the intervention
ADKAR separates five outcomes of individual change:
Awareness → Desire → Knowledge → Ability → Reinforcement
The practical rule is to find the earliest outcome without sufficient evidence for each affected group. More training is useful for a Knowledge gap. It will not repair an unclear purpose, an unacceptable trade-off, a blocked workflow or a system that still rewards the old behaviour.
The new ADKAR guide shows how to define observable adoption, segment by real differences in context, establish a privacy boundary, diagnose all five outcomes, match support to the earliest barrier and reassess after a bounded intervention.
One method, five connected ways to work
The release connects:
- the bilingual method guide and a structured workspace;
- an in-depth article on avoiding the training trap;
- a lesson, ten-question assessment and three advanced scenarios in Innovation Fundamentals;
- a scored field-service AI adoption case with privacy, safety and authority constraints;
- an original protected infographic and a claim-to-source review record.
The practical case makes the diagnostic difference visible. Technicians who cannot explain the safety need have an Awareness problem. Experienced technicians who reject the removal of legitimate judgement raise a Desire and authority-design issue. Supportive users who fail when connectivity drops face an Ability constraint. One organisation-wide adoption score would hide all three.
Why ADKAR is relevant in Fiction Lab
The Rise of Endymion is the most relevant current Fiction Lab work because its central transformation must spread through a distributed network without keeping its originator as a permanent centre of control.
The work page now includes a dedicated five-stage ADKAR application. It asks whether local participants can explain the change, choose to participate without hidden coercion, teach it, enact it under real conditions and sustain it through peer evidence and founder-independent institutions.
The analogy is intentionally bounded. A civilisation-scale movement is not an employee rollout. ADKAR does not by itself resolve power, legitimacy, institutions, dissent or the right to refuse. Fiction is useful here because it reveals both the model's diagnostic value and what remains outside its frame.
Connected in the Knowledge Map
This release note is itself a new node in the Knowledge Map. Its explicit relations connect the ADKAR method, article, learning path, practice case and Fiction Lab work, so the release can be entered from change management, learning, practice or systems fiction.
The method also connects to Stakeholder Mapping and PDCA/PDSA. Use Stakeholder Mapping when affected groups, power or impact are still unclear. Use PDCA/PDSA to test whether a support intervention changes observed adoption instead of assuming that activity caused the result.
Evidence and ethical boundary
ADKAR is a practical diagnostic heuristic with limited independent causal validation. Published applications show how organisations have used it; they do not establish universal effectiveness or superiority over other change approaches.
The package therefore rejects inferred loyalty scores, emotion detection and hidden employee profiling. Prefer the minimum necessary evidence, role or context aggregates, confidential routes for concerns and a clear separation between coaching information and performance records. The purpose of diagnosis is to improve support and the system—not to make reluctance easier to punish.
Explore the ADKAR method, read the diagnostic article or examine the five-stage application in Fiction Lab.