Writing on product management, knowledge work, and personal productivity. First-person, opinionated, written for mid-to-senior PMs navigating real environments.
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.
Your product spec was written once, then abandoned the moment the first sprint started. Now your backlog is the only record of intent. It’s not a plan. It’s a pile of corrections to a plan that was never revisited. But once you see User Stories as Product Spec patches, you can begin managing accordingly. This shift changes everything.