Choosing an improvement portfolio under capacity limits
6 min read
Lesson objectives
- Apply choosing an improvement portfolio under capacity limits to a service case with evidence and decision limits.
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.
After mapping the service, assigning decision rights and recording risks, leaders face a problem that a highest-risk list cannot settle on its own: the team can test only two interventions this quarter while four weaknesses deserve attention. Selection is not a color contest in a risk table. A rare but potentially severe problem may require immediate precaution, while a broad redesign needs a longer test and stronger evidence. A quick change may help one service yet remove coordinators from another, moving the problem rather than resolving it. A portfolio is a balanced set of decisions about what to test now, what to contain temporarily, and what to defer with a reason and review date. Do not let one score conceal the tradeoff. Show the committee plausible effect, evidence quality, feasibility, distribution of benefits, side effects and opportunity cost. State the actual constraint, such as team hours, system capacity or a test window, rather than inventing a financial figure.
Apply an eligibility gate before ranking. If an option requires an administrative employee to choose clinical care, it lies outside this program's authority and should be redesigned with qualified clinical leadership before consideration. If an intervention conflicts with an active local policy, seek verification by the responsible body before testing it. For eligible options, describe what is expected to change and how it will be observed. Increasing the number of reminder messages is an activity, whereas reducing referrals with no verifiable destination after reconciliation is a testable operational result. Add a balancing measure that reveals duplicate requests or unacceptable load on receiving staff. To avoid always favoring the easiest project, ask who benefits and who may wait longer. Does the mechanism work on night shift? Does it reach a small site without an analytics team? An organizational average can conceal a meaningful disparity among sites.
Explain A and B as predictions that could prove wrong. For A, if identifier mismatch is a material cause, shared identifiers and daily exception review should reduce requests whose destination cannot be determined. If unresolved requests persist despite successful matching, investigate another cause rather than declaring that the new tool worked. For B, if absence of a shift backup drives delayed handover, naming a substitute and confirming receipt should improve handover during absence shifts. If the added work delays intake on the next shift, the design needs adaptation. These hypotheses are not promises of improved clinical outcomes that have not been measured. Set a review point after a small test and a stop condition if duplicate requests or unaddressed risk signals appear. Each option needs an implementation owner and an effect reviewer. Identifying who decides when a prediction fails prevents a learning test from continuing indefinitely.
A finance committee might say that option C produces a more visible executive display or that training D can be deployed quickly. The reply is not that these ideas have no value. Explain dependencies. The dashboard first needs an agreed event and denominator definition; that small piece of work can proceed while A is tested without committing to the whole build. Training needs a stable description of the revised work after identifiers and backup coverage are repaired. Training the old workflow now could harden a method that will soon change. These dependencies make deferral an active decision rather than neglect. Conversely, new evidence of recurring harm in one department would change priority and might stop a less pressing test. State reopening triggers: documented harm, a rise in unresolved cases, or failure of an existing control. Do not merely say the committee will review later. Name who reviews, when, and with what evidence.
The committee can learn from its choice even if the first test fails. Record rejected alternatives and reasons because institutional memory later tends to treat the chosen project as though it had been the only option. Distinguish immediate containment of a live risk from a longer system-improvement investment: an individual case may need escalation now while the committee designs a repair over weeks. Examine portfolio effects in small groups. The overall figure may be stable while a remote site or one shift waits longer. At the end of the cycle, ask not only how many projects were completed, but which predictions held, which side effects appeared, what remains unknown, and which resources produced useful learning. Those answers make priority setting a revisable leadership decision rather than an opinion voiced at one meeting.
Lesson summary
Apply choosing an improvement portfolio under capacity limits to a service case with evidence and decision limits.