The Productologist

Bug scrub is a word that strikes fear and hatred into the hearts of many Product Managers (Developers, QA leads, Release Managers, and Project Managers, too). Not because of the purpose of bug scrub–dispositioning recently filed product defects–but because the process behind the purpose can end up being so heinous and painful.

For the uninitiated, the Cranky Product Manager provides a valuable, albeit hyperbolic glimpse inside the bug scrub process. She highlights the frequent discord and conflicting interests that makes bug scrub such an ordeal and one that all-to-frequently ends up being internally-focused rather than customer- or market-focused.

On my work calendar, I have the first 30 minutes of each morning blocked off so that I can review the tasks for the day and read any email and listen to voicemails that came in overnight. I do this because I know that it will help me stay focused on what needs my attention most. Unfortunately, this level of organization doesn’t fit well with what my job requires.

Most mornings, I get into the office 20-30 minutes before my scheduled review block. I regularly do the one or more of the following things: