Building a credible case for action
4 min read
Lesson objectives
- Build a credible case for action and justify the decision using case evidence.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A case for change is more than “transformation is necessary” or a list of benefits without costs. It connects a documented problem to a specified intervention, states what may improve, shows the work required to implement it, considers what waiting might cost, and identifies what is still unknown. Even when the direction is attractive, the decision maker needs workable alternatives: a limited improvement, a staged pilot, or a deliberate pause to gather evidence. Useful urgency explains a real opportunity or harm; it does not manufacture fear from a number stripped of context.
Start with the baseline and the causal chain. In the returned-case example, the proposed action is to check the request description before handoff. The expected intermediate effect is fewer incomplete files, followed by fewer returns caused by that omission. If half of all returns have other causes, promising to eliminate all returns is unsound. Record the numerator, denominator, measurement period and number of cases the mechanism could affect. Pair the intended benefit with a burden measure, such as extra minutes per request. This lets a decision maker see the gain and the cost together.
Compare alternatives using the **relevant total effort**, not the purchase price alone. A new tool may require training, transition time, integration work and data handling. A manual step may appear free but consumes staff time and can increase waiting. Inaction can also have a cost, yet it is not automatically the worst choice: when causal evidence is weak, a small experiment may be wiser than a broad launch. Do not present illustrative numbers as a certain forecast. Give a range or two plausible cases and explain how the recommendation would change if its key assumption were false.
Suppose fixing a returned case takes another 15 minutes and 120 cases per month are returned because a description is missing. The present burden is 120×15=1,800 minutes, or 30 hours a month. If a new check adds two minutes to each of 800 monthly cases, it uses 1,600 minutes, or about 26.7 hours. Even if every description-related return disappears, the net labour saving is only about 3.3 hours before training. If the check prevents just half of them, it saves 15 hours and uses 26.7; workload rises. This is not an argument against quality. It is a reason to target higher-risk cases or redesign the field so that every case does not need two extra minutes.
Write a conditional decision rather than an absolute recommendation: “Pilot the check for the case type where omissions are concentrated for two weeks. Expand if omission-related returns fall without breaching an agreed waiting-time guardrail; redesign if effort rises.” Name who approves the pilot and who can stop it. If the change touches customer rights or organizational obligations, the team must check its own applicable policy and authorized decision maker; a general teaching example cannot supply a legal rule. A credible case makes its assumptions and authority visible even to someone who disagrees.
Lesson summary
Build a credible case for action with stated assumptions and verification.