An organization with established processes for managing incidents, changes, and problems, receives a high volume of calls from users complaining that their issues are not being resolved efficiently…

Question

Options

• AUse value stream mapping to help understand the end-to-end flow of user support
• BEncourage teams to collaborate so they can focus on value for users
• CImprove the integration of tools to ensure there are no gaps between processes
• DReview skills and competencies of user support staff to ensure they have the required capability

• A
  77% (40)
• B
  4% (2)
• C
  12% (6)
• D
  8% (4)

Explanation

Value stream mapping is the correct first step because the organization already has processes in place, yet issues persist - meaning the problem likely lies in how those processes connect and flow, not simply in their existence. Mapping the end-to-end user support journey reveals bottlenecks, handoff gaps, and waste before any corrective action is taken, ensuring changes are evidence-based rather than guesswork.

Why the distractors are wrong:

• B (collaboration) is a healthy practice but too vague to act on without first knowing where collaboration is breaking down in the flow.
• C (tool integration) assumes the problem is technical; without mapping, you may invest in integrations that don't address the real bottleneck.
• D (staff skills review) assumes the problem is human capability, which may not be the issue - the processes themselves could be the culprit.

Memory tip: Think "diagnose before you prescribe." Value stream mapping is the diagnosis tool - it shows you the full patient (the end-to-end flow) before you decide on treatment. The other options are all treatments that jump ahead without a diagnosis.

No community discussion yet for this question.