{"id":18613,"date":"2023-12-11T14:41:05","date_gmt":"2023-12-11T14:41:05","guid":{"rendered":"https:\/\/productcollective.com\/?p=18613"},"modified":"2024-01-26T16:23:21","modified_gmt":"2024-01-26T16:23:21","slug":"mastering-stakeholder-management-for-product-leaders","status":"publish","type":"post","link":"https:\/\/productcollective.com\/mastering-stakeholder-management-for-product-leaders\/","title":{"rendered":"Deep-Dive – Mastering Stakeholder Management for Product Leaders"},"content":{"rendered":"

As a product manager or leader, your ability to manage stakeholder relationships is as critical as your strategy and execution skills. In fact, those relationships have a real chance to make or break a project whether it\u2019s a new product launch, product strategy planning process, or any other project your product team is working on.\u00a0<\/span><\/p>\n

Think about it: When you\u2019ve experienced a project going off the rails in some way \u2013 how strong was the stakeholder communication in that failed project? Chances are, it wasn\u2019t very strong at all \u2013 as <\/span>a leading cause of tech projects failing comes down to ineffective stakeholder communication<\/span><\/a>. This reality highlights the crucial role of stakeholder management in the tech industry, making it an indispensable skill for product professionals aiming to drive successful outcomes.<\/span>Yet, sometimes conflict gets confused with a lack of communication. Conflict with stakeholders can be quite healthy\u2026 and it\u2019s simply inevitable. Understanding the inevitability of conflict in our highly interconnected roles to learning how to manage it constructively can equip Product Managers and Product Leaders with practical insights and tools that can ultimately translate into more successful projects. This isn’t just about <\/span>avoiding<\/span><\/i> pitfalls; it’s about transforming potential conflicts into opportunities for innovation and effective collaboration. By the end of this read, you’ll have a clearer understanding of how to turn challenging interactions into productive dialogues and build stronger, more successful products through enhanced stakeholder management.<\/span><\/p>\n

\"\"<\/a><\/b><\/p>\n

The inevitability of conflict within your Product Team<\/span><\/h3>\n

On any product team, conflict isn’t just a possibility; it’s a given. The role of a Product Manager is inherently collaborative, requiring constant interaction with a diverse set of stakeholders, each with unique goals and perspectives. These stakeholders range from developers and designers to marketing teams, sales departments, and upper management. The diversity of these groups, essential for a well-rounded product, naturally leads to a variety of viewpoints and, inevitably, conflicts.<\/span><\/p>\n

However, that conflict, when managed properly, can be a powerful tool. Avoiding conflict, as tempting as it may seem, often leads to more significant issues down the line. This was a key point emphasized by Roman Pichler in <\/span>his talk at the European edition of INDUSTRY: The Product Conference<\/span><\/a>. He argued that avoiding conflicts might temporarily create a facade of harmony, but underneath, unresolved issues continue to simmer, potentially leading to bigger problems. Instead, embracing and constructively managing these conflicts can lead to innovative solutions and stronger product strategies.<\/span><\/p>\n

Consider the development of the original iPhone. <\/span>According to Walter Isaacson<\/span><\/a>, who literally wrote the book about Steve Jobs, the development of the original iPhone was a period marked by intense internal conflict, primarily between the hardware and software teams at Apple. Steve Jobs, known for his exacting standards and visionary approach, pushed for a device that was not only technologically advanced but also impeccably designed. This ambition set the stage for a series of challenges and disagreements among teams.<\/span><\/p>\n

On one side, the hardware team, led by design guru Jony Ive, was focused on creating a sleek, minimalist device. They envisioned a phone that was not only functional but also a piece of art. This vision often clashed with the practical realities faced by the software team, led by Scott Forstall. The software team had to ensure that the operating system and applications not only worked seamlessly but also fit into the design constraints set by the hardware team. This clash was particularly evident in the development of the iPhone’s touch screen interface. The hardware team’s insistence on a button-less, all-screen design posed significant challenges for the software team, which had to develop a user-friendly and intuitive interface for a touch-based phone \u2013 something that had never been done before on such a scale.<\/span><\/p>\n

These internal conflicts, while challenging, ultimately proved to be a driving force behind the iPhone’s groundbreaking design and functionality. The tensions between maintaining a minimalist design and delivering advanced features led to innovative solutions, such as the development of the multi-touch interface, which allowed for gestures like pinching and swiping. This interface became a defining feature of the iPhone and set a new standard for smartphone interaction.<\/span><\/p>\n

Make no mistake \u2013 the conflicts felt during the iPhone’s development were very difficult for the teams at Apple. But they <\/span>were<\/span><\/i> instrumental in pushing the boundaries of what was possible in smartphone technology. They fostered a culture of innovation and problem-solving that not only resolved the immediate challenges but also led to the creation of a device that would revolutionize the telecommunications industry.<\/span><\/p>\n

But that\u2019s <\/span>Apple<\/span><\/i> \u2013 and Apple is <\/span>always<\/span><\/i> different. Right? Let\u2019s consider a more relatable scenario\u2026<\/span><\/p>\n

At INDUSTRY, Pichler introduced another scenario that may be hypothetical, but I bet you\u2019ve experienced this more than a few times. In this scenario, a conflict arises when \u201cSophie\u201d, the Head of Sales, demands the inclusion of a new feature in the upcoming release. This feature was not part of the original plan, and adding it would put a strain on the already tight resources and timelines. Sophie, as a senior stakeholder, wields considerable influence, and her insistence on this addition presents a significant challenge for the Product Manager.<\/span><\/p>\n

\"\"<\/a><\/p>\n

So\u2026 what do you do if you\u2019re the one dealing with Sophie?<\/strong><\/p>\n

On one hand, there’s the pressure to accommodate the requests of influential stakeholders like senior executives \u2013 especially when they\u2019re well respected internally. On the other, there’s the reality of resource constraints and the importance of adhering to the product vision and roadmap. The Product Manager in this situation faces a tough decision of how to balance these competing interests without compromising the product’s integrity or timeline.<\/span><\/p>\n

Possible reactions in this scenario vary.\u00a0<\/span><\/p>\n

A product manager might initially consider outright rejection of the request to stay on track with the current plan. However, this risks alienating an important stakeholder and potentially missing out on valuable input. Alternatively, they could acquiesce to the demand, but this sets a dangerous precedent, opening the door for future disruptions and potentially harming the product’s overall strategy and coherence.<\/span><\/p>\n

A more nuanced approach involves negotiation and collaboration. This would mean engaging in a dialogue with Sophie to understand her motivations and the significance of the feature she’s requesting. Perhaps there’s a compromise to be found \u2013 a way to incorporate her input in a manner that aligns with the product’s goals and resources. This route requires strong communication skills, empathy, and a deep understanding of both the product’s needs and the stakeholder’s interests.<\/span><\/p>\n

The key here is not to view the scenario as a win-lose situation but as an opportunity for collaborative problem-solving. It’s about striking a balance between being receptive to stakeholder input and staying true to the product vision, all while managing resources effectively. This delicate balancing act is at the heart of what makes product management both challenging and rewarding.<\/span><\/p>\n

So how do you actually effectively manage this kind of conflict?<\/span><\/h3>\n

First, it\u2019s important to consider what <\/span>not<\/span><\/i> to do. In Pichler’s discussion, he highlights four common but unproductive strategies that Product Managers might deploy when dealing with difficult stakeholders. These aren\u2019t what\u2019s recommended \u2013 but they\u2019re strategies that are more common that we all care to admit:<\/span><\/p>\n

\"Competitive<\/a> Competitive Confrontation:<\/strong> This approach involves directly opposing the stakeholder, often with a combative stance. While it might feel satisfying to stand your ground, this strategy can lead to damaged relationships and a hostile work environment. It creates a win-lose dynamic where collaboration and mutual understanding become secondary to ‘winning’ the argument.<\/span><\/p>\n

\"Passive<\/a> Passive Aggression: Here, a Product Manager might outwardly agree or seem compliant but internally resist or undermine the stakeholder\u2019s request. This approach can breed a toxic atmosphere of mistrust and hidden agendas. It often leads to a breakdown in communication and hinders the possibility of finding a constructive resolution.<\/span><\/strong><\/p>\n

 <\/p>\n

\"Conflict<\/a> Conflict Avoidance:<\/strong> Opting to sidestep or ignore the conflict might seem like a path to maintaining peace. However, this strategy often leads to unresolved issues simmering beneath the surface, potentially erupting later in more severe forms. Avoidance fails to address the root causes of the conflict, preventing any chance of a productive outcome.<\/span><\/p>\n

 <\/p>\n

\"Passivity\"<\/a> Passivity:<\/strong> This involves acquiescing to the demands of the stakeholder without any pushback. While this might maintain a superficial harmony, it often comes at the cost of the product\u2019s integrity and the Product Manager’s authority. Over time, this can lead to a pattern where the loudest voice always wins, rather than the best idea.<\/span><\/p>\n

There is a better way though, according to Pichler.\u00a0<\/span><\/p>\n

An effective alternative to these strategies is the Behavioral Change Stairway Model, developed by the FBI for crisis negotiations. And hey, if it\u2019s good enough for diffusing intense crises, it\u2019s probably sufficient enough to help us manage conflict within our Product Teams!\u00a0 This model provides a structured approach to transforming potentially adversarial interactions into collaborative dialogues.<\/span><\/p>\n