Help you truly get good tools adopted—from understanding the current situation to creating a plan, from diagnosing resistance to providing response plans, Claude accompanies you step by step throughout.
Applicable Scenarios
| Scenario | Trigger Signal | Output |
|---|---|---|
| New Tool Introduction | "Which department should we start promoting to?" | Department priority ranking + launch plan |
| Promotion Blocked | "Why are people unwilling to use it?" | Resistance diagnosis + response plan |
| Plan Creation | "How should the Q2 promotion plan be made?" | Phased promotion roadmap |
| Stalled Results | "The adoption rate is stuck at 20% and won't move" | Breakthrough strategy + quick action checklist |
| Non-technical Managers | "I don't understand technology, how should I promote it?" | 5-minute quick assessment + simplified execution path |
Fast Track
5-Minute Quick Assessment
If you don't have time for a full plan, just tell Claude the following information and immediately get promotion priority recommendations:
"Our company has [X] people, divided into [department list]. We want to promote [tool name], currently [current status]."
Claude will immediately provide:
- Which department to start with (priority ranking)
- What to do in the first month (specific action checklist)
- The most likely resistance (early warning + response)
Resistance Diagnosis Fast Track
Stuck on promotion? Just describe the situation you're facing, and Claude will provide a targeted response plan:
"The sales department manager says this has nothing to do with them" "Employees say they don't have time to learn" "Leadership supports it but employees don't use it" "adoption rate stuck at 20%"
Claude will directly diagnose the root cause and provide 3 immediately executable response actions.
Complete Workflow (Claude-led Interaction)
Step 1: Understand the Current Situation (Claude will proactively ask you)
Claude will ask in sequence:
Basic Information(2 minutes)
- Company size and department composition
- What is the tool/Skill you want to promote
- Target coverage scope and time frame
Current Situation Assessment(3 minutes)
- Is there already a pilot or early users?
- Which departments have high acceptance of new technology?
- Have you already encountered resistance? What specifically?
Tip for non-technical managers: You don't need to understand technology, just describe the phenomena you've observed and the difficulties you've encountered, and Claude will help you analyze.
Step 2: Department Analysis (Claude outputs directly)
Based on the information you provide, Claude analyzes each department:
Analysis Dimensions：
- Technology Acceptance: Openness to new technology (High/Medium/Low)
- Usage Frequency Potential: Proportion of daily work AI can help with
- Influence: Demonstration effect on other departments
- Promotion difficulty: Level of training and support required
Output: Department priority scoring table + recommended starting department
Step 3: Identify key roles
Claude helps you find the key people for successful promotion:
Seed users（Seed Users）
- Characteristics: tech-savvy, willing to try, influential
- Role: early trial → provide feedback → word-of-mouth spread
- Number: 1-2 people per department
Key influencers（Key Influencers）
- Characteristics: department heads, opinion leaders
- Role: drive adoption, provide resource support
- Number: 1 person per department
Potential resisters（Resistors）
- Characteristics: conservative, worried about being replaced, accustomed to existing methods
- Response: focused communication, demonstrate concrete value, resolve concerns in advance
Step 4: Develop a promotion plan
Four promotion strategies(Claude recommends based on your situation):
| Strategy | Applicable scenarios | Characteristics |
|---|---|---|
| Technology-driven | Strong and influential technical team | Start with the technical department and gradually expand outward |
| Business-driven | Clear business pain points | Start with the department with the greatest pain points and most significant ROI |
| Top-down | Strong management support | Leaders take the lead in using it, all staff follow |
| Bottom-up | Grassroots innovation culture | Seed users spontaneously spread it, forming organic growth |
Phased plan template：
第一阶段：试点（1-2 周）
- 目标：验证工具可用性和价值
- 范围：1 个部门，5-10 名种子用户
- 重点：收集真实反馈，快速调整
第二阶段：扩展（2-4 周）
- 目标：积累成功案例，扩大使用范围
- 范围：2-3 个部门，20-50 人
- 重点：复制成功经验，建立培训材料
第三阶段：全面推广（4-8 周）
- 目标：覆盖所有目标部门
- 范围：全员或大多数员工
- 重点：持续优化，效果评估，激励机制
Step 5: Resistance prediction and response
Common resistance and response strategies：
| Resistance | Typical manifestations | Root cause | Response strategy |
|---|---|---|---|
| Learning cost | "It's too complicated, I can't learn it" | High perceived tool threshold | Simplify the onboarding path, video tutorials, 1-on-1 coaching |
| Time pressure | "No time to learn new things" | Short-term benefits are not visible | Show ROI data, leadership support, gradual use |
| Trust issues | "AI is unreliable" | Lack of success stories | Manual review mechanism, internal success stories, gradual trust |
| Replacement anxiety | "Will I be replaced by AI?" | Misunderstanding of AI's role | Emphasize the assistive positioning, show skill upgrade opportunities |
| Habitual inertia | "The original way is pretty good" | Perceived switching cost | Comparative demonstrations, colleague recommendations, incentive mechanisms |
| Relevance doubts | "This has nothing to do with us" | Unclear use scenarios | Use the department's specific work scenarios for demonstrations |
Output format
Promotion planning report
Skill 推广规划
━━━━━━━━━━━━━━━━━━━━━━
企业：[企业名称]（[人数]人）
目标：[推广目标描述]
推广策略：[策略类型]
部门优先级排序：
┌────────────────────────────────────────┐
│ 优先级 │ 部门 │ 人数 │ 接受度 │ 建议 │
├────────────────────────────────────────┤
│ 1 │ 技术部 │ 50 │ 高 │ 种子 │
│ 2 │ 产品部 │ 20 │ 高 │ 扩展 │
│ 3 │ 销售部 │ 60 │ 中 │ 重点 │
│ 4 │ 市场部 │ 30 │ 中 │ 跟进 │
│ 5 │ 财务部 │ 20 │ 低 │ 后期 │
│ 6 │ HR部 │ 20 │ 低 │ 后期 │
└────────────────────────────────────────┘
关键角色识别：
- 种子用户：[名单或特征描述]
- 关键影响者：[名单或特征描述]
- 需重点沟通：[名单或特征描述]
推广时间线：
┌────────────────────────────────────────┐
│ 阶段 │ 时间 │ 目标 │ 重点 │
├────────────────────────────────────────┤
│ 试点 │ 第1-2周 │ 技术部 10 人 │ 验证 │
│ 扩展 │ 第3-4周 │ +产品部 20人 │ 培训 │
│ 重点推广 │ 第5-8周 │ +销售部 60人 │ 案例 │
│ 全面覆盖 │ 第9-12周│ 全员 200 人 │ 优化 │
└────────────────────────────────────────┘
预期阻力与应对：
1. [阻力1] → [应对策略]
2. [阻力2] → [应对策略]
3. [阻力3] → [应对策略]
成功指标：
- 第1个月：采用率 > 30%
- 第2个月：采用率 > 60%
- 第3个月：采用率 > 80%
关键成功因素：
1. [因素1]
2. [因素2]
3. [因素3]
Department characteristics reference
Technical department
Characteristics: High technical acceptance, strong learning ability, use cases: code generation, document writing, troubleshooting
Promotion recommendations: Prioritize as a seed department, emphasize efficiency improvement, encourage custom Skills, and let it become a model and internal evangelist for other departments.
Product department
Characteristics: High technical acceptance, frequent cross-department collaboration, use cases: requirements analysis, competitive research, document writing
Promotion recommendations: Promote in sync with the technical department, emphasize collaboration efficiency improvement, and provide product-specific scenario Skills.
Sales department
Characteristics: Medium technical acceptance, results-oriented, use cases: customer communication, proposal writing, data analysis
Promotion recommendations: Use ROI data to make the case (saving X hours per week), provide ready-to-use Skills (no learning curve), and show successful cases from similar companies.
Marketing department
Characteristics: Medium technical acceptance, high demand for creativity, use cases: content creation, data analysis, event planning
Promotion recommendations: Emphasize creative assistance rather than replacement, provide content generation Skills, and show human-machine collaboration efficiency comparisons.
Finance department
Characteristics: Low technical acceptance, high compliance requirements, use cases: report analysis, data processing, audit assistance
Promotion recommendations: Emphasize accuracy and manual review mechanisms, start from low-risk scenarios, and require clear leadership direction to drive adoption.
HR department
Characteristics: Low technical acceptance, frequent interpersonal communication, use cases: resume screening, training materials, policy interpretation
Promotion recommendations: Provide simple and easy-to-use Skills, emphasize assistance rather than replacement, and start with administrative affairs scenarios.
Administrative department
Characteristics: Low technical acceptance, high repetition in daily affairs, use cases: document processing, meeting minutes, internal notices
Promotion recommendations: Start with the most repetitive tasks (such as meeting minutes) and quickly demonstrate the intuitive effect of "how much time was saved."
Corporate culture fit
Innovative companies
Characteristics: Encourage experimentation, tolerate failure Strategy: Bottom-up, rapid iteration Focus: Stimulate innovation, establish an internal sharing mechanism, and let early users' success stories spread naturally
Stable companies
Characteristics: Standardized processes, risk-averse Strategy: Top-down, fully validated Focus: Compliance review, leadership endorsement, and building trust starting from low-risk scenarios
Results-oriented companies
Characteristics: KPI-driven, efficiency-first Strategy: Business-driven, ROI-first Focus: Quantify results (save work hours/increase output), achieve quick wins, and let data speak
A simplified path for non-technical managers
Can you promote it without understanding technology? Absolutely. Follow these steps:
Step 1: Find your seed users (Week 1)
- Find 2-3 influential colleagues who are interested in new things
- Ask them to try it for 1 week and record "what time it saved me"
Step 2: Collect the first batch of success stories (Weeks 2-3)
- Have seed users share 1 real usage experience with the team
- Collect 3-5 specific examples ("Use it to write meeting minutes, from 30 minutes down to 5 minutes")
Step 3: Leverage success stories to spread (Weeks 4-8)
- Showcase these cases in departmental meetings
- Ask seed users to help bring in new users, forming a "mentor-apprentice" system
Step 4: Leaders set an example (ongoing)
- Management uses it themselves and demonstrates the value the tool brings in reports/meetings
- This is the strongest promotion signal
Example: A 3-month promotion plan for a 300-person company
Scenario: The R&D department (80 people) is already using Claude Code, and now it needs to be promoted company-wide. The sales department says "It's fine," and the administrative department says "We can't learn it."
Claude's analysis and recommendations：
推广规划（300人公司，3个月）
━━━━━━━━━━━━━━━━━━━━━━
推广策略：技术驱动 + 分部门定制
部门优先级：
1. 产品部（30人）- 与研发协作密切，接受度高，第1个月
2. 运营部（50人）- 有数据分析需求，中等接受度，第2个月
3. 销售部（100人）- 需展示业务价值，第2-3个月
4. 行政部（40人）- 需简化入门，第3个月
销售部阻力应对（"没关系"）：
→ 根因：没看到和自己工作的具体关联
→ 对策：用销售场景做演示（"用 AI 帮你写客户跟进邮件"），
邀请研发部的成功用户做内部分享
行政部阻力应对（"学不会"）：
→ 根因：学习门槛感知过高
→ 对策：提供"5分钟上手"教程，专注单一场景（会议纪要），
请 HR 或行政负责人作为种子用户带头
成功指标：
- 第1个月末：产品部采用率 > 70%
- 第2个月末：运营+销售采用率 > 40%
- 第3个月末：全员采用率 > 60%
Notes
- Adapt to local conditions: Every company's situation is different, and the plan needs to be adjusted flexibly. Claude will customize recommendations based on your description.
- Continuous communication: Maintain communication with all departments throughout the promotion process. Whenever you encounter new resistance, come back for diagnosis at any time.
- Rapid response: Stalled adoption is normal; the key is to quickly identify the root cause and adjust.
- Celebrate success: Share success stories to motivate more people to participate and let good results spread on their own.