adoption-plan

name	adoption-plan
description	Build a customer adoption plan that connects desired outcomes to workflows, users, prerequisites, enablement, milestones, ownership, product evidence, and measurable value realization.

Customer Adoption Plan

Use when a customer has purchased or committed but needs a deliberate path from access to durable product use.

Procedure

1. Define customer outcomes, priority use cases, stakeholders, target users, existing workflow, and constraints.
2. Map the smallest set of product capabilities and integrations needed to deliver the first meaningful value.
3. Identify prerequisites such as data, permissions, configuration, training, security review, migration, or internal customer decisions.
4. Sequence milestones from setup through first value, repeat use, broader team adoption, and mature operation as appropriate.
5. Assign customer and provider owners to each dependency and milestone so adoption does not become an unowned checklist.
6. Plan enablement by audience and task rather than delivering the same training to every stakeholder.
7. Define adoption and outcome measures plus review dates and warning conditions for stalled progress.
8. Adjust the plan from observed use and customer feedback rather than forcing the original timeline after circumstances change.

Decision rules

• Adoption is achieved value, not license activation.
• Start with the smallest workflow that proves usefulness.
• Customer-owned dependencies need explicit owners too.
• Training should solve actual workflow needs.

Quality gate

The plan is ready when customer outcomes map to concrete workflows and milestones, prerequisites and owners are explicit, first-value and repeat-value measures exist, enablement fits each audience, and progress can be adjusted from evidence rather than account-team optimism.