Adoption Friction Diagnosis

When the adoption curve flattens during the acceleration phase, something is blocking it. The blocker is adoption friction — a barrier that prevents willing users from adopting or prevents adopted users from deepening their usage. Friction comes in three forms: technical (the solution is hard to use), organizational (the organization does not support adoption), and behavioral (users do not see the value). Diagnosing the friction type determines the intervention. Technical friction requires product fixes. Organizational friction requires stakeholder engagement. Behavioral friction requires value demonstration.

1. Technical Friction Signals Users who start the adoption process but do not complete it. High support ticket volume from new users. Common complaints about usability, integration, or performance. Technical friction is the most visible and usually the easiest to address — because it has a specific, identifiable cause and a specific, deliverable fix.
2. Organizational Friction Signals Users who want to adopt but cannot because their manager has not approved it, their team is not using it, or the adoption is not part of their goals. Organizational friction is invisible to product analytics because the barrier is upstream of the product. It surfaces in conversation: "I would use it, but my team has not been told to."
3. Behavioral Friction Signals Users who have access and organizational permission but choose not to engage. They do not see the value, do not believe the solution will help them, or do not want to change their workflow. Behavioral friction is the hardest to overcome because it requires attitude change, not process change. It surfaces as passive non-adoption — no complaints, no tickets, just silence.