Continual Improvement practice questions

Enable Incident Management auto-closure rules.

Why wrong: Incident management rules govern IT support tickets, not CIM initiative review workflows.

Configure a UI Action with client-side script validation.

Why wrong: While UI actions can validate inputs, ServiceNow provides native workspace checklist configurations specifically designed for step-by-step task verification.

Modify the out-of-the-box Service Level Agreement (SLA) definition.

Why wrong: SLAs measure elapsed time, not checklist compliance.

BMC Client Management automatic asset discovery scanner.

Why wrong: Asset discovery is used for hardware and software inventory management.

BMC Helix Change Management risk assessment engine.

Why wrong: Risk assessment is designed for evaluating individual change failures, not prioritization of general improvement backlog items.

BMC Helix Multi-Cloud Service Management integration engine.

Why wrong: Multi-Cloud integrations synchronize data between external providers, not prioritize internal items.

Change Management [change_request]

Why wrong: While an improvement might result in a change request, capturing the raw opportunity itself belongs in the CIM register.

Project Portfolio Management [pm_project]

Why wrong: PPM is for large-scale enterprise projects, whereas CIM is specifically tailored for agile, smaller improvement initiatives.

Problem Management [problem]

Why wrong: Problem Management focuses on diagnosing the root cause of incidents, not managing lifecycle continual improvement initiatives.

Measurement and Reporting

Why wrong: Measurement and Reporting supports data collection but does not own the improvement register.

Service Level Management

Why wrong: Service Level Management defines, documents, and manages service levels.

Change Enablement

Why wrong: Change Enablement manages the lifecycle of individual changes.

Global permissions settings restricting project creation.

Why wrong: Global permissions control who can access or create projects, not individual workflow state transitions.

Jira Service Management automation rules sending an email notification to the steering committee.

Why wrong: Notifications inform stakeholders but do not technically enforce a governance gate or prevent state transition.

Service Level Agreements (SLAs) configured on the 'Backlog' status.

Why wrong: SLAs track time-based metrics, not workflow validation criteria.

Outsource the technology management dimension to a third-party managed service provider.

Why wrong: Outsourcing does not fix the internal imbalance of improvement focus areas.

Decommission the tooling improvement initiatives and replace them exclusively with process tasks.

Why wrong: Decommissioning all tool enhancements is counterproductive; the portfolio needs rebalancing, not wholesale cancellation.

Transition the Continual Improvement Register from a shared spreadsheet to an automated ITSM tool.

Why wrong: Tooling the register does not address the fundamental strategic imbalance in what types of improvements are being prioritized.

To establish metrics for measuring past operational performance.

Why wrong: Measuring performance relates to 'Where are we now?' and 'Did we get there?'

To identify root causes of recent major incidents.

Why wrong: Root cause analysis is an operational activity, not the high-level vision setting.

To procure external toolsets for workflow automation.

Why wrong: Tool selection happens during the implementation planning phase ('How do we get there?').

Execute the improvement plan and implement the changes.

Why wrong: Execution occurs in step 5 ('How do we get there?').

Define the vision and objectives of the initiative.

Why wrong: Defining the vision is step 1, which precedes establishing the baseline.

Evaluate metrics to determine if the target state was achieved.

Why wrong: Evaluating achievement is step 6 ('Did we get there?').

Only when an audit fails to meet compliance standards.

Why wrong: Baselines are proactive measures for all improvements, not just reactionary audit fixes.

After the improvement changes have been fully implemented and stabilized.

Why wrong: That is done during step 6 ('Did we get there?').

At the exact moment the corporate vision statement is drafted.

Why wrong: Vision setting (Step 1) precedes baseline measurement (Step 2).

Initiate a Major Problem Review with external vendors.

Why wrong: Major Problem Reviews focus strictly on severe incident remediation.

Perform a SWOT analysis on the enterprise organizational structure.

Why wrong: SWOT analysis is used for strategic planning and high-level evaluation, not immediate project post-mortems.

Execute a root cause analysis using the Ishikawa (fishbone) diagram.

Why wrong: Fishbone diagrams diagnose why an incident or failure occurred, not overall project lessons learned.

Implement mandatory quotas requiring each employee to submit three improvement ideas per month.

Why wrong: Forcing quotas without trust leads to low-quality, spam submissions and damages culture further.

Tie employee performance bonuses exclusively to the number of completed IT tickets.

Why wrong: Tying bonuses to ticket volume encourages gaming the metrics rather than fostering genuine continual improvement.

Outsource the collection of improvement ideas to an external third-party consultancy.

Why wrong: Outsourcing distances leadership from employees, worsening internal engagement.

To execute the tactical implementation plan.

Why wrong: Executing the plan is step 5 ('How do we get there?').

To identify new improvement opportunities from scratch.

Why wrong: Identifying opportunities is an ongoing activity across all steps, but step 6 specifically validates completion.

To define the strategic vision for the organization.

Why wrong: Defining the vision is step 1.

Waste of Overproduction

Why wrong: Overproduction means producing more than is needed or producing it too early.

Waste of Transportation

Why wrong: Transportation refers to unnecessary movement of materials or information.

Waste of Defects

Why wrong: Defects refer to errors, rework, or incorrect information requiring correction.

Merge all regional instances into a single database schema using database-level triggers.

Why wrong: Database-level merging is not a supported ServiceNow configuration and violates multi-tenancy best practices.

Export weekly XML dumps from each region and import them into a spreadsheet.

Why wrong: Manual XML exports are inefficient, non-real-time, and prone to error.

Configure individual SLAs for every regional business unit.

Why wrong: SLAs measure time to resolve, not financial ROI rollup across organizational hierarchies.

Total budget allocated to software licensing and number of staff resignations.

Why wrong: These are financial and HR metrics unrelated to continual improvement velocity and value.

Total number of major incidents reported and average speed of hardware replacements.

Why wrong: These measure incident management and asset management performance, not continual improvement practice effectiveness.

Number of open improvement tickets and average time spent on training courses.

Why wrong: Open tickets and training hours do not measure value realization or actual improvement delivery.

To establish the initial vision and mission of the enterprise.

Why wrong: Initial vision setting is step 1.

To perform root cause analysis on unresolved outages.

Why wrong: Root cause analysis is handled by Problem Management.

To archive the Continual Improvement Register and close the practice.

Why wrong: Continual improvement is ongoing, never closed or archived.

Define phase

Why wrong: The Define phase outlines project goals and customer requirements (Voice of the Customer).

Improve phase

Why wrong: The Improve phase focuses on implementing solutions and testing changes.

Control phase

Why wrong: The Control phase ensures that improvements are sustained over time through monitoring and standard operating procedures.

Service Level Agreement (SLA) breach escalation actions.

Why wrong: SLAs handle time thresholds, not financial expenditure routing logic.

Access Control Lists (ACLs) restricting write permissions.

Why wrong: ACLs secure data access and editing rights, not workflow routing.

Data Archiving retention policies.

Why wrong: Archiving moves old records to historical tables, unrelated to active workflow routing.

It applies exclusively to software development and Agile release trains.

Why wrong: Continual improvement applies organization-wide, not just to software development.

It is restricted to infrastructure hardware and network availability improvements.

Why wrong: It covers all four dimensions, including people and processes, not just hardware.

It is limited to major problem remediation and incident reduction.

Why wrong: Problem and incident management are specific practices; continual improvement is an overarching organizational practice.

Opportunity

Why wrong: Opportunities are external positive conditions that could be exploited.

Strength

Why wrong: Strengths are internal positive attributes.

Weakness

Why wrong: Weaknesses are internal negative attributes.