The Intertwined Worlds of Stakeholders, Politics, and Enterprise Projects
Enterprise project management, encompassing individual projects, programs, and entire portfolios, operates within complex organizational ecosystems. Central to these ecosystems are stakeholders—individuals, groups, or organizations that can influence or are influenced by project activities and outcomes. The management of these stakeholders is a critical determinant of project success. However, this management process is rarely straightforward; it is often permeated by organizational politics, driven by personal motivations and risk perceptions. This report delves into the multifaceted nature of stakeholder management within enterprise project contexts, exploring the inherent political implications. It critically examines the interplay between descriptive realities—how stakeholder dynamics and politics actually unfold—and normative ideals—how they ethically should be managed. Furthermore, it analyzes how different project management methodologies, stakeholder management tools, and communication methods are perceived by stakeholders and how these perceptions, in turn, shape the political landscape of projects.
Term | PMI Definition/Perspective | Axelos Definition/Perspective | Key Implication for Political Dynamics |
Stakeholder | "Any individual, group or organisation that can affect, be affected by, or perceive itself to be affected by, an initiative (programme, project, activity, risk)".1 Evolution from Freeman (1984).2 | PRINCE2: Three main categories for Project Board (Business, User, Supplier) 4; wider group affected/affecting project.5 | PMI's "perception" clause broadens the field of potential political actors. Axelos's defined board roles formalise specific power channels. |
Stakeholder Management/ Engagement | Processes to identify, analyse expectations, develop strategies for effective engagement, continuous communication, manage conflicts.3 | PRINCE2: Process of identifying and communicating effectively with those interested/influential; 6-step procedure.5 | Both emphasise proactive engagement. PRINCE2's structured procedure may channel political interactions more formally. |
Program Management | Coordination of related projects for benefits not available from managing them individually.7 | MSP: Aligns programs/projects to strategy, enables agility, focuses on benefits, risk mitigation, stakeholder engagement.9 | Focus on "benefits" makes their definition and distribution a potential political focal point. MSP’s explicit stakeholder engagement focus makes it a formal part of program politics. |
Portfolio Management | Aligns projects/programs with strategic objectives.7 EPPM uses EPMOs for strategic alignment and resource allocation.6 | MoP: Choosing optimal projects/programs for strategic objectives and executing to maximise stakeholder value.11 | Resource allocation and strategic alignment are inherently political; EPMOs and MoP frameworks become arenas for these politics. |
Governance | PMBOK® Guide: "oversight function that is aligned with the organisation’s governance model and encompasses the project life cycle".13 Includes framework, roles, stakeholder engagement, monitoring.13 | Axelos ProPath emphasises governance across PRINCE2, MSP, MoP, P3O.15 M_o_R focuses on risk governance.17 | Governance structures define formal power, decision-making processes, and accountability, directly shaping the rules of the political game. |
Risk | An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives.7 Political risk is a key category.19 | Axelos M_o_R: Framework to identify, assess, control risks, and make informed decisions.18 Risk management is integral at strategic, program/project, and operational levels.17 | Perceptions of risk and decisions on risk mitigation strategies are often politically charged, influenced by stakeholder motivations. |
The Political Dimension: Power, Motivations, and Risk
The political dimension of enterprise project management is characterized by the interplay of power, individual motivations, and the perceived risks associated with project activities and outcomes. Organizational politics, far from being an anomaly, is a pervasive feature that project managers must navigate.
Primary Motivation | Typical Thoughts/Concerns | Common Political Tactics Employed | Potential Positive Project Impact | Potential Negative Project Impact/Risk |
Need for Affiliation 31 | Maintaining relationships, being liked, avoiding disapproval, group harmony. | Building social alliances/cliques, avoiding conflict, choosing friends over experts, seeking consensus. | Enhanced team cohesion, good morale if managed well, strong informal networks for support. | Suboptimal decisions to please others, resistance to necessary conflict, favoritism, exclusion of non-group members. |
Need for Power 31 | Exercising control and influence, getting opinions accepted, shaping situations, gaining leadership. | Seeking leadership roles, active networking, controlling/withholding information, forming strategic alliances, forceful action. | Driving decisions, overcoming obstacles, securing resources, championing projects. | Manipulation, creating "I-win-you-lose" scenarios, stifling dissent, information hoarding, demotivating others. |
Need for Achievement 31 | Attaining goals, outperforming others, fear of failure, innovation, efficiency. | Taking initiative, calculated risk-taking, setting high standards, potentially coercive behaviour, reluctance to delegate. | High performance, innovation, driving for results, meeting challenging goals. | Undermining others to appear superior, burnout, resistance to delegation leading to bottlenecks, overly critical of others. |
Fear 35 | Rejection, failure, job loss, conflict, being labeled a troublemaker. | Avoiding conflict, withholding ideas, excessive caution, seeking scapegoats, forming defensive alliances. | Careful risk assessment (if fear is channeled constructively). | Stifled innovation, lack of proactive problem-solving, project delays due to indecision, toxic blame culture. |
Financial/Career Gain 32 | Personal enrichment, promotion, increased departmental budget, enhanced status. | Lobbying for pet projects, exaggerating project benefits, forming alliances for resource acquisition, self-promotion. | Championing projects that do offer genuine value (if aligned), driving resource acquisition. | Prioritisation of projects with personal payoff over strategic value, misallocation of resources, unhealthy competition. |
Protecting Self-Interest/Territory 23 | Maintaining current role/power, resisting changes perceived as threatening, controlling specific tasks. | Territorialism (hoarding tasks/roles), resisting new initiatives, gatekeeping information related to their domain. | Deep expertise in a specific area (if domain is critical). | Resistance to change, innovation blockage, creation of silos, lack of collaboration. |
Stakeholder Theory: Descriptive Realities vs. Normative Ideals
Stakeholder theory provides a crucial lens through which to analyse the complex interactions within and around enterprise projects. It offers two primary perspectives: the descriptive, which seeks to understand the factual realities of stakeholder interactions, and the normative, which explores the ethical values and principles that should guide these interactions.
Aspect | Descriptive Approach | Normative Approach |
Core Question | What is the nature of the firm and its stakeholder relationships? How do managers and stakeholders behave? 25 | What ought to be the purpose of the firm? What moral obligations do managers have to stakeholders? 25 |
Primary Focus | Explaining and modeling existing realities, behaviours, and characteristics of stakeholder interactions and corporate management. 25 | Identifying moral/philosophical guidelines for corporate operation; justifying why stakeholders should be treated in certain ways. 25 |
Key Theorists/Concepts | Empirical observation, stakeholder mapping, power analysis, influence networks. Focus on actual influence and salience. 26 | Freeman (stakeholders as moral agents), Donaldson & Preston (intrinsic value of stakeholder interests), Kantian ethics, utilitarianism, virtue ethics. 25 |
View of Stakeholder Value | Value is often described in terms of influence, power, or impact on the firm. Stakeholders are valuable if they can affect the firm. 26 | Stakeholder interests have intrinsic value; each group merits consideration for its own sake, not just for its instrumental utility to the firm. 26 |
Implications for Political Management | Aims to understand and predict political behaviours based on observed power dynamics and interests. Can be used to strategise how to manage existing political realities to achieve project goals. May inadvertently reinforce existing power imbalances if not critically applied. | Provides ethical frameworks to evaluate political behaviours and decisions. Guides managers to act fairly, transparently, and respectfully, even in politically charged situations. Challenges power-based decisions if they violate moral principles. Seeks to align political actions with ethical values. |
Methodologies, Tools, and Communication: Perceptions and Political Effects
The choice and application of project management methodologies, stakeholder management tools, and communication strategies are not neutral acts. They are perceived differently by various stakeholders and can significantly shape the political dynamics within enterprise projects. These elements act as structuring agents, defining the arenas and rules for political interaction.
Feature | Waterfall | Agile | Hybrid |
Perceived Control (Executives) | Higher (upfront planning, defined scope) 71 | Lower (scope evolves), but appreciate rapid updates 71 | Varies; aims to balance predictability with iterative progress. |
Perceived Control (End-Users) | Lower (limited involvement post-requirements) 68 | Higher (continuous feedback, influence on evolving product) 68 | Varies; potentially more involvement than pure Waterfall. |
Perceived Control (Technical Teams) | Lower (work rigidly defined) 71 | Higher (autonomy, self-organising) 71 | Varies; may offer more autonomy than pure Waterfall in execution. |
Perceived Flexibility | Low (changes difficult and costly) 66 | High (adaptive to changing requirements) 66 | Moderate; aims to combine upfront planning with adaptive execution. |
Perceived Risk Profile | Risk of delivering wrong product due to late feedback; late bug discovery. Predictable if requirements stable.68 | Risk of scope creep; uncertain outcomes without fixed plan; risk of stakeholder disengagement.68 | Aims to mitigate risks of both pure approaches; new risks from managing the blend. |
Typical Stakeholder Involvement | Concentrated at start (requirements) and end (UAT).68 | High and continuous throughout the project lifecycle.68 | Varies; typically more than Waterfall, potentially less intensive than pure Agile. |
Common Manifestations of Political Conflict | Major conflicts at phase gates or when scope changes are resisted; late-stage blow-ups due to unmet expectations.70 | More frequent, smaller negotiations; conflicts surface early due to transparency; potential conflict over required involvement levels or changing priorities.73 | Potential conflicts over methodology interpretation; balancing fixed elements with agile execution; managing expectations across diverse stakeholder preferences. |
Tool Category | Specific Examples | Typical Stakeholder Perception (Fairness, Transparency) | Impact on Information Control/Gatekeeping | Potential Political Effects (Positive/Negative) | Normative/Ethical Guidelines for Use |
Stakeholder Mapping Grids | Power-Interest Grid 32 | Can be seen as reductive; fairness depends on criteria and application. Transparency of classification is rare. | Can concentrate focus on "high power" individuals, potentially leading to gatekeeping by those managing them. | Positive: Prioritises engagement efforts. Negative: Can lead to neglect of "low power" groups; labels can alienate. | Use as a guide, not rigid labels. Supplement with qualitative data. Ensure criteria are relevant and fairly applied. Avoid offensive terminology.84 |
Salience Models | Mitchell, Agle, Wood Model (Power, Legitimacy, Urgency) 26 | Labels ("Dangerous," "Demanding") can be perceived negatively and unfairly.84 | Helps identify who commands attention, potentially guiding information flow towards or away from certain groups. | Positive: Helps prioritize critical stakeholders. Negative: Risk of miscategorisation and alienating stakeholders; "Dangerous" label can create adversarial stance. | Use with caution; be mindful of label connotations. Focus on understanding needs behind salience. Ensure legitimacy is fairly assessed.93 |
Real-time Chat (e.g., Slack, Teams) | Public/Private Channels, Direct Messages 103 | Public channels perceived as transparent; private channels can be seen as exclusive or secretive. Fairness depends on access rules. | Public channels reduce gatekeeping; private channels can enable it. Searchability increases information accessibility over time (if retained).103 | Positive: Facilitates rapid collaboration, quick issue resolution, builds informal networks. Negative: Information overload, exclusion from private channels, potential for miscommunication in informal settings. | Establish clear communication norms, manage channel access fairly, ensure critical decisions are formally documented.112 |
Project Management Software (e.g., Jira) | Task Tracking, Issue-linked Comments 105 | Perceived as transparent regarding work progress and accountability. | Centralises task-specific information, making it accessible to team members. | Positive: Increases accountability, clarifies responsibilities, provides data for discussions. Negative: Can be used to micromanage; data can be selectively reported in political contexts. | Ensure data accuracy. Use for collaborative problem-solving, not just monitoring. |
Project Dashboards & Reporting Tools | Visual KPI summaries, progress reports 118 | Can be perceived as highly transparent if data is accurate, contextualised, and accessible. Fairness depends on metric selection and presentation. | Democratises access to performance data, reducing reliance on specific individuals for updates.118 | Positive: Enables informed decision-making, increases accountability, facilitates consensus. Negative: Risk of oversimplification, misinterpretation, or manipulation of data to support political agendas. | Ensure data integrity, provide context, design for clarity, make accessible, and iterate based on feedback.118 |
Formal Memos, Threaded Discussions 109 | Perceived as formal and providing a record. Transparency can be low in long, exclusive threads. | Can lead to information silos; gatekeeping possible by controlling distribution lists or withholding replies. | Positive: Provides official record, good for formal decisions. Negative: Slow, can hide information, may reinforce hierarchical power dynamics. | Use for formal communication and decisions; supplement with more collaborative tools for ongoing discussions. Ensure appropriate stakeholders are included.110 |
Synthesising Descriptive and Normative Approaches for Effective Stakeholder Politics Management
Successfully navigating the political landscape of enterprise projects requires a sophisticated approach that acknowledges the descriptive realities of power and motivation while simultaneously striving to uphold normative ethical values. This involves implementing strategies to mitigate negative political behaviors, foster ethical engagement, build trust, and thoughtfully integrate project management tools and methodologies.
Towards Politically Astute and Ethically Grounded Stakeholder Management
The landscape of enterprise project management is inextricably linked with the complexities of human interaction, personal motivations, and the pursuit of power, rendering organisational politics an unavoidable reality. This report has examined the multifaceted nature of stakeholder management within this politically charged environment, contrasting the descriptive realities of "what is" with the normative ideals of "what ought to be."
Definitions
Work Cited