Writing on product management, knowledge work, and personal productivity. First-person, opinionated, written for mid-to-senior PMs navigating real environments.
Has discovery ever killed a feature at your company? Not delayed one. Not reshaped one around the edges. Killed one. The answer tells you everything. Every product team I’ve worked with in the last five years runs continuous discovery. Weekly customer interviews, opportunity solution trees on the wall, synthesis sessions in the calendar. And in almost every case, the actual product decisions still get made by whoever holds the most organizational authority in the room.
Someone in a post-mortem always says it: “Why didn’t anyone flag this?” The risk register exists to make that sentence unsayable. Not because it tracks risks, every project does that informally, but because it forces the people in the room to say, on the record, what they plan to do about them. That’s not an organizational function. It’s a political one. And most PMs are using it wrong because they’ve never understood what it actually is.
In my first years in product management, I had all the tools: Jira boards, sprint backlogs, wiki pages, stakeholder decks. Yet the same conversations kept recurring. About priorities. About why we’d dropped things. When I mapped two sprints of actual work against the type of contribution each task made, the pattern was obvious. I wasn’t overloaded. I was unbalanced. The category I was systematically ignoring was Clarity — the one that makes every other type of work more effective.
I often walk into a planning session knowing that a significant portion of my team’s capacity is already spoken for. Not by features. Not by tech debt. By compliance. And when I present a roadmap that reflects this reality, colleagues look at it and ask: “Why is Q2 so thin?” It isn’t thin. It’s honest. But most roadmaps in regulated industries aren’t.
In December 2022, my team at Trusted Shops killed the biggest feature of the year. Not because it stopped working. Because it worked too well on the wrong axis. We had pushed review questionnaire conversion up by a huge percentage. Internally, the win of the year. Three months later, we rolled it back. We learned that the volume of negative reviews mattered more to our customers than the volume of reviews overall.
Most product teams I’ve worked with believe they have a strategy. They can talk about it in meetings, reference it in planning sessions, and nod along when leadership mentions it. But when I ask a simple question, “Can you show it to me?”, the room gets quiet. That silence tells me more about the state of a product organization than any roadmap ever could.
Your VP rewrote the project scope in April, championed it in the all-hands in June, and by September, when the integration failed and three teams were blocked, opened the incident review with “Help me understand what went wrong on the execution side.” You were the execution side.
Even talented PMs get crushed by a fundamental misunderstanding: they think accountability flows upward. The real skill isn’t documenting your blockers — it’s weaponizing transparency to force organizational change. This isn’t another article about documentation trails. It’s about making organizational inaction as visible as your own delivery commitments, and what it tells you when that still isn’t enough.
There is a specific kind of frustration that comes from looking upward in an org chart and realizing that multiple layers of leadership are staffed by people who are clearly intelligent, clearly skilled, and clearly wrong for their roles. Your direct manager rewrites your proposals. Their manager cannot make a strategic decision without a committee. The VP above them treats every product conversation like a sales pitch because that is what got them promoted fifteen years ago.
A debt sprint is a confession, not a strategy. It’s an admission that debt was never part of normal prioritization, dressed up as a responsible act. If you’re a PM who has ever scheduled one, you already know this. You felt the relief when it landed on the roadmap, and you felt the velocity drop resume two sprints later. Technical debt doesn’t accumulate despite your backlog decisions. It accumulates because of them.