5. Stakeholder Analysis and Change Impact Assessment

Introduction and Context

Change initiatives rarely fail because the proposed technical solution is impossible. They more often fail because the people and groups affected by the change are misunderstood, inadequately prepared, or insufficiently involved. A new quality-management system, redesigned process, enterprise-resource-planning platform, merger, regulatory requirement, or lean transformation alters patterns of authority, work, information, accountability, and professional identity. Stakeholder analysis and change impact assessment provide the disciplined means of understanding these consequences before implementation begins.

Stakeholder analysis asks who can affect the change, who will be affected by it, what each party values, and how relationships may influence outcomes. Change impact assessment goes further by examining what will change in processes, roles, capabilities, behaviours, systems, measures, and working conditions. Together, the two practices convert a broad change proposal into an evidence-based engagement and implementation strategy.

For Total Quality Management (TQM), this perspective is especially important. Quality is produced through interconnected processes rather than by a quality department alone. Customers, suppliers, operators, supervisors, process owners, support functions, regulators, and senior leaders may all influence quality outcomes. A change that improves one part of the system can create unintended burdens or risks elsewhere. Effective assessment therefore requires both a human and a systems perspective.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Define stakeholders, stakeholder salience, influence, power, interest, and impact.

2. Identify and classify stakeholders using appropriate analytical frameworks.

3. Assess process, role, capability, behavioural, cultural, technological, and performance impacts.

4. Distinguish between stakeholder influence and stakeholder impact.

5. Design differentiated communication, participation, support, and resistance-management strategies.

6. Apply stakeholder and impact assessment to quality and organizational-change situations.

7. Recognize ethical, governance, analytical, and implementation risks in stakeholder analysis.

The Stakeholder Perspective in Organizational Change

A stakeholder is an individual, group, or institution that can affect a change initiative, is affected by it, or perceives itself to be affected by it. This definition includes obvious participants such as employees and managers, but also less visible parties such as customers, contractors, communities, auditors, professional bodies, and future users of a process.

Stakeholders should not be treated as a single homogeneous audience. Employees may differ according to role, location, tenure, skills, union representation, and previous experience of change. A regulator may possess high formal authority but limited day-to-day involvement. A frontline employee may have little hierarchical power but substantial practical influence because the employee understands how work is actually performed. A customer may have no internal decision authority yet determine whether the change creates value.

Three distinctions are central. Power is the capacity to influence decisions or outcomes. Interest is the degree to which a stakeholder cares about, depends on, or is affected by the change. Impact is the magnitude and nature of the change experienced by the stakeholder. Influence refers to the stakeholder’s actual or potential ability to shape other people’s perceptions and actions. These concepts overlap but are not identical. A stakeholder may have high impact and low formal power, or high power and low personal impact.

A further distinction concerns the stakeholder’s current and desired position. A stakeholder may be supportive, neutral, uncertain, resistant, or actively opposed. The desired position depends on the change. Not every stakeholder must become an enthusiastic champion; some need only understand the change, comply with it, or provide informed oversight. Engagement should therefore be proportionate and purposeful rather than universally intensive.

A Framework for Stakeholder Analysis

A robust analysis normally proceeds through five linked activities: identification, segmentation, assessment, relationship analysis, and engagement design.

Identifying the stakeholder system

Initial identification should begin with the change objective and the affected value stream. The analysis should examine who approves the change, funds it, designs it, performs changed work, receives outputs, supplies inputs, monitors compliance, bears risk, and may be unintentionally affected. Useful techniques include interviews, workshops, organizational charts, process maps, customer-journey maps, document reviews, lessons from earlier projects, and “who else?” questioning.

A stakeholder register provides a practical foundation. Typical fields include stakeholder or group, role, interests, expected benefits, concerns, power, influence, impact, current attitude, desired attitude, preferred communication channel, engagement owner, and review date. The register is a working management document, not a one-time administrative record.

Segmenting by power and interest

The power-interest grid is a simple and useful first model. Stakeholders with high power and high interest should be managed closely. High-power, low-interest stakeholders require satisfaction and concise assurance. Low-power, high-interest stakeholders should be kept informed and given meaningful opportunities to contribute. Low-power, low-interest stakeholders require monitoring, although their status may change.

The grid should not be used mechanically. “Low power” may reflect formal position rather than actual influence. A technical specialist, respected informal leader, or union representative can mobilize support or resistance. Similarly, a group with low current interest may become highly interested when implementation affects workload, employment conditions, or professional autonomy.

Assessing salience

Mitchell, Agle, and Wood’s stakeholder-salience framework evaluates stakeholders according to power, legitimacy, and urgency. Power concerns the ability to impose or secure action. Legitimacy concerns whether the stakeholder’s relationship or claim is recognized as appropriate. Urgency concerns the time sensitivity and criticality of the claim. Stakeholders possessing one, two, or all three attributes receive different levels of managerial attention.

The model adds depth to a simple power-interest grid. For example, a community affected by environmental consequences may have limited direct power but a legitimate and urgent claim. A regulator may possess power and legitimacy. A senior sponsor may have power, legitimacy, and urgency. Salience should be reviewed over time because attributes can change during implementation.

Understanding networks and informal influence

Formal hierarchy does not reveal the whole stakeholder system. Social-network analysis can identify opinion leaders, brokers, isolated groups, and communication bottlenecks. A broker connects otherwise separate groups; an informal leader shapes attitudes without holding managerial authority. Network information can be obtained through interviews, collaboration data, meeting patterns, or carefully designed surveys, subject to privacy and ethical safeguards.

The purpose is not to manipulate informal networks. It is to understand how information, trust, concern, and practical knowledge move through the organization. Engagement plans are stronger when they include credible voices from the work system rather than relying exclusively on formal sponsors.

Change Impact Assessment: From Proposal to Consequence

Stakeholder analysis explains who matters and how relationships operate. Impact assessment explains what will be different. A change impact assessment compares the current state with the future state and identifies the consequences of the transition.

Dimensions of impact

Process impact concerns changes to sequence, hand-offs, decision points, controls, cycle time, documentation, and performance requirements. Process mapping and value-stream analysis help reveal where work is added, removed, centralized, automated, or transferred.

Role impact concerns changes in authority, accountability, workload, decision rights, reporting relationships, and job boundaries. A new quality gate may transfer responsibility from inspection staff to process operators. A digital workflow may remove clerical tasks while increasing exception-management responsibilities.

Capability impact concerns the knowledge, skills, judgement, tools, and support needed to perform the future-state work. Capability gaps may be technical, managerial, digital, analytical, or interpersonal. Training is only one response; coaching, job aids, simulation, mentoring, recruitment, and process redesign may also be required.

Behavioural impact concerns observable changes in habits and choices. Examples include recording defects rather than concealing them, escalating problems earlier, using standardized work, collaborating across functions, or making decisions from data. Behavioural change requires credible incentives, psychological safety, role modelling, feedback, and reinforcement.

Cultural impact concerns assumptions about authority, learning, error, customer value, and accountability. A TQM initiative may challenge a culture that views quality as the inspection department’s responsibility and replace it with shared process ownership. Cultural effects are gradual and cannot be produced by slogans alone.

Technology and information impact concerns systems, data structures, access rights, interfaces, automation, cybersecurity, and information quality. A new dashboard may improve visibility but also create surveillance concerns or encourage gaming if measures are poorly designed.

Performance and reward impact concerns targets, measures, incentives, promotion criteria, and consequences. If employees are told to prioritize first-time-right quality but rewarded exclusively for output volume, the change contains a structural contradiction.

Emotional and identity impact concerns uncertainty, perceived loss of status, fear of redundancy, reduced autonomy, or pride in acquiring new expertise. These effects are legitimate parts of implementation risk, not merely personal reactions to be dismissed.

Assessing magnitude and readiness

A useful impact assessment records the affected stakeholder or unit, current state, future state, impact type, magnitude, timing, duration, risk, readiness, mitigation, owner, and evidence. Magnitude may be rated on a defined scale, such as low, moderate, high, or transformational, but ratings should be supported by observable criteria. A high-impact change may alter core responsibilities, require new certification, affect customer safety, or disrupt a critical process.

Readiness is not the same as willingness. Organizational readiness includes perceived need, confidence in the solution, leadership support, available resources, capability, trust, and capacity to absorb additional work. A willing department may still be unable to implement the change because it lacks time, systems, or skills.

Interdependencies and cumulative impact

Individual impacts can interact. A new system, revised performance measures, and reduced staffing may each appear manageable but become highly disruptive in combination. Impact assessment should therefore examine dependencies, sequencing, peak workload, and effects on adjacent processes. Scenario testing and pilot implementation are valuable when uncertainty is high.

Translating Analysis into Engagement Strategy

Engagement is the planned process of creating understanding, participation, commitment, capability, and feedback. It is not synonymous with communication. Communication transmits information; engagement involves dialogue, influence, learning, and sometimes shared decision-making.

A differentiated strategy commonly includes four dimensions: the purpose of engagement, the level of participation, the message or evidence required, and the support mechanism. A high-power sponsor may need decision dashboards, risk escalation, and milestone assurance. A frontline group may need demonstrations, protected time, practical involvement in process design, and rapid issue resolution. A regulator may require formal evidence, traceability, and compliance documentation. A customer may require proof of continuity, safety, service quality, or data protection.

The participation level should match the decision and the stakeholder’s knowledge. Participation may range from informing and consulting to involving, collaborating, or delegating. Token consultation damages trust when decisions have already been fixed. Conversely, involving every stakeholder in every decision is inefficient and can obscure accountability.

Resistance should be interpreted rather than automatically suppressed. It may indicate loss, lack of understanding, inadequate design, previous breach of trust, resource constraints, professional ethics, or a valid safety concern. A useful response distinguishes between resistance to the purpose, the proposed solution, the implementation method, or the personal consequences. Each requires a different intervention.

A practical engagement plan may include:

• the stakeholder and assessed position;
• desired outcome and engagement objective;
• decision or issue requiring participation;
• responsible relationship owner;
• message, evidence, and communication channel;
• participation activity and timing;
• capability or emotional support;
• feedback and escalation route; and
• indicators for reviewing effectiveness.

Engagement is cyclical. Feedback may change the impact assessment, the design of the solution, or the required support. Stakeholder analysis should therefore be updated at major milestones, after pilots, when external conditions change, and when unexpected resistance or benefits emerge.

Analytical Tools and Methods

Several methods complement one another. A stakeholder register organizes basic information. A power-interest grid supports prioritization. A salience assessment adds legitimacy and urgency. A RACI or responsibility matrix clarifies who is responsible, accountable, consulted, and informed. A process map identifies affected activities and hand-offs. A change-impact heat map displays the concentration and severity of impacts across departments or stakeholder groups. A readiness assessment examines capacity, confidence, leadership, resources, and competing initiatives.

Interviews provide depth and reveal concerns that surveys may miss. Surveys enable broader comparison but can conceal ambiguity or fear. Workshops generate shared understanding but may be dominated by senior or vocal participants. Observation and work shadowing are especially valuable in quality improvement because documented procedures may differ from actual work. Pilot testing supplies behavioural and operational evidence before full-scale rollout.

Quantitative scoring can improve transparency, but numerical precision should not be confused with objectivity. Scores are judgements based on assumptions. Teams should record the rationale, evidence, confidence level, and owner for important ratings. Sensitivity analysis is useful: if changing an uncertain rating alters the engagement priority, that uncertainty should itself become a management issue.

Application in TQM and Quality Transformation

Stakeholder and impact assessment is relevant to many quality initiatives. In a lean implementation, operators may gain problem-solving authority but experience increased visibility of performance. In an ISO-based management-system revision, employees may face new documentation and audit requirements. In customer-experience redesign, service staff may receive greater discretion while back-office functions face new service-level obligations. In supplier-quality development, vendors may need to change controls, data-sharing practices, and traceability.

Quality leaders should assess whether the proposed change strengthens systems thinking or merely transfers problems. For example, reducing inspection may be beneficial if process capability improves, but dangerous if responsibility is shifted without training, measurement, or authority. Similarly, a defect dashboard can support learning when used for root-cause analysis, but create concealment when linked to punitive individual targets.

Useful quality-related indicators include defect escape rates, first-pass yield, customer complaints, audit findings, process adherence, training effectiveness, adoption of standard work, issue-resolution time, and employee-reported confidence. These indicators should be interpreted together. A temporary rise in reported defects may represent improved transparency rather than deteriorating quality.

Illustrative Case: Introducing Digital Traceability in a Medical-Device Manufacturer

Background

The following fictional case illustrates the application of stakeholder analysis and change impact assessment. MedSure Components, a medium-sized medical-device manufacturer, decided to replace paper-based batch records with a digital traceability system. The objectives were to reduce transcription errors, improve recall readiness, and shorten release time.

Situation and problem

Senior management initially identified production, quality assurance, information technology, and the software supplier as the main stakeholders. The implementation plan assumed that operators would receive two days of training before go-live. During early testing, operators reported that barcode scanning was difficult in a clean-room environment, maintenance technicians were not included in access design, and quality reviewers were concerned that electronic approvals would alter accountability. Temporary staff and an external calibration provider had also been overlooked.

Analysis

A revised stakeholder analysis showed that the quality director and regulatory affairs manager had high power, high interest, and high urgency. Production operators had high impact and high practical influence but limited formal power. Maintenance technicians had moderate formal power but high system influence because equipment connectivity affected data integrity. The external calibration provider had low internal power but high legitimacy in relation to measurement compliance. Temporary staff had high process impact and low voice, creating a hidden implementation risk.

The impact assessment identified the following changes:

• Process: batch-record completion, deviation handling, and release approval would become digital and sequential.
• Role: operators would be responsible for real-time data entry; quality reviewers would approve exceptions rather than verify every transcription.
• Capability: users needed scanning, exception-management, and data-integrity skills.
• Behaviour: staff would need to report incomplete or erroneous entries immediately rather than correct paper records retrospectively.
• Technology: network availability, user permissions, audit trails, and backup procedures became critical.
• Emotional: some experienced employees feared that the system would monitor individual speed and expose mistakes.

Approach and strategy

The project team created a stakeholder register and conducted observation during actual production shifts. Operators participated in redesigning screen sequences and scanner placement. Quality assurance clarified approval responsibilities through a RACI matrix. Maintenance staff tested offline procedures and system recovery. Temporary workers received simplified role-based training, while the calibration provider was included in data-verification testing.

Engagement was differentiated. Senior leaders received risk and compliance dashboards. Operators joined practical simulations and daily feedback sessions. Quality reviewers participated in approval-rule workshops. The software supplier attended defect-triage meetings. A “no-blame data integrity” principle was communicated, while deliberate falsification remained subject to formal investigation.

The rollout was piloted on one production line. Measures included data-entry error rates, batch-release time, unresolved exceptions, user confidence, system availability, and audit-trail completeness. The pilot revealed that the original release target was unrealistic during the first weeks. Management adjusted production expectations, provided floor support, and postponed expansion until critical issues were resolved.

Outcome

The pilot produced a more reliable implementation plan and exposed risks that the original stakeholder list had missed. The organization proceeded with phased deployment rather than immediate full rollout. More importantly, the assessment prevented the system from being treated as a software installation alone. Process ownership, accountability, capability, behaviour, and trust were addressed together.

Learning points

The case demonstrates that stakeholder importance cannot be judged solely by hierarchy. Impact and practical influence may be greatest among employees who are least visible in formal governance. It also shows why observation, pilot evidence, and feedback must be used to revise initial assumptions. Finally, quality and compliance depend not only on system controls but on whether people can and will use those controls correctly.

Risks, Limitations, and Common Errors

Stakeholder analysis can become superficial when teams list only senior managers, confuse communication with engagement, or assign ratings without evidence. A further error is treating resistance as irrationality. Such an approach suppresses useful information and may intensify opposition.

Impact assessments also suffer from optimism bias. Project teams may underestimate learning time, temporary productivity loss, emotional strain, or the effect on external parties. They may assess each change independently and overlook cumulative impacts. Another common mistake is to identify impacts without assigning mitigation owners, resources, or decision rights.

Confidentiality is a significant concern. Stakeholder registers may contain sensitive views about influence, trust, capability, or resistance. Access should be controlled, language should remain professional, and information should not be used to stigmatize individuals. Network analysis and employee-survey data require transparency about purpose, privacy, storage, and use.

Scoring models have limitations. They can create false confidence, conceal disagreement, and privilege easily measurable factors over ethical or experiential concerns. They should support judgement rather than replace it. Critical safety, dignity, legal, and human-rights issues should not be traded away because a stakeholder has been assigned a low numerical priority.

Governance, Ethics, and Professional Responsibility

Good governance requires clear sponsorship, accountable decision-making, documented assumptions, escalation routes, and traceability from identified impact to action. Stakeholders should know which decisions are open for influence and which constraints are fixed. Consultation without disclosure of constraints is misleading.

Ethically, engagement should respect dignity, voice, fairness, informed participation, and non-discrimination. Groups with limited power should not be ignored. A change that improves organizational efficiency but imposes disproportionate and unacknowledged harm on vulnerable workers or communities requires reconsideration and mitigation. Regulatory and professional requirements may also mandate consultation, competence, data protection, worker safety, or evidence of control.

Quality professionals have a particular responsibility to distinguish legitimate confidentiality from concealment. Information should be protected where necessary, but material risks must reach those accountable for decisions. Stakeholder analysis is valuable only when it supports responsible action rather than political manipulation.

Digital Tools, Analytics, and Emerging Developments

Digital collaboration platforms, survey tools, process-mining systems, learning-management systems, and visualization dashboards can make stakeholder and impact information easier to collect and update. Process mining may reveal actual work patterns and bottlenecks that differ from documented processes. Sentiment analysis can identify themes in large volumes of feedback, but it should not be treated as a reliable substitute for conversation, especially where language, culture, or fear affects expression.

Artificial intelligence may help classify feedback, detect recurring concerns, simulate process impacts, or identify stakeholder groups that are underrepresented in consultation. However, AI outputs may reproduce sampling bias, misinterpret sarcasm or context, and create privacy risks. Human review, explainability, data minimization, and appropriate access controls are essential. Technology should extend professional judgement, not remove accountability for engagement decisions.

Emerging practice is moving toward continuous change sensing rather than one-time assessment. Organizations increasingly combine employee listening, operational data, customer signals, risk indicators, and network information to detect changing readiness. The challenge is to avoid surveillance cultures and data overload. Effective systems connect evidence to decisions and preserve meaningful human dialogue.

Best-Practice Principles

Several principles provide a reliable professional standard:

1. Start with the change objective, value stream, and affected outcomes rather than with an organizational chart.

2. Include stakeholders who perform, receive, regulate, enable, or bear the consequences of changed work.

3. Separate formal power, practical influence, interest, and impact.

4. Use multiple evidence sources, including observation and direct dialogue.

5. Assess process, role, capability, behaviour, culture, technology, performance, and emotional effects.

6. Make assumptions, confidence levels, and disagreements visible.

7. Match engagement intensity and participation rights to the decision and stakeholder need.

8. Treat resistance as data requiring diagnosis.

9. Assign owners, resources, measures, and review dates to mitigation actions.

10. Reassess stakeholders and impacts as the change, evidence, and external context evolve.

11. Protect privacy and use stakeholder information for responsible implementation.

12. Evaluate adoption and outcomes, not merely the completion of communication activities.

Chapter Summary

Stakeholder analysis and change impact assessment are complementary disciplines. Stakeholder analysis identifies the people and groups connected to change, evaluates their power, interest, legitimacy, urgency, influence, attitudes, and relationships, and supports differentiated engagement. Change impact assessment compares current and future states across processes, roles, capabilities, behaviours, culture, technology, performance, and emotional experience.

The power-interest grid, stakeholder-salience model, stakeholder register, responsibility matrix, process mapping, readiness assessment, heat maps, interviews, observation, and pilots provide useful but imperfect evidence. Their value depends on thoughtful interpretation and continuous review. In TQM, these methods help ensure that quality improvements strengthen the whole system rather than shifting risk from one group or process to another.

Effective practice is ethical, evidence-based, participative, and adaptive. It recognizes that low formal power does not mean low influence, that resistance may reveal valid design problems, and that communication alone does not create readiness. The ultimate purpose is not to produce a sophisticated map but to make better decisions, prepare people for changed work, and achieve sustainable improvement.

Key Terms

Stakeholder: An individual, group, or institution that can affect, is affected by, or perceives itself affected by a change.

Stakeholder analysis: A systematic examination of stakeholder characteristics, relationships, interests, influence, and likely responses.

Power: The capacity to influence decisions, resources, behaviour, or outcomes.

Interest: The degree of concern, involvement, dependence, or benefit associated with a change.

Impact: The magnitude and nature of consequences experienced by a stakeholder or organizational unit.

Influence: The ability to shape the attitudes or actions of others.

Stakeholder salience: The priority assigned to a stakeholder based on power, legitimacy, and urgency.

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

Urgency: The time sensitivity and critical importance of a stakeholder’s claim.

Stakeholder register: A structured record of stakeholder characteristics, concerns, engagement needs, and responsibilities.

Power-interest grid: A matrix that prioritizes stakeholders according to their power and interest in a change.

Change impact assessment: A structured comparison of current and future states to identify consequences of change.

Readiness: The extent to which people and the organization possess willingness, capability, resources, and capacity to implement change.

Process impact: The effect of change on activities, sequences, hand-offs, controls, and outputs.

Capability gap: The difference between capabilities required in the future state and those currently available.

Behavioural impact: The change in observable habits, choices, and actions required by a new state.

Engagement: A planned process of dialogue, participation, influence, support, and feedback.

Informal influence: The ability to shape views or behaviour without relying on formal authority.

Change saturation: The condition in which simultaneous initiatives exceed the organization’s capacity to absorb change.

Psychological safety: A shared belief that people can raise concerns, admit errors, and contribute without fear of humiliation or unfair punishment.

Review Questions

Short Answer Questions

1. Distinguish between stakeholder power, interest, influence, and impact.

2. What are the three attributes in the stakeholder-salience model?

3. Why should a stakeholder register be treated as a living document?

4. Identify four dimensions that may be examined in a change impact assessment.

5. Why is resistance not always evidence of poor commitment?

Long Answer Questions

1. Explain how the power-interest grid and stakeholder-salience model can be used together in a change initiative.

2. Describe a systematic process for conducting a change impact assessment in a TQM project.

3. Discuss how process, role, capability, behavioural, and cultural impacts are related.

4. Explain why engagement strategies should be differentiated rather than uniform.

5. Evaluate the ethical and governance responsibilities associated with stakeholder analysis.

Analytical / Application Questions

1. A hospital introduces electronic medication administration records. Identify the major stakeholder groups, classify them by power, interest, and impact, and propose an engagement approach for three groups.

2. A factory introduces a first-time-right performance measure, but supervisors continue rewarding output volume. Analyze the stakeholder and impact risks and recommend corrective action.

3. A project team rates temporary workers as low-priority stakeholders. Using the concepts in this chapter, critically evaluate that judgement and design a more reliable assessment approach.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes stakeholder impact from stakeholder power?

A. Impact is the ability to make decisions, while power is concern about the change.

B. Impact is the consequence experienced from change, while power is the capacity to influence outcomes.

C. Impact and power are interchangeable measures of stakeholder importance.

D. Impact applies only to external stakeholders, while power applies only to employees.

Correct Answer: B. Impact is the consequence experienced from change, while power is the capacity to influence outcomes.

Question 2

In the power-interest grid, a stakeholder with high power and low interest should generally be:

A. Managed closely through continuous participation in all decisions.

B. Kept informed through extensive operational training.

C. Kept satisfied through appropriate assurance and concise information.

D. Ignored because low interest means no possible influence.

Correct Answer: C. Kept satisfied through appropriate assurance and concise information.

Question 3

Which combination represents stakeholder salience attributes?

A. Power, legitimacy, and urgency

B. Interest, capability, and resistance

C. Impact, readiness, and communication

D. Authority, workload, and technology

Correct Answer: A. Power, legitimacy, and urgency

Question 4

Which is primarily a capability impact of implementing a digital quality system?

A. A change in the sequence of approval steps

B. A requirement for users to learn data-entry and exception-management skills

C. A change in the organization’s reporting hierarchy

D. An increase in anxiety about performance monitoring

Correct Answer: B. A requirement for users to learn data-entry and exception-management skills

Question 5

A frontline operator has little formal authority but is trusted by colleagues and can strongly affect adoption. This illustrates:

A. Low impact and low interest

B. Formal power without influence

C. Informal influence

D. Regulatory legitimacy

Correct Answer: C. Informal influence

Question 6

What is the most appropriate interpretation of resistance during change?

A. It always demonstrates an unwillingness to improve.

B. It may reveal concerns about design, trust, resources, capability, or consequences.

C. It should be suppressed to protect implementation speed.

D. It proves that communication has been unnecessary.

Correct Answer: B. It may reveal concerns about design, trust, resources, capability, or consequences.

Question 7

Which practice best reduces the risk of false precision in stakeholder scoring?

A. Assigning numerical ratings without discussion

B. Using only senior managers’ opinions

C. Recording evidence, assumptions, confidence, and reasons for ratings

D. Changing ratings whenever a stakeholder objects

Correct Answer: C. Recording evidence, assumptions, confidence, and reasons for ratings

Question 8

In the illustrative medical-device case, why was observation of actual production work valuable?

A. It eliminated the need for stakeholder interviews.

B. It revealed practical conditions and overlooked impacts not visible in the original plan.

C. It allowed management to avoid conducting a pilot.

D. It proved that technology was the only important impact.

Correct Answer: B. It revealed practical conditions and overlooked impacts not visible in the original plan.

Question 9

Which engagement approach is most appropriate when a stakeholder must help shape a decision and possesses relevant operational knowledge?

A. Inform only

B. Monitor without contact

C. Consult or collaborate, depending on decision authority

D. Provide a fixed message after the decision is complete

Correct Answer: C. Consult or collaborate, depending on decision authority

Question 10

Why should AI-supported sentiment analysis not replace direct stakeholder engagement?

A. AI cannot process any organizational data.

B. Sentiment analysis always produces identical results.

C. It may misinterpret context, reproduce bias, and overlook concerns that require dialogue.

D. Direct engagement is useful only for external stakeholders.

Correct Answer: C. It may misinterpret context, reproduce bias, and overlook concerns that require dialogue.