Understanding change and making its case

Review questions

Integrated summary: Understanding change and making its case

Change management begins with a testable problem, not a tool selected in advance. Calculate a return rate with a defined numerator, denominator and period, then inspect its distribution across teams and tasks. Map changes in behavior, decisions and data, including dependencies and exclusions: an interface edit may be limited while moving approval authority has broader consequences. Compare expected benefits, effort, uncertainty and alternatives; distinguish temporary containment from a permanent remedy. A future state describes proficient use and measurable outcomes, not merely a system launch. Track adoption and results alongside a service-time or quality guardrail, and set a review point with expansion and stop conditions. If the denominator changes or evidence contradicts the assumed cause, revisit the diagnosis before scaling the intervention.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1Eighteen of 90 cases closed for the first time in June were returned. A May report says 12 of 80 cases received were returned. What is the soundest conclusion before claiming that rework rose?
  2. Question 2After a new intake tool launched, returns increased in one team. Seven of ten returned cases lack a request description. Which step can distinguish unclear handoff instructions from a data-transfer defect?
  3. Question 3A fictional service log labels 30 of 80 cases as returned, but 12 are duplicate scans without a new request. What should the diagnosis correct first?
  4. Question 4A team reports slow closure, but half its open cases await an external approval unchanged by the proposed project. Which problem boundary keeps the change decision accurate?
  5. Question 5After a new route launches, 14 of 20 late requests in a report entered before launch. Which analysis avoids blaming the new route for all delay?
  6. Question 6Complaints about “waiting” rise at a walk-in office, yet observation shows a fast queue and delays before attachments are complete. What initial diagnosis fits?
  7. Question 7A central dashboard reports average rework, but three service types have very different review steps. What should precede a common remedy?
  8. Question 8An association proposes a new intake form, while approval authority, eligibility rules and disbursement stay unchanged. What best describes the first initiative's scope?
  9. Question 9In a trial of a new description field, a downstream reviewer relies on that description but never uses the intake screen. How should the plan treat the reviewer?
  10. Question 10The team proposes reordering intake fields without changing eligibility rules or decision authority. How should scope be classified?
  11. Question 11An intake error message changes, but the team must ensure rejected cases follow the same route. Which dependency belongs on the boundary map?
  12. Question 12A project map includes “digitisation” but omits a backlog of paper requests. How should the boundary be repaired?
  13. Question 13The proposal moves approval of defined exceptions from a branch supervisor to a central officer while entry stays the same. What matters most on the map?
  14. Question 14The project pilots in two branches, but duplicate blocking uses a database shared with an excluded third branch. What is a safe boundary?
  15. Question 15Forty requests a month are returned for a missing attachment; each repair takes 18 minutes. A new check adds one minute to each of 400 requests and prevents half the returns. What is the monthly operating-time effect before setup cost?
  16. Question 16A pilot case assumes 70% of returns come from missing descriptions, but only three of ten reviewed cases show that omission. What is the best response before promising a 70% reduction?
  17. Question 17A proposal predicts fewer repeat calls, but no baseline calls-per-request count exists. What first condition makes the business case testable?
  18. Question 18A manual check may avoid 40 hours of monthly rework but consumes 30 new hours, its effect on customer waiting is unknown. What is an honest case?
  19. Question 19Management compares one project reducing case errors with another shortening email response, but the teams report benefits over different periods. What makes comparison defensible?
  20. Question 20A funding request assumes a mandatory field prevents every current error, although some occur after entry. What sensitivity test fits?
  21. Question 21A small pilot improves median time but worsens the slow tail for complex cases. What belongs in the investment decision?
  22. Question 22Of 110 eligible cases, 90 pass through the new form and 14 of those need correction before handoff. What is correct-use rate among all eligible cases?
  23. Question 23Returns fall after a new form, but median closure time rises by one day. Which dashboard reading supports a sound expansion decision?
  24. Question 24A success plan targets training completion only, though the goal is a changed request process. Which measure comes closer to the outcome?
  25. Question 25Digital entry reaches 90%, but one fifth of cases revert to paper for completion. Which pair of measures is needed?
  26. Question 26Returns fall in a pilot service while eligible request volume halves. What dashboard check is essential?
  27. Question 27A dashboard shows a good overall service average, but assisted cases exceed their local limit. How should expansion be gated?
  28. Question 28A plan targets 80% correct use but does not define who counts as “eligible.” How should measurement be repaired?