Most Product Managers have, at one time or another, heard the apocyphal quote often attributed to Henry Ford, “If I asked my customers what they wanted, they’d have said a faster horse.” And when we hear the line, we laugh because there’s no way that we would do such a thing — the “faster horse” is a fictional thing that we’d never actually spend out time and effort working on. We slap each other on the back, smile, and then go back to our office where all too often we return to working on the “faster horse” that we’ve deluded ourselves into thinking is innovative and fresh. It’s an unfortunate fact that much of what we do really is just delivering faster horses, giving our customers what they say they want (or worse, what sales tells us they say they want), and not digging deep enough to uncover the real need, problem, and desire that’s driving the request.
Prioritization is More Art Than Science
A very common challenge faced by Product Managers of all experience levels is understanding and implementing some form of repeatable process around prioritization. Some people take a very light approach, making decisions based on their own experience, data, and beliefs about the direction of the product. Others take a much more rigorous approach, applying scorecards and “objective” measures across a plethora of different possible metrics. I’m here to tell you, there’s nothing wrong with either of those approaches, but it’s also become clear to me in my years as a Product Manager that there’s no “silver bullet” to ensure that your prioritization decisions will be right more often than they’re wrong, and placing too much value in systems and scores often just results in a false sense of security that the “process” was right, when digging in you’ll find that those “objective scores” are nothing more than a system to be gamed. There are, however, three things that I think every prioritization system needs to take into account. So, without further ado, let’s discuss value, difficulty, and instinct…
Certifications — Are They Worth It?
I’ll be attending my second formal training this year, getting my Certified Scrum Master certification to match the Certified Product Manager certification that I picked up earlier this year. After 15 years in the business, you might wonder why I’m just now getting around to being “certified”, and I hate to say it but the real reason is simple — the company I work for is paying for it. Otherwise, I’d happily chug away for another 15 years without any form of certification, because I firmly believe that the experience that I have in transforming companies into agile engines is far more valuable in the abstract than any specific certification that I might collect along the way. But, there are a few times when and where a certification might be worth pursuing…let’s talk about those today.
10 Questions with Stephen Cognetta
One of the best things about my blog and other activities is to meet new and interesting people in the Product Management community. Today I’m happy to present the latest in my 10 Questions series, featuring none other than Stephen Cognetta. His latest project is an ambitious online Product Management interview course that was launched just last month. Stephen’s a really great guy, and a strong voice in Product Management; in his own words…
Stephen Cognetta is the founder and CEO of PMLesson, the best online PM course focused on practice-based learning. Stephen is passionate about mental health and has also founded HackMentalHealth, the world’s largest community of mental health + technology advocates. Stephen is a minimalist and owns under 115 items.
Without further ado, here’s his installment of 10 Questions with the Clever PM!
Data v. Opinion: The Ultimate Battle
Sometimes Failure is the Best Result
As a Product Manager, it’s in our bones to always do the best job possible, to deliver the best product possible, and to satisfy the most customers possible. But what if I told you that by always succeeding, we’re actually hampering ourselves? While it might feel good to hit a home run every time you step up to the plate, you’re probably not playing in the right league. It can be easy to fall into a pattern of complacency, of certainty, of feeling invincible because you never miss a swing — but the simple fact is that if you’re never wrong, you’re playing it too safe and you’re limiting yourself to only what you know that you can accomplish. It takes bravery to step outside our comfort zones, to stretch ourselves and test our boundaries, and to try new things that aren’t guaranteed to be winners. In fact, failure is essential to growth not only as a Product Manager but as a person in general — for it is only in failure that we learn from our mistakes and can adjust to ensure that the next stretch, the next test of our abilities, passes with flying colors. If you never fail, you never grow…
Five Differences Between a Junior PM and a Senior PM
Even though it’s been around as a formal role in software organizations for nearly 20 years (or more, depending on who you talk to), Product Management still struggles with a lot of definition problems — what is the role, how do we grow, when do we get promoted and to where, etc. One of the common issues that we run into are companies who don’t have any form of structure around their product teams, who struggle to define the actual differences between their “associate”, “general”, and “senior” Product Managers without simply resorting to the amount of time they’ve been in the role. As anyone with extensive experience in the profession can tell you, how long you’ve been doing the job has little to no bearing on your actual ability to do the job — you can work for 10 years practicing all sorts of bad behaviors that have resulted in zero growth as a Product Manager. Similarly, you can go deep and hard for 2-3 years and come out the other side as a true product leader and influencer, capable of taking on much more advanced products and projects than your companions. Here are a few of the common differences that I think draw dividing lines between a “junior” Product Manager and a “senior” Product Manager, where age is not the most important factor…
- 1
- 2
- 3
- …
- 16
- Next Page »