@monoes/monomindcli 2.15.3 → 2.15.5

package/org-skills/cfo-advisor/references/fundraising_playbook.md

@@ -0,0 +1,419 @@
+# Fundraising Playbook
+
+From timing to close. What investors actually look for, how valuation works, and the term sheet clauses that matter.
+
+---
+
+## 1. When to Raise
+
+**Optimal timing:**
+```
+Target: 18-24 months runway post-close
+Minimum: 12 months runway post-close (leaves no buffer for slip)
+
+Start process when: 9-12 months runway remaining
+  → 3-6 months for process (typically 4-5 months for Series A/B)
+  → Leaves 3-6 months buffer if process drags
+
+Never start when: < 6 months runway
+  → You're negotiating from desperation
+  → Investors can smell it
+  → Terms get worse, or you don't close at all
+```
+
+**Rule:** Your leverage is maximum when you don't *need* to raise. Raise from a position of momentum, not necessity.
+
+---
+
+## 2. What Investors Look For at Each Stage
+
+### Pre-seed
+- Team (are these people credible for this problem?)
+- Problem clarity (is the problem real and meaningful?)
+- Early signal (any customers paying, waitlist, prototype)
+- Market size (worth building a VC-scale company?)
+
+**Typical ask:** $500K–$2M | **Typical valuation:** $3M–$10M pre-money
+
+### Seed
+- Product-market signal (customers using and paying)
+- Founding team with domain expertise
+- ARR: $100K–$1M (or strong usage for PLG)
+- Clear hypothesis for what Series A looks like
+
+**Typical ask:** $2M–$5M | **Typical valuation:** $8M–$20M pre-money
+
+### Series A
+
+Investors are buying a *repeatable sales motion*. Not just customers — a machine.
+
+**What they need to see:**
+- ARR: $1M–$5M growing > 100% YoY
+- LTV:CAC > 2.5x (and improving)
+- Net Dollar Retention > 100%
+- CAC Payback < 18 months
+- Gross margin > 65%
+- At least 5-10 reference customers (not just lighthouse)
+- Sales motion that converts without the founder closing every deal
+
+**Typical ask:** $8M–$15M | **Typical valuation:** $25M–$60M pre-money
+
+### Series B
+
+Investors are buying *scalable go-to-market*. Can you pour fuel on the fire?
+
+**What they need to see:**
+- ARR: $5M–$20M growing > 100% YoY
+- LTV:CAC > 3x, CAC Payback < 18 months
+- Sales capacity model (hiring plan → pipeline → revenue)
+- NDR > 110% (expansion motion working)
+- Some proof of market expansion (new segments, geographies, use cases)
+- Path to category leadership
+
+**Typical ask:** $15M–$40M | **Typical valuation:** $60M–$200M pre-money
+
+### Series C and Beyond
+
+Investors are buying *market leadership* and *path to profitability*.
+
+**What they need to see:**
+- ARR: $20M+ (often $30-50M for credible Series C)
+- Rule of 40 > 40 (or credible path)
+- Gross margin > 70%
+- NDR > 115%
+- Evidence of market leadership (brand, win rates, analyst mentions)
+- Clear path to $100M+ ARR
+
+---
+
+## 3. Valuation Methods
+
+### Revenue Multiples (Primary Method for SaaS)
+
+```
+Pre-money Valuation = ARR × Revenue Multiple
+
+Revenue multiple benchmarks (2024-2025):
+  > 100% YoY growth:  8x–15x ARR
+  50-100% YoY growth: 4x–8x ARR
+  20-50% YoY growth:  2x–4x ARR
+  < 20% YoY growth:   1x–2x ARR
+
+Adjustments:
+  NDR > 120%:          +1x–2x premium
+  Gross margin > 75%:  +0.5x–1x premium
+  Burn multiple < 1x:  +0.5x–1x premium
+  Capital efficient:   Investors pay up for efficiency
+  Declining growth:    Compress multiple aggressively
+```
+
+### The Investor's Math (Know This)
+
+Every VC has a required return. Work backwards from their constraints:
+
+```
+Investor targets: 3x fund return
+Fund size: $200M, check size: $15M (initial), $25M (with follow-on)
+Ownership at exit needed: 15%
+At 15% ownership: needs $25M / 15% = $167M post-money valuation
+Exit needed to return 3x on that check: $25M × 10 = $250M company value
+  (10x because most deals fail, winners must carry the fund)
+
+Implication: If you think you'll exit for $150M, that VC will pass or price you accordingly.
+```
+
+This is why Series A investors rarely lead rounds where they can't see a $300M+ exit path. It's not about your business being bad — it's about fund math.
+
+### Comparable Company Analysis
+
+For later stages (Series B+):
+
+```
+1. Find 5-10 comparable public SaaS companies
+2. Calculate their EV/NTM Revenue multiples (use latest data)
+3. Apply a private market discount (typically 20-40% vs public comps)
+4. Adjust for your growth rate relative to comps
+
+Example (2024):
+  Public SaaS comps: 6x NTM Revenue (median)
+  Private discount: 30%
+  Adjusted: ~4.2x
+  Your NTM Revenue: $8M
+  Implied valuation: ~$33M pre-money
+```
+
+### DCF (Late Stage Only)
+
+DCF is unreliable for early-stage startups (terminal value dominates, growth rate assumptions are fantasy). Use it as a sanity check at Series C+, not as the primary valuation method.
+
+---
+
+## 4. Term Sheet Breakdown
+
+### Liquidation Preference (Most Important Economic Term)
+
+This determines who gets paid first in an exit — and how much.
+
+```
+1x Non-Participating Preferred (BEST for founders):
+  Investor gets 1x money back OR converts to common (their choice).
+  At acquisition: investor takes larger of {1x invested} or {% ownership × proceeds}
+  Example: $10M invested, exits at $100M, owns 20%
+    Option A: $10M (1x)
+    Option B: $20M (20% of $100M)
+    Investor takes $20M. Founders split $80M.
+
+1x Participating Preferred (WORSE for founders):
+  Investor gets 1x money back AND participates in remaining proceeds.
+  Example: same scenario
+    $10M (1x) + 20% of remaining $90M = $10M + $18M = $28M
+    Founders split $72M instead of $80M
+    Cost to founders: $8M (10% of exit value)
+
+2x Participating (RED FLAG):
+  Investor gets 2x back AND participates.
+  Only accept under duress. Push hard against this.
+
+Full Ratchet Anti-Dilution (AVOID):
+  Down-round triggers full repricing of investor shares to new (lower) price.
+  Founders get massively diluted. Never accept if alternatives exist.
+```
+
+### Anti-Dilution Protection
+
+```
+Broad-based weighted average (standard):
+  Adjusts investor conversion price based on all dilutive securities.
+  Most founder-friendly anti-dilution. Accept this.
+
+Narrow-based weighted average (slightly worse):
+  Same mechanism but uses smaller denominator.
+  Gives investors slightly more protection. Usually acceptable.
+
+Full ratchet (avoid):
+  Price drops to whatever the new round prices at.
+  Devastating in down rounds. Fight this.
+```
+
+### Pro-Rata Rights
+
+```
+Standard pro-rata: Investor can maintain their % ownership in future rounds.
+  Reasonable. Accept for major investors.
+
+Super pro-rata: Investor can increase their % in future rounds.
+  Caps your ability to bring in new lead investors.
+  Avoid unless the investor is exceptional and you want them in future rounds.
+
+Major investor threshold: Typically investors with > $500K–$1M check get pro-rata.
+  Don't give pro-rata to every small check — clogs future rounds.
+```
+
+### Board Composition
+
+```
+Seed (3 members):     2 founders, 1 lead investor
+Series A (5 members): 2 founders, 2 investors, 1 independent
+Series B (5-7 seats): Watch for investor majority — negotiate hard
+
+Rule: Founders should retain majority through Series A.
+      Independent director should be your choice, not investor's.
+      Never accept investor majority before Series C.
+
+Board observer rights: Common for smaller investors. No vote but present in meetings.
+                       Limit to 1-2 observers or meetings become unwieldy.
+```
+
+### Other Terms That Matter
+
+```
+Drag-along: Majority can force minority shareholders to vote for acquisition.
+  Standard and reasonable. Check what threshold triggers drag.
+
+Information rights: Investors get financial statements.
+  Standard. Monthly for major investors, quarterly for others.
+
+Redemption rights: Investors can force buyback after X years.
+  Push to remove or add carve-outs for insufficient funds.
+
+No-shop clause: You can't shop the term sheet to other investors.
+  Standard (14-30 days). Reasonable.
+
+Exclusivity: Stronger version of no-shop. Sometimes includes no other fundraise discussions.
+  Acceptable for 30 days; push back on > 45 days.
+```
+
+---
+
+## 5. Cap Table Management
+
+### Dilution Planning Model
+
+Run this before every round. Know your number before walking into any negotiation.
+
+```
+         Pre-Seed    Post-Seed    Post-A    Post-B    Post-C
+Founder A  45.0%      36.0%       26.5%     21.2%     18.7%
+Founder B  45.0%      36.0%       26.5%     21.2%     18.7%
+Angel 1     5.0%       4.0%        2.9%      2.4%      2.1%
+Angel 2     5.0%       4.0%        2.9%      2.4%      2.1%
+Seed Fund      -      12.0%        8.8%      7.1%      6.2%
+Option Pool    -       8.0%       12.0%     10.0%      8.0%
+Series A       -          -       20.4%     16.3%     14.4%
+Series B       -          -           -     19.5%     17.2%
+Series C       -          -           -         -     12.6%
+
+Round size / pre-money:
+Pre-Seed: $500K / $9M pre = 5% dilution
+Seed: $2M / $8M pre = 20% dilution (includes 8% pool)
+Series A: $10M / $38M pre = 20.8% dilution (pool refresh to 12%)
+Series B: $20M / $80M pre = 20% dilution
+Series C: $30M / $170M pre = 15% dilution
+```
+
+**Option pool shuffle:** Investors often require you to create/expand the option pool *before* the round closes, which dilutes existing shareholders (not the incoming investor). Model this explicitly — a 20% round with a 5% pool expansion is really 24%+ dilution to founders.
+
+### Cap Table Hygiene
+
+```
+Tools: Carta, Pulley, Capshare (all acceptable)
+Never: Track cap table in a spreadsheet past seed stage. Errors compound.
+
+Keep it clean:
+  - Repurchase departed co-founder shares immediately (don't let unvested shares linger)
+  - Convert SAFEs to equity cleanly at each priced round
+  - Document every grant with a board resolution
+  - Cliff + vesting for ALL employees and founders (standard: 1-year cliff, 4-year vest)
+  - 409A valuation required before every option grant (IRS requirement)
+```
+
+---
+
+## 6. Data Room Preparation
+
+### Core Documents (Required)
+
+```
+Financial:
+  □ 3 years historical financials (or all history if < 3 years)
+  □ Monthly P&L and cash flow (last 24 months)
+  □ Current financial model (18-24 months forward)
+  □ Budget vs actual (last 4 quarters)
+  □ Cap table (fully diluted, with all SAFEs/convertibles modeled)
+  □ Bank statements (last 3-6 months)
+
+Legal:
+  □ Certificate of incorporation + all amendments
+  □ All prior financing documents (SAFEs, convertible notes, stock purchase agreements)
+  □ Cap table (Carta/Pulley export)
+  □ IP assignment agreements (all founders and employees)
+  □ Material contracts (top 10 customers, key vendors)
+  □ Employee list (titles, start dates, salaries, equity grants)
+
+Product & Business:
+  □ Product demo / walkthrough video
+  □ Architecture overview (for technical investors)
+  □ Customer case studies (3-5 named references)
+  □ NPS / CSAT data
+  □ Competitive landscape analysis
+
+Metrics:
+  □ MRR/ARR by month (all history)
+  □ Cohort retention chart
+  □ CAC by channel
+  □ LTV by cohort
+  □ NPS trend
+```
+
+### What Investors Actually Check First
+
+In order of typical priority during due diligence:
+
+1. **Cap table** — Is it clean? Any concerning structures?
+2. **Cohort retention** — Is churn improving or deteriorating?
+3. **Revenue quality** — What % is recurring? Any one-time or non-recurring?
+4. **Top 10 customers** — Concentration risk? Any logos at risk?
+5. **Bank statements** — Does cash match what was reported?
+6. **IP assignments** — Does the company own its IP? (Founders who didn't assign IP kill deals)
+
+### Red Flags That Kill Deals
+
+- Missing IP assignment agreements for founders (most common deal killer at early stage)
+- Cap table with > 20 angels/small investors (messy, hard to get consent for future rounds)
+- Customer concentration > 30% in single customer without explanation
+- Revenue recognition issues (booking ARR on contracts that allow easy cancellation)
+- Cohort data that gets worse in later cohorts
+- Bank balance doesn't match reported cash position
+
+---
+
+## 7. Investor Communication Cadence
+
+### During Fundraise
+
+```
+Week 1-2:   Warm intro sourcing, LP/network mapping
+Week 3-6:   First meetings (aim for 20-30 first meetings)
+Week 7-10:  Partner meetings, deep dives, due diligence
+Week 11-14: Term sheets, negotiation
+Week 15-18: Legal, closing
+```
+
+**Parallel process is essential.** Never negotiate with one investor at a time. Competition is your leverage.
+
+### Post-Close: Investor Updates
+
+Monthly investor update (send within 10 days of month-end):
+
+```
+Subject: [Company] Monthly Update — [Month Year]
+
+Highlights (3 bullets max):
+  • [Biggest win]
+  • [Biggest learning/challenge]
+  • [What we're focused on next month]
+
+Metrics:
+  ARR: $X (+X% MoM)
+  Net new ARR: $X
+  Gross margin: X%
+  Cash: $X (X months runway)
+  Headcount: X
+
+Asks (be specific):
+  • Looking for intro to [persona/company] for [specific reason]
+  • Need advisor with experience in [specific area]
+  • [Other concrete ask]
+```
+
+**Why this matters:** Investors who are informed and engaged are better positioned to help when you need it. The investor who hasn't heard from you in 6 months is less likely to write a bridge check or make a warm intro when you ask.
+
+---
+
+## Key Formulas
+
+```python
+# Post-money valuation
+post_money = pre_money + investment_amount
+
+# Investor ownership %
+ownership_pct = investment_amount / post_money
+
+# Dilution to existing shareholders
+dilution = investment_amount / post_money  # as a fraction
+
+# New shares issued
+new_shares = (investment_amount / post_money) * total_post_shares
+# equivalent: new_shares = pre_money_shares * (investment_amount / pre_money)
+
+# Option pool expansion impact (pool shuffle)
+# Creating X% option pool pre-close dilutes founders:
+pool_shares_needed = target_pct * (pre_shares + new_round_shares + pool_shares_needed)
+# Solve: pool_shares_needed = target_pct * (pre_shares + new_round_shares) / (1 - target_pct)
+
+# LTV:CAC ratio
+ltv_cac = ltv / cac  # target: > 3x
+
+# CAC payback (months)
+payback_months = cac / (arpa * gross_margin_pct)
+```

package/org-skills/change-management/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Alireza Rezvani
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/org-skills/change-management/SKILL.md

@@ -0,0 +1,250 @@
+---
+name: change-management
+description: "Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes."
+tags: ["leadership","operations"]
+tools: []
+license: MIT
+source: https://github.com/alirezarezvani/claude-skills
+source_path: "c-level-advisor/skills/change-management"
+source_commit: 19392f7a08264ed00486a251f5b2098321771f94
+---
+# Change Management Playbook
+
+Most changes fail at implementation, not design. The ADKAR model tells you why and how to fix it.
+
+## Keywords
+change management, ADKAR, organizational change, reorg, process change, tool migration, strategy pivot, change resistance, change fatigue, change communication, stakeholder management, adoption, compliance, change rollout, transition
+
+## Core Model: ADKAR Adapted for Startups
+
+ADKAR is a change management model by Prosci. Original version is for enterprises. This is the startup-speed adaptation.
+
+### A — Awareness
+
+**What it is:** People understand WHY the change is happening — the business reason, not just the announcement.
+
+**The mistake:** Communicating the WHAT before the WHY. "We're moving to a new CRM" before "here's why our current process is killing us."
+
+**What people need to hear:**
+- What is the problem we're solving? (Be honest. If it's "we need to cut costs," say that.)
+- Why now? What would happen if we didn't change?
+- Who made this decision and how?
+
+**Startup shortcut:** A 5-minute video from the CEO or decision-maker explaining the "why" in plain language beats a formal change announcement document every time.
+
+---
+
+### D — Desire
+
+**What it is:** People want to make the change happen — or at least don't actively resist it.
+
+**The mistake:** Assuming communication creates desire. Awareness ≠ desire. People can understand a change and still hate it.
+
+**What creates desire:**
+- "What's in it for me?" — answer this for each stakeholder group, honestly
+- Involving people in the "how" even if the "what" is decided
+- Addressing fears directly: "Some people are worried this means their role is changing. Here's the truth: [honest answer]"
+
+**What destroys desire:**
+- Pretending the change is better for everyone than it is
+- Ignoring the legitimate losses people will experience
+- Making announcements without any consultation
+
+**Startup shortcut:** Run a short "concerns and questions" session within 48 hours of announcement. Not to reverse the decision — to address the fears and show you're listening.
+
+---
+
+### K — Knowledge
+
+**What it is:** People know HOW to operate in the new world — the specific skills, behaviors, and processes.
+
+**The mistake:** Announcing the change and assuming people will figure it out.
+
+**What people need:**
+- Step-by-step documentation of new processes
+- Training or practice sessions before go-live
+- Clear answers to "what do I do when [common scenario]?"
+- Who to ask when they're stuck
+
+**Types of knowledge transfer:**
+| Method | Best for | When |
+|--------|---------|------|
+| Live training | Skill-based changes, complex tools | Before go-live |
+| Documentation | Process changes, reference material | Always |
+| Video walkthroughs | Tool migrations | Available 24/7, self-paced |
+| Shadowing / peer learning | Behavior changes | Weeks 2–4 after launch |
+| Office hours | Any change with many edge cases | First 4–6 weeks |
+
+---
+
+### A — Ability
+
+**What it is:** People have the time, tools, and support to actually do things differently.
+
+**The mistake:** "We've trained everyone" ≠ "everyone can now do it." Training is knowledge. Ability is practice.
+
+**What creates ability:**
+- Time to practice before being evaluated
+- A safe environment to make mistakes (no public shaming for early struggles)
+- Reduced load during transition (if you're asking people to learn new skills, don't simultaneously pile on new work)
+- Access to help (a Slack channel, a point person, documentation)
+
+**Signs of ability gap:**
+- People revert to old behavior under pressure
+- Workarounds emerge (people invent their own way around the new system)
+- Training scores are high but actual behavior hasn't changed
+
+---
+
+### R — Reinforcement
+
+**What it is:** The change sticks. The new behavior becomes the default.
+
+**The mistake:** Declaring victory at go-live. Changes fail because they're never reinforced.
+
+**What creates reinforcement:**
+- Visible measurement (are we tracking adoption?)
+- Recognition of early adopters ("Sarah fully migrated to the new workflow in week 2 — ask her how")
+- Leader modeling (if the CEO uses the old way, everyone will)
+- Removing the old option (when possible — eliminate the path of least resistance)
+- Consequences for non-adoption (stated clearly, applied consistently)
+
+**Adoption vs. compliance:**
+- **Compliance:** People do it when watched, revert when not
+- **Adoption:** People do it because they believe it's better
+
+Only reinforcement creates adoption. Compliance is the result of enforcement. Aim for adoption.
+
+---
+
+## Change Types and ADKAR Application
+
+### Process Change (new tools, new workflows)
+
+**Timeline:** 4–8 weeks for full adoption
+**Hardest phase:** Ability (people know what to do but haven't built the habit)
+**Critical reinforcement:** Remove or deprecate the old tool/process
+
+**Communication sequence:**
+1. Week -2: Announce the why + go-live date
+2. Week -1: Training sessions available
+3. Week 0 (go-live): Launch + point person available
+4. Week 2: Adoption check-in (who's using it? Who isn't?)
+5. Week 4: Feedback collection + public wins
+6. Week 8: Old system deprecated
+
+---
+
+### Org Change (reorg, new leader, team splits/merges)
+
+**Timeline:** 3–6 months for full stabilization
+**Hardest phase:** Desire (people fear for their roles and relationships)
+**Critical reinforcement:** Consistent behavior from new leadership
+
+**Communication sequence:**
+1. Day 0: Announce the change with the "why" — in person or synchronous video
+2. Day 1: 1:1s with most affected team members by their manager
+3. Week 1: FAQ published with honest answers to the 10 most common concerns
+4. Week 2–4: New structure is operating (don't delay implementation)
+5. Month 2: First retrospective — what's working, what needs adjustment
+6. Month 3–6: Regular check-ins on team health and morale
+
+**What to say when a leader is leaving or being replaced:**
+Be honest about what you can share. Never: "We can't share the reasons." Always: either a truthful explanation or "we're not able to share the specifics, but I can tell you [what this means for you]."
+
+---
+
+### Strategy Pivot (new direction, killed products)
+
+**Timeline:** 3–12 months for full alignment
+**Hardest phase:** Awareness (people don't believe the pivot is real)
+**Critical reinforcement:** Resource reallocation that visibly proves the pivot is happening
+
+**Communication sequence:**
+1. Internal first, always. Employees should never hear about a pivot from a press release.
+2. All-hands with full context: what changed in the market, what you're doing, what it means for teams
+3. Each team leader runs a "what does this mean for us?" conversation with their team
+4. Resource reallocation announced within 2 weeks (if the money doesn't move, people won't believe the pivot)
+5. First milestone of the new direction celebrated publicly
+
+**What kills pivots:** Announcing a new direction while still funding the old one at the same level.
+
+---
+
+### Culture Change (values refresh, behavior expectations)
+
+**Timeline:** 12–24 months for genuine behavior change
+**Hardest phase:** Reinforcement (behavior doesn't change just because values were announced)
+**Critical reinforcement:** Visible decisions that reflect the new values
+
+**Communication sequence:**
+1. Build with input: involve a representative sample of the company in defining the change
+2. Announce with story: "Here's what we observed, here's what we're changing and why"
+3. Behavior anchors: for each culture change, state the specific behavior in observable terms
+4. Leader behavior: leadership team must visibly model the new behavior first
+5. Performance integration: new expected behaviors appear in reviews within one cycle
+6. Celebrate the right behaviors: when someone exemplifies the new culture, name it publicly
+
+---
+
+## Resistance Patterns
+
+Resistance is information, not defiance. Diagnose before responding.
+
+| Resistance pattern | What it signals | Response |
+|-------------------|-----------------|---------|
+| "This won't work" | Awareness gap or credibility gap | Explain the evidence base for the change |
+| "Why now?" | Awareness gap | Explain urgency — what happens if we don't change |
+| "I wasn't consulted" | Desire gap | Acknowledge the gap; involve them in the "how" now |
+| "I don't have time for this" | Ability gap | Reduce their load or push the timeline |
+| "We tried this before" | Trust gap | Acknowledge what's different this time. Be specific. |
+| Silent non-compliance | Could be any gap | 1:1 conversation to diagnose |
+
+**The worst response to resistance:** Dismissing it. "Some people are resistant to change" as if resistance is a personality flaw rather than a signal.
+
+---
+
+## Change Fatigue
+
+When organizations change too fast, people stop believing any change will stick.
+
+### Signals
+- Eye-rolls during change announcements ("here we go again")
+- Low attendance at change-related sessions
+- Fast compliance on paper, slow adoption in practice
+- "Last month we were doing X, now we're doing Y" comments
+
+### Prevention
+- **Finish what you start.** Don't announce a new change while the last one is still being absorbed.
+- **Space changes.** One significant change at a time. Give 2–3 months of stability between major changes.
+- **Announce what's NOT changing.** People in change-fatigue need to know what's stable.
+- **Show results.** Publish what the previous change achieved before launching the next.
+
+### When you're already in change fatigue
+- Pause non-critical changes
+- Run a "change inventory": how many changes are in progress simultaneously?
+- Prioritize ruthlessly: which changes are essential now? Which can wait?
+- Communicate stability: "Here's what is NOT changing this quarter"
+
+---
+
+## Key Questions for Change Management
+
+- "Who are the most skeptical people about this change? Have we talked to them directly?"
+- "Do people understand why we're doing this, or just what we're doing?"
+- "Have we given people time to practice before we measure performance on the new way?"
+- "Is the old way still available? If so, people will use it."
+- "Are leaders modeling the new behavior themselves?"
+- "How many changes are we running simultaneously right now?"
+
+## Red Flags
+
+- Change announced on Friday afternoon (people stew over the weekend)
+- "This is final, questions are not welcome" framing
+- No published FAQ or way to ask questions safely
+- Old system/process still running 6 weeks after "go-live"
+- Leaders exempted from the change they're asking everyone else to make
+- No measurement of adoption — assuming go-live = success
+
+## Detailed References
+- `references/change-playbook.md` — ADKAR deep dive, resistance counter-strategies, communication templates, change fatigue management