AMA: GitLab Group Product Manager, Derek Ferguson on Product Strategy

Executives care about impact on the business, risk, and whether you've actually thought it through. Your job is to address all three without making them sit through a 40-slide deck. The biggest mistake I see PMs make is leading with the product case. They start with the customer problem or the technical architecture. Execs care about those things, but only in service of business outcomes. Start with the business case: here's the market opportunity, here's how we capture it, here's what it means ...Read More

The instinct most market leaders have is to play defense by protecting what they have. A competitor ships something and the reaction is "we need that too." That's exhausting and usually wrong. You stay ahead by delivering better outcomes and investing forward, not by playing whack-a-mole every time someone ships a feature your users might like. The real defensibility of a market leader isn't the feature set. Features can be copied in a quarter. What's hard to replicate is how deeply you're embed ...Read More

People often approach competitive strategy reactively. A competitor ships something, the team scrambles to respond, and the roadmap turns into a game of catch-up. You'll always be a step behind if your competitive strategy is "watch what they do and respond." The goal is to build a practice where you're consistently making better decisions about where the market is going, so that when a competitor does something surprising, it's a data point, not a crisis. On staying competitive: Maintain a livi ...Read More

I revisit strategy at three cadences, each doing something different. Weekly (continuous): I'm always scanning for signals that challenge my assumptions. Customer conversations, usage data, competitor moves, things the engineering team discovers during implementation. I keep a running log of "things that surprised me" and review it weekly. Most weeks, nothing rises to the level of a strategic change. But the habit means that the one week something does, I catch it early rather than three months ...Read More

TLDR: engineering leadership, your management chain, design, sales/customer success, and cross-functional product peers. Engineering leadership is first on purpose. This is the most important internal relationship a PM has. If your engineering counterpart doesn't believe in the strategy, execution will suffer regardless of how good your deck is. I involve engineering leads early, before the strategy is fully formed. Not to get sign-off, but to stress-test feasibility and surface constraints I mi ...Read More

A big mistake PMs make with strategy is treating it like a document you produce once and then "have." Strategy is a living argument for why your product should exist, who it should serve, and what bets you're making to win. The document is just the artifact. The thinking is the strategy. Start with the landscape, not your product. Before I write anything, I spend time understanding market forces, competitive dynamics, and customer pain. That means talking to customers, reading analyst reports, m ...Read More

Retention feels like it should be a simple metric, but it's actually one of the more strategic problems you'll work on. A lot of retention frameworks give you a useful structural map, but even the ones that move beyond funnels into loops tend to treat retention as a distinct problem category rather than a quality signal that runs through the entire product experience. Viewing it that way changes where teams look when retention drops. If you're thinking in stages or sub-curves, you tend to reach ...Read More

Both. But the second one is what separates good PMs from great ones. Every organization has a planning cadence… annual planning, quarterly OKRs, six-month roadmaps, whatever the rhythm is. You should absolutely participate in those cycles and use them as forcing functions. But if you're only doing strategy when the org tells you to, you're already behind. What "always on" means in practice is that every customer conversation, every competitive signal, every data anomaly feeds your strategic thin ...Read More