Locate the binding adoption threshold before teams fund awareness, trust, communication, product, or conversion interventions against the wrong break.
Use when
Sales, adoption, participation, or conversion is weak and teams are proposing different fixes without agreeing where movement is actually dying.
What it prevents
Awareness, trust, communication, and product interventions being funded as one generic “conversion” problem.
Run it
- Put the canonical thresholds on the table: Attention → Meaning → Permission → Trust → Action → Sustained Adoption.
- For the defined person/cluster, write the evidence that the threshold is present, weak, or unknown.
- Identify the current leading break and the strongest competing break.
- Match one intervention to that threshold.
- State the evidence that would move the diagnosis upstream or downstream.
Redline example
People who already cite the proof desk have Attention and much of Meaning. Permission and Trust attach specifically to proof and earned access. The visible break is Action under the current VIP/membership pathway; Sustained Adoption is unknown because Dayline has not launched. Buying more awareness would test the wrong stage.
Your live decision
Name the person, the stage that appears broken, the evidence for the diagnosis, and the next intervention.
Route next
Complete FN09 / Adoption Threshold Diagnosis. If machine/procurement control changes the path, add FN10 / Decision Locus & AI Expansion Map.
Stop rule
If changing the named threshold does not move behavior, update the diagnosis rather than blaming execution indefinitely.
Core Field Read update
Record the binding threshold, matched intervention, alternative hypothesis, falsifier, and what remains unknown.