Leading Organizational Change
Transform culture, structure, and operations without breaking the business.
The Guide
6 key steps synthesized from 19 experts.
Identify the levers of change
Start by identifying the sacred cows and unwritten rules that keep the organization stagnant. Use this list as a prioritized roadmap for what to dismantle first to enable new ways of working.
Featured guest perspectives
"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."— Kayvon Beykpour
"Ultimately, where you want to be as much as possible is being the person who recognizes that change should happen, figures out a plan to make it happen, and then makes it happen. This is what being a senior leader is all about."— Lenny Rachitsky
Isolate and protect innovation
Incubate new initiatives by shielding a small, talented team from standard corporate overhead and short-term performance cycles. Allow them to operate with startup-like intensity and distinct success metrics.
Featured guest perspectives
"And those four people over the course of maybe nine months or so, built a time and attendance product. It was the only thing they were doing. They didn't have to worry about what was going on with our payroll product except to the extent they had to integrate with them a little bit. They were monomaniacally focused on this one thing and then identifying the places where yes, you, there's connectivity to the rest of the suite, and that allowed them to move extremely quickly."— Jeremy Henrickson
"If you're a large organization and you do some performance management process twice a year and you're 0 to 1 incubator, you've already killed it. It's the wrong incentive."— Noam Lovinsky
"The thing Cash App did right was like 10 things, not one. There were like 10 things that actually best in class, like insane talent density, insane focus, very strong at fraud, a lot of the way Brian, and Dustin, and Jesse, and Dangi tried to organize the amount... Like you know, with Jack's support was just really firewalled from the rest of the square, the hero customer was the consumer, not the merchants, so it was like literally in 100% of the trade offs the consumer's needs came first."— Ayo Omojola
Translate the vision through narrative
Communicate the new direction at every opportunity, but tailor the language to fit existing expertise. Use a consistent narrative paired with a clear North Star KPI to serve as the ultimate measuring stick.
Featured guest perspectives
"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."— Chris Hutchins
"we had had a pretty entrenched consensus-based culture, where we would really debate a lot of decisions and a lot of features. And on the one hand, I think that that does lead to good outcomes, right? Thoughtful products that have a lot of viewpoints really baked into the core of the thinking. On the other hand, not fast."— Tim Holley
Build momentum through low-stakes rituals
Before enforcing new frameworks or technical shifts, establish celebrations or small rituals to build cultural buy-in. This reduces friction when moving to formal process changes.
Featured guest perspectives
"I've had CEOs who said, 'Well, it was the middle of the quarter, so we didn't start OKRs, but we did start Friday celebrations and oh my God, things are already changing. Things are already getting better.'"— Christina Wodtke
Execute with radical transparency
During turbulent times, acknowledge difficulties openly and maintain a high clock speed of communication. Help the team make meaning of the change by referring back to a shared purpose.
Featured guest perspectives
"It’s possible, through dialogue, to create a shared purpose for your role and your team, and a primary leadership responsibility is to help others make meaning. Step back and ask yourself: what matters most to me? Regular self-reflection will help you re-orient or double down on what you are doing and why."— Lenny Rachitsky
"Our whole parenting philosophy is resilience over happiness. When we're thinking about a resilient work culture, we want people who can say, 'This is hard and I can do hard things.'"— Dr. Becky Kennedy
Stress-test the new structure
Use leader sabbaticals or temporary absences to see where dependencies remain. Observe which processes fail or slow down when you are not there to manually drive them, then fix the gaps.
Get this guide as an AI skill for Claude Code
Install This Skill
Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.
Quick Install (Recommended)
Install this skill directly using npx:
npx skills add RefoundAI/lenny-skills --skill leading-org-change Or install all 76 skills:
npx skills add RefoundAI/lenny-skills Manual Installation
Download the skill
Download Skill (.zip)Add to your project
Create a folder in your project root and add the skill file:
.claude/skills/leading-org-change/SKILL.md Start using it
Claude will automatically detect and use the skill when relevant. You can also invoke it directly:
Help me with leading organizational change Or receive these install instructions in your inbox:
Guest Perspectives
Deep dive into what 18 podcast guests shared about leading organizational change.
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."
- Identify low-risk 'seeds' or projects that can grow independently with minimal intervention.
- Direct extra energy toward existing momentum rather than trying to force outcomes against the grain.
- Prioritize initiatives that have the potential to create value far beyond the manual effort invested in them.
Ayo Omojola
"The thing Cash App did right was like 10 things, not one. There were like 10 things that actually best in class, like insane talent density, insane focus, very strong at fraud, a lot of the way Brian, and Dustin, and Jesse, and Dangi tried to organize the amount... Like you know, with Jack's support was just really firewalled from the rest of the square, the hero customer was the consumer, not the merchants, so it was like literally in 100% of the trade offs the consumer's needs came first."
- Firewall the new product team from the parent company's existing organizational structures and stakeholders.
- Define a specific 'hero customer' and ensure 100% of product trade-offs favor that customer's needs.
- Recruit for extreme talent density to ensure the team has the specialized skills required for its unique domain.
Brian Tolkin
"I've slept on the floor in China before launching uberPOOL, and when you reflect the stress onto your teams, everybody tenses out. It counterintuitively doesn't produce better outcomes."
- Absorb high-level pressure rather than reflecting it onto the team to prevent collective tension.
- Maintain focus on immediate execution goals, such as meeting specific launch windows, despite exhaustion.
- Reframe high-stress crisis moments as valuable shared experiences once the pressure has subsided.
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."
- State the product vision and mission at every possible opportunity, including all-hands meetings, to ensure the team remains inspired.
- Cultivate internal influence and public speaking skills to effectively persuade the teams that will build and market the product.
- Treat internal buy-in as a critical milestone of the product development process rather than an afterthought to customer insights.
Christina Wodtke
"I've had CEOs who said, 'Well, it was the middle of the quarter, so we didn't start OKRs, but we did start Friday celebrations and oh my God, things are already changing. Things are already getting better.'"
- Launch 'Friday celebrations' to highlight team wins and build a sense of shared purpose before rolling out complex goals.
- Introduce new processes during 'temporal landmarks' like the start of Q1 or a Monday to leverage natural fresh starts.
- Clarify the 'why' and mission behind the company's existence so that new goals feel purpose-built rather than arbitrary.
Dan Shipper
"We have a head of AI operations. She's just constantly building prompts and building workflows that I and everyone else on the team are just automating as much as possible."
- Designate a head of AI operations to build and maintain company-wide automation workflows.
- Convert expert feedback and instructions into prompts to ensure institutional knowledge is never lost.
- Empower every employee to use an array of specialized agents to increase individual leverage.
Dr. Becky Kennedy
"Our whole parenting philosophy is resilience over happiness. When we're thinking about a resilient work culture, we want people who can say, 'This is hard and I can do hard things.'"
- Acknowledge to your team that a situation is difficult rather than minimizing it.
- Affirm the team's ability to handle hard things while validating the struggle.
- Prioritize building a resilient culture over maintaining high short-term happiness.
Eric Simons
"And our team's like 15, 20 people, so it's just dealing with, we're going to be closing on 100,000 customers, and our support team's like three people. So we're trying to scale as fast as we can. So it's just kind of mind-boggling, just the scale of the demand, and how we've had to turn things around to match the demand as best as we can."
- Design products with 'dead simple' interfaces to minimize the need for a large customer support organization during spikes.
- Leverage bidirectional AI agents to automate technical workflows and reduce manual engineering overhead.
- Pivot existing technical expertise into emerging high-growth verticals like AI to capture market demand overnight.
Jeetu Patel
"What large companies don't do is when an experiment works, they don't go all in and double down. They try to keep hedging. We didn't hedge on AI. We said we were going to go all in."
- Identify the difference between a temporary hype cycle and a foundational megatrend before committing resources.
- Reassure employees that their career success is tied to becoming AI-dexterous rather than being replaced by it.
- Eliminate the 'pocket veto' by making high-conviction strategic bets non-negotiable across the organization.
Jeremy Henrickson
"And those four people over the course of maybe nine months or so, built a time and attendance product. It was the only thing they were doing. They didn't have to worry about what was going on with our payroll product except to the extent they had to integrate with them a little bit. They were monomaniacally focused on this one thing and then identifying the places where yes, you, there's connectivity to the rest of the suite, and that allowed them to move extremely quickly."
- Start new initiatives with a very small team—sometimes just one engineer—and a one-page vision.
- Shield the incubation team from the operational complexities and distractions of existing core products.
- Maintain a flat communication structure where senior leadership can unblock the team directly without layers of management.
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."
- Ask the product team to list every rule or constraint they believe is off-limits for change.
- Use that list of perceived constraints as a prioritized roadmap for new product initiatives.
- Adopt a high-ambition mindset that is willing to risk total failure in order to break internal deadlock.
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."
- Execute layoffs through individual one-on-one meetings between managers and their direct reports.
- Eliminate mass communication methods for the delivery of life-altering professional news.
- Provide a private outlet for departing employees to process their emotions with a human being.
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 the Scaled Agile Framework (SAFe).
- Focus on core agile principles like rapid iteration and value delivery rather than just ceremonies.
- Tailor scaling processes to the organization's specific needs instead of using off-the-shelf templates.
Noam Lovinsky
"If you're a large organization and you do some performance management process twice a year and you're 0 to 1 incubator, you've already killed it. It's the wrong incentive."
- Adopt a longer time horizon for evaluating the success of early-stage experiments.
- Exempt incubator teams from mainline corporate performance cycles.
- Create unique incentive structures tailored specifically for innovation and risk-taking.
Peter Deng
"You have to plan your chess moves out in advance. You have to really think before you act and build systems that were going to let you go sustainably faster."
- Plan product strategy several chess moves in advance.
- Build systems that enable sustainable growth velocity.
- Prioritize deep thinking and systems design before taking action.
Tanguy Crusson
"The company has a tendency to over-invest. Startups have the benefit of starving, and so you need to create scarcity. What we try to do is remind everyone things are going to fail, let's not drag the rest of the company into it."
- Create artificial scarcity to force ruthless prioritization.
- Silo the team to protect them from standard corporate design guidelines.
- Communicate clearly that the bet is a test and may fail.
"Now, evaluating success can look very different between early stage and established products. For a long time at Atlassian, we were treating everything a little bit equally in that the metrics success for the same."
- Create a structured incubator program with its own stage-gates.
- Decouple early-stage bets from metrics like Monthly Active Users (MAU).
- Ensure leadership buy-in to provide the necessary time for product-market fit.
Tim Holley
"we had had a pretty entrenched consensus-based culture, where we would really debate a lot of decisions and a lot of features. And on the one hand, I think that that does lead to good outcomes, right? Thoughtful products that have a lot of viewpoints really baked into the core of the thinking. On the other hand, not fast."
- Establish a North Star KPI to serve as the ultimate measuring stick for all prioritization.
- Identify areas where identity is tied to legacy ways of working and address the existential feeling of change.
- Prioritize faster feature launches over perfect alignment achieved through endless debate.
Will Larson
"I think that we often treat engineers a little bit like children instead of giving them the responsibilities and ability to actually thrive as adults. And so like, "Oh, the engineers won't want to do that work." Well, that's actually not good for the engineers to be sheltered from what is important."
- Shift leadership focus from high-volume hiring and retention to operational efficiency and team sizing.
- Involve engineers in senior leadership roles and expose them to real organizational problems rather than sheltering them.
- Hold engineers accountable for results to give them the opportunity to grow into truly senior roles.
"Systems thinking is basically you try to think about stocks and flows. So stocks are things that accumulate and flows are kind of the movement from a stock to another thing."
- Map out organizational processes as stocks (accumulated resources) and flows (rates of movement between stocks).
- Identify gaps where your mental model conflicts with reality to learn where the system is actually failing.
- Balance analysis with action to avoid the trap of prioritizing measurement over making actual improvements.
Make your product team AI-native
These skills work best as a system. Get a free 8-email course: map how your team works today, wire agents into real workflows, and make it stick. From the team that does this for a living.
Related Skills
Other Team & Organization skills you might find useful.
Organizational Design for Product and Engineering
To prevent internal resentment and organizational rejection, innovation teams must be positioned as...
View Skill → →Coaching and Talent Development
Senior product management impact is defined by the ability to provide strategic clarity and prioriti...
View Skill → →Building High-Performing Team Culture
High-performing cultures require leaders to prioritize clear performance standards and organizationa...
View Skill → →Hiring World-Class Product Talent
In the AI era, the value of the generalist has increased significantly because tools allow individua...
View Skill → →