| name | leading-org-change |
| description | Help users navigate complex transitions, from scaling new business units to managing crises and driving AI adoption across large organizations. |
Leading Organizational Change
Transform culture, structure, and operations without breaking the business.
Help the user with leading organizational change using insights from 29 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Diagnose the friction - Identify whether the change is driven by growth, crisis, or technological shifts to determine the right posture.
- Align stakeholders - Map key influencers and translate product principles into language that resonates with different departments.
- Structure the rollout - Design phased implementations, from small-scale pilots and isolated teams to company-wide adoption.
- Establish rituals - Create feedback loops and cultural milestones to cement the change into daily operations.
Core Principles
Act as a gardener, not a builder
Alex Komoroske: "What I look for instead are things that can be gardened, things that can grow on their own and that you can direct or maybe give a little bit of extra energy to or curate over, and is a totally different mindset for it. If you do this properly, it looks like magic."
Nurture emergent, self-sustaining ideas rather than forcing rigid structures. Identify low-risk projects that can grow independently with minimal intervention.
Prioritize internal alignment over external research
Chris Hutchins: "But you think that customer research is all you need to build a product at a company, but figuring out how to create excitement internally and get buy-in from other teams because they're the ones that are going to build it. They're the ones that are going to help market. It's all a team effort."
Innovation within large orgs requires a shift in focus toward intensive internal alignment. State your vision at every opportunity to keep the team inspired.
Target sacred cows
Kayvon Beykpour: "The sacred cows are like their own roadmap. What are all the things that you think we're not allowed to change? Let's start there."
Explicitly identify and target the unwritten rules and perceived constraints that prevent the team from taking creative risks.
Humanize difficult transitions
Matt Mochary: "The biggest marker that I've seen between a botched layoff and a successful layoff is at the moment someone hears that they no longer have a job, did they hear it from their manager in a one-on-one? If that's when they heard it, it'll be okay. But if they heard it in an email, in a group chat, in any kind of thing where they were sitting next to or they're hearing it along with other people, it wasn't personalized, it wasn't one-on-one, that is terrible. That's when people get really angry and that's when they start going on to Twitter and going to newspapers and et cetera, because it feels dehumanizing."
The success of a major change, like a layoff, is determined by whether the news is delivered personally by managers rather than through mass announcements.
Prioritize value over frameworks
Melissa Perri: "I do not recommend using SAFe. Every single person I have talked to who likes SAFe, found success with SAFe, they ended up ripping it up and making it into something else."
Avoid dogmatic implementations of scaling frameworks. Focus on core agile principles like rapid iteration and delivering customer value.
Templates & Frameworks
- Five Factors for Adaptive Resilience During Change (Surviving reorgs, tactically and emotionally - Issue 32) - A framework combining Dr. Michael Cavanagh's Four-Factor Model (Perspective, Purpose, Dialogue, Mindfulness) plus Katherine Hosie's addition of Humor, for build
- Bridges' Transition Model (Ending → Neutral Zone → New Beginning) (Surviving reorgs, tactically and emotionally - Issue 32) - William Bridges' three-stage model for understanding any transition, used here to explain why constant reorgs create 'transition fatigue' when you're stuck in t
- Ally Mapping for Organizational Change (Turning around an underperforming team - Issue 17) - A framework for categorizing stakeholders into three groups when driving change on a team.
- Bureaucracy Mirror Doc (This Week #9: Breaking into growth, leading with influence, and (not) stepping on toes 🦶) - A doc or deck format for highlighting organizational inefficiency and proposing fixes
- Internal Team Communication During Crisis Checklist (Leading your company through a pandemic - Issue 20) - Guidelines for maintaining team morale and trust through transparent communication during uncertainty
- KPI + Narrative Leadership Model (Tim Holley) - Josh Silverman's approach to driving organizational change by combining a clear KPI with a consistent narrative repeated over time
- Motivation Mapping for Change Management (Turning around an underperforming team - Issue 17) - A framework for connecting proposed team changes to individual team members' personal motivations to build intrinsic buy-in.
- Three-Step Layoff Process (Matt Mochary) - A step-by-step guide to conducting a company-wide layoff that minimizes trauma.
- Give Away Your Legos (Scaling Metaphor) (Essential reading for product builders—part 2) - A mental model for managing the emotional challenge of scaling teams—instead of grabbing back responsibilities from new hires, find bigger problems to solve.
See references/artifacts.md for the full list with details.
Questions to Help Users
- "What specific unwritten rules or constraints are currently preventing your team from changing?"
- "Is this change being driven by a growth opportunity, a defensive crisis, or a technological shift like AI?"
- "How are you protecting your new innovation teams from standard corporate performance management?"
- "What is the core principle of your founder that must be preserved during this transition?"
- "Have you mapped out your internal stakeholders to identify who will be your champions versus your skeptics?"
- "Are you delivering high-impact news personally, or relying on mass communication channels?"
Common Mistakes to Flag
- Copying operational rituals blindly - Adopting the processes of companies like Amazon or Netflix without understanding their context leads to cultural rejection.
- Reflecting high-level stress - Leaders who project their own anxiety onto the team cause paralysis rather than productive urgency during a crisis.
- Over-investing in rigid frameworks - Focusing on process adherence rather than customer value delivery leads to bloated organizations that cannot innovate.
- Hiding the difficulty - Minimizing the reality of a hard situation destroys trust; employees need leaders to acknowledge struggle while affirming their ability to handle it.
Deep Dive
For all 50 sourced insights from 29 guests, see references/guest-insights.md
Related Skills
- Hiring Product Talent
- Interviewing Evaluating Candidates
- Org Design
- Building Growth Team
