Stakeholders, Communication and Project Leadership

Introduction and Context

Projects are temporary organizations created to produce change under conditions of uncertainty. Their success depends not only on scope, schedule, cost, and technical performance, but also on the relationships through which work is authorized, interpreted, coordinated, and accepted. A technically excellent project can fail if a regulator withdraws approval, a user group rejects the solution, a sponsor loses confidence, or project staff disengage. Stakeholder management and project leadership are therefore central capabilities in operations management.

Stakeholders are individuals, groups, or organizations that may affect, be affected by, or perceive themselves to be affected by a project decision, activity, or outcome. This definition includes formal actors—such as sponsors, customers, suppliers, regulators, and employees—and less visible actors, such as communities, professional associations, future users, and groups whose interests are represented indirectly.

This chapter examines how project managers analyze stakeholder power and interests, design communication and engagement strategies, lead diverse teams, manage conflict and change, and apply emotional intelligence, negotiation, and ethical leadership. It treats leadership as a relational and ethical practice rather than simply a position of authority.

Learning Objectives

By the end of this chapter, students should be able to:

1. Identify and classify project stakeholders using power, interest, legitimacy, urgency, and influence.
2. Develop communication and engagement strategies appropriate to stakeholder needs and project conditions.
3. Explain how leadership theories apply to temporary, multicultural, and cross-functional project teams.
4. Diagnose conflict and select proportionate resolution and negotiation approaches.
5. Lead organizational and project change while addressing resistance and uncertainty.
6. Apply emotional intelligence and ethical reasoning to project decisions.
7. Critically evaluate stakeholder-management practices, including the use of digital tools and artificial intelligence.

1. Stakeholders as a System of Relationships

A stakeholder is not merely a person to whom information must be sent. Stakeholders interpret project events through their own objectives, identities, risks, values, and experiences. The same schedule variance may be viewed by a sponsor as a manageable control issue, by a customer as a threat to service continuity, and by a community as evidence of weak governance.

Stakeholder management is consequently a process of understanding relationships and shaping conditions for legitimate cooperation. It includes four connected activities:

• Identification: determining who may affect or be affected by the project.
• Analysis: examining interests, expectations, power, legitimacy, urgency, risks, and relationships.
• Engagement planning: determining how the project should listen, inform, consult, involve, negotiate, or collaborate.
• Monitoring and adaptation: revising assumptions as stakeholders, contexts, and project phases change.

Stakeholder analysis is not a one-time administrative exercise. Project environments are dynamic. A supplier may become highly influential during commissioning; a regulator may become urgent after a compliance concern; and a previously supportive executive may become resistant after a strategic change.

Stakeholder Categories

Stakeholders can be examined through several complementary distinctions:

These categories should not be treated as fixed labels. They are hypotheses to be tested through conversations and observation.

2. Models for Stakeholder Analysis

2.1 Power–Interest Analysis

The power–interest grid is a practical screening tool. Power refers to the ability to influence decisions, resources, constraints, or outcomes. Interest refers to the degree to which the stakeholder cares about project consequences or wishes to influence them.

The grid is useful but incomplete. It may overlook stakeholders whose power is not formally recognized, such as activist groups, professional experts, or communities capable of mobilizing public opinion.

2.2 The Stakeholder Salience Model

The salience model evaluates stakeholders according to three attributes:

• Power: capacity to impose or secure outcomes.
• Legitimacy: perceived appropriateness or validity of the stakeholder’s relationship with the project.
• Urgency: the degree to which claims require prompt attention.

Stakeholders possessing one attribute may be less salient than those possessing two or three. A regulator may possess all three during a safety incident. A vulnerable community may have legitimate and urgent claims but limited formal power. Ethical project management requires that low formal power not be confused with low moral importance.

2.3 Stakeholder Networks and Interdependence

Stakeholders should also be analyzed as a network rather than as isolated entries in a register. Questions include:

• Who influences whom?
• Which stakeholders share information or resources?
• Where are trust relationships strong or weak?
• Which actors can accelerate or block decisions?
• Are there coalitions, competing narratives, or hidden alliances?

Network thinking is especially important in matrix organizations, public projects, infrastructure programs, and digital transformations. A project manager who communicates only through formal reporting lines may miss the informal system through which decisions actually develop.

2.4 Stakeholder Registers and Assumption Testing

A stakeholder register commonly records the stakeholder’s role, interests, influence, expectations, current attitude, desired engagement, communication preferences, risks, and responsible relationship owner. It should also record assumptions. For example, “operations managers support automation” is an assumption until supported by evidence.

A useful review process asks:

1. What evidence supports our assessment?
2. Whose perspective is missing?
3. What could change this stakeholder’s position?
4. What does the stakeholder stand to lose, not merely gain?
5. What commitments have been made, and by whom?

3. Communication as a Governance and Leadership Process

Communication is the creation of shared understanding sufficient for coordinated action. It is not synonymous with transmission. A message may be delivered but not understood, understood but not believed, or believed but not acted upon.

Project communication has at least four purposes:

1. Coordination: aligning tasks, dependencies, decisions, and timing.
2. Governance: enabling authorization, oversight, escalation, and accountability.
3. Sensemaking: helping people interpret uncertainty and change.
4. Relationship building: creating trust, legitimacy, and willingness to cooperate.

Communication Planning

A communication plan should specify the audience, purpose, message, sender, channel, timing, frequency, format, feedback mechanism, owner, and confidentiality requirements. The plan should distinguish information that is merely available from information that stakeholders need in order to decide or act.

A project dashboard may be suitable for trend monitoring but unsuitable for communicating a safety concern to affected employees. A formal report may satisfy governance requirements but fail to answer the questions users actually have. Communication design must therefore consider the recipient’s context, literacy, language, accessibility, time constraints, cultural norms, and decision authority.

Push, Pull, and Interactive Communication

• Push communication sends information to recipients, such as email alerts or status reports.
• Pull communication makes information available for recipients to access, such as repositories or dashboards.
• Interactive communication enables exchange and clarification, such as workshops, interviews, and negotiation meetings.

Interactive methods are usually more appropriate when ambiguity, conflict, or commitment is significant. Push communication is efficient for routine updates but is weak for building shared meaning.

Communication Quality and Feedback

High-quality communication is timely, accurate, relevant, accessible, consistent, and appropriately transparent. Feedback must be designed rather than assumed. Useful mechanisms include decision logs, question-and-answer sessions, retrospectives, anonymous reporting channels, user demonstrations, and escalation routes.

A project manager should distinguish information asymmetry from information overload. Withholding relevant information undermines trust, while excessive information can conceal priorities and delay action. Executive communication should make decisions, implications, risks, and required actions visible without manufacturing certainty.

4. Engagement Strategies Across the Project Life Cycle

Engagement should correspond to the degree of influence and the nature of the relationship. Common levels include inform, consult, involve, collaborate, and empower. These are not automatically superior in that order. Empowerment is inappropriate if the project cannot genuinely delegate the relevant decision; consultation is unethical if stakeholder input is collected only to create an appearance of participation.

Engagement strategies should also address resistance. Resistance may express rational concerns about workload, job security, safety, status, or feasibility. Treating resistance as irrational opposition encourages concealment and reduces learning. The project manager should ask whether resistance identifies a genuine design weakness, an unresolved distributional issue, or a communication failure.

5. Project Leadership in Temporary and Diverse Teams

Project leadership differs from routine line management because authority is often temporary, distributed, and incomplete. Project managers may coordinate people who report elsewhere, work across organizations, or possess greater technical expertise than the manager. Influence therefore depends on credibility, clarity, fairness, relationship quality, and the ability to create conditions for performance.

Leadership Perspectives

Trait perspectives emphasize characteristics such as integrity, resilience, judgment, and social competence. They can identify useful tendencies but risk implying that leadership is an innate possession.

Behavioral perspectives focus on what leaders do. Effective project leaders combine task behaviors—planning, clarification, monitoring, and decision-making—with relationship behaviors—listening, coaching, recognition, and conflict management.

Situational perspectives argue that effective behavior depends on task uncertainty, team capability, time pressure, and stakeholder conditions. A directive approach may be justified during an immediate safety threat, while a participative approach may be superior during solution design.

Transformational leadership emphasizes purpose, meaning, intellectual stimulation, and commitment beyond immediate transactions. It can support change but should not become charismatic manipulation or a substitute for operational discipline.

Servant and inclusive leadership emphasize listening, removal of obstacles, development of others, and participation by people whose voices are often marginalized. These approaches are particularly relevant to diverse and cross-cultural teams.

Leading Diversity and Inclusion

Diversity includes differences in professional background, culture, nationality, language, gender, age, disability, cognition, employment status, and experience. Diversity can improve problem solving by broadening perspectives, but it does not automatically produce better outcomes. Without psychological safety and inclusive processes, minority viewpoints may be ignored and conflict may become personal.

Inclusive project practices include rotating meeting times across time zones, clarifying decision rules, using accessible documents, inviting dissent, checking whose data or experience is absent, and separating fluency from competence. The leader should prevent tokenism: one representative should not be treated as responsible for speaking for an entire group.

Psychological Safety and Accountability

Psychological safety is the shared belief that people can raise questions, report mistakes, and disagree without humiliation or retaliation. It is not permissiveness. High-performing teams combine interpersonal safety with demanding standards, clear ownership, and consequences for negligence or misconduct.

Project leaders create psychological safety by admitting uncertainty, responding constructively to bad news, distinguishing learning-oriented errors from reckless behavior, and ensuring that concerns are investigated. A “blame-free” culture must not become an “accountability-free” culture.

6. Emotional Intelligence in Project Leadership

Emotional intelligence concerns the recognition, understanding, and regulation of emotion in oneself and in relationships. A practical leadership model includes:

• Self-awareness: recognizing one’s emotions, assumptions, triggers, and impact.
• Self-management: regulating reactions and maintaining purposeful behavior under pressure.
• Social awareness: noticing others’ emotions, perspectives, status concerns, and cultural signals.
• Relationship management: using empathy, influence, feedback, and conflict skills to support constructive action.

Emotional intelligence is not emotional compliance. Empathy does not require agreement, and calmness does not require suppressing legitimate concerns. In a difficult meeting, a project manager might acknowledge frustration, restate the decision criteria, test assumptions, and establish the next action rather than responding defensively.

Useful practices include reflective journaling, after-action reviews, 360-degree feedback, coaching, and deliberate pauses before responding to provocative messages. Leaders should also recognize the limits of emotional-intelligence instruments: self-report measures can be affected by self-perception, culture, and social desirability.

7. Conflict Diagnosis and Resolution

Conflict occurs when people perceive incompatible interests, goals, values, interpretations, or methods. It is not always harmful. Task conflict can expose risks and improve decisions; relationship conflict and unmanaged process conflict are more likely to damage performance.

Sources of Project Conflict

Common sources include scarce resources, unclear roles, interdependent schedules, technical disagreement, competing success criteria, communication failures, cultural expectations, power asymmetry, and changes to scope. The visible argument may not be the underlying issue. A dispute about a design may conceal fear of accountability or disagreement about who owns the decision.

Conflict-Handling Approaches

The familiar approaches are competing, collaborating, compromising, accommodating, and avoiding. Each has conditions of usefulness:

• Competing: appropriate when immediate action, safety, or legal compliance requires a clear decision.
• Collaborating: appropriate when the issue is important and a durable, integrative solution is possible.
• Compromising: useful when parties have comparable influence and time is limited, although it may produce a mediocre solution.
• Accommodating: appropriate when preserving the relationship matters more than the issue or when one party recognizes the stronger case.
• Avoiding: sometimes useful for cooling emotions or when the issue is trivial, but dangerous when it merely postpones necessary action.

A disciplined process is to define the issue, separate people from the problem, identify interests, establish evidence and decision criteria, generate options, agree on commitments, and record unresolved risks. Leaders should be alert to power differences: a formally voluntary agreement may not be genuinely voluntary if one party controls employment or access to resources.

8. Negotiation and Influence

Negotiation is a structured process through which parties seek agreement despite differences in interests. Effective project negotiation begins with preparation:

• Define objectives, constraints, and authority.
• Distinguish positions from underlying interests.
• Identify alternatives if no agreement is reached.
• Determine which issues can be traded and which are non-negotiable.
• Establish evidence, standards, and decision rights.
• Plan questions, concessions, and documentation.

Interest-based negotiation seeks mutually beneficial arrangements where possible, while recognizing that some interests genuinely conflict. A project manager should not promise benefits outside authority merely to end a meeting. Agreements should specify scope, ownership, timing, assumptions, dependencies, acceptance criteria, and consequences of non-performance.

Influence should be based on expertise, legitimate authority, relationships, reciprocity, and a compelling rationale—not deception, coercion, or selective disclosure. Negotiation ethics require accurate representation of facts, respect for confidentiality, avoidance of improper pressure, and disclosure of conflicts of interest.

9. Managing Change and Resistance

Project change can involve requirements, technology, organizational structures, roles, processes, funding, or strategic priorities. Change management connects the technical solution to adoption and sustained use.

A useful analysis considers:

1. Why is the change necessary?
2. Who gains, who bears costs, and who may lose status or control?
3. What capabilities and behaviors must change?
4. What support, training, incentives, and reinforcement are required?
5. How will adoption and unintended effects be monitored?

Resistance should be analyzed at individual, team, organizational, and institutional levels. Individuals may lack capability or trust; teams may fear workload or loss of identity; organizations may have incompatible incentives; institutions may impose regulatory or professional constraints.

Change communication should be honest about what is known, unknown, negotiable, and non-negotiable. Leaders should avoid false certainty and explain the rationale for decisions. Pilots, staged implementation, peer champions, training, feedback loops, and visible executive sponsorship can reduce adoption risk. However, “change champions” should not be used to pressure colleagues into silence.

10. Ethical and Responsible Project Leadership

Ethical leadership involves applying principles of fairness, respect, responsibility, transparency, and accountability to decisions. A project manager may face dilemmas involving procurement favoritism, manipulation of performance data, unsafe schedule compression, exclusion of affected communities, surveillance, conflicts of interest, or pressure to hide bad news.

A practical ethical analysis asks:

• Who may be harmed or excluded?
• Are benefits and burdens distributed fairly?
• What rights, duties, or professional standards apply?
• Would the decision withstand transparent public explanation?
• Are vulnerable stakeholders represented?
• What alternatives reduce harm without undermining legitimate objectives?

Compliance is a minimum threshold, not the complete meaning of ethics. A decision can be legal yet exploitative or procedurally unfair. Governance mechanisms—approval gates, independent assurance, audit trails, escalation routes, conflict-of-interest declarations, and protected reporting—help convert ethical intentions into accountable practice.

11. Digital Communication, Data, and Artificial Intelligence

Digital platforms support distributed work through shared repositories, collaboration tools, dashboards, virtual meetings, and automated alerts. They improve traceability and speed but can also create notification overload, surveillance concerns, fragmented records, and exclusion of people with limited access or digital confidence.

Artificial intelligence can assist with stakeholder mapping, sentiment classification, meeting transcription, issue clustering, and drafting communication. Its use requires caution. Automated analysis may reproduce bias, misinterpret sarcasm or culturally specific language, expose confidential information, or give false confidence through apparently objective scores. AI-generated stakeholder profiles should be treated as hypotheses requiring human validation.

Responsible use requires purpose limitation, data minimization, access control, transparency, human review, retention rules, and an avenue for correction. Sensitive stakeholder data should not be collected merely because technology makes collection possible. The project manager remains accountable for decisions, even when analytical tools are used.

12. Applied Case: The Riverside Integrated Mobility Project

Background

The fictional Riverside Integrated Mobility Project aims to introduce an electric bus network, redesign several routes, and deploy a mobile payment system for a metropolitan authority. The project has a two-year implementation window and involves the transport authority, a technology vendor, bus operators, drivers, passengers, accessibility advocates, local businesses, a labor union, a data-protection regulator, and neighborhood associations.

Problem

The initial plan treated the transport authority and vendor as the principal stakeholders. Public consultation was limited to an online survey. As implementation approached, drivers raised concerns about training and job roles, accessibility advocates reported that the proposed application excluded users without smartphones, and neighborhood associations objected to route changes. A regulator also questioned the proposed handling of travel data. The sponsor considered the objections a communications problem and proposed issuing a stronger public-relations campaign.

Analysis

The project manager conducted a revised stakeholder analysis. The regulator and authority had high power and high interest. Drivers and the union had substantial operational influence because service continuity depended on their cooperation. Accessibility advocates had limited formal power but high legitimacy and urgency. Small businesses were initially classified as low interest, but route changes threatened customer access and therefore increased their interest. The analysis also identified a network: neighborhood associations could influence public opinion, while drivers possessed practical knowledge about route feasibility.

The project team discovered that the online survey systematically underrepresented older passengers, people with disabilities, and residents with limited internet access. It also found that the vendor’s proposed data architecture collected more location information than was necessary for fare processing.

Approach and Solution

The project manager replaced the public-relations approach with a participation strategy:

• Workshops with drivers and dispatchers were used to redesign training and escalation procedures.
• Accessibility advocates participated in prototype testing and acceptance reviews.
• Public meetings and paper-based feedback channels supplemented online consultation.
• A route-change working group included businesses and neighborhood representatives.
• The vendor was required to revise the data design according to data-minimization principles.
• A decision log recorded which suggestions were accepted, rejected, or deferred and why.
• The sponsor received a risk report showing that early engagement would delay some design decisions but reduce implementation and reputational risk.

Conflict between the vendor and accessibility advocates was managed through shared acceptance criteria rather than positional debate. The project team agreed that payment should remain possible through a physical card and staffed service points, while the vendor retained flexibility in application design.

Outcome

The project launched six weeks later than originally planned but achieved higher user adoption, fewer service disruptions, and stronger regulatory confidence than the original plan predicted. Not every request was accepted, and some route changes remained controversial. However, the process was viewed as more legitimate because decisions and trade-offs were explained. The project also established a permanent accessibility review group for future transport initiatives.

Learning Points

The case illustrates that stakeholder engagement is not public relations. It is a form of risk management, design learning, governance, and ethical accountability. It also demonstrates that stakeholders with limited formal power may possess essential knowledge and legitimacy. Finally, meaningful participation may require accepting short-term schedule costs to protect long-term value and trust.

13. Limitations and Critical Evaluation

Stakeholder frameworks simplify complex social systems. A power–interest grid can conceal informal influence, changing identities, and moral claims. Salience models may privilege powerful actors if legitimacy and urgency are interpreted narrowly. Communication plans can become bureaucratic artifacts rather than instruments of dialogue. Engagement may also become symbolic when decisions are effectively predetermined.

Project managers should therefore avoid false precision. Assigning a stakeholder a numerical influence score can create an illusion of objectivity. Qualitative judgment, triangulation of evidence, direct engagement, and periodic review are often more reliable than a single ranking. Leaders should also recognize that stakeholder interests may be internally diverse: “the community,” “employees,” or “customers” rarely speak with one voice.

A further limitation is that project frameworks often prioritize the project’s success criteria over broader social outcomes. Graduate-level practice requires asking whether the project itself is legitimate, whether its benefits are distributed fairly, and whether its success creates external costs. Stakeholder management should not be used to neutralize legitimate opposition to harmful projects.

Best-Practice Principles

1. Identify stakeholders early, but expect the register to evolve.
2. Analyze both formal authority and informal influence.
3. Distinguish communication delivery from genuine understanding.
4. Match engagement intensity to impact, uncertainty, and legitimacy.
5. Treat resistance as potential information, not automatically as obstruction.
6. Combine task clarity with psychological safety and accountability.
7. Use conflict to improve decisions while preventing personal harm.
8. Negotiate interests transparently and document commitments.
9. Communicate uncertainty honestly and explain trade-offs.
10. Protect privacy, accessibility, dignity, and the right to raise concerns.
11. Validate digital and AI-supported analysis through human judgment.
12. Review stakeholder assumptions at every major project transition.

Chapter Summary

Stakeholders shape project authorization, design, implementation, acceptance, and long-term value. Effective management begins with identification and analysis, using tools such as the power–interest grid, salience model, stakeholder register, and network perspective. These tools are aids to judgment rather than substitutes for direct engagement.

Communication is a governance and leadership process that creates shared understanding for coordinated action. Plans should distinguish push, pull, and interactive communication and should provide feedback, accessibility, appropriate transparency, and clear accountability. Engagement may involve informing, consulting, involving, collaborating, or empowering, but the chosen level must correspond to genuine decision authority.

Project leadership requires influence across temporary, diverse, and often matrixed teams. Situational, inclusive, servant, and transformational perspectives offer useful insights when combined with operational discipline. Emotional intelligence supports self-regulation, empathy, and constructive relationships, while psychological safety enables learning without removing accountability.

Conflict can expose valuable differences but must be diagnosed and managed according to its source and consequences. Negotiation should focus on interests, alternatives, evidence, authority, and ethical commitments. Change leadership requires attention to capability, incentives, identity, trust, and distributional effects. Ethical leadership extends beyond legal compliance to fairness, transparency, protection of vulnerable stakeholders, and responsible governance. Digital tools and AI can improve coordination and analysis, but they introduce privacy, bias, surveillance, and accountability risks.

Key Terms

Stakeholder: An individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a project.

Stakeholder analysis: The systematic assessment of stakeholder interests, influence, expectations, risks, and relationships.

Power–interest grid: A framework classifying stakeholders according to their ability to influence and level of interest.

Stakeholder salience: The relative priority of a stakeholder based on power, legitimacy, and urgency.

Stakeholder register: A controlled record of stakeholder characteristics, expectations, engagement needs, and relationship responsibilities.

Engagement: Deliberate interaction designed to inform, consult, involve, collaborate with, or empower stakeholders.

Communication plan: A structured specification of audiences, purposes, messages, channels, timing, owners, and feedback mechanisms.

Information asymmetry: A condition in which parties possess unequal access to relevant information.

Psychological safety: A shared belief that people can speak up, ask questions, and report concerns without humiliation or retaliation.

Emotional intelligence: The capability to recognize, understand, regulate, and use emotions constructively.

Inclusive leadership: Leadership that enables meaningful participation and voice across differences.

Task conflict: Disagreement about work content, evidence, methods, or decisions.

Relationship conflict: Interpersonal tension involving identity, disrespect, distrust, or perceived personal threat.

Interest-based negotiation: Negotiation that seeks to understand underlying interests rather than relying only on stated positions.

Resistance to change: Opposition, hesitation, or concern arising from perceived risks, losses, uncertainty, or capability gaps.

Ethical leadership: Decision-making and conduct based on responsibility, fairness, integrity, respect, and accountability.

Stakeholder legitimacy: The perceived appropriateness or validity of a stakeholder’s relationship or claim.

Data minimization: The principle of collecting and retaining only data necessary for a legitimate purpose.

Review Questions

Short Answer Questions

1. What is the difference between stakeholder identification and stakeholder analysis?
2. Explain the four categories in a power–interest grid.
3. Distinguish push, pull, and interactive communication.
4. What is psychological safety, and why does it not eliminate accountability?
5. Name and explain the three attributes in the stakeholder salience model.

Long Answer Questions

1. Critically evaluate the usefulness and limitations of the power–interest grid in a complex public-sector project.
2. Explain how emotional intelligence can improve conflict management without requiring a project manager to agree with every stakeholder.
3. Compare transformational, servant, inclusive, and situational leadership in the context of a cross-functional project team.
4. Discuss the ethical risks of using artificial intelligence for stakeholder sentiment analysis and engagement planning.
5. Explain how a project manager can design a communication plan that supports both governance and genuine stakeholder participation.

Analytical / Application Questions

1. A software implementation has strong executive sponsorship but increasing resistance from frontline employees. Construct a stakeholder analysis and recommend an engagement strategy.
2. A contractor proposes reducing safety testing to recover a schedule delay. Analyze the stakeholder, ethical, communication, and leadership issues and recommend a course of action.
3. Design a negotiation approach for a project in which a regulator demands additional controls, the sponsor rejects added cost, and users require an earlier launch. Identify interests, alternatives, decision criteria, and ethical safeguards.

Multiple Choice Questions with Answers

Question 1

Which stakeholder should generally be managed closely according to the power–interest grid?

A. A stakeholder with low power and low interest

B. A stakeholder with high power and high interest

C. A stakeholder with high power and low interest

D. A stakeholder with low power and high interest

Correct Answer: B. A stakeholder with high power and high interest

Question 2

Which combination constitutes the three attributes in the stakeholder salience model?

A. Power, legitimacy, and urgency

B. Authority, cost, and schedule

C. Interest, risk, and complexity

D. Influence, communication, and trust

Correct Answer: A. Power, legitimacy, and urgency

Question 3

Which communication mode is most appropriate when ambiguity and commitment are significant?

A. A routine dashboard only

B. An automated notification only

C. Interactive communication such as a workshop

D. A document repository with no discussion

Correct Answer: C. Interactive communication such as a workshop

Question 4

What does psychological safety enable team members to do?

A. Avoid all performance standards

B. Raise concerns and disagree without fear of humiliation

C. Make decisions without accountability

D. Replace formal governance processes

Correct Answer: B. Raise concerns and disagree without fear of humiliation

Question 5

A project manager uses shared acceptance criteria to resolve disagreement between a vendor and users. Which approach is being emphasized?

A. Interest-based conflict resolution

B. Avoidance through postponement

C. Unilateral competition

D. Personal accommodation without criteria

Correct Answer: A. Interest-based conflict resolution

Question 6

Which statement best describes ethical stakeholder engagement?

A. Consultation should be used even when input cannot affect any decision

B. Only stakeholders with formal authority deserve meaningful participation

C. Engagement should be proportionate, honest, accessible, and connected to real decision rights

D. Stakeholder objections should be reframed as communication failures

Correct Answer: C. Engagement should be proportionate, honest, accessible, and connected to real decision rights

Question 7

What is a major risk of using AI for stakeholder sentiment analysis?

A. It always eliminates human bias

B. It may misinterpret language and reproduce embedded bias

C. It prevents all data collection

D. It makes stakeholder engagement unnecessary

Correct Answer: B. It may misinterpret language and reproduce embedded bias

Question 8

Which action best reflects inclusive project leadership?

A. Allowing the most fluent speaker to represent all perspectives

B. Rotating meeting times and inviting dissenting views

C. Avoiding disagreement to preserve harmony

D. Delegating all relationship work to human resources

Correct Answer: B. Rotating meeting times and inviting dissenting views

Question 9

A stakeholder has legitimate and urgent claims but little formal power. What is the most responsible conclusion?

A. The stakeholder can be ignored

B. The stakeholder has no relevance unless legally empowered

C. The stakeholder may require attention despite limited formal power

D. The stakeholder should automatically control the project

Correct Answer: C. The stakeholder may require attention despite limited formal power

Question 10

Which practice best supports ethical negotiation?

A. Making promises outside one’s authority

B. Hiding material information to gain leverage

C. Clarifying interests, authority, evidence, and commitments

D. Using pressure to obtain agreement quickly

Correct Answer: C. Clarifying interests, authority, evidence, and commitments