Prioritizing Improvements: Impact vs. Effort

A Simple Two-Axis Framework

This framework is deliberately broader than automation specifically — it works for any process improvement idea on your list: a new form, a reorganized approval chain, a software switch, a changed meeting cadence, or an automation project. If "Choosing What to Automate First" is for sequencing automation candidates specifically, this is for sequencing everything else your team wants to fix, all at once, on one page.

Step 1 — List Every Improvement Idea You're Considering

Don't filter yet. Write down everything: the quick annoyances, the big structural fixes, the "someday" ideas. A messy list of ten is more useful here than a pre-filtered list of three.

Step 2 — Score Each on Impact (1–5)

Ask: if this were fixed, how much would it actually move the needle? Consider time saved, errors reduced, customer or employee experience improved, or risk removed. Score honestly — not every idea deserves a 5.

Step 3 — Score Each on Effort (1–5)

Ask: how much time, money, and organizational disruption would this actually take? Include the real cost of change management (see "Change Management Fundamentals"), not just the technical build time.

Step 4 — Plot on the Grid

``` High Impact | QUICK WINS | MAJOR PROJECTS | (do these first) | (plan deliberately, | | don't rush) -------------+----------------------+--------------------- Low Impact | QUESTION MARKS | AVOID / DEPRIORITIZE | (nice-to-have — | (not worth the | do if there's | disruption right now) | spare capacity) | +----------------------+--------------------- Low Effort High Effort ```

- Quick Wins (high impact, low effort): tackle these immediately. They build momentum and prove the value of continuing this work. - Major Projects (high impact, high effort): worth doing — but plan them deliberately, with a clear owner, a realistic timeline, and real change-management attention. Don't squeeze these in alongside everything else. - Question Marks (low impact, low effort): fine to do when there's spare time, but never at the expense of a Quick Win or a Major Project. - Avoid / Deprioritize (low impact, high effort): be honest about these. They're the ideas that feel important because they're loud or visible, but the math doesn't support doing them now.

Step 5 — Apply the Risk Modifier

Before you finalize your order, ask one more question of anything that landed in Quick Wins: does this touch something regulated, customer-facing-and-irreversible, or a single point of failure (only one person understands it)? If yes, treat it as one tier riskier than its grid position suggests — it may still be worth doing first, but with more care, documentation, and a rollback plan than a typical quick win needs.

Why This Works

The value of plotting ideas on a grid isn't the grid itself — it's that it forces an honest conversation about effort before commitment, instead of discovering six weeks in that a "quick win" was actually a major project in disguise. Revisit the grid every few months; effort and impact both shift as your business changes.

---