Angela Blake

I asked a Product Ops lead last week: "What did you accomplish this quarter?" She pulled up a slide deck. Twelve pages. Charts showing meeting attendance, workshop completion rates, and roadmap decks delivered on schedule. I asked a different question. "What decision did a product team make faster because of your work?" Silence. Here is what I have learned. The best Product Ops work I see has nothing to do with meetings. It is about designing systems that make coordination unnecessary most of the time. Three examples from this year: A Product Ops lead at a B2B company killed five recurring dependency syncs. She replaced them with a one-page decision rights map. Teams went from four hours per week in alignment meetings to decisions made in a Slack thread. Another built a self-service platform adoption dashboard. Leadership stopped asking for weekly status reports. They started asking how to get more teams onboarded faster. A third gave teams an outcome hypothesis template. The roadmap went from 400 output items to 60 measurable bets. Lead time dropped from 11 weeks to 4 weeks. None of these examples involved adding more "meetings". All of them involved designing systems. If your Product Ops role is spending 70 percent of their time in coordination meetings, they are not fixing the system. They have become part of the problem you hired them to solve. New blog post breaks down what high-value Product Ops work actually looks like, plus a "What to Stop Doing" section that most teams need to read. Link in first comment! ProductOps #ProductManagement #AgileLeadership #TeamTopologies #DORA #TechLeadership

Great product management isn’t just about what we build — it’s about how we build it. One of the most underrated parts of a PM’s role is partnering closely with developers and architects to create a development plan. Not just hearing time and resource estimates, but digging in enough to appreciate why certain implementations are harder, why constraints exist, and what trade-offs we’re really making. The best PMs don’t need to be software engineers, but they do need enough technical fluency to ask the right questions, challenge assumptions, and spot when a “small change” is actually a significant shift. Equally important is respect — respecting the craft of defining the right approach, anticipating future needs, and the reality that there’s rarely only one “correct” solution. Strong PM/engineering relationships are built on trust, healthy debate, and the shared goal of delivering customer value without compromising long-term quality and maintainability. Great PMs know when to listen, when to push back, and how to navigate that space in between — where real product excellence is created.

18

2 Comments