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.

When was the last time you included User Interface (UI) requirements in an MRD? If you are like most Product Managers, you may have included a reference like these in your MRD (I’ll admit to using at least one of them)–

• Need to make the UI easier to use
• The new screens must follow the existing screen design
• Replace old icons with new ones
• Change the colors to match our new logo

Unfortunately, not only are these not easily actionable, but they don’t get to the root requirement, which is how to make the product more clearly understood and easier to use so that the user has a positive experience.