What a Bad Product Manager Would Do and Countering With What a Good Product Manager Would Do

For a non-programmer, non-entrepreneur, non-consultant, non-manager, and non-innovator I read a lot of articles on programming, entrepreneurship (e.g. natural enterprise), consulting, management, and innovation. I read articles about, for example, requirements gathering best practices (pointed out by Boris) without ever expecting to gather requirements. And yet, I can't get enough, probably so that I can properly evaluate those who are programmers/entrepreneurs/consultants/managers/innovators or maybe just because those types of people and those types of careers interest me.

So, as a non-product manager, I spent the last couple of hours reading with interest the entire archives—yes, the entire archives—of Good Product Manager a weblog written by Jeff Lash. There's an emphasis on software/online product management, but Jeff is careful to include links to others in the field and collects anecdotes about physical product management as well. The weblog follows the model of briefly stating what a bad product manager would do and countering with what a good product manager would do. Posts are short but meaty, for 'fast food readers' out there.

(If you were wondering, someone has already claimed the title and I can't claim to have invented the phrase for the field because the phrase pre-exists on the web, but I bet if you were a product manager for the new generation of online community and collaboration tools, you could legitimately call yourself a 'social product manager'.)

Comments

Haven't you attended related seminars to improve more your practices in the field you are into?