name: sofka-adoption-strategy
author: Equipo PreSales Sofka
description: >
Adoption strategy design producing communication plan, training roadmap, resistance management tactics, and reinforcement mechanisms.
Use when the user asks to "design adoption strategy", "plan change adoption", "communication plan", "training needs analysis",
"resistance management", "adoption roadmap", "change communication", or mentions "post-implementation adoption",
"user onboarding strategy", "technology adoption plan".
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- Bash

Adoption Strategy

Designs a comprehensive adoption strategy: phased rollout plan, stakeholder communication strategy, training needs analysis and curriculum design, resistance management tactics, reinforcement mechanisms, and adoption KPIs with measurement cadence.

Guiding Principle

Adoption is not an event, it is a process. It does not end at go-live — it begins there. Every user who does not adopt represents an investment that does not return.

1. Adoption is designed, not hoped for. Each stakeholder group requires a deliberate strategy of awareness, enablement, and reinforcement. "Send an email and run a training" is not a strategy.
2. Communication is 60% of adoption. People adopt what they understand, value, and trust. The right message to the right group at the right time is more powerful than any training.
3. Measuring adoption without acting on the metrics is theater. Every KPI must have a threshold that triggers a concrete intervention.

Inputs

• $1 — Path to project context (change readiness assessment, solution roadmap, stakeholder map)
• $2 — Strategy scope: full (default), communication (comms plan only), training (training plan only)

Parse from $ARGUMENTS.

Parameters:
- {MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
- {FORMATO}: markdown (default) | html | dual | pptx (sponsor presentation)
- {MODO_OPERACIONAL}: estrategia (default, full strategy) | comunicacion (communication plan focus) | capacitacion (training plan focus)
- {VARIANTE}: ejecutiva (~40% — rollout phases + KPIs) | técnica (full, default)

Input Requirements

Mandatory:
- Defined change/transformation (what is being adopted)
- Stakeholder groups identified (who needs to adopt)

Recommended:
- Change readiness assessment (ADKAR scores, resistance map)
- Solution roadmap (phases, timeline)
- Current communication channels inventory
- Training infrastructure assessment (LMS, facilitators, budget)

Assumptions & Limits

Assumptions:
- Change has executive sponsorship
- Timeline for adoption is defined (at least rough phases)
- Budget for communication and training exists (even if limited)

Cannot do:
- Execute communication campaigns (designs them)
- Deliver training (designs curriculum and materials spec)
- Resolve interpersonal conflicts or political dynamics
- Guarantee adoption rates (provides strategy to maximize them)

Workarounds When Inputs Missing

Edge Cases

• Global rollout (multi-timezone, multi-language): Localization matrix per region. Cultural adaptation of messaging. Train-the-trainer cascade.
• Mandatory adoption (compliance-driven): Compliance deadlines as hard milestones. Legal language in communications. Audit trail for training completion.
• Voluntary adoption (tools/practices): Incentive design. Champion network. Gamification considerations.
• Phased rollout with pilot: Pilot selection criteria, feedback loop design, go/no-go criteria for scale.
• Remote-only teams: Digital-first communication strategy. Async training options. Virtual champion network.
• Change fatigue present: Lighter-touch strategy. Integrate into existing ceremonies. Avoid "another initiative" framing.

Trade-off Matrix

8-Section Framework

S1: Adoption Context & Goals

Change summary, affected stakeholder groups (from readiness assessment), adoption timeline, success definition (quantitative targets: adoption rate %, proficiency %, satisfaction score).

S2: Rollout Strategy

Phased approach: Pilot → Early adopters → Majority → Laggards. Per phase: scope, duration, entry criteria, exit criteria, rollback plan. Wave planning for large organizations.

S3: Communication Plan

Per stakeholder group: key messages (why, what, how, when), preferred channels, sender (who delivers the message matters), frequency, feedback mechanism. Communication calendar (Gantt).

Message framework by ADKAR stage:
- Awareness: Business case, urgency, vision
- Desire: WIIFM (What's In It For Me), success stories, sponsor endorsement
- Knowledge: How-to guides, FAQs, demos
- Ability: Practice opportunities, support channels
- Reinforcement: Success celebrations, metrics sharing, recognition

S4: Training Needs Analysis & Curriculum

Per role: current skills, required skills, gap analysis, training method (classroom, e-learning, peer, on-the-job), duration, materials needed. Curriculum map with prerequisites and sequencing.

S5: Resistance Management

Per resistance type identified in readiness assessment: tactic, responsible party, timeline. Tactics catalog: education, participation, facilitation, negotiation, co-optation. Escalation path for unresolved resistance.

S6: Champion Network Design

Champion selection criteria, champion responsibilities, champion enablement plan (train-the-trainer), champion communication cadence, champion recognition/incentive structure.

S7: Reinforcement Mechanisms

Post-go-live: coaching plan, help desk/support model, knowledge base maintenance, feedback loops, iteration cadence for process improvements. Sustainability plan (what happens when the project team leaves).

S8: Adoption KPIs & Measurement

| KPI | Definition | Target | Measurement Method | Cadence | Intervention Threshold |
Per KPI: what triggers action, what action is triggered. Dashboard specification.

Core KPIs: adoption rate, proficiency rate, utilization rate, satisfaction (NPS/CSAT), time-to-competency, support ticket volume.

Cross-Section Traceability

• S1 Goals → S8 KPIs (goals define success metrics)
• S2 Rollout → S3 Communication (phase drives message timing)
• S2 Rollout → S4 Training (phase drives training schedule)
• S3 Communication → S5 Resistance (messaging addresses resistance)
• S4 Training → S6 Champions (champions deliver peer training)
• S5 Resistance → S7 Reinforcement (unresolved resistance needs sustained attention)
• S7 Reinforcement → S8 KPIs (reinforcement sustains adoption metrics)

Escalation to Human

• Adoption rate <30% after Phase 2 (majority rollout)
• Executive sponsor disengaged or actively resistant
• Training budget eliminated mid-execution
• Champion network cannot be established (no volunteers, no mandated participation)
• Cultural/language barriers require specialist localization

Execution Workflow

1. Context Review (1-2 hours): Ingest readiness assessment, stakeholder map, solution roadmap
2. Strategy Design (3-5 hours): Rollout phases, communication plan, training curriculum
3. Resistance & Champions (2-3 hours): Resistance tactics, champion network design
4. Measurement (1-2 hours): KPIs, dashboard spec, intervention thresholds

Typical engagement: 3-4 days for transformations affecting <500 users.

Output Configuration

• Language: Spanish (Latin American, business register — simple, clear, concise, direct)
• Attribution: Expert committee of the Sofka Discovery Framework
• Tagline: "Construido por profesionales, potenciado por la red agéntica de Sofka."

Output Artifact

Primary: Estrategia_Adopcion_{project}.md (or .html if {FORMATO}=html|dual) — Full 8-section adoption strategy.

Secondary: Plan_Comunicacion_{project}.md — Communication calendar + message templates.

Included diagrams:
- Gantt chart: rollout phases and communication calendar
- Flowchart: escalation path for resistance management
- Mindmap: champion network structure

Validation Gate

• [ ] All 8 sections populated with evidence-based content
• [ ] Communication plan covers all stakeholder groups from S1
• [ ] Training curriculum aligned with role-based gaps from S4
• [ ] Every resistance type from readiness assessment has a tactic in S5
• [ ] KPIs have concrete targets and intervention thresholds
• [ ] Champion network design is actionable (not aspirational)
• [ ] Cross-section traceability complete

Output Format Protocol

Operational Modes

Additional Resources

References (Progressive Disclosure — Level 3)

• Read ${CLAUDE_SKILL_DIR}/references/knowledge-graph.mmd — Domain knowledge graph
• Read ${CLAUDE_SKILL_DIR}/references/body-of-knowledge.md — Academic and industry sources
• Read ${CLAUDE_SKILL_DIR}/references/state-of-the-art.md — Trends 2024-2026

Examples

• Read ${CLAUDE_SKILL_DIR}/examples/sample-output.md — Golden reference output
• Read ${CLAUDE_SKILL_DIR}/examples/sample-output.html — Branded HTML

Prompts

• Read ${CLAUDE_SKILL_DIR}/prompts/use-case-prompts.md — Ready-to-use prompts
• Read ${CLAUDE_SKILL_DIR}/prompts/metaprompts.md — Meta-strategies