The Invisible Engine Behind Great Products ========================================== Melissa Perri and Denise Tilles make the case that product ops isn't bureaucracy, it's the connective tissue that lets teams actually move. We dig into the three pillars and the trap of becoming a gatekeeper. ---------------------------------------- SAM: Hey, welcome back to 7 Minute Books. I'm Sam, and today we're talking about Product Operations by Melissa Perri and Denise Tilles, which is all about the invisible machinery that makes product teams actually work. Sophie, I have to ask, did this book make you feel seen, or did it make you feel a little attacked? SOPHIE: Oh, a bit of both, honestly. Hi there Sam. So this is Perri and Tilles arguing that the thing most companies are missing isn't a better roadmap or a genius leader. It's an operational discipline, product ops, and they lay out exactly what that function does and why it matters at scale. SAM: And the core idea is so simple it almost sounds obvious. As a company grows, the complexity of managing information just explodes. And nobody owns that complexity, so it just piles up on the product managers. SOPHIE: Right, and the product manager becomes this human switchboard. They're chasing data, chasing alignment, chasing feedback, and the actual job of figuring out what customers need gets squeezed into whatever time is left. SAM: Which is wild, because that's the whole job. That's the reason you hired them. SOPHIE: Exactly. So the book says product ops is the connective tissue between product, engineering, design, data, sales, support, and all of it. It's not a replacement for product management. It's the engine that lets product managers do the discovery work they're actually supposed to be doing. SAM: And they break it into three pillars, which I thought was a really clean way to organize it. The first one is data and insights. And their point isn't that teams lack data. It's that they're drowning in it. SOPHIE: Yeah, that's the part that got me. A product manager spends half a day piecing together one simple answer about user behavior, and then the marketing numbers don't match the engineering numbers, and now nobody trusts anything. SAM: I've lived that. You ask a basic question and you get three different answers from three different dashboards, and you just pick the one that tells the story you already wanted to tell. SOPHIE: Which is the opposite of evidence-based anything. So product ops owns the data infrastructure for the product team. It defines a single source of truth, it builds dashboards people actually use, and it sets up data governance so the numbers stay clean. SAM: And they're clear this isn't just hiring an analyst and calling it a day. It's building a systematic way for every team to ask the right question and get a reliable answer fast. SOPHIE: Then the second pillar is strategy and execution, and this one's about the gap between the CEO's big vision and what teams are actually building in Q3. SAM: The strategy-deployment gap. I love that phrase. The annual vision gets announced, everyone nods, and then the quarterly roadmap looks like it came from a completely different company. SOPHIE: And product ops bridges that by creating a shared language, like using OKRs consistently, and by designing the operational rhythms so the planning sessions and the reviews actually tie back to outcomes. SAM: There's also the roadmap piece, which I think a lot of people will feel. Instead of a static feature list that's obsolete the second it's printed, product ops helps build a dynamic, outcome-focused roadmap that explains the why behind the work. SOPHIE: And they manage dependencies, which sounds boring until you've been the team blocked for three weeks waiting on another team that didn't know you existed. SAM: Right. Product ops creates the visibility so those conversations happen before the blockage, not after. SOPHIE: Then the third pillar is customer and market insights. And the problem they name is that feedback gets collected haphazardly. A comment from a support call here, a feature request from a sales meeting there, and none of it ever gets synthesized. SAM: So product ops formalizes the loop. A central repository for research, a standard way to run interviews, and feedback from support and sales actually flowing into discovery instead of evaporating. SOPHIE: And the goal is to democratize customer understanding. A designer working on a feature should be able to pull up the latest research on that exact user segment without begging anyone for it. SAM: That reframes the whole company, right? From internally focused on output to externally focused on customer outcomes. SOPHIE: Okay, but here's where I want to push back a little, because when I first heard product ops I thought, great, more process. Isn't this just bureaucracy with a nicer name? SAM: And the authors actually call that out directly. They warn against turning product ops into a project management office for the product team, where it becomes a gatekeeper that slows everything down. SOPHIE: Right, and that's the failure mode. If product ops becomes the team you have to get approval from, it has failed. The whole point is removing obstacles and providing clarity so teams move faster with more confidence. SAM: There's also a whole section on how you actually build the function, and they're clear there's no one-size-fits-all. In a small company it might be one person wearing five hats. In a big enterprise it could be a centralized team or embedded partners in each vertical. SOPHIE: And the hiring profile is interesting. A good product ops person isn't a junior PM. They're a blend of project manager, data analyst, process designer, and and change agent. A systems thinker who's also detail-oriented enough to build a reliable data pipeline. SAM: Which is a rare combination. You need someone who can see the big picture and also care whether the dashboard numbers reconcile. SOPHIE: They also make the case that this needs executive sponsorship, because it's a top-down shift. Leaders have to invest in the infrastructure and be patient, because the payoff is often invisible. SAM: That's the line that stuck with me. The payoff is the friction that doesn't happen. The meeting that doesn't need to be scheduled. The data that's just trusted. That's really hard to put on a slide. SOPHIE: So they suggest tracking things like cycle time, data accuracy, and team satisfaction to show the value. And there's a whole chapter on tooling, where product ops stewards the tech stack so you don't end up with fifteen tools that don't talk to each other. SAM: Which is its own kind of chaos. You buy a tool to solve a problem and create three new integration problems. SOPHIE: Exactly. And they're clear product ops isn't IT. They're the advocate for the product team's operational needs. SAM: So the big reframe for me is that product management is the art of deciding what to build, and product ops is the science of making sure it actually gets built, learned from, and improved. That's the one thing I'm taking away. SOPHIE: And if you want to go deeper, everything's over at 7minutebooks.com/app, with over 6,000 fiction and nonfiction titles you can read or listen to in any language. It's $2.99 a month, $9.99 a year, or $19.99 once for lifetime access. SOPHIE: The whole point is that scaling doesn't have to mean chaos. Build the system, and the smart work becomes the default. We'll see you in the next one.