All articles on Practice.
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.
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.