| name | sacred-cow-product-roadmap |
| description | A strategy for breaking organizational stagnation by identifying and challenging "untouchable" product constraints. Use this when your roadmap has become purely incremental, when the team is risk-averse, or when customers complain that the product hasn't changed in years. |
Sacred Cow Product Roadmap
The "Sacred Cow" approach transforms organizational taboos into a high-value innovation roadmap. In stagnant companies, "refining the core" often leads to a calcified culture where the most impactful changes are considered off-limits. By identifying these "sacred cows," you reveal exactly where the most significant opportunities for product evolution reside.
The Process
1. Identify the Sacred Cows
Inventory the rules, features, or constraints that the organization believes are "not allowed" to be changed.
- Ask the team: "What are the things we are afraid to touch?"
- Look for features that have stayed the same for 5+ years despite shifts in user behavior.
- Identify "religious" constraints (e.g., "We will never have an edit button," "We must stay under X characters").
2. Staff for Obsession
Do not staff "sacred cow" projects based on availability. Staff them with "believers."
- Recruit internal entrepreneurs or use small acquihires (founders) who have a natural obsession with the problem.
- Ensure the lead has the "savviness" to navigate the system but the "will" to break it.
- Rule: If the team doesn't believe in the heresy, the project will fail at the first sign of friction.
3. Protect the "Speculative Bet" Silo
Sacred cow projects often hurt core metrics (like DAU or Revenue) in the short term. Protect them from standard performance frameworks.
- Create a "startup" environment for the team.
- Exempt them from quarterly OKRs that favor "refining the core."
- Judge success based on "learning" and "capability creation" rather than immediate top-line growth.
4. Apply the "Smell Test" for Trade-offs
When frameworks (like Jobs-to-be-Done or OKRs) suggest a decision that feels customer-hostile, prioritize "product taste."
- Ask: "Even if this drives the metric, do I hate this as a user?"
- If the framework leads to a subjectively bad experience (e.g., hiding order details to force a login), the framework is failing.
- Use leadership judgment to overrule metrics when a sacred cow project creates a long-term "vector for conversation" that the current product cannot support.
Examples
Example 1: Challenging Feed Structure
- Context: A social platform has used a reverse-chronological feed for a decade. Leadership is afraid to move to a ranked feed because "users will revolt."
- Input: User growth is declining; "refining the core" is no longer working.
- Application: Identify the "reverse-chron" as a sacred cow. Staff a small, isolated team to build an algorithmic ranking system.
- Output: A ranked timeline that, despite initial friction, dramatically increases long-term retention and DAU.
Example 2: Introducing User-Moderation
- Context: A platform believes only the company should moderate content; giving users control is seen as "dangerous to free speech."
- Input: Harassment is high, and the internal "policing" team cannot scale.
- Application: Identify "company-only moderation" as the sacred cow. Create a feature (e.g., "Hide Replies") that gives the original poster control over their space.
- Output: Users feel more empowered to share content, reducing the burden on central moderation.
Common Pitfalls
- Staffing by Availability: Assigning a "sacred cow" project to a PM who is just "free" leads to lukewarm execution. These projects require irrational obsession to survive.
- Religious Adherence to Frameworks: Following Jobs-to-be-Done or OKRs so strictly that you ignore the "forest for the trees." If a framework prevents a big, bold bet because it doesn't fit a specific "job," discard the framework for that project.
- Competing Internally: Building a "new" version of a feature on a separate stack while the "core" team builds their own version. This creates political deadlock and technical debt.
- Ignoring the Short-Term Dip: Killing a project because it moved a core metric down (e.g., moving ads down to make room for a new feature). You must "squint" to see the long-term value.
