empowered-product-team-transition
Installation
SKILL.md
Moving from a feature team to an empowered product team is the difference between being a "project manager" herding cats and a "product manager" driving business value. This framework allows you to run a low-risk experiment to prove the value of outcome-based product management.
The Three Sacred Access Points
Before starting a transition, you must ensure the Product Manager has unencumbered, direct access to three groups. Without these, the role is effectively paralyzed:
- Users and Customers: You must be able to talk to them directly without "gatekeepers" (Sales, Support, or Research) blocking the path.
- Engineers: You must work daily with developers to solve problems, not just hand off requirements.
- Stakeholders: You must understand the constraints of Legal, Finance, Sales, and Marketing directly to ensure the solution is "viable."
The 4-Part PM Preparation
To earn the right to lead an empowered team, the PM must bring four specific areas of expertise to the table that designers and engineers do not have:
- Customer Knowledge: Deep understanding of user pain points (ideally from 30+ recent customer interviews).
- Data Expertise: Mastery of user analytics, sales data, and warehouse metrics.
- Business Savvy: Understanding how the product is sold, marketed, financed, and regulated.
- Market/Competitive Landscape: Knowledge of industry trends and what competitors are building.
Step-by-Step: The "Empowered Experiment"
Instead of asking for a total organizational overhaul, pitch a one-quarter experiment for a single team.