organizational-design
Installation
SKILL.md
Organizational Design
Scope
Covers
- Designing or redesigning an organization's structure + operating model to improve speed, accountability, and customer outcomes
- Choosing between centralized vs decentralized models (Apple ↔ Amazon spectrum) and functional vs divisional/value-stream orientations
- Reducing coordination tax by minimizing dependencies and clarifying decision rights
- Setting management roles/layers so leaders know the work and can drive craft, not just process
When to use
- "Propose a reorg / org design for my product + engineering organization."
- "We're slow due to dependencies—redesign teams so we can run in parallel."
- "Our UX is fragmented—should we centralize decisions or strengthen functional leadership?"
- "We grew fast and added layers—help us simplify and get back to startup speed."
When NOT to use
- You need product strategy/vision first (use
defining-product-visionorworking-backwards). - This is mainly a people-performance issue (use coaching/feedback workflows, not a reorg).
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