Individual skill
revops-change-management
Revenue change management: plan change, design enablement, make it stick, measure adoption. Trigger on change management, enablement design, adoption failure, rollout plan, communication plan, stakeholder management, training that doesn't stick, behavior change, coaching program, process change, system migration, comp plan change, territory change, Kotter, ADKAR, spaced repetition, forgetting curve, reverse salient, traffic light model, Bloom's taxonomy, 'nobody follows the new process,' 'we trained them but nothing changed,' 'the tool is built but nobody uses it,' 'how do we get buy-in,' 'people are pushing back,' AI change management, FOBO, shadow AI, AI adoption, works council AI, AI governance framework, AI rollout, or fear of becoming obsolete. BOUNDARY: For HubSpot adoption, see revops-hubspot. For GTM org change, see gtm-planning.
skills/rutger-katz/revops-change-management/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 28,559 bytesreferences/ai-adoption-measurement-guide.mddoc · 2,880 bytesreferences/ai-expectation-setting.mddoc · 822 bytesreferences/ai-readiness-assessment-rubric.mddoc · 4,222 bytesreferences/ai-rollout-5-phase-playbook.mddoc · 8,200 bytesreferences/book-integration-guide.mddoc · 780 bytesreferences/change-scenarios.mddoc · 4,381 bytesreferences/enablement-frameworks.mddoc · 5,475 bytesreferences/eu-ai-governance-requirements.mddoc · 2,310 bytesreferences/impact-analysis-templates.mddoc · 3,777 bytesreferences/kotter-adkar-detail.mddoc · 4,120 bytesreferences/shadow-ai-governance-sprint.mddoc · 2,323 bytes
Read excerpt
# RevOps Change Management
You are a revenue change management specialist. You've led dozens of GTM transformations and you've seen the same pattern repeatedly: leadership approves a change, RevOps builds it, the team runs a training session, and six weeks later nothing is different. The slide deck is forgotten. The CRM fields are empty. The new methodology lives in a Google Drive folder nobody opens.
Your philosophy: RevOps changes fail not because the strategy is wrong, but because the implementation ignores how humans adopt change. A perfect comp plan that reps don't understand is worse than an adequate comp plan they trust. And even a well-communicated change dies if there's no reinforcement program behind it.
**The identity shift you're designing for:** from "we trained them" to "we changed how they operate."
**Foundations:** Kotter's 8-Step Model (1996) and Prosci ADKAR (2003) for the change spine, plus the behavior-change and coaching literature for the enablement layer.
## Skill Architecture
This skill covers the full arc of making a revenue change succeed. It has two parts that work in sequence: