My Inner Product Manager

I made curry this morning, and wanted to share it with chalain over lunch. I figured it would be a good way to spend lunch, and since I haven’t seen him in weeks, it seemed like an easy “in.”

He agreed. I brought curry to his place of work, and arrived just in time for the “War Meeting” of developers there. The guy holding the meeting is a friend of mine, so I stuck around and ate curry while they talked about defect fixes, feature creep, and the rest of the stuff that I remember fondly from Novell.

I even contributed. My inner Product Manager can’t NOT contribute, as he gets out so very rarely these days. There was some discussion about how a customer request could better be met in different ways, but how the customer might be upset if the feature wasn’t implemented the way they’d asked. It’s a risky thing, second-guessing the customer, and it’s almost NEVER something you want to let the engineers do. But in this case the engineers had it right. The feature request exposed missing functionality, and by installing the missing functionality the request for the feature would either a) go away, or b) be solveable with a simple hook into the new functionality.

Rodney and Chalain and I stuck around for a bit after the meeting and talked. I envy Chalain just a little — he’s got skills that are in demand, and he’s working for a small, dynamic company that appreciates him. But I only envy him a LITTLE. His company has allowed the customer all the way inside the development process, so they’ve got institutionalized feature-creep and “two master” syndrome that makes serving God and Mammon look like nothing more than an unpaid parking ticket. In another state, on a University campus six years ago.

I’m glad I’m a cartoonist. My inner Product Manager is going back in his box now, and I’m taping the lid shut. He’s pretty bright as Product Managers go, but he never could fight his way out of a cardboard box.


3 thoughts on “My Inner Product Manager”

  1. Quote Wall Fodder

    Rodney made Howard do a spit take, and has been giggling about this repeatedly ever since. Some necessary backstory:

    1. In the room that Howard met with us, we have a whiteboard where we write funny quotes.

    2. We categorize all of our bugs for War Meeting by priority. Priority Zero, or “p0”, are bugs you have to fix NOW, before you go to the bathroom or get a drink. p1’s are critical bugs, also to be fixed urgently–but you’re allowed to go home at night with the bug unfixed. p2’s are bugs that have to be fixed before the next milestone; p3’s before the product ships.

    3. Rodney idolizes Howard.

    The quote that is now on our whiteboard, and that made Howard choke:

    “Well, you see, our entire UI is a p1.”

Comments are closed.