organizational-transformation
Installation
SKILL.md
Organizational Transformation
Scope
Covers
- Designing and leading a practical transformation plan to move a company toward a modern product operating model
- "Nudging" legacy orgs: sequencing change so it's adopted, not rejected
- Avoiding the trap of treating framework adoption (Spotify, SAFe, etc.) as the end goal
- Coordinating structure + process + culture changes (teams, decision rights, discovery/delivery, incentives, rituals)
When to use
- "Help me move us from feature teams to empowered product teams."
- "We keep adopting frameworks but nothing changes—build a real transformation plan."
- "Create a 90-day pilot plan plus a roadmap for rolling out a product operating model."
- "Our leaders want transformation; teams are skeptical. Build a change + comms plan that reduces rejection."
When NOT to use
- You need strategy/vision first (use
defining-product-visionorworking-backwards). - You only need an org chart / team topology change (use
organizational-design).
Related skills
More from liqiongyu/lenny_skills_plus
problem-definition
Define a product problem: problem statement, JTBD, alternatives, evidence, metrics. See also: writing-prds (solution spec).
13giving-presentations
Plan and deliver presentations: brief, narrative, slide outline, Q&A bank, rehearsal plan. See also: written-communication (async writing).
13competitive-analysis
Produce a Competitive Analysis Pack (alternatives map, landscape, battlecards, monitoring plan).
11pricing-strategy
Create a Pricing Strategy Pack (value metric, packaging, price points, conversion mechanics, rollout).
11startup-ideation
Generate and evaluate startup ideas: theses table, scorecard, top idea brief, validation plan. See also: startup-pivoting (existing product).
11writing-prds
Write a decision-ready PRD for cross-functional alignment. See also: writing-specs-designs (build-ready spec).
11