Start Every Process Improvement Effort with the Primary Metric

One of the most common mistakes in process improvement projects is also one of the most avoidable.

Teams start with ideas.

They start with complaints.

They start with what they believe is wrong.

What they don’t start with is data.

And more specifically, they don’t start with trended data.

The Primary Metric

At Gemba Academy, we call this the “Primary Metric.” It is not just another section on the project charter; it’s the foundation of the entire effort. If you don’t get this right, everything that follows becomes less clear, less focused, and far less likely to succeed.

The Problem With Starting Anywhere Else

When a project begins without a defined and trended primary metric, a few predictable things happen.

1. The problem starts off unclear. You’ll see vague language such as “too many issues,” “long delays,” or “frequent errors.” These statements may feel accurate, but they’re not actionable.
2. Symptoms start creeping into the problem statement. Teams begin describing what they think is happening instead of what is actually measurable. This leads to assumptions, and assumptions lead to solutions that probably won’t address the real problem.
3. The project loses alignment. Without a single quantifiable metric, stakeholders begin to interpret the problem differently. What one person sees as the issue may not match what another is trying to solve.

All of this stems from the same root cause of project failure: The absence of a clearly defined, trended primary metric.

What a Primary Metric Actually Is

Your primary metric is the core measure of the problem you are trying to improve. It’s not just a label or a category. It’s a quantified, time-based measure of performance and the defect.

The keyword here is trended.

A metric without a trend is just a number. A trend tells a story.

For example, saying “the number of help desk tickets is too high” is not enough. You might even have an actual count, but that doesn’t tell anyone whether the process is stable, increasing, decreasing, or inconsistent.

When you convert that into something like “the weekly average number of help desk tickets is… (insert data),” you now have something meaningful. You can graph it, observe the patterns, establish a baseline, and see the variation.

That is where real process understanding begins.

Build The Primary Metric First

Most teams treat the project charter as the starting point.

That’s backward.

The primary metric chart should come first!

Before writing a single sentence in your problem statement, you should already have:

• A clearly defined data definition (Operational Definition).
• A time-series-based trend (per instance, daily or weekly). Unless impossible, avoid data with monthly or longer cycles.
• Enough data points to establish a solid baseline (typically 15 to 30).

When you build the primary metric first, something important happens.

Clarity emerges.

You can see the average performance, the spikes, the instability, and the possibilities. This leads you to ask better questions.

Without it, you’re just guessing.

With it, you’re observing.

The Primary Metric Drives the Entire Project Charter

Once the primary metric is established, the rest of the project charter becomes much easier to complete and much more precise.

The Business Need

The business need should define the expectation for the primary metric.

If you don’t know the current performance, you can’t set a meaningful expectation. You end up with statements that are either vague or disconnected from reality.

When the primary metric is known, the business need becomes a clear, measurable target.

The Problem Statement

A strong problem statement contains three elements:

1. The process or object.
2. The quantified defect (from the primary metric).
3. The quantified impact.

Without the primary metric, you can’t properly quantify the defect. You’re left with general statements instead of measurable facts.

Without knowing the business need, you can’t identify the gap between the need and the current performance (aka the defect).

When the primary metric is clear, the problem statement becomes clear, simple, and direct. It ties directly to what is actually happening in the process, not what people think is happening.

The Objective Statement

The objective is simply the improvement of the primary metric—it’s the closing of the gap between the business need and the current performance.

An objective statement should be written in a SMART format and should directly reflect the desired future state of that primary metric. Without a defined metric, objectives often drift into activities or solutions. With a defined metric, the objective stays focused on a measurable outcome.

The Benefit

Benefits of a project (specifically, the financial benefits) are calculated based on how you plan to improve the primary metric in the objective statement, which will reduce the impact of the problem. If you can’t quantify the current state, you can’t quantify the improvement. Thus, this makes it nearly impossible to establish credible financial benefits.

Why The Primary Metric Matters More Than You Think

Starting with the primary metric isn’t just about better documentation; it’s about culture and discipline.

It forces process improvement efforts to:

• Focus on facts instead of opinions.
• Separate problems from causes.
• Avoid jumping to solutions.
• Align around a single definition of success.

This is where culture and discipline begin to show up in process improvement. Organizations that consistently start with data develop a different mindset. They become more objective, more analytical, and more patient in understanding the problem before acting.

Organizations that skip this step tend to chase issues, implement quick fixes, and struggle to sustain results.

A Simple Standard to Follow

If you want to improve the quality of your process improvement projects, establish a simple rule:

Do not approve a project without a proper primary metric chart!

Not a description.

Not a statement.

A chart!

If the team can’t show the measurable trend, they don’t yet understand the problem well enough to begin. This, by itself, will eliminate a significant number of project failures before they ever start. It will also elevate the quality of the projects that do move forward.

In fact, it will elevate your entire operation over time.

Process improvement is not about activity. It is about results. And results are measured. If you don’t start with a clear, trended primary metric, you’re not starting with the problem; you’re starting with a story.

Build the primary metric chart first. Everything else will follow.

---