Individual skill
leading-org-change
Help users navigate complex transitions, from scaling new business units to managing crises and driving AI adoption across large organizations.
skills/leading-org-change/SKILL.md
Source commit 13598cc54e09399bc1bc1398b0fca284110efb2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,476
- Repository last updated
- Jul 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-assistant Repository topic
- claude Repository topic
- claude-code Repository topic
- lenny-rachitsky Repository topic
- llm Repository topic
- pm-tools Repository topic
- product-management Repository topic
- skills Repository topic
- product-skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,122 bytesreferences/artifacts.mddoc · 32,774 bytesreferences/guest-insights.mddoc · 56,662 bytes
Read excerpt
# 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
1. **Diagnose the friction** - Identify whether the change is driven by growth, crisis, or technological shifts to determine the right posture.
2. **Align stakeholders** - Map key influencers and translate product principles into language that resonates with different departments.
3. **Structure the rollout** - Design phased implementations, from small-scale pilots and isolated teams to company-wide adoption.
4. **Establish rituals** - Create feedback loops and cultural milestones to cement the change into daily operations.
## Core Principles