Communication And Organizational Change Management practice questions

Keep the two departments physically and digitally segregated to avoid any interaction.

Why it fails: Segregation perpetuates silos and prevents the realization of merger synergies.

Fire all employees from the agile department who question the rigid processes.

Why it fails: Mass firings destroy organizational capability and morale.

Impose the rigid process culture on the agile team to ensure strict corporate uniformity.

Why it fails: Imposing a rigid culture destroys innovation and drives away agile talent.

Monitor them passively through automated newsletters without direct contact.

Why it fails: Passive monitoring suits low-power, low-interest stakeholders; high-power, high-interest parties require active, direct engagement to shape decisions. It is tempting because newsletters scale cheaply across large stakeholder groups, but that efficiency is irrelevant to the quadrant's engagement demand.

Ignore their feedback to maintain strict project schedule discipline.

Why it fails: High-power, high-interest stakeholders must be managed closely, so disregarding their input forfeits the engagement the grid mandates. It is tempting when schedule pressure dominates, yet the grid reserves such treatment for low-power, low-interest parties who need only monitoring.

Keep them satisfied with minimal touchpoints and low-priority updates.

Why it fails: Keeping satisfied applies to high-power, low-interest stakeholders; those with high interest as well must be fully engaged, not given minimal updates. It is tempting because it limits effort, but the grid assigns that strategy to a different quadrant entirely.

Aligning employee performance metrics and reward systems with the new behaviors.

Why it fails: Alignment actually helps sustain change, not cause failure.

Increase the frequency of the CIO newsletter from monthly to weekly to ensure the message is seen more often.

Why it fails: Simply increasing the frequency of a one-way broadcast amplifies volume without creating engagement. The pilot feedback was that employees feel uninformed about local impact and lack a contact point, not that they receive too few emails. More emails from the same distant source may even increase fatigue and reinforce the perception that communication is top-down.

Publish the full project plan and detailed technical specifications to all employees so they have complete information.

Why it fails: Sharing exhaustive technical specifications and the full project plan does not address the emotional and practical concerns of affected staff. It may overwhelm non-technical audiences and obscure the key messages about what is changing and why. Communication should be audience-appropriate, focusing on impact and benefits rather than raw project artefacts.

Identify and equip local change champions in each region to reinforce messages and gather frontline feedback.

Why it fails: Local change champions are valuable for advocacy and feedback, but the question asks for TWO actions to revise the communication plan itself. Champions support engagement, yet without a structured two-way channel their feedback has nowhere formal to go. This option is plausible but does not by itself fix the missing dialogue mechanism that the pilot identified.

Ignore employee complaints about workload and mandate mandatory overtime until projects conclude.

Why it fails: Mandating overtime addresses attendance hours, not the number of concurrent changes draining stakeholder capacity, so fatigue persists and trust erodes. It is tempting because it appears to guarantee throughput, and would be correct where a short, bounded surge is needed and workload, not initiative volume, is the limiting factor.

Accelerate all remaining projects to finish them as quickly as possible, regardless of resource limits.

Why it fails: Accelerating every project increases the volume of concurrent change, deepening fatigue rather than restoring capacity. It is tempting because compressing timelines can relieve pressure when a single project overruns, and it would be correct for one isolated project with slack resources and no portfolio-wide saturation.

Assign all change management responsibilities to end users to reduce the project team's workload.

Why it fails: Delegating change duties to end users shifts accountability away from the change team, deepening fatigue rather than restoring capacity; users already saturated by simultaneous projects cannot absorb ownership work. It is tempting because distributing tasks can ease a stretched team's load, and would suit a small, well-resourced pilot group with genuine bandwidth.

Hiding the campaign details deep inside the corporate wiki directory structure.

Why it fails: Burying details in the wiki gives no active delivery or reinforcement, so staff never encounter the messages. It tempts because a wiki is a legitimate repository for policy reference material; it would be correct as a supporting resource linked from campaign communications, not as the campaign itself.

A single email sent on a Friday afternoon with a 200-page PDF attachment.

Why it fails: A single dense PDF on a Friday afternoon gives no reinforcement, no repetition and no interactive channel, so retention collapses. It tempts because email remains a valid campaign channel; it would be correct as one element of a multi-channel mix with short, timely, digestible content.

Relying solely on word-of-mouth rumors spread through the office cafeteria.

Why it fails: Rumour carries no authoritative content, no consistency and no measurable reach, so key messages cannot be reinforced. It tempts because informal conversation does spread awareness; it would be correct only as a supplementary channel alongside formal, managed communications, never as the sole mechanism.

Evaluating the hardware inventory depreciation schedules across regional data centers.

Why it fails: Evaluating depreciation schedules measures asset accounting, not cultural or behavioural readiness, so it cannot assess transformation capability. It is tempting because hardware lifecycle data legitimately informs infrastructure capacity planning and budgeting, where depreciation schedules would be the correct input. Here the stem demands cultural and behavioural evaluation, which financial asset records do not capture.

Counting the total number of change requests approved by the change advisory board over the last month.

Why it fails: Counting approved change requests measures change-management throughput, not cultural or behavioural readiness. It is tempting because CAB approval volumes genuinely indicate process activity and control effectiveness, making it useful for capacity planning or change-advisory workload reporting — but ITIL 4 readiness assessment requires evaluating mindsets, competencies and organisational culture, which this metric never captures.

Reviewing the historical IT incident backlog from the previous fiscal year.

Why it fails: Reviewing incident backlog measures operational stability and service performance, not cultural or behavioural readiness. It is tempting because incident trends genuinely inform continual improvement and change planning, where historical data would be the correct choice. Here the stem demands assessment of cultural and behavioural readiness, which incident records cannot evidence.

Increase the volume of standard broadcast emails detailing the strategic benefits of cloud computing.

Why it fails: Broadcast emails are one-way push communication that cannot surface the managers' control concerns or involve them in shaping the change. They suit awareness campaigns, not resistance rooted in loss of autonomy; ITIL 4 OCM prescribes stakeholder engagement and addressing concerns directly.

Revoke their administrative access credentials immediately to force compliance with the new workflow.

Why it fails: Revoking credentials treats a people-and-culture barrier as a security breach, escalating resistance rather than addressing the fear driving it. It is tempting because access revocation is the standard containment step for insider misuse; in an actual policy violation or compromised account, immediate revocation would be the right call.

Escalate the non-compliant managers directly to human resources for disciplinary review.

Why it fails: Escalating to HR treats resistance as a disciplinary matter, which destroys trust and ignores the underlying fear of losing control that ITIL 4 OCM addresses through engagement. Disciplinary escalation fits wilful misconduct, not change resistance requiring dialogue and involvement.

Monitor this group with minimal effort and low-touch automated newsletters to avoid bothering them.

Why it fails: High-power, low-interest stakeholders need to be kept satisfied, not merely monitored; monitoring suits low-power, low-interest parties. Automated newsletters give them no reason to engage, so their latent power can block the initiative. The correct strategy targets raising their interest through tailored, meaningful communication.

Delegate their management entirely to junior project coordinators using standard ticketing updates.

Why it fails: Delegating to junior coordinators with ticketing updates gives this high-power group minimal senior attention, so their low interest is never raised and resistance risks grow. It is tempting because delegation suits low-power, low-interest stakeholders, and it would be correct for that quadrant rather than high power.

Keep them informed via broad company-wide town halls and general intranet announcements.

Why it fails: Broad town halls and intranet posts address low-power, high-interest stakeholders who need informing. High-power, low-interest parties require targeted, personalised engagement that raises their interest, since generic broadcasts reach them but do not secure their active support or address their specific concerns.

Publicly reprimand the dissenting employees during the next all-hands meeting to deter others.

Why it fails: Public reprimand escalates conflict, destroys psychological safety and hardens the resistance rather than surfacing the usability concerns driving it. Addressing dissent openly through dialogue and feedback channels is the appropriate route when criticism is legitimate and voiced in meetings.

Exclude the department from subsequent training sessions to protect the rest of the rollout.

Why it fails: Excluding the department denies its staff the knowledge needed to adopt the tool, deepening alienation and guaranteeing the resistance persists. Targeted training is withheld only where a group poses a security or conduct risk, not to quarantine legitimate feedback during a rollout.

Replace the department head immediately without consulting human resources or business partners.

Why it fails: Removing the department head bypasses HR and business-partner governance, creating legal and morale risk while leaving the underlying usability objection unresolved. Leadership change follows formal people-management process when a manager actively obstructs delivery, not as a first response to public criticism.

A strictly one-way executive broadcast newsletter published quarterly.

Why it fails: Quarterly one-way broadcasts give no channel for staff to raise concerns, so uncertainty persists. ITIL 4 effective communication is bidirectional, with feedback informing decisions. One-way executive updates suit stable periods where information cascades downward and no input is sought, not a restructure generating anxiety requiring dialogue.

Posting static policy updates on the corporate intranet comment-disabled page.

Why it fails: Comment-disabled intranet pages transmit information without any return path, so concerns go unheard. ITIL 4 communication requires interaction and feedback. Static publication suits policy reference material that staff consult as needed, not a morale crisis where the change manager must capture and respond to sentiment.

An anonymous suggestion box with no commitment to reviewing or publishing responses.

Why it fails: Anonymous boxes with no review commitment provide no feedback loop, so staff see no response and trust erodes further. ITIL 4 communication requires meaningful, bidirectional exchange. Anonymous channels are useful where retaliation risk is high and responses are genuinely acted upon and published, which this option explicitly excludes.

Send out the raw, unedited ITIL process flow diagrams to all staff to ensure complete technical transparency.

Why it fails: Raw process diagrams use technical ITIL vocabulary, directly contradicting the requirement to avoid jargon for regional stakeholders. Sharing source artefacts is tempting when the audience is a practitioner community that already understands the notation and wants full detail.

Restrict all communication strictly to the executive steering committee to avoid operational leaks.

Why it fails: Limiting communication to the steering committee excludes the regional stakeholders the value stream must inform, so the launch message never reaches its audience. Executive-only reporting is tempting when governance or funding decisions require confidentiality before wider announcement.

Rely exclusively on automated broadcast emails to guarantee maximum reach without requiring feedback loops.

Why it fails: Broadcast emails push content one way, so the manager cannot confirm understanding or gather regional feedback, which the scenario's stakeholder alignment requires. Automated distribution is tempting for time-critical announcements where reach matters and no dialogue is needed.

Take over all administrative payroll duties for the entire IT department.

Why it fails: Champions advocate and communicate to build momentum, not absorb payroll administration, which is an operational finance function. Taking over payroll removes them from their advocacy role and creates segregation-of-duties and accuracy risks unrelated to the ITSM communication plan.

Write all enterprise software code without peer review.

Why it fails: Champions communicate and advocate, not write code; peer review is a separate software engineering control. The role here is to model and spread adoption of the ITSM initiative, so assigning unreviewed enterprise code introduces risk and delivers no communication value.

Enforce strict compliance by auditing peer computer screens daily.

Why it fails: Champions persuade and model adoption; daily screen auditing is a compliance-monitoring control that breeds resentment and undermines the voluntary enthusiasm the initiative needs. Enforcement belongs to management or audit, whereas champions should influence peers positively during the communication plan.

The IT service desk failed to categorize incidents according to ITIL 4 service desk practices.

Why it fails: Incident categorisation concerns service desk triage, not how improvement outcomes are communicated or embedded across teams, so it cannot explain improvements failing to sustain organisation-wide. It is tempting because ITIL 4 service desk practise is a recognised capability, and would be correct if the symptom were misrouted or misclassified incidents.

The steering committee held meetings via video conference instead of in-person boardrooms.

Why it fails: Meeting delivery format does not govern whether improvement changes are communicated to affected teams or embedded in their working practices. It is tempting because in-person sessions can aid engagement, and would be correct if the gap were specifically poor participation or decision-making during steering committee meetings.

The continual improvement register was stored in a spreadsheet instead of a relational database.

Why it fails: The storage medium for the improvement register does not determine whether improvements are communicated, adopted and reinforced across the organisation. It is tempting because a relational database offers better reporting and integrity, and would be correct if the problem were data quality, concurrency or reporting limitations in the register itself.

Inform staff that restructuring is a minor administrative task requiring no adjustment on their part.

Why it fails: Labelling restructuring a minor administrative task denies the real changes to roles and reporting lines, so staff cannot prepare and trust erodes. It tempts because it appears reassuring, but anxiety stems from uncertainty about concrete role impacts; honest, specific communication about what changes and when is required.

Direct employees to research the new operating model independently on external blogs.

Why it fails: Pointing employees to external blogs leaves them without authoritative, organisation-specific information about their own roles and reporting lines, so uncertainty persists. It tempts as a low-effort way to share context, but reducing anxiety requires leadership to communicate directly about the actual restructuring and its impact on each team.

Keep all restructuring details secret until the exact day of implementation to avoid early panic.

Why it fails: Withholding restructuring details until implementation day removes the information staff need to prepare, amplifying rumour and anxiety rather than reducing it. It tempts as a way to avoid premature panic, yet transparent, timely communication about role and reporting changes is what actually lowers uncertainty during a product-management transition.

The project team failed to use agile software development methodologies for the hardware rollout.

Why it fails: Agile delivery methods govern software iteration cadence, not cross-cultural change adoption; the failure stems from ignoring local cultural context in the OCM plan. Agile would be the right focus if the rollout were failing due to rigid waterfall release scheduling rather than cultural mismatch.

The corporate intranet site used an outdated cascading style sheet design.

Why it fails: Intranet styling is a presentation concern with no bearing on whether a subsidiary adopts a new operating model. CSS refresh would be the correct remedy only if the failure were poor portal usability, not cultural resistance to centralised change.

The IT service desk ticketing tool lacked automated incident routing rules.

Why it fails: Ticketing routing rules are an ITSM tooling concern and have no bearing on whether a change plan is adopted across cultures. The failure reflects neglecting local cultural context and stakeholder engagement. Automated routing would be the right fix for misdirected incident tickets, not change adoption.

Post signs in every store reminding staff that customer service is secondary to IT modernization.

Why it fails: Signage declaring customer service secondary to modernisation directly contradicts retail's core value proposition and does nothing to address checkout-speed anxiety. It is tempting as a cheap visible endorsement of the change, but communication of this kind is the correct choice only when the message aligns with, rather than undermines, the operational outcome being protected.

Reduce store operating hours permanently to accommodate slower transaction speeds.

Why it fails: Permanently cutting trading hours sacrifices revenue to accommodate a system limitation, rather than resolving the throughput concern the managers raised. It is tempting because reducing peak load does lower transaction pressure, but that is the right lever only when demand genuinely exceeds capacity, not when the fix is process or configuration.

Dismiss their concerns as resistance to technology and mandate immediate adoption without training.

Why it fails: Mandating adoption without training removes the very capability store managers need to hit checkout-speed targets, and dismissing concerns leaves the operational risk unaddressed. It is tempting as a way to force pace, yet it is the correct choice only when leadership has already decided and resistance is purely political, not performance-based.

The total number of emails sent by the communications server daemon.

Why it fails: Emails sent by the daemon count outbound volume, not whether recipients opened, read or acted on the message, so reach and effectiveness remain unmeasured. It is tempting because send volume genuinely confirms the campaign dispatched, and would suit a question about delivery throughput or server load.

The financial cost of the graphic design software used to create posters.

Why it fails: Design software cost measures production expenditure, not audience reach or campaign effectiveness, so it cannot evidence how many people saw or acted on the portal messaging. It is tempting because budgeting and cost tracking are legitimate communication-planning activities, and spend analysis would be the right metric when justifying campaign expenditure to finance.

The physical weight of printed flyers distributed across regional offices.

Why it fails: Flyer weight quantifies printing and distribution volume, not whether the audience received, understood or engaged with the campaign message. It is tempting because physical distribution genuinely evidences offline outreach activity, and would suit a question about print logistics or regional coverage.

Outsource all middle management functions to external management consultants.

Why it fails: Outsourcing middle management removes the very layer whose passive resistance the OCM plan must convert into active sponsorship; it addresses headcount, not the stakeholder-engagement gap. External consultants are engaged for capability gaps or transformation delivery, whereas this scenario demands targeted interventions such as coalition-building and incentive alignment within existing management.

Remove all middle management layers and have executives manage operational staff directly.

Why it fails: Removing middle management destroys the layer that translates executive vision into team-level practice and absorbs frontline concerns, worsening resistance. Flattening structures is appropriate in very small organisations where no meaningful management tier exists, not as a remedy for passive resistance.

Increase the frequency of executive video broadcasts directed solely at end-users.

Why it fails: Broadcasting more executive videos bypasses the managers whose endorsement determines whether staff adopt the change, leaving the passive resistance untouched. Executive broadcasts suit building awareness across a large dispersed workforce, not converting sceptical middle managers into active sponsors.

Strict instructions to forbid any questions from staff during team meetings.

Why it fails: Forbidding questions blocks the upward feedback loop that cascade communication depends on, preventing leaders from surfacing confusion or resistance. It is tempting because it appears to keep meetings efficient and on-message, and would be correct only where a strictly one-way, no-interruption briefing is genuinely required.

A detailed list of disciplinary actions for anyone who fails the software assessment.

Why it fails: Disciplinary actions address compliance enforcement, not the purpose, timing, or impact information staff need to understand the upgrade. It is tempting because accountability matters in change adoption, and would be correct when communicating consequences of failing a mandatory compliance requirement after training.

Technical source code snippets for the new application modules.

Why it fails: Source code snippets expose implementation detail that team leaders cannot relay meaningfully; cascade messaging requires the business rationale, impact and timing of the upgrade. Code-level detail belongs in developer release notes or technical handover sessions, not in leader-led communication to affected staff.