Follow up to Product or Project Management

As a short and sweet follow up to my previous posts around product or project management (Part 1 and Part 2), I wand to add two more perspectives from other sources to the conversation:

1) The classic: Ben Horowitz – Good Product Manager / Bad Product Manager

2) A more recent article: Aha!-Blog – 5 Signs you should be a product manager

Product or Project Management – Part 2

I had previously shared my thoughts around the differences between Product Management and Project Management; yet, life moves on, and we learn more (hopefully) and our perspectives may change as a result of that learning. At least, we’d hope it would.

I have recently embarked on a new adventure, of which I am not sure yet where the journey will lead me (feel free to take a peak and comment on my idealistic ideas). Alas, as part of that journey, I have revisited the thoughts and definitions around product management and project management.

My current thought process defines those two terms as follows:

Product Management – conceive and nurture ongoing the greater idea of a product or service, its value proposition and idealistic goal

Project Management – implement the vision via smaller, logically sequenced incremental iterations (projects) that range end-to end (scope, development, test, communicate, deploy, teach)

Reflecting on those two high level definitions today, I still arrive at the conclusion that both are intricately connected, dependent on each other for insight and progress alike. As such, attempting to draw a dividing line between the two definitions would inherently cut off a vital component of each concept’s very nature, without which neither can succeed.

Which school of thought do you align with more closely? I would love to hear about it!

Do whatever it takes if it has the potential to improve the user’s experience

Expounding on a previous short post, I felt strongly to add some more after this morning’s first cup of coffee.

Cannot get this out of my head:

Most people make the mistake of thinking design is what it looks like. That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.

…says Steve Jobs in an excellent article on the birth of the iPod.

While navigating my favorite information sources this morning, I found this awesome post – “Could you really be a UX designer“.

There are so many “job descriptions” and titles out there, and they all mean different things to different people. The author, Paul, doesn’t lose time with labels, instead, he hones right into what matters at the heart of it:

adjust your attitude and collaborate!!

The closing sentence sums it up for me especially:

Do whatever it takes, if it has the potential to improve the user’s experience.




Every day