Chapter 4
Unlocking Strategic Insights Through Data
The Business Data and Insights pillar drives value by helping executives understand the "why" behind product work. It provides the connective tissue for a holistic view of product strategy impacts on both top and bottom lines.
To determine which data informs strategy, product operations uses the layers outlined in "Escaping the Build Trap": vision, strategic intents, product initiatives, and options. For strategic intents-prioritized business challenges on the path to the company vision-product operations gathers data about revenue by product, persona purchasing patterns, customer retention, and resource allocation to determine which products solve which problems for different customer segments.
For product initiatives, teams need deeper metrics like NPS decreases, feature usage increases, and cross-product adoption that can predict future outcomes. These metrics must be segmented across customer types and cohorts to identify issues with usage and adoption early.
At Pipeline 3K, product manager Marcus discovered that midsize customers who adopted three products were adding network capability, which helped them close positions 15 times faster. However, onboarding was cumbersome with only 25% completion rates, revealing an opportunity to improve the workflow and increase upsell potential.
Once you've identified the questions you need to answer, you must determine which metrics will help and where that data lives. Core engagement metrics typically include product stickiness (DAU/WAU/MAU), frequency, feature adoption and retention rates, and product usage data. Beyond product metrics, tracking R&D resource allocation is crucial.
When cross-functional data sources aren't readily available, start with a manual baseline to agree on the views needed to inform and monitor strategy. This process may take several month-over-month cycles to ensure you're measuring the right things, but it demonstrates to cross-functional partners how their data is being used.
Product operations should consolidate metrics into effective dashboards for different organizational levels. The Executive & Board Strategy Dashboard provides portfolio-level views of product and business performance, showing roadmap status, ARR by customer segmentation, revenue bridge by initiative, bookings by product, debt views, and portfolio allocations.
After completing your manual baseline, automation becomes essential for making quick, data-driven decisions. This investment pays dividends as team members gain rapid access to the insights they need. The automation process includes selecting a BI tool, implementing tagging rules, continuously improving dashboards, and creating different data views for various teams.
A powerful example comes from athenahealth, where the product operations team tackled a labor-intensive software capitalization reporting process that was consuming over 400 hours of leadership time annually. By leveraging Atlassian's Jira to create a standardized product development lifecycle hierarchy, they eliminated administrative burden while increasing accuracy. The biggest ROI came from unexpected wins beyond their original goal-the team now has a valuable data asset and operating cadence that enables data-backed decision-making at all leadership levels.
Chapter 5
Building a Customer Insights Engine
Customer research often fails not because product teams don't understand its importance, but because of logistical challenges. Sales and customer success may restrict access to clients, and management might fear burdening customers with constant feedback requests. Recruiting research participants is time-consuming, yet there's no excuse for skipping customer research.
The customer and market research pillar enables external insights to reach product teams from various sources: win/loss analysis, customer reviews, support interactions, existing research, and more. Market research provides understanding of industry trends, competition, and opportunity sizing.
At Pipeline 3K, Rebecca assembled a cross-functional team to tackle their customer insights problem, discovering that sales already collected extensive customer information in Salesforce that product teams couldn't access. This revelation highlighted three core challenges: accessing internal customer data across teams, streamlining research processes, and making insights accessible company-wide.
Product operations for customer insights involves mapping where customer interactions happen, assessing data quality, and creating systems to share this knowledge. The chapter emphasizes that while one-on-one interviews remain valuable, companies often have untapped customer data scattered across departments. Effective product operations creates "connective tissue" between product teams and customer-facing roles, ensuring insights flow freely rather than disappearing into departmental silos.
Even with existing customer data systems, gaps remain that require direct user research. However, companies face common research problems: repeatedly interviewing the same customers creates echo chambers, insights remain siloed within teams, and product managers avoid customer conversations due to logistical hassles.
Market research complements user research by helping teams understand the broader business landscape and quantify opportunities. For expansion opportunities, product teams must evaluate the Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Service Obtainable Market (SOM). In one energy company case study, market analysis revealed that their initial $200M opportunity would only yield $2M in two years, while redirecting resources to API development could generate $30M in one year.
Fidelity Investments provides an inspiring case study in democratizing research. Facing a scaling challenge with just 65 User Researchers supporting hundreds of agile product development squads, they established a Research Operations function to help researchers accelerate their work and extend research capabilities to non-researchers. Their initiatives included UX research frameworks, a User Access System that reduced recruitment time from two months to two days, and a Democratization Program that trained over 300 associates to conduct unmoderated usability testing. They also built "Lighthouse," a research repository containing user, market, customer experience, and third-party research to prevent duplicative work.
Chapter 6
Creating an Effective Product Operating Model
As product management matures as a discipline, standardization of processes becomes increasingly important, especially in larger organizations. Hubert Palan, CEO of Product Board, notes that while sales, customer success, and engineering have well-defined methodologies, product management is still developing standardized approaches.
The Product Operating Model translates business and product strategies into execution by codifying how teams work together. In this model, the CPO establishes product principles and values, while product operations defines processes for roadmapping, strategy reviews, idea management, and planning-ultimately aligning the entire company around product development.
"Process" can be a loaded word that triggers allergic reactions, but when applied judiciously, it creates valuable structure. Simon Hilton, former Director of Product Operations at Willow, reframes process as "method" or "service," running product operations like an API product with methods that should evolve through versions.
At Pipeline 3K, Ashley evaluated their current state across four key components: Roles and Responsibilities earned an A- with standardized roles and clear boundaries between departments; Processes for Product Teams received a B with improving execution but inconsistent templates; Guidelines for Working with Other Teams also earned a B after educating teams on the development lifecycle; and Governance and Annual Planning received an F due to ad hoc reporting and chaotic planning sessions.
Effective governance ensures work aligns with product strategy through consistent review of objectives and key results (OKRs) with the right decision-makers present. Good governance encompasses product oversight, review mechanisms, risk management, compliance, accountability, and continuous improvement-linking processes with strategy and business capabilities.
Planning cycles are expensive and time-consuming, with a ProductOps HQ survey showing 25-50% of product and engineering teams spend weeks or months on quarterly planning. Companies typically plan annually due to this cost, sacrificing agility. The goal should be implementing cadences for vital conversations that enable responsiveness to market needs.
Product Operations designs and orchestrates planning cadences, ensuring the right people participate in strategic discussions. They handle organization, create templates for OKR reporting and business cases, manage agendas, track action items, and drive continuous improvement through feedback. They make strategic choices transparent to the organization, implement appropriate software tools, and help select prioritization frameworks that develop a culture of "either/or" trade-offs rather than "yes and..." additions that overload teams.
After establishing governance and planning processes, Rebecca shifted focus to day-to-day product processes. The key is not standardizing everything but focusing on templates affecting cross-functional areas and consistent practices. Core standardization areas include idea management, roadmapping, product tool kits, and onboarding.
Oscar Health provides an excellent case study in annual planning. Senior Director Clare Hawthorne perfected their process by designing clear input cadences, generating momentum, bringing together key stakeholders, setting focused meeting agendas, and providing simple templates. Oscar divides initiatives into "global" (organization-wide efforts managed centrally) and "local" (pod-specific projects with fewer dependencies), giving teams flexibility while maintaining alignment with company goals.
Chapter 7
Implementing Product Operations Successfully
When advocating for product operations, you'll face objections from leadership. Common concerns include budget constraints, questions about necessity, and overlap with other roles. Having ready answers to these challenges strengthens your case for implementing this critical function.
Product managers don't always welcome product operations, fearing it will "take over" their work or become merely reactive. Education clarifies the key distinction: product operations enables decisions rather than making them. As Anabela Cesario of OutSystems explains, "Our product operations team acts just like a miniature product team, and our customers are the product managers."
When implementing product operations, tailor your value proposition to each stakeholder group. For UX and User Research, position product ops as a bridge that helps product managers become self-sufficient with research tools. For Sales/Marketing, emphasize how it aligns product teams with revenue goals and improves transparency. Data Science benefits from seeing their analyses systematically applied to product decisions. Customer Support gains a structured approach to feedback collection and distribution. Engineers appreciate the consistency in methodologies and earlier involvement in roadmap planning.
As the first product operations hire at Amplitude, Shintaro Matsui took an iterative approach focused on quick wins rather than attempting massive transformations. He conducted a three-step discovery process: a listening tour of 35 one-on-one interviews across the organization, clustering pain points for impact, and plotting needs in an impact-effort matrix.
Matsui's first win addressed the common complaint that "the product team was a black box." He created a simple monthly product newsletter sharing updates on what the product team was working on. Though product managers spent just five minutes filling templates, the newsletter had immediate impact with the go-to-market team, preventing alignment issues and reducing ad hoc inquiries.
For his second win, he tackled inconsistent product development processes. Rather than imposing a top-down solution, he co-created an alpha process with stakeholders and piloted it with just one pod. By framing the process as "here to support you" and letting product managers take ownership, he achieved genuine bottom-up adoption.
Chapter 8
Building and Scaling Your Product Operations Team
Most product operations functions start small rather than adding large teams immediately. The approach typically involves identifying the most critical need and building from there. As Christine Itwaru's experience at Pendo demonstrates, starting with a single focused role can lead to significant growth-her team expanded from one to eleven members in under two years.
Starting with a team of one offers the advantage of easier approval compared to requesting an entire new function. Hugo Froes from OLX Motors Europe demonstrates that a single person can significantly impact product operations while evangelizing the discipline. His key advice: resist becoming the default problem-solver for unwanted tasks by clearly defining your vision, mission and strategy for product operations from the beginning.
When scaling beyond one person, you can be more intentional about addressing multiple needs across the three pillars simultaneously. At Sam's Club, CPO Tim Simmons recognized the opportunity to unlock capacity through efficiency and improve work quality through product operations. With CEO support, he created a staggered hiring plan for directors across core product operations functions.
Finding the right people for product operations often starts with internal talent who've already identified and solved discrete problems. When hiring externally, match candidates to specific pillars based on their skills and experience. For data and insights roles, seek candidates with consulting backgrounds, Excel mastery, SQL skills, and storytelling abilities. Process and governance roles require product management experience, tool expertise, and high emotional intelligence. Customer insights may come from user research backgrounds.
When structuring your product operations team, you'll need to decide between embedding specialists with individual product teams or creating a centralized shared service model. Neither approach is inherently superior-each has distinct advantages and disadvantages that must be weighed against your organization's specific needs, culture, and product complexity.
Blake Samic brings rare experience founding and expanding product operations at multiple companies, including OpenAI, Uber, and Stripe. At Uber and Stripe, he built product operations from a team of one to over 70 and 50 people respectively. His approach focused on creating leverage through streamlining core processes and efficiently bringing new products into operation. He developed frameworks for scaling, transitioning from manual processes to more systematic approaches, and eventually moved from a centrally funded "free service" model to having product teams fund their embedded Product Operations Partners (PoPs).
Chapter 9
Lessons Learned and Future Outlook
The product operations community is remarkably transparent about sharing lessons learned. From conversations with numerous practitioners, several recurring themes emerged that are crucial for success.
Executive support is essential whether establishing product operations from scratch or expanding an existing function. Some executives like Sam's Club CPO Tim Simmons initiate the function themselves, while in other cases it grows organically when a product manager identifies and addresses operational gaps. Regardless of origin, securing C-suite buy-in is critical.
Organizational culture is critical to product operations success. As Helmut Stueber of Tricentis notes, "The cultural aspect is as important as the technical one." Leaders must actively reinforce the value of product operations by consistently using the data it produces in decision-making processes like QBRs and strategy planning.
Product operations must connect product usage data with business outcomes to deliver maximum value. While engagement metrics provide leading indicators, they're insufficient without understanding how product decisions impact revenue, churn, and other business metrics. This analytical capability to connect product metrics to business metrics is product operations' secret sauce.
Since product operations is a cost center rather than directly revenue-generating, demonstrating value quickly is crucial. Focus on creating quick wins that address the organization's most acute needs while acknowledging you can't solve everything at once.
Product operations isn't about creating process for process's sake, but providing ways of working that help teams focus on doing the work rather than figuring out how to do it. The key is finding the right balance between providing structure and maintaining flexibility.
While product operations may only exist in about 20% of software companies today, this percentage could double within five years, particularly for enterprise-level companies building multiple products in parallel. The function will likely evolve toward more centralized models with increased automation and better observability systems that help product teams gain leverage.
Information flow will become an even greater focus, with manual processes eventually transitioning to scalable software solutions-similar to how concierge experiments work in product development. Large enterprises transitioning to software companies stand to gain the most from product operations as a key accelerant, while successful product operations teams are already expanding by absorbing adjacent functions like engineering operations.
Career paths in product operations are proving viable, with some leaders like OutSystems' Anabela Cesario moving from VP of Product Operations to VP of Product Management, demonstrating that the function is here to stay and will continue to grow as more companies recognize its multifaceted leverage.
Small, timely improvements can contribute more to long-term success than major process overhauls. Whether you're establishing product operations from scratch or evolving an existing function, the key is to customize your approach to your company's specific situation, find like-minded supporters within your organization, demonstrate value quickly through proof-of-concept initiatives, and connect with the broader product operations community for ongoing support and guidance.
