| name | content-first-product-leadership |
| description | A framework for shifting from "process management" to "product creation." Use this when you feel trapped in project management (Jira/Scrum), when launching a 0-to-1 product that requires high vision, or when hiring product leaders who need to "do the work" rather than just manage it. |
Content-First Product Leadership
Product Managers often fail by becoming "process monkeys"—experts at moving tickets and managing meetings but disconnected from the actual product. Content-First Leadership prioritizes the "Content" (what to do and when) over the "Process" (how to do it).
Core Principles
1. Distinguish Content vs. Process
- Content: The core "what" and "why." It is the roadmap, the user insight, the specific feature requirements, and the strategy.
- Process: The "how." It is Scrum, Agile, Jira, and meeting cadences.
- Rule: Hire for content and teach process. It is nearly impossible to teach a "process person" how to have product intuition (content), but easy to teach a "content person" how to run a sprint.
2. Practice Intentionality (The GPS Metaphor)
Never ask the data to tell you where to go.
- The Vision: Like a GPS, you must input the destination first (your "Intentionality").
- The A/B Test: Use testing only to find the fastest/most efficient route to that pre-defined destination.
- The Trap: Avoid "lazy PMing," where you run A/B tests to see if you should do something rather than how to do it best.
3. Design the "15-out-of-10" Experience
When building a new feature or product, remove all constraints (time, budget, engineering) to find the "ideal" end state.
- Start by designing the perfect experience (the 15/10).
- Work backward to a 7/10 or 8/10 "lovable" version.
- Do not start at a 5/10 and try to optimize your way to a 10.
