An Improvement Opportunity Assessment is a structured review used before committing significant improvement resources to an idea or problem.

Its purpose is to answer:

Is this opportunity important enough, clear enough, and ready enough to become active improvement work?

Not every suggestion requires a project.

Not every problem is ready for one.

Define the opportunity

Start with the current condition and the gap.

Problem Statement helps clarify:

  • expected condition;
  • actual condition;
  • scope;
  • timing;
  • impact.

An opportunity stated only as a solution, such as “install automation,” should be reframed around the underlying need.

Quantify the potential value

Possible value may include:

  • capacity;
  • quality;
  • lead time;
  • cost;
  • safety;
  • customer experience.

Benefits Realization provides useful thinking for linking expected improvement with measurable operational or financial benefit.

Avoid false precision before the problem is understood.

Check strategic fit

Ask whether the opportunity supports:

  • business priorities;
  • customer needs;
  • operational goals;
  • known constraints.

Improvement Portfolio Management helps balance opportunities across strategic value, risk, and available capacity.

An attractive local project may be lower priority than a smaller project affecting the system constraint.

Check evidence quality

The team should know whether the opportunity is based on:

  • verified data;
  • repeated observation;
  • isolated anecdote;
  • assumption.

Process Baseline can establish the current performance condition before a project target is set.

Weak evidence may mean the next step is measurement, not implementation.

Check scope

An opportunity should be narrow enough to manage.

Ask:

  • What process is included?
  • What is excluded?
  • Which site or product?
  • Who owns the process?

A broad topic such as “improve maintenance” is not yet a workable improvement scope.

Estimate effort and dependencies

Consider:

  • specialist support;
  • capital;
  • system changes;
  • supplier involvement;
  • downtime.

Improvement Capacity Planning helps match improvement workload with available execution capacity.

A valuable idea can still fail if the required support is unavailable.

Decide the appropriate path

Possible decisions include:

  • quick local action;
  • formal project;
  • data collection first;
  • defer;
  • reject.

The assessment should not force every opportunity into the same method.

Common mistakes

Starting with a preferred solution, overstating benefits before evidence exists, accepting broad scopes, ignoring dependencies, selecting work based only on financial value, launching more projects than the organization can support, and keeping low-value ideas active because no one formally closes them are common mistakes.

Practical sequence

  1. define the opportunity.
  2. quantify the current gap.
  3. assess expected value.
  4. check strategic fit.
  5. assess evidence quality.
  6. define scope.
  7. identify dependencies.
  8. estimate required capacity.
  9. choose the appropriate improvement path.
  10. record the decision and rationale.

The practical lesson

An Improvement Opportunity Assessment protects improvement capacity.

The goal is not to approve more projects; it is to choose the work most likely to create meaningful value.

This topic also connects with Improvement Value Hypothesis. Use that method when the improvement requires the related operating or management discipline.