In many organizations, conflict is part and parcel of the culture — some conflict can be constructive, some destructive, but most of it can just be downright annoying. And, because we often sit right in the middle of all of the random agendas, battles of ego, and emotional storms that can rage throughout the company, Product Managers often wind up dealing with the outcome of these conflicts if we’re not pulled deeply into them by one or more of our stakeholders. And while it can often be tempting to take on all comers, to defend your territory and your teams to the bitter end, the sad truth is that all too often, these conflicts simply aren’t set up in a way for us to “win” — and seeking that extra mark in our “W” column can often be counterproductive rather than helpful in the long run. All of the best Product Managers know that sometimes when there’s a fight that you’re not going to win, it’s far more important to lose gracefully than it is to die on a hill for something that ultimately didn’t really matter much.
At some point in my meanderings online, I heard tell of a Slack channel that had been set up for Product Managers to engage with each other and discuss topics of concern to those in the profession. And, being the Clever PM that I am, I had no choice but to check it out — that channel turned out to be hosted by the folks at the Product Coalition, and administered by none other than Jay Stansell. The channel has turned out to be an exceptionally popular location for PMs to share articles they’ve written, ask for thoughts or feedback on idea that they have about how to improve the craft, and even to just humbly ask for advice when they’ve hit a brick wall on something. When creating my list of participants for this 10 Questions series, I knew right away that I’d want Jay’s thoughts on the role, and he was more than happy to oblige.
In his own words:
I’m a product person, who is grounded in design, shaped by technology and inspired by profitable business models. I “cut my teeth” in a travel start up in 2007, and grew it into one of Australia’s leading travel products. I’ve since been fortunate to craft products and product experiences for some of Australia’s largest brands. Today, I take my start-up learnings, attitude and culture, into coaching Agile, Lean Startup and Design Thinking methodologies at Australia’s most innovative insurer, IAG.
What I’ve enjoyed the most from my story so far, is the talented people who have become friends. It’s these connections that inspired me to launch the product community ProductCoalition.com – a place for product people globally, to connect, collaborate and inspire.
And without further ado…my ten (eleven) questions for Jay…
A recurring challenge that many Product Managers face is coping with stakeholders who attempt to block our efforts, either covertly or overtly. Sometimes these situations arise due to simple miscommunication, but other times they’re power plays, the results of internal politics, or even caused by grudges held from previous slights — real or imagined. To excel in Product Management, one must not only deal with these blockades as they arise, but you need to predict when, where, and how they’re likely to come up so that you can head them off before they even become an issue. To do that, though, we have to try to figure out what the most common reasons are for stakeholders to actively or passively interfere — and that’s what the Clever PM is here to share with you. In this first installment I’m going to focus on overcoming passive resistance, and we’ll address more active resistance in a future piece.
There are a great many different corporate cultures to be found in the world, but one consistency among far too many of them is decision-making processes that rely more on gut-level instinct and whomever yells the loudest rather than on hard data. For some companies, this has served the CEO well — a small, nimble startup can’t always waste time doing detailed validation or data-gathering in a “stop moving forward and you’ll die” environment. In other companies, it’s become the de facto standard due to strong personalities who may prefer authoritarian leadership styles over more democratic and empowering styles. Regardless of the reason, though — companies like this eventually wind up struggling because they make the wrong choice one time too many, based on the leaderships “market instinct”. And it’s our job as Product Managers to shepherd these companies into a more modern-day, data- and hypothesis-driven approach. Here are three major reasons why data-driven management is far more effective than management by gut or personality.
We’re often told that Product Managers “lead through influence” — that we don’t generally have the direct authority to get things done, but rather do so through convincing others of the best option available from the myriad choices they have. The bad news is, that’s really damn hard. The good news is, we’re not alone — in any given organization there are many different teams and members who lead through influence rather than authority…and identifying who they are and how we can work together with them is an essential tool that every Product Manager needs to have in their back pocket in order to be successful. Here are some clues that we can look for to identify those fellow influencers so that we can work with them and not against them.