One of Amazon’s prized leadership principles is “Be right, a lot.” And we should certainly strive for that as Product Managers, no matter what company we work for, or what product we’re working on. But there’s a corollary to that statement that’s equally important — that you’re not going to be right all the time. And that’s a good thing, believe it or not. Making mistakes is part of the game that we play on a daily basis, and it’s only through making these mistakes that we learn, we grow, and we understand that we’re willing to take the chances needed to truly innovate! If you’re not wrong at least part of the time, you’re either a certifiable genius who outranks even the Elon Musks and Bill Gates of the world — or you’re not truly taking chances.
Archives for March 2018
10 Questions: Greg Hartrell
A few weeks ago, I was perusing Quora as I often do, and came across a really great and insightful answer describing the differences between a “good” and “bad” roadmap by Greg Hartrell. The answer was so good that I couldn’t help but reach out him, and invite him to share some of his insights here on my blog. Here’s a bit about Greg in his own words…
Greg Hartrell is a product leader with a 15 year history helping large teams build high performing software products and businesses. At Google, he heads product for Google Play Books and previously led the creation of their mobile game services. Before that, he was VP of Product Development at Capcom/Beeline, and a product leader for 8 years at Microsoft for Xbox Live/360 and Windows.
Sometimes Success Takes a Little Luck
Have you ever stopped to think about what makes some products successful while others languish in obscurity? What made Orkut fail while Facebook took the world by storm? What made StackExchange such a tremendously popular forum when there are literally thousands of others who have attempted the same thing? As much as we Product Managers want to believe that there’s some magical formula of product/market fit, compelling MVP features, and user-centered design that is guaranteed to make our product a success, the simple fact of the matter is that there’s a lot of luck involved in whether or not our solutions “stick” in the market and whether or not our ideas lead to successful products.
Looking Back to Look Forward — Understanding Retrospectives
There’s a tool in the Scrum toolbelt that is so utterly critical to success yet so fundamentally misunderstood by far too many development teams, Scrum Masters, and Product Owners. I’m talking, of course, about the Sprint Retrospective. I’ve seen it time and again, teams that are able to hit all the right notes in their standups, reviews, and planning sessions — but who wind up botching their Retrospectives in such a horrible fashion that they miss out on the single most important part of agile product development, continuous improvement. Certainly, it’s never fun to take time out of our day to look back and discuss what went wrong in the past two weeks — much less try to come up with new things to try on a sprint-by-sprint basis. But it’s the single most important part of the culture that we’re trying to build — the culture of agility, of adjusting, of improving…of change.
What is the Value of Agility?
One of the many challenges that Product Managers face in trying to move organizations toward a more agile approach to product development is that some stakeholders simply don’t see the value in the shift. They believe that, since their way has worked for them for so long that there’s no need to change — after all, it can’t be broken if it works, right? But the simple fact is, the bad old ways of product development are dying, as markets and customers move faster and have more options available to them to solve their problems every single day. There’s not a single industry that isn’t facing high-investment newcomers who are able to move fast and adjust — and leave they’re slow-moving, waterfall-based competition in the dust.