[Podcast] S1 E3: Change Fatigue, Chaos, and the PM in the Middle
- Andrew A. Rosado Hartline
- Jun 25
- 4 min read
Too much change too fast? Yeah, we’ve all been there. This week’s episode dives deep into how relentless transformation sabotages team morale, innovation, and even company performance and why empathetic Project Managers are the antidote to chaos.
Whether you're a frontline PM or a portfolio lead juggling overlapping transformations, this episode unpacks the human toll of change fatigue and the playbook for navigating it.
Lessons Learned (So You Don’t Have to)
This episode unpacks the tactical, emotional, and neurological toll of constant change and why the role of the PM is more critical than ever in chaotic organizations.
Here’s your cheat sheet of the biggest takeaways:
Key Lessons
Pace beats race. If you’re managing projects in high-change environments, slow the rollout to protect the outcome. Your team can’t sprint through a storm with no water breaks.
Empathy scalesA single genuine check-in creates a ripple effect that builds team culture. Human-centered PMs retain more talent. Period.
Clarity is a subscription service. Don’t assume that a Slack message last week was enough. Repeat, clarify, and renew understanding regularly.
Receipts matterWhen you push back on unrealistic timelines, document it. Your future self—and your team—will thank you.
Celebrate survival, not just shipping. Did your team make it through the pivot? That’s a win. Make resilience visible and valued.
Change fatigue is measurable, not just a “vibe”. Employee willingness to support change has dropped from ~74% to ~40% in just a few years. Teams aren't resisting change—they're resisting chaos. Source
Relentless change lowers innovation, morale, and revenue. Change-saturated orgs see a 32% dip in productivity and a higher risk of turnover, burnout, and failed initiatives. Source
PMs play a pivotal buffering role. It’s not enough to just “roll out” change. Empathetic PMs act as shock absorbers—sequencing, pacing, translating, and sometimes pushing back.
Burnout prevention is a PM skill. Listen, validate, celebrate micro-wins, and manage upward. Teams thrive when they feel heard, prepared, and paced.
Turn This Episode into Action
Here’s a breakdown of how to use the CO-START prompt from the blog post to build your own Weekly Change Digest using GenAI tools like ChatGPT, Claude, or Gemini:
Why This Matters
In high-change environments, your team is often juggling context switches, shifting expectations, and unclear communication. A Weekly Change Digest gives everyone a single, reliable source of truth to reduce cognitive load and start the next week with confidence.
Step 1: Understand the CO-START Structure
Each part of CO-START gives your GenAI the right ingredients to produce a useful output:
Element | What It Means |
Context | Who is this for? What’s going on? Set the scene. |
Objective | What are you trying to get out of the AI response? |
Specifics | The facts or data points to include (e.g., names, tools). |
Tone | How should it sound? Friendly, formal, technical, etc. |
Audience | Who’s going to read it? (Peers? Execs? Cross-functional teams?) |
Requirements | Formatting constraints or word limits. |
Type | The desired format (list, table, email, CSV, Mermaid chart). |
Step 2: Copy the Prompt Template
Use this exact prompt block in ChatGPT or Claude:
You are a project manager creating a weekly change digest for your team.
CO-START
- CONTEXT: A high-change cross-functional team in a tech org experiencing leadership churn.
- OBJECTIVE: Create a concise summary of all changes this week.
- SPECIFICS: Include date, change summary, decision-maker, impact area, next step.
- TONE: Professional, calm, transparent.
- AUDIENCE: Your internal team.
- REQUIREMENTS: Use a bullet list grouped by theme.
- TYPE: Markdown block with sections: Tooling, Process, People.
Step 3: Replace the Placeholders with Real Data
Fill in the changes that happened this week. For example:
- DATE: June 24, 2025
- CHANGE SUMMARY: Jira board automation rules updated.
- DECISION-MAKER: Team Member 1 (Product Ops)
- IMPACT AREA: Tooling – sprint planning and ticket triage
- NEXT STEP: Update team SOPs by June 28
Group the bullets under headings like this:
### Tooling
- **Jira automation rules updated** (Team Member 1). Sprint planning logic changed; impacts ticket triage. SOPs will be updated by June 28.
### Process
- **Retro cadence moved from weekly to biweekly** (Team Member 2). Requested by Design to reduce meeting load.
### People
- **New engineering lead onboarded** (Team Member 3). Shadowing begins next sprint.
Step 4: Run It in ChatGPT or Claude
Paste the filled-in prompt into your AI assistant. It will return a clean, organized digest that you can:
Post in Slack every Friday at 3PM
Include in your sprint wrap-up email
Archive in Confluence as your “Change History” log
Pro Tip: Automate It Weekly
Save your prompt as a template in your notes or task manager
Block 20 minutes on your calendar every Friday to fill it in
Use a reminder tool like Slackbot, Reclaim.ai, or Todoist to nudge you
The Result
Instead of scattershot DMs and "Did we ever decide on that?" moments, your team gets:
One trusted source of change updates
Less confusion
Fewer meetings to “align”
A documented trail for future retros or handoffs
Call to Action
🛑 Before you sprint into the next quarter:
Pull up your current backlog.
Identify one change your team is still digesting.
Ask: Have I clarified the "why"? Have I absorbed some of the load? Have I celebrated their resilience?
Then go do one small thing to reduce fatigue.
A Change Digest. A Check-in. And if you do?
📲 Post your tactic on LinkedIn with #PMLifeHacksAI and tag me. I’d love to hear how you’re navigating chaos with clarity.
Resources Used
Research & Data
Gartner, 2025–Employees now experience 5x more organizational change than in 2019.
Microsoft Work Trend Index 2025–61% of knowledge workers report feeling “physically drained” by tool sprawl.
Gartner, 2024–High-change orgs see a 26% drop in idea generation.
Amy Edmondson, Harvard Business School–“Cognitive whiplash” and the cost of chronic context switching on team performance.
Raconteur–Is Change Fatigue Blocking Your Business Transformation?
Center for Creative Leadership–The Importance of Empathy in the Workplace
FutureCIO–Change Fatigue in Digital Transformation
PM Lifehacks Blog Posts
Let’s make space for sustainable change. PMs, your teams need you well-paced and ready—not reactive and burned out.
Comments