One of the primary things that Product Managers are constantly working on is change — changing the way people view our customers, changing the way our customers view our product, changing the culture of our company to be more agile, changing peoples’ minds about what’s important and what’s not…the list goes on and on. And, not surprisingly, nearly every Product Manager eventually comes to the realization that change is hard. I mean really, really hard. And sometimes it seems like even the smallest changes are the hardest to get people to commit to and deliver on a regular basis. So why is change so hard? Here are a few of the common reasons…
It’s been awhile since I’ve posted one of my “PM 101” articles, so I figured with 2017 just kicking off now is as good a time as ever! Past articles have focused on marketing, sales, and design teams, but this time I want to focus on service teams. These types of teams are your integration specialists, your technical sales people who come in after a deal has closed to help clients onboard, or even your own internal team that uses your product on behalf of your customers. No matter where exactly they sit in your organization, service teams can be a prime source of information and validation for any Product Manager.
A couple years ago, shortly after I launched the blog, I posted my first New Year’s Resolutions for Product Managers, which was a big hit. Somehow it slipped my mind to update it for 2016, but here I am with an update as we roll into the new year…one as full of uncertainties as it is full of opportunities! Without further ado, here are five new resolutions for Product Managers moving into 2017…
Here we are at the end of another year — I honestly can’t believe that 2017 is just around the corner!! Over the past year I’ve had the pleasure of engaging with all sorts of new folks, provided some mentoring to new and experienced Product Managers, taught a couple classes at General Assembly, and even started work on a book I hope to launch next year! I hope the past year’s been just as varied and interesting for all of you regular readers out there, and to close out 2016, I’ve put together the following list of the “Best of” for the past year. So, without further ado, here’s the top 10 Clever PM posts for the year!!
It’s become an annual exercise here at The Clever PM to create a list every year of the five things that Product Managers should be thankful for — it started the first year, continued into the second year, and is now rolling into the third year as your go-to source for tips, tricks, and hacks to become a better Product Manager. So, without further ado, the 2017 list:
Never have I heard a better description of the challenge that faces Product Managers than a quote that I overheard at this year’s ProductCamp Seattle — “Humans are hard…” spoken by none other than my fellow General Assembly Product Management instructor Tricia Cervenan, as part of a panel discussion. Those simple words struck a chord with me, as it made me think about all of the different ways in which we as Product Managers attempt to understand, document, and predict human behavior. Every single day I can come up with some variation on the idea that “humans are hard” impacts us in some way. [Read more…]
I’ve touched on User Stories on several occasions, my favorite being Why Your User Stories Suck! Today I’m here to share with you a very common, yet very commonly overlooked, way to check each and every User Story on your backlog to see whether or not it’s really “ready” for your Dev teams. One of the most frequent causes of delays and slowdowns in most Agile implementations that I’ve seen comes from a lack of balance in the User Stories that the team is being given to deliver — stories that are too big, or which are dictates, or which just exist on the backlog because “someone asked for it”. What we need to do as Product Managers is to occasionally take a close look at each of our backlog items and make sure that they meet the INVEST criteria — Independent, Negotiable, Valuable, Estimable, Small, and Testable. If we do this simple gut-check on a regular basis, we’re far more likely to see our teams succeed and to reduce the amount of time wasted in long, drawn-out planning sessions.