How to Prioritise Improvement Ideas When Everything Feels Urgent

At the end of a review of operations, the whiteboard holds 31 ideas. Sales wants a faster quotation process. Finance wants the bank reconciliation automated. The warehouse wants a second loading bay. The general manager wants a dashboard. Every idea is reasonable, every sponsor says theirs is urgent, and the team that will do the work is the same five people who also run the business every day.

This is the point where many improvement programmes quietly fail. The ideas are usually sound. The organisation tries to start all of them, finishes few and loses faith in the process.

Urgent is not the same as important

Urgency is usually a measure of who is shouting loudest, or which problem caused pain most recently. A delivery that went wrong last week feels urgent. A slow, steady loss of margin through unapproved discounts may be far more important, yet nobody raises it because it never causes a crisis.

Prioritising well means replacing the feeling of urgency with a few questions that can be answered for every idea in the same way. It also means accepting that most ideas will wait, and saying so openly.

Score every idea on the same four questions

Keep the scoring simple enough to use in a meeting. For each idea, give a score from 1 to 5 on four criteria.

The dependency criterion is often missing from scoring methods, and it matters. Cleaning the customer master data may score modestly on impact by itself, but if the CRM (customer relationship management) project, the collections automation and the sales dashboard all depend on it, it should move up the list.

Sort the scored ideas into four groups

Once the ideas are scored, the totals matter less than the pattern. Sort them into groups that call for different handling:

• Quick wins. High impact, low effort, high confidence. Do them now, with a named owner and a date within the next few weeks. Examples include fixing a confusing form, adding a missing field to the ERP (enterprise resource planning) system or setting up an approval delegate.
• Major projects. High impact, high effort. Choose one or two at most, plan them properly and give them protected time.
• Foundations. Moderate impact but high dependency, such as data clean-up, process ownership or decision rights. Schedule them early, because they make other improvements possible.
• Parked. Low impact or low confidence. Record them, explain why they are waiting and review them each quarter. Parking an idea openly is better than leaving it in limbo.

Limit how much is in progress

The most useful rule in any improvement programme is a firm limit on work in progress. A team of five people who also run daily operations can realistically drive perhaps two significant improvements at a time, plus a handful of quick wins. Starting eight projects does not make eight things happen faster. It makes all of them slower, because attention is split and nothing reaches the finish line.

Set the limit explicitly, for example “no more than two major projects and five quick wins open at any time”. A new item starts only when another finishes. This also makes trade-offs visible: when a director asks to add a project, the question becomes which current project should pause, rather than whether people can simply work harder.

An illustrative example: a clinic group

Consider a group of four outpatient clinics after an operational review. The list includes 24 ideas, from a new appointment system to a better process for insurance claim rejections and a staff scheduling tool.

Scoring shows that insurance claim rejections have high impact on cash, moderate effort and high confidence, since the review already identified the main reasons for rejection. That becomes the first major project. Cleaning the patient and insurer master data scores as a foundation, because both the claims work and any future appointment system depend on it. Five small changes to reception checklists become quick wins. The new appointment system, though popular, is parked until the data and claims work are complete, with a review date set three months ahead. Everyone can see why.

Running a monthly prioritisation review

1. Review what finished. Close completed items and note the result against what was expected.
2. Check active work. Is each item on track? If not, decide whether to add help, reduce scope or pause it.
3. Score new ideas. Add them to the list using the same four criteria, in the meeting, with the people who raised them.
4. Fill free slots. If a project finished, choose the next one from the scored list.
5. Revisit parked items quarterly. Circumstances change, and an idea that was low priority may now matter more.

Fewer things, finished properly

When everything feels urgent, the way to prioritise improvement ideas is to score them consistently, sort them into clear groups, limit how much runs at once and review the list every month. It turns a long, stressful list into a sequence the whole organisation can follow. This is the Evaluate stage of the KEMLAT Method in practice: assessing gaps, priorities and waste honestly before committing effort.

Our Operations Transformation service helps leadership teams audit operations, build and score a list of improvement ideas and turn the top priorities into finished work with clear ownership.