Product Operations: Map of Content

This is a garden entry that maps out my thinking and resources on Product Operations, particularly structured around the three pillars as defined by Melissa Perri and Denise Tilles in their book “Product Operations”.

What is Product Operations?

Product Operations (ProdOps) is an enablement function that makes decision-making processes easier and more transparent in product organizations. As I wrote in my blog post Why Product Teams Fail (And It’s Not What You Think):

Most product managers don’t fail because they lack skills. They fail because they’re trying to build products while simultaneously building the systems to do their jobs.

Product Operations provides the infrastructure that allows product managers to focus on product management rather than systems building or administrative overhead.

The Three Pillars of Product Operations

1. Business Data and Insights

This pillar focuses on enabling the collection and analysis of internal data for strategy creation and monitoring. It connects product metrics to business outcomes in ways that inform strategic decisions.

Key aspects:

• Provides leaders with data to track progress on outcomes and ROI
• Connects business metrics (ARR, retention) with product metrics
• Helps leaders understand how product investments impact financial outcomes

My approach and tactics:

• Setting up dashboards that answer specific strategic questions, not just display metrics
• Product Metrics Hierarchy - How I organize metrics from strategic to tactical levels
• Product Thinking – Connecting KPIs to Outcomes - Frameworks for linking product work to business value

2. Customer and Market Insights

This pillar facilitates and aggregates research from external sources, making customer insights accessible throughout the organization.

Key aspects:

• Streamlines customer feedback collection and organization
• Makes insights accessible for team exploration
• Organizes competitive intelligence and market research

My approach and tactics:

• Customer Feedback Loop System - How I set up feedback collection across touchpoints
• Making User Research Accessible - Tactics for organizing research for maximum utility
• Market Research for Product Decisions - How I structure competitive and market intelligence

3. Process and Practices

This pillar scales product management value through consistent cross-functional practices and frameworks, defining the product operating model.

Key aspects:

• Establishes consistent processes while minimizing bureaucracy
• Creates templates and frameworks that reduce friction
• Implements tool governance and evaluation
• Establishes communities of practice

My approach and tactics:

• Product Operating Model Framework - How I structure cross-functional collaboration
• Prioritization Frameworks That Actually Work - Decision models I’ve used successfully
• Tool Evaluation Framework - How I assess and roll out product tools

Why This Matters in Infrastructure

As I worked through in my Product Operations Excellence for Infrastructure ideal state, infrastructure teams face unique ProdOps challenges:

• Engineering-heavy contexts often lack product culture
• Complex technical dependencies complicate prioritization
• Measuring value is often more abstract than in customer-facing products
• Stakeholders span multiple technical domains with varying perspectives

My experience implementing ProdOps practices in infrastructure contexts has shown that:

1. Clear service boundaries are essential for measuring impact
2. Product thinking must be translated for engineering-first cultures
3. Success metrics differ significantly from customer-facing products

Key Resources

My Writing

• Why Product Teams Fail - My blog post on the importance of product operations
• Product Operations Excellence for Infrastructure - How I approach ProdOps in technical contexts

External References

• Product Operations by Melissa Perri and Denise Tilles
• 9 Key Responsibilities of Product Operations
• Takeaways from Transformed by Marty Cagan - Understanding modern product operating models

Key Insights

• Product operations functions best as a service provider, not a process enforcer
• Start with the area of highest friction rather than trying to implement all pillars at once
• Success looks like product teams spending more time on customer problems and less on administrative tasks
• Think “APIs, not process documentation” when designing ProdOps services

“Process can be a good thing—if applied judiciously.”

Questions I’m Still Exploring

• How does an engineering organization operate without product management at all?
• What is the minimum viable product allocation? (10:1 vs. 40:1 engineer-to-PM ratios)
• What would product development look like if we built the operating system first, then hired the talent?
• How can we better measure the ROI of product operations investments?

This garden entry serves as a map to my thinking and resources on Product Operations. It’s a living document that will evolve as I continue to explore and implement these concepts in my work.