The Productologist

If you are like most Product Managers that I know, you spend more time than you like in meetings. In the best of worlds, meetings can be productive endeavours where decisions get made and progress happens. Sadly, I don’t live in the best of worlds. Meetings in my world are sometimes useful. They can impart information, allow for vigorous dialogue and keep everyone’s priorities and effort in alignment. They can also be a colossal waste of time, especially when attendees are late or absent altogether.

There’s an interesting thread going on across several blogs about the Agile development method (Agile, here and across other posts, is being used as a catch-all for many rapid release methodologies) and the role of Product Management. I have posted an article and made comments on several of these blogs, but this post isn’t about that. It’s about the relationship between Product Management and Engineering.

The Cranky Product Manager, in her post about Agile, and a response from one of the other bloggers involved in the discussion demonstrates the tension between Product Managers and Engineering groups.

In a post I wrote back in March [Hiring for Success], I discussed the importance of finding and hiring great Product Managers. But in the same way that great workers can be a boon to your organization, poor performers can drag you down. Not only do they create more work for others on the team, but they can poison the atmosphere and cause other members to become frustrated or leave.

“When they (managers) finally decide to get rid of the under-performing slob who plays PC solitaire all day in her cubicle, it can be surprisingly tough to do. And that, in turn, affects productive workers. Few things demotivate an organization faster than tolerating and retaining low performers,” says Grant Freeland, a regional leader in Boston Consulting Group’s organization practice.