agentleFS
poorvith-mppoorvith-mp/skills-business/skills/change-management/SKILL.md

change-management

Skill1 starsChanged 3 months agoMITView on GitHub

Plan organizational change with ADKAR: impact assessment, alignment, and adoption tracking. Use when leading company restructuring or M&A integration.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use andreessen, business-investment-advisor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hussain-ElfalahSkill

    andreessen

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    business-investment-advisor

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 4 projects that use this

  • +8 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ability: Remove psychological and operational barriers.

    line 22
  2. Distinctive:

    When navigating company reorganizations, divestitures, or M&A integrations:

    line 36
  3. Distinctive:

    Never measure change success by training completion.

    line 47
  4. Distinctive:

    NEVER announce a major restructuring without briefing direct managers at least 24 hours prior with tactical Q&A scripts.

    line 59
  5. Distinctive:

    NEVER treat resistance as insubordination.

    line 60
  6. Distinctive:

    NEVER declare victory after the initial rollout phase.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Change Management

Most change resistance is rational: it surfaces a hidden friction, risk, or loss that leadership failed to account for. Effective change management treats resistance as information and structures rollout so that affected teams actively adopt the new operating reality rather than passively waiting out the announcement.

1. Core Frameworks: ADKAR & Kotter Integration

Combine individual-level behavior change (ADKAR) with organizational-level pacing (Kotter):

A. The ADKAR Individual Transition Model

  • Awareness: Establish why the change is happening now and what breaks if nothing changes. Explain the market, financial, or technical imperative in terms of daily frontline impact.
  • Desire: Address personal motivation and loss aversion ("What's in it for me?"). Identify perceived losses (autonomy, status, mastery) and surface trade-offs transparently.
  • Knowledge: Provide practical training tailored to daily role tasks rather than conceptual overviews. Document explicit "stop doing / start doing" behaviors.
  • Ability: Remove psychological and operational barriers. Provide coaching, sandbox environments, and dedicated support during the transition phase.
  • Reinforcement: Align incentive structures, recognition rituals, and KPIs to lock in new behaviors and prevent backsliding to legacy habits.

B. Kotter's 8-Stage Execution Discipline

  1. Create Urgency: Ground the case for change in unignorable data (churn rates, margin decay, system failures).
  2. Build a Guiding Coalition: Assemble cross-functional influencers with operational credibility, not just executive titles.
  3. Form Strategic Vision: Articulate a plain-language target state that frontline employees can explain in two sentences.
  4. Enlist a Volunteer Army / Communicate Multi-Channel: Repeat the core rationale through trusted direct managers, not just company-wide town halls.
  5. Enable Action by Removing Barriers: Eliminate conflicting legacy metrics, outdated approval gates, and redundant tools.
  6. Generate Short-Term Wins: Sequence early milestones achievable within 30–60 days to prove progress and build momentum.
  7. Sustain Acceleration: Leverage early wins to tackle entrenched architectural or organizational bottlenecks.
  8. Institute Change into Culture: Codify new practices into onboarding docs, promotion rubrics, and day-to-day SOPs.

2. Restructuring & M&A Integration Protocol

When navigating company reorganizations, divestitures, or M&A integrations:

  • Day 1 Alignment: Provide clear reporting lines, tool access, and interim approval chains immediately upon close.
  • System Harmonization: Map duplicated systems (CRM, ERP, ticketing) and publish explicit retirement dates for legacy tools.
  • Cultural Due Diligence: Identify conflicting operating norms (e.g. documentation-first vs meeting-first culture) and declare company standards explicitly.

3. Adoption Measurement & Deliverables

  • Stakeholder Impact Assessment: Heatmap of all teams by disruption intensity, readiness score, and operational dependencies.
  • Change Champion Network: Designated peer advocates embedded across each department.
  • Adoption Health Dashboard: Track daily/weekly active usage (DAU/WAU), error rates, and support ticket trends, not merely training session attendance.

Critical Rules

  1. Never measure change success by training completion; measure voluntary, sustained system adoption and legacy tool abandonment.
  2. Direct managers must deliver organizational change messages; company announcements provide context, but direct reports look to their lead for impact.
  3. Pilot all large-scale operational shifts with a high-capacity, high-influence team before company-wide rollouts.

Verification Checklist

  • Business case for change articulates explicit risks of inaction.
  • ADKAR transition plan details specific support mechanisms for each phase.
  • Guiding coalition includes operational leaders across affected departments.
  • Adoption metrics defined by usage thresholds and error rates rather than passive attendance.
  • System deprecation dates and legacy process sunsets formally scheduled.

Anti-Patterns

  • NEVER announce a major restructuring without briefing direct managers at least 24 hours prior with tactical Q&A scripts.
  • NEVER treat resistance as insubordination; investigate the operational friction causing reluctance.
  • NEVER declare victory after the initial rollout phase; reinforcement must continue for at least 90 days.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.