The Productologist

I recently decided that it was time to get a replacement to my dead USB mouse, which I used when I moved my laptop to conference rooms, prospect and customer sites and while traveling. I had put off replacing it, since the laptop provided by my employer has both a track pad and keyboard nub pointing device and I figured that I could get by using one of those when I had to undock from my desk. However, I have come to the conclusion that pointing devices that are built into the laptop are fine for general UI navigation (starting apps, opening files and the like), but not so much for hard-core navigation inside an app or through a document. Enter the Logitech VXNano.

I have read (examples here and here) and heard in numerous places that a Product Manager is like the CEO of the product. I’ve even used it to describe what I do to folks who are unfamiliar with the job. It makes for a nice visual and makes Product Managers feel good about themselves and the role that they play in a company. But it’s not really true.

I’m a big fan of addressing human factors in product design. Since I primarily deal with software products, my focus is on usability and simplicity (two similar, but not identical concepts).

In a recent edition of Business 2.0, I came across an article entitled, “Design that Captures the Buzz,” which highlights how cellphone headset makers are hiring product designers to improve the “fashion factor” of bluetooth headsets. While I don’t think that fashion, per se, is that important to software design, I applaud the use of designers to improve both the appeal and functionality of a product.

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.