organizational-transformation
refoundai/lenny-skills
Guide organizations toward modern product practices through structured transformation, not just framework adoption.
What is organizational-transformation?
Help users shift from feature teams to empowered product teams, modernize legacy processes, and drive cultural change. Use this when someone needs to transform how their organization builds products—whether starting a pilot, managing resistance, or scaling change across teams.
- Diagnose current organizational model and readiness for change
- Design transformation approaches: pilots, gradual nudges, or broader initiatives
- Guide structural, cultural, and process changes simultaneously
- Help communicate change and measure progress
- Identify and manage resistance from stakeholders
How to install organizational-transformation
npx skills add https://github.com/refoundai/lenny-skills --skill organizational-transformationHow to use organizational-transformation
- 1.Understand the user's current organizational model and what's driving the need for change
- 2.Assess readiness by identifying who has authority and will to sponsor change, and what resistance to expect
- 3.Help design the transformation approach—whether pilot teams, nudges, or broader initiatives
- 4.Guide implementation of structural, cultural, and process changes together
- 5.Support communication strategy and progress measurement
Use cases
- Shifting a feature-driven organization to empowered product teams
- Introducing modern practices into legacy enterprises without systemic rejection
- Piloting new ways of working in one team before broader rollout
- Modernizing waterfall processes toward iterative product development
- Building executive sponsorship and managing organizational resistance to change
- Product leaders driving organizational change
- Executives sponsoring transformation initiatives
- Organizational design practitioners
- Teams implementing new operating models
- Change management leads in enterprises
organizational-transformation FAQ
Frameworks are means, not ends. Evaluate any framework by whether it solves your specific organizational problems and improves outcomes. Implementing Scrum without changing culture and structure won't transform how you work.
Start with a small pilot team that can demonstrate the new model works. Use their success to build credibility and spread the approach. Radical organization-wide change proposals often get rejected; nudging through pilots is more effective.
Treating framework adoption as the goal, or trying to change everything at once. Successful transformation requires simultaneous changes to structure (how teams are organized), culture (how people think), and processes (how decisions get made). Changing only one dimension won't stick.
Identify who will resist and why. Avoid threatening existing power structures unnecessarily. Ensure executive sponsorship—transformation without senior support gets crushed by organizational antibodies. Communicate the outcome you're trying to achieve, not just the process changes.
Define success metrics upfront tied to outcomes you care about—faster time-to-market, better product decisions, improved team engagement. Track progress against these, not just adoption of new ceremonies or processes.
Full instructions (SKILL.md)
Source of truth, from refoundai/lenny-skills.
name: organizational-transformation description: Help users transform organizations toward modern product practices. Use when someone is trying to shift from feature teams to product teams, introduce empowered teams, modernize legacy processes, or drive cultural change in how product is built.
Organizational Transformation
Help the user transform their organization toward modern product practices using insights from 2 product leaders.
How to Help
When the user asks for help with organizational transformation:
- Understand their starting point - Ask what their current model looks like (feature teams, output focus, waterfall) and what's driving the need for change
- Diagnose readiness - Determine who has the authority and will to drive change, and what resistance they should expect
- Design the approach - Help them decide between pilot teams, gradual nudges, or broader transformation initiatives
- Manage the change - Guide them on communicating, measuring progress, and handling resistance
Core Principles
Frameworks are means, not ends
John Cutler: "Most companies see adopting frameworks as the end goal." The goal is better outcomes, not implementing Scrum or SAFe or any specific methodology. Evaluate frameworks by whether they help your specific organization solve its specific problems.
Transform through pilots, then spread
Marty Cagan: "The goal of TRANSFORMED was to share how to actually change - transformation techniques." Start with a small number of empowered product teams that can demonstrate the model works. Use their success to build credibility for broader change.
Nudge legacy companies carefully
John Cutler emphasizes "nudging" non-Silicon Valley companies toward modern practices without causing systemic rejection. Radical change proposals often get rejected. Find ways to introduce new practices that don't threaten existing power structures.
It's structural, cultural, AND process change
Marty Cagan describes moving from "feature teams" to a "product operating model" - this requires changing structures (how teams are organized), culture (how people think about their work), and processes (how decisions get made). Changing only one dimension won't work.
Questions to Help Users
- "What's driving the need for transformation? What's broken today?"
- "Who has the authority and will to sponsor this change?"
- "What's your current model - feature teams, waterfall, something else?"
- "Where would you start? Is there a team or area that could pilot the new approach?"
- "What resistance should you expect, and from whom?"
- "How will you know if the transformation is working?"
Common Mistakes to Flag
- Treating framework adoption as the goal - Implementing Scrum doesn't mean you've transformed. Focus on outcomes, not ceremonies
- Big-bang transformation - Trying to change everything at once usually fails. Start with pilots
- Ignoring culture - Process changes without cultural change get worked around. Address beliefs, not just behaviors
- No executive sponsorship - Transformation without senior support gets crushed by organizational antibodies
- Copying Silicon Valley blindly - What works at Google may not work at a 50-year-old enterprise. Adapt, don't copy
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- Organizational Design
- Building Team Culture
- Managing Up
- Having Difficult Conversations
Related skills
More from refoundai/lenny-skills and the wider catalog.
partnership-bd
Navigate strategic partnerships and BD deals using proven frameworks from product leaders.
personal-productivity
Help users manage time and tasks effectively using proven techniques from product leaders.
planning-under-uncertainty
Navigate product planning when outcomes are unpredictable using adaptive frameworks from 44 product leaders.
platform-infrastructure
Design and scale internal platforms and shared technical infrastructure with proven patterns from engineering leaders.
platform-strategy
Design and execute platform business strategies using frameworks from 24 product leaders.
positioning-messaging
Craft compelling product positioning and messaging using frameworks from 58 product leaders.