Hard Difficulty Questions

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

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

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

Why wrong: Incident categorization impacts service metrics, not long-term cultural change sustainability.

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

Why wrong: Meeting medium has negligible impact on the sustainability of operational improvements.

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

Why wrong: Database type does not determine whether organizational behaviors are sustained.

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

Why wrong: Ignoring high-power stakeholders is dangerous, as they can easily derail the initiative if unexpected impacts arise.

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

Why wrong: Junior delegates lack the influence required to manage high-power stakeholders effectively.

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

Why wrong: General announcements do not adequately address the unique needs of high-power stakeholders.

Ignore their potential veto and deploy the software without regulatory sign-off.

Why wrong: Bypassing regulatory compliance officers risks legal penalties and project shutdowns.

Send them daily automated operational ticketing reports to keep them busy.

Why wrong: Operational noise annoys high-power stakeholders and leads them to ignore important updates.

Invite them to every daily agile standup meeting across all development squads.

Why wrong: Requiring attendance at granular operational meetings wastes their time and alienates them.

Abolish all regional business units and manage all operations from global headquarters.

Why wrong: Centralizing everything ignores local market needs and legal requirements.

Abandon the continual improvement initiative entirely in regions that show any initial resistance.

Why wrong: Abandoning initiatives prematurely prevents global organizational capability growth.

Enforce a single, rigid global change plan without exception to ensure standardization.

Why wrong: Rigid global plans fail when they violate local labor laws or cultural norms.

Bypass the finance department by routing all project funding through unauthorized corporate credit cards.

Why wrong: Bypassing finance violates corporate governance and leads to legal action.

Tell financial controllers that agile teams do not need budgets or financial governance.

Why wrong: Eliminating financial governance is irresponsible and alienates financial controllers.

Send them weekly motivational quotes about the beauty of agile transformation.

Why wrong: Motivational quotes do not address legitimate financial control and risk concerns.

Increase the volume and frequency of simultaneous change projects to force rapid adaptation.

Why wrong: Increasing concurrent projects worsens change fatigue and drives higher resistance.

Mandate strict adherence to new processes without providing any channels for feedback or support.

Why wrong: Forcing compliance without support or feedback channels increases resentment and failure rates.

Eliminate the security compliance team entirely to speed up delivery.

Why wrong: Eliminating compliance exposes the organization to unacceptable risks.

Increase the number of approval sign-offs to ensure absolute compliance.

Why wrong: Adding approval sign-offs increases bureaucracy and worsens delays.

Isolate the development team from the security team to avoid interpersonal conflicts.

Why wrong: Isolation exacerbates silo mentalities and prolongs feedback cycles.

Evaluating the hardware inventory depreciation schedules across regional data centers.

Why wrong: Hardware depreciation is a financial metric completely unrelated to organizational change readiness.

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

Why wrong: CAB approval volume measures process throughput, not human readiness or cultural sentiment.

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

Why wrong: Incident backlogs reflect past technical performance, not future behavioral readiness for change.

Increase the duration of classroom lecture hours by an additional 40 hours.

Why wrong: More lectures do not solve application gaps if operational workflows or incentives are misaligned.

Assume employees are lazy and mandate weekly testing on ERP system theory.

Why wrong: Punitive testing does not resolve systemic adoption barriers.

Replace the ERP software vendor immediately with a different market leader.

Why wrong: Changing vendors is an extreme overreaction when the issue is operational adoption support.

Prioritize rapid technical deployment above all else, assuming cultural adoption will naturally follow once users see the system.

Why wrong: Assuming adoption follows deployment without active OCM often results in low utilization and unrealized value.

Separate the technical project team completely from the change management team to avoid conflicting priorities.

Why wrong: Isolating technical and change teams leads to a disconnect between system capabilities and user readiness.

Focus exclusively on cultural workshops for two years before initiating any technical planning or software configuration.

Why wrong: Excessive delay without technical grounding causes initiative fatigue and loss of executive sponsorship.

Reviewing personal employee credit score reports from external financial agencies.

Why wrong: Credit reports are privacy violations and irrelevant to IT readiness.

Randomly guessing employee readiness levels based on executive intuition.

Why wrong: Guessing lacks empirical validity and leads to flawed planning.

Publicly reprimand the managers during an all-hands meeting to deter others from following their example.

Why wrong: Public reprimands cause defensiveness, increase covert resistance, and destroy psychological safety.

Ignore their behavior on the assumption that peer pressure from compliant colleagues will eventually correct them.

Why wrong: Ignoring influential resisters allows negative cultural norms to spread unchecked.

Reassign the managers to non-critical administrative roles with no team responsibilities.

Why wrong: Reassignment avoids the root cause of the resistance and wastes valuable organizational leadership talent.

Add three additional managerial approval gates to every standard service request to increase control.

Why wrong: Adding approval gates increases waiting waste and slows flow, contrary to Lean principles.

Increase batch sizes of service requests to maximize administrative processing efficiency.

Why wrong: Lean advocates for single-piece flow rather than large batch sizes, which create delays.

Stakeholder Perceptions (customer and employee feedback results)

Why wrong: Stakeholder Perceptions belongs to the EFQM Results group.

Strategic Performance Results (financial and operational outcomes)

Why wrong: Strategic Performance Results belongs to the EFQM Results group.

Conducting mandatory agile coding bootcamps for internal software developers.

Why wrong: Coding bootcamps for internal staff belong to the 'Organizations and people' dimension.

Migrating legacy monolithic databases to containerized microservices on Kubernetes.

Why wrong: Containerization and databases belong to the 'Information and technology' dimension.

Actively collaborating across organizational silos.

Why wrong: Collaborating across silos is a positive practice, not a pitfall.

Iteratively reviewing feedback from customers and employees.

Why wrong: Iterative feedback is a best practice, not a pitfall.

Service Level Agreement (SLA) percentage breach calculation

Why wrong: SLA breach calculation measures operational performance against targets, not root causes.

Balanced Scorecard financial depreciation modeling

Why wrong: Balanced Scorecard is a strategic performance measurement framework, not an RCA technique.

Outsource 100% of governance decisions to external auditors with no internal stakeholder oversight.

Why wrong: External auditors provide compliance check-ups, not internal governance ownership.

Exempt all continual improvement projects from any security or architectural review to maximize speed.

Why wrong: Exempting projects from security review introduces unacceptable organizational risk.

Bypassing all legal and regulatory compliance reviews.

Why wrong: Governance ensures compliance; bypassing it violates core governance duties.

Micromanaging daily software coding tasks for individual developers.

Why wrong: Governance sets direction and monitors; it does not micromanage operational coding.