Hard Difficulty Questions

Prioritize quality above all, as documentation is the foundation of service.

Why it fails: Prioritizing one extreme without considering customer value is dangerous. If the customer values speed, excessive documentation will lead to dissatisfaction. The goal is to find the right balance that satisfies the user's requirements, not to enforce an arbitrary rule that may not align with the actual value delivered.

Prioritize speed, as delivering value quickly is the only way to satisfy users.

Why it fails: Prioritizing speed at the expense of quality can result in technical debt and poor service consistency. If the quality falls below a threshold, the service becomes unusable, defeating the purpose of speed. A balanced approach is needed to ensure long-term sustainability and consistent value delivery to the end users.

Ask the IT manager to decide, as they have the best technical understanding.

Why it fails: Technical managers often favor quality and stability, which may conflict with business needs for speed. Decision-making should be driven by the value provided to the customer, not by the personal expertise or preferences of an individual manager, regardless of how technically capable or experienced they may be.

Include highly detailed technical logs to prove the team was working hard.

Why it fails: Senior stakeholders are not interested in technical logs or evidence of 'hard work.' They are interested in outcomes, value, and strategic alignment. Providing technical detail obscures the business message and indicates a lack of understanding regarding the needs of the audience, which can undermine the project's credibility.

Focus only on the successful aspects and omit any project setbacks.

Why it fails: Transparency is a key DPI principle. Omitting setbacks misleads stakeholders and damages trust. If issues occurred, they should be documented along with the mitigation strategies applied. This shows maturity and honesty, which is necessary for maintaining long-term credibility and support from the organization's governing body.

Provide only verbal reports to ensure that sensitive details are not documented.

Why it fails: Verbal reports are not a substitute for formal documentation, which is required for governance and accountability. Excluding documentation prevents tracking progress over time and creates a knowledge gap for other stakeholders. All significant project reporting should be documented and accessible to the relevant parties as part of good governance.

Focus primarily on the Information and Technology dimension to ensure technical stability.

Why it fails: Focusing solely on technology creates a skewed plan that ignores the human, process, and partnership elements. Even a technologically perfect service will fail if it does not account for user needs, organizational capability, or supplier support. Holistic planning is required to avoid siloed and ineffective outcomes.

Use the Value Stream Mapping technique to identify bottlenecks in the process.

Why it fails: Value stream mapping is excellent for analyzing processes, but it does not inherently address the other three dimensions, such as partners or organization/people. While useful for process optimization, it is not a complete tool for ensuring all four dimensions are represented in a broad service plan.

Develop the plan based on historical performance data from previous projects.

Why it fails: Historical data is useful but limited to past experiences. It does not ensure the consideration of current organizational realities, technological advancements, or changing supplier ecosystems. Relying only on the past prevents the necessary forward-looking perspective required to build a resilient and modern service plan.

Implementing punitive measures for any process deviation.

Why it fails: Punitive measures create a culture of fear, which suppresses innovation and hides issues. Employees will prioritize compliance over improvement, leading to a stagnant environment where problems are buried rather than addressed. This is antithetical to the DPI principle of 'Collaborate and promote visibility'.

Limiting improvement initiatives to senior leadership teams.

Why it fails: Restricting improvements to leadership creates a bottleneck and disconnects strategy from operational reality. Improvements are most effective when informed by those performing the actual work. Limiting input limits the scope of potential gains and misses critical opportunities for optimization within the service value system.

Ensuring all improvements are mandated by external auditors.

Why it fails: Improvements driven solely by external mandates are usually reactive and compliance-focused rather than proactive and value-driven. A healthy culture of improvement should be self-sustaining and aligned with internal business goals, not just responding to external pressures, which can lead to superficial or unsustainable changes.

Culture is static and should not be influenced by strategic planning.

Why it fails: Culture is highly dynamic and is constantly influenced by leadership actions, organizational policies, and communication. Ignoring the need to align culture with strategy can result in significant resistance to change. A static view of culture fails to recognize the human element necessary for successful service management implementation.

Culture is strictly an HR function and does not involve IT management.

Why it fails: Culture is a shared responsibility that permeates every department, including IT. IT managers must be cultural advocates to promote collaboration and adoption of new practices. Limiting cultural management to HR ignores the vital role that technical leadership plays in modeling behaviors and driving organizational change initiatives.

Culture is only relevant during large-scale digital transformations.

Why it fails: Culture is a daily reality that impacts all activities, regardless of the scale of transformation. Continuous improvement requires a culture that supports learning and experimentation. Neglecting culture during routine operations or smaller improvements will lead to fragmented efforts and a lack of organizational cohesion over time.

Immediately terminate the employee who performed the manual change to enforce strict policy compliance.

Why it fails: Immediate termination ignores the potential systemic issue that forced the employee to bypass the pipeline. Investigating the root cause is essential in DPI to determine if the automation tool failed or if the policy is impractical. Reactive punishment often hides underlying process failures that require systemic correction.

Update the policy to permit manual changes during peak hours to increase operational flexibility.

Why it fails: Loosening restrictions without understanding why they were bypassed creates security and audit risks. The objective of DPI is to ensure governance is effective and supportive. Permitting manual changes without addressing the root cause of the failure risks further drift from the established control framework and operational standards.

Ignore the violation as long as Cluster_A remains stable and fully operational for users.

Why it fails: Ignoring policy violations undermines governance and exposes the organization to unnecessary risk. DPI requires that all deviations from standard procedures be analyzed and addressed to ensure consistent control. Failing to act sends a message that policy compliance is optional, which leads to long-term operational degradation and risk.

Hardware Procurement Audits.

Why it fails: Hardware audits are specific to asset management and financial compliance. They do not provide a comprehensive view of the organization's capabilities, culture, or strategy. While they can identify cost-saving opportunities, they are too granular and technically focused to serve as a primary assessment method for organizational planning and improvement.

Randomized Staff Resignation Surveys.

Why it fails: Resignation surveys provide limited data biased toward departing employees. They do not offer a systematic or representative view of the organization’s current state. While employee satisfaction is important, using this specific method as a primary assessment tool would provide an incomplete and potentially misleading picture of organizational health.

The action is appropriate because it enforces compliance with the established policy.

Why it fails: While it enforces the rule, it does not address the root cause of the non-compliance. A DPI strategist must understand why the policy was bypassed to ensure the migration is successful and long-term compliance is maintained. Enforcement without investigation is a reactive, short-sighted approach to management.

The action is unnecessary because the project team is likely protecting sensitive data.

Why it fails: Security concerns do not justify ignoring a central policy. If the policy is flawed, it should be updated, not bypassed. Assuming the team is right without investigating undermines the organization's governance. All documentation must follow established standards to ensure auditability and transparency within the service system.

The action should include a penalty for the project manager to prevent future issues.

Why it fails: Punitive actions rarely solve systemic problems and can discourage open communication. A DPI strategist focuses on learning and improvement, not punishment. If a policy is consistently bypassed, it usually points to a flaw in the process or tools rather than individual negligence or malicious intent.

Start where you are.

Why it fails: The log does not indicate that the starting point was ignored. The issue was not the assessment of the existing state, but the lack of focus on how the change would impact the user experience. The failure is specifically tied to a narrow definition of success criteria.

Optimize and automate.

Why it fails: The initiative clearly optimized and automated processes to achieve a 15% efficiency gain. The problem was not the optimization itself, but the lack of holistic consideration for how that optimization affected the user. It is not the principle of optimization that was missing, but the principle of value.

Iterate with feedback.

Why it fails: While feedback is a component of 'Iterate with feedback', the fundamental failure here is the definition of value. If the team had focused on value correctly from the start, they would have likely gathered user input before implementing the change, making this a failure of the 'Focus on value' principle.

Automate the CAB approval process to eliminate the human element entirely.

Why it fails: Automating before understanding the cause of the delay is risky. If the delay is caused by poor data in the change request, automation will just process bad data faster. Understanding the 'why' behind the delay is essential before deciding whether automation is the appropriate solution for the problem.

Remove the CAB approval stage completely to speed up the process.

Why it fails: Removing the CAB approval stage without understanding its purpose or why it is causing delays could introduce significant risk to the organization. Governance requires that changes are reviewed; if the process is broken, it must be fixed or redesigned, not simply removed without careful consideration of the consequences.

Replace the existing CAB members with new staff who may be more efficient.

Why it fails: Assuming the bottleneck is caused by the individuals involved is rarely the correct conclusion. The problem is usually systemic, related to the process, the information provided, or the frequency of meetings. Replacing staff without addressing the underlying process issues will not resolve the delay and may create new problems.

The initiative should be immediately cancelled because the current error rate of 22% exceeds acceptable operational tolerances.

Why it fails: High error rates indicate a need for improvement rather than project cancellation. Identifying high error rates is the primary purpose of assessing the current state so targeted automation can resolve the underlying issues.

The action plan lacks a mechanism to measure progress against the defined baseline, making success verification impossible.

Why it fails: The current state metrics establish a clear baseline (14 days cycle time, 22% error rate) against which the target state (2 days, 2%) will be measured using the specified weekly reviews and automation steps.

Step 1 of the action plan violates ITIL 4 principles by introducing CI/CD pipelines before establishing a formal change advisory board.

Why it fails: ITIL 4 emphasizes flow and value over bureaucratic change advisory boards. Automating deployment scripts aligns with modern lean and agile practices supported by the DPI guiding principle 'Optimize and automate'.

Increase the frequency of status meetings to daily

Why it fails: Increasing meeting frequency is a reactive tactic that often adds administrative burden without addressing the root cause of project stagnation. If the underlying issues are lack of priority or resource scarcity, more meetings will only frustrate the team further. The problem is strategic oversight, not the lack of reporting frequency.

Mandate the immediate completion of all items in the register

Why it fails: Mandating completion without reviewing resource availability or strategic alignment is unrealistic and ignores the complexity of the work. This approach leads to poor quality outputs and burnout. Effective management requires understanding why these items are stalled, rather than simply demanding an outcome regardless of the underlying obstacles or current context.

Automate the status update process to improve visibility

Why it fails: Automation improves transparency but does not solve the underlying lack of progress. If the items are stagnant due to resource or strategic conflicts, automation only highlights the failure faster. The organization needs to fix the decision-making and resourcing processes before focusing on the technology used to track status updates.

Governance roles must be performed by external consultants to ensure objectivity.

Why it fails: While external consultants can advise on governance, the ultimate accountability for governance must remain with internal stakeholders. They are responsible for the outcomes of the organization. Outsourcing governance accountability leads to a lack of ownership and a breakdown in the direct link between strategy and organizational performance.

Management must dictate the governance policies to ensure operational efficiency.

Why it fails: Governance sets the boundaries and objectives within which management operates. If management dictates governance, it creates a conflict of interest where operational shortcuts might bypass necessary controls. Governance must exist as a separate oversight layer to ensure that operational efficiency does not come at the cost of compliance.

Governance is redundant if management is highly experienced and trustworthy.

Why it fails: Governance is not about trust; it is about accountability, consistency, and risk management. Even the most trustworthy management team requires a governing framework to ensure their efforts remain aligned with the evolving strategic goals of the organization and to protect stakeholders from unforeseen risks in complex environments.

Governance is responsible for daily execution and operational tasks

Why it fails: Governance is about oversight, direction, and accountability, not daily execution. Operational tasks are the responsibility of the management function. Confusing these two levels leads to micromanagement, where governance bodies focus on details instead of strategic alignment, effectively preventing them from fulfilling their primary role of high-level oversight and control.

Governance focuses primarily on the technical tools used for improvement

Why it fails: Governance does not define the technical toolset; that is a management or operational decision. Governance sets the policies that dictate how those tools must be used to ensure security, privacy, and compliance. Focusing on the tools themselves ignores the broader strategic mandate of governance and risks operational over-reach.

Governance is only relevant during the initial planning phase

Why it fails: Governance is a continuous process that spans the entire lifecycle of a strategy, from planning to operation and improvement. It is not a one-time event or phase. Organizations must continuously monitor performance against governance policies to ensure that they remain compliant and aligned throughout the entire duration of their initiatives.

Governance is the process of delegating all decisions to frontline teams.

Why it fails: Governance is about establishing boundaries, setting strategic direction, and ensuring accountability, not abdicating decision-making. While delegation is encouraged, it must occur within a framework of oversight and alignment with organizational goals. Total delegation without governance would lead to fragmented efforts and significant, unmanaged risks for the organization.

Governance should be rigid to prevent any deviation from standard procedures.

Why it fails: Rigid governance stifles innovation and prevents the agility needed in a fast-moving market. Effective governance provides a flexible framework that allows for adaptation while maintaining control. Excessive rigidity leads to bureaucratic slowdowns that prevent the organization from responding effectively to changes in the customer or business environment.

Governance is only relevant for large, publicly traded companies.

Why it fails: Governance is essential for all organizations, regardless of size or sector. Every organization needs oversight to ensure resources are used effectively and risks are managed. Without a governance framework, organizations of any size are prone to drift, inefficiency, and avoidable failures that can threaten their long-term viability.

Redesign all existing processes to be more simplistic and easier for employees to follow.

Why it fails: Redesigning processes without first measuring their current effectiveness is premature and likely to be ineffective. Without baseline metrics, there is no way to tell if the new processes are actually performing better than the old ones, leading to wasted effort and potentially disrupting stable workflows.

Increase training sessions for staff to ensure better compliance with the documented processes.

Why it fails: Training staff on processes that are not measured for effectiveness is a poor use of resources. If the processes themselves are flawed or misaligned with business needs, improved compliance will simply result in the efficient execution of ineffective activities, failing to solve the core organizational problem.

Implement an automated workflow engine to force users to follow the documented steps.

Why it fails: Automating an unmeasured process often hardcodes inefficiencies into the system. Without performance measurement, automation simply makes the current state faster or more rigid, which may not be beneficial. The organization must understand performance metrics before investing in automation to ensure it supports the desired business outcomes.

Establish a separate, isolated compliance department that reviews projects only after they have been fully deployed.

Why it fails: An isolated department reviewing only after deployment breaks holistic integration, since compliance must be embedded across the value stream rather than bolted on at the end. It is tempting because specialist review adds assurance, and would be correct where independent post-implementation audit is the stated requirement.

Focus compliance efforts exclusively on financial reporting while ignoring technical and operational risks.

Why it fails: Ignoring technical and operational risks contradicts holistic thinking, which requires GRC to span all risk domains as one interconnected system. It is tempting because narrowing scope to financial reporting eases regulatory audit effort, and would suit a purely finance-focused SOX compliance programme where operational risk sits outside the mandate.

Automate all compliance audits and remove human governance oversight to accelerate software delivery speed.

Why it fails: Removing human governance oversight breaks the holistic principle: automation cannot own accountability, and ITIL 4 treats governance as inseparable from delivery. It is tempting because automating audit evidence collection genuinely accelerates CI/CD pipelines, and would be right where routine, low-risk compliance checks need continuous, repeatable validation without manual intervention.

Auto-approve the plan since it is below the max_risk_score of 5.0

Why it fails: Auto-approval is limited to plans with a score of 2.5 or lower. A score of 3.2 exceeds this threshold, meaning the policy requires a formal review. Simply relying on the max score ignores the distinction between automated and manual processes defined in the policy's thresholds for risk management.

Reject the plan immediately because it exceeds the auto_approve_threshold

Why it fails: Exceeding the auto-approval threshold does not mean the plan is rejected; it means it requires manual intervention. Rejecting the plan without a proper review is premature and could lead to the loss of a valuable improvement opportunity that simply needs to be assessed by the appropriate human oversight.

Ignore the risk score and proceed, as it complies with all other policies

Why it fails: Ignoring a risk score violation is a direct breach of organizational policy. The policy is designed to enforce strict risk controls. Proceeding without addressing this violation would be a failure of governance and could expose the organization to unacceptable risks that the policy was explicitly designed to prevent.

Centralized oversight.

Why it fails: While governance is maintained, the primary shift is towards streamlining processes through automation. Simply calling it centralized oversight ignores the specific action taken to remove the manual bottleneck, which is the core of the change. The move is designed to empower teams while maintaining the required compliance levels.

Standardization of manual processes.

Why it fails: The change is explicitly moving away from manual processes. Standardization is a good step, but the goal here is the removal of the manual step entirely. The focus is on replacing manual effort with logic-driven automation to improve efficiency without compromising on the established quality and risk controls.

Strategic risk avoidance.

Why it fails: The policy is not avoiding risk, but managing it differently through automation. Avoiding risk would mean stopping all changes. Instead, this policy accepts risk for low-impact changes to gain speed. It is a calculated, risk-based approach to governance that supports rather than hinders the flow of value.

Keep it simple and practical.

Why it fails: While the plan is not practical, the violation of collaboration is more fundamental. The directive fails because it ignores the input of the people tasked with doing the work. This lack of collaboration is the primary driver of the failure, making it a more significant breach of DPI principles.

Focus on value.

Why it fails: While this may not result in long-term value, the primary failure is the process of setting the goal. The lack of collaborative planning is the immediate problem. If the goal were reached through effective collaboration, it might provide value, but the current approach guarantees failure and poor morale.

Start where you are.

Why it fails: The directive does acknowledge the current state (the need for faster response times), but it ignores the capabilities and constraints of that state. The bigger issue is the top-down, non-collaborative approach to mandate change. The lack of collaboration is the root cause of the directive's failure to succeed.