Prioritizing improvement opportunities against strategy
4 min read
Lesson objectives
Rank improvement opportunities by harm, alignment and readiness and revisit the decision when weights change.
Reading tools
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.
The CPHQ leadership outline calls for advising leaders on improvement opportunities, helping establish priorities, and aligning quality and safety activities with strategic goals. These are not three labels for the same presentation. An opportunity describes a changeable gap; prioritization compares opportunities under real constraints; alignment asks whether an expected result serves an explicit organizational aim. The most visible project may have less patient impact, while a high-impact project may lack a team or data needed to begin. A professional decision should not collapse these differences into a manager's intuition or an opaque score.
Begin by defining a baseline, population and time period for each opportunity. ‘Reduce delays’ cannot be compared until we know what was delayed, for whom, how often and with what plausible effect. Then select a small number of distinct criteria, such as potential harm severity, number affected, alignment with a strategic aim, and feasibility with available resources. Keep severity separate from frequency: twenty minor defects do not automatically outrank one rare event with severe consequences. Keep ability to start separate from a project's value: weak readiness may call for a data-gathering phase or a bounded pilot rather than dismissal. Any weights used in this example are an explicit fictional team choice, not an official NAHQ formula.
The comparison should become an accountable proposal to leadership. For every selected project, record the problem definition, baseline, intended outcome, provisional owner, data source and decision requested. In this case, the request might be approval to pilot A at two clinics for four weeks and an assigned lead to negotiate C's transfer process. Do not promise a numerical reduction before seeing pilot performance. Track a balancing effect: moving a staff member from test-result calls to general phone reception could improve call waits while worsening result notification. Review a balancing indicator such as notification time alongside complaints and implementation measures. A score should never silence a clinical objection supported by new evidence; update the facts and reconsider the decision.
Lesson summary
Rank improvement opportunities by harm, alignment and readiness and revisit the decision when weights change.