Direct, Plan and Improve practice questions

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.

Ensuring that all failures are punished to prevent repetition.

Why it fails: Punishing failure creates a culture of fear, which suppresses transparency and innovation. DPI promotes a 'blameless' approach to learning where failures are viewed as opportunities for improvement. Punitive measures discourage teams from reporting issues, leading to hidden risks and systemic weaknesses that ultimately harm the organization's performance.

Mandating that improvement ideas only originate from senior management.

Why it fails: Limiting improvement sources to senior leadership ignores the vast knowledge of frontline staff who interact with services daily. A successful DPI culture encourages participation from all levels. Excluding the workforce results in missed opportunities and reduced employee engagement, both of which are critical for sustainable, effective organizational improvement.

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.

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.

Ensuring the plan is kept confidential until the final stages of completion.

Why it fails: Secrecy in planning prevents collaboration and reduces visibility. DPI encourages transparency, as it allows stakeholders to provide feedback and ensures alignment throughout the planning process. Keeping plans hidden creates silos and increases the risk of misalignment with other organizational activities or strategic shifts that occur during development.

Focusing solely on the budget constraints to minimize expenditure.

Why it fails: Focusing only on budget ignores the actual value the service is supposed to deliver. While fiscal responsibility is important, a plan that only targets cost reduction can degrade service quality and user satisfaction, ultimately failing the primary intent of service management: to create value for the customer.

Delegating all planning tasks to external consultants to save internal time.

Why it fails: While consultants provide expertise, delegating the entire planning process removes internal ownership and context. Effective plans require deep knowledge of the specific organizational culture and constraints. Relying exclusively on outsiders often results in generic plans that lack the necessary buy-in and organizational fit required for successful, sustainable implementation.

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.

Increase the target reduction goal to 20% to account for initial project delays.

Why it fails: Arbitrarily increasing the target goal without addressing the root cause of delays is counterproductive. It adds pressure without providing the necessary resources or risk management, potentially leading to lower quality outcomes and failing to resolve the underlying issues that are causing the current project stall.

Bypass the risk assessment phase to accelerate the allocation of resources and save time.

Why it fails: Bypassing the risk assessment phase introduces unnecessary risk into the organization. This action contradicts the principles of sound governance, which require that initiatives are carefully evaluated for potential threats to stability and value creation. Shortcuts at this stage often lead to costly rework later in the process.

Re-run the compliance check to confirm if the initial results are still valid for the current quarter.

Why it fails: Re-running a passed compliance check provides no value when the project is already stalled by resource and risk issues. The focus must be on resolving the blockers identified in the log, not repeating tasks that have already been verified as complete and compliant with organizational standards.

Collaborate and promote visibility.

Why it fails: While communication might have happened, the log specifically shows an adjustment to project scope based on resource availability. This is an optimization decision designed to keep the project on track, not a deliberate effort to promote visibility or collaboration, although these might be secondary benefits.

Focus on value.

Why it fails: While the decision to adjust scope is intended to protect the value of the project, the primary action taken here is a resource-based optimization. 'Focus on value' would be more clearly demonstrated by checking if the adjusted scope still provides the necessary business outcomes for the stakeholders.

Start where you are.

Why it fails: 'Start where you are' would involve evaluating the current state of the project before making any changes. While the team acknowledged the current resource situation, the action taken was a specific optimization of scope, which is distinct from the general principle of assessing the starting point.

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'.

The Four Dimensions of Service Management.

Why it fails: While 'Organizations and People' is one of the four dimensions, it is a broad framework component, not a specific concept for shaping culture. DPI focuses on using leadership influence and change management practices to align culture with strategy, rather than just identifying the dimension as a broad category.

Continual Improvement Model.

Why it fails: The Continual Improvement Model provides a structured approach for iterative progress. While it can be used to improve cultural aspects, it is not the primary mechanism for establishing or directing organizational culture. Leadership, communication, and behavioral alignment are the specific drivers for defining and managing the culture.

Service Value System architecture.

Why it fails: The Service Value System describes how all components work together to create value. While culture is an implicit part of the system, the SVS is an overarching structure. Shaping specific cultural behaviors requires direct intervention through leadership and change management rather than just referencing the high-level SVS model.

Metrics must be easily automated to ensure zero human effort in reporting.

Why it fails: While automation is desirable, it is not the primary requirement for a measurement framework. If the automated metric does not provide insight into strategic success, it is worthless. The importance of the metric's relevance to business outcomes far outweighs the technical convenience of its automated collection method.

Reporting should include all operational data to ensure complete transparency.

Why it fails: Including all operational data creates noise and obscures the important trends. Effective reporting is about clarity and focus. Practitioners should curate the information so that the most important insights regarding strategic progress are immediately visible, rather than overwhelming stakeholders with raw data that lacks context or actionable significance.

Standardize all metrics globally to ensure comparison across disparate business units.

Why it fails: While some standardization is helpful, forcing identical metrics on every business unit can lead to irrelevant data. Different units have different goals and contexts. A flexible framework that balances standardization with unit-specific relevance is superior to a rigid, global approach that ignores local realities and nuances.

The service level agreement (SLA) for individual customers.

Why it fails: An SLA is an operational tool focused on specific service targets for a customer. It is too narrow in scope to guide the overall strategic direction of an organization. While SLAs contribute to service quality, they do not provide the high-level strategic alignment required for effective 'Direct' governance.

The daily task list for the help desk team.

Why it fails: A task list is an operational document that provides no strategic value. It is concerned with the execution of daily activities rather than the planning or direction of the organization. Relying on such documents for strategic oversight would lead to a complete lack of long-term vision and alignment.

The project charter for an infrastructure upgrade.

Why it fails: A project charter is specific to a single initiative. While important for project management, it does not serve as a tool for the broader 'Direct' phase of DPI. It describes the scope and objectives of one project, not the holistic, organization-wide strategy required for effective strategic direction.

Mandating that all teams submit improvement logs daily

Why it fails: Strict mandates for daily logging often lead to 'tick-box' compliance rather than genuine improvement culture. This creates administrative overhead that discourages staff from engaging meaningfully with the improvement process. Quality of improvements is far more important than the quantity of entries generated by forced, repetitive daily administrative tasks.

Assigning improvement tasks to a centralized task force

Why it fails: Centralizing improvement tasks creates a silo and limits the organization's capacity for innovation. It disconnects those who identify the problems from those who implement the solutions. Effective improvement requires distributed accountability where teams closest to the work are empowered to contribute their own ideas and technical insights.

Removing all performance metrics to minimize pressure

Why it fails: Removing metrics leads to a lack of feedback loops, making it impossible to determine if improvements are actually working. Evidence-based decision-making relies on data to validate hypotheses. Without measurements, the organization loses the ability to learn from success or failure, which hinders the overall maturity of the improvement culture.

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.

To reduce the number of employees required for a specific service process.

Why it fails: Reducing headcount is not the primary objective of value stream mapping. The focus is on improving flow and eliminating non-value-added activities. Misinterpreting this can lead to staff morale issues and the loss of critical organizational knowledge that is essential for long-term service delivery and operational success.

To document every technical task performed by the IT infrastructure team.

Why it fails: Documenting every single task leads to excessive detail that obscures the broader value stream. DPI focuses on the flow of value to the customer, not just recording granular technical steps. Over-documentation consumes valuable time without necessarily providing actionable insights for improving overall organizational efficiency or service quality.

To establish a new hierarchy for reporting within the IT department.

Why it fails: Changing the reporting hierarchy is a structural intervention that does not address how value is delivered. DPI emphasizes process improvement and cultural alignment over organizational charts. Focusing on reporting structures ignores the underlying workflow issues that value stream mapping is specifically designed to uncover and resolve.

It lacks clear definitions for the term 'high-risk' changes.

Why it fails: While lack of definitions is a concern, it is secondary to the lack of strategic alignment. The policy's primary flaw is the directive nature of the goals without assessing organizational readiness. Focusing solely on terminology misses the broader DPI failure of imposing change without proper planning or consultation.

It requires CIO sign-off which slows down decision-making processes.

Why it fails: While hierarchy can create bottlenecks, the core issue is the disconnect between strategic direction and tactical implementation. Focusing on the sign-off process overlooks the fundamental problem: the arbitrary nature of the mandated targets. The priority is to address the lack of planning and strategic alignment first.

It uses automated testing which is not considered a best practice.

Why it fails: Automated testing is a widely recognized best practice in modern IT service management. The issue is not the use of automation, but the mandate to implement it without considering the specific context or current skill sets. Criticizing the practice itself is incorrect; the error lies in the implementation approach.

A comprehensive list of all technical metrics to be tracked daily.

Why it fails: Tracking excessive technical metrics often leads to 'analysis paralysis' and fails to reflect value. Focus on Value requires selecting metrics that demonstrate how IT services directly support business goals. Collecting technical data for its own sake is a waste of resources that does not contribute to strategic outcomes.

A mandate that all departments implement the same improvement methodology.

Why it fails: A 'one size fits all' approach contradicts the principle of flexibility and context-sensitivity. Different departments have different value chains and needs. Forcing a single methodology can create friction and reduce overall efficiency. Value is context-dependent, and the approach to improving it must be tailored to specific organizational needs.

A budget that prioritizes cost reduction over service innovation.

Why it fails: Focusing solely on cost reduction often destroys value rather than creating it. Innovation is frequently the primary driver of competitive advantage and long-term value. A balanced DPI approach considers both efficiency and the capacity for innovation to ensure that the organization remains relevant and competitive in the market.

To identify which staff members are responsible for past performance issues.

Why it fails: DPI focuses on improving processes and systems, not blaming individuals. Identifying individuals for punishment creates a hostile environment that prevents future improvement. The focus must remain on systemic analysis and organizational growth rather than finding scapegoats for historical performance problems, which is counter-productive to the improvement objective.

To ensure that no new technology is introduced during the initiative.

Why it fails: The objective of the current state assessment is to understand the environment, not to restrict technology adoption. New technology might be an essential part of the improvement. The assessment helps determine if the organization is ready for such technology and how best to integrate it for maximum value.

To reduce the time required to complete the planning phase.

Why it fails: Assessing the current state takes time and effort. While it may feel like a delay, it is a critical investment that saves significant time and resources in the long run by preventing misguided initiatives. Prioritizing speed over thorough assessment typically leads to rework and failure in the execution phase.

Initiate a competitive tender process to find potential vendors.

Why it fails: Starting the procurement process before understanding the strategic implications is premature. A tender might result in selecting a vendor that doesn't fit the organization's long-term objectives. Strategy must drive procurement, not the other way around. This approach risks losing control over core competencies and failing to deliver value.

Consult the legal department to draft the service level agreement.

Why it fails: Legal considerations are important, but they come after the strategic decision to outsource. Drafting contracts before deciding if outsourcing makes sense is an inefficient use of legal resources. This step assumes that the decision has already been made, which bypasses the necessary strategic analysis required by DPI.

Notify the internal team that their roles will be redundant.

Why it fails: Communicating redundancy before a decision is finalized is destructive to morale and productivity. It creates unnecessary uncertainty and could lead to the loss of key talent before a clear plan is in place. Managing the human aspect of change should be done with care, transparency, and correct timing.

Scrap the current automation script and build a new one from scratch.

Why it fails: Rebuilding from scratch is a costly and risky undertaking that ignores the value in the existing script. It might introduce new bugs and does not address the fundamental issue of dependency management. Starting where you are means preserving what works while specifically targeting the actual technical failure for remediation.

Manually run the process until a vendor support ticket is resolved.

Why it fails: Manual intervention is a temporary patch that does not solve the underlying problem. It creates operational inefficiency and delays. While necessary in the short term, the DPI-focused response is to analyze why the dependencies are failing and improve the process, not just work around the failure indefinitely.

Disable the automation to prevent further error logs.

Why it fails: Disabling the automation removes the visibility of the problem but does not solve it. It forces the organization to revert to inefficient manual processes. DPI requires that organizations face their performance issues and actively improve them, rather than hiding them or avoiding the work required to fix them.