Measure What Builds Problem Solvers

About the Event

"Tell me how you measure me and I'll tell you how I'll behave." — Eliyahu Goldratt

You can walk into any room and pull up a problem-solving metric. Closed corrective actions. Time to resolve. Number of kaizens completed.

But what if those numbers are measuring the wrong thing entirely?

Most leaders are trained to measure outputs — problems solved, tickets closed, fires put out. The faster the turnaround, the better the leader looks. But that instinct has a ceiling. And at some point it starts working against you.

Because here's what the data doesn't capture: whether your team is actually getting better at solving problems, or whether they're just getting better at waiting for you to solve them.

The leaders who build lasting organizations aren't the ones with the best problem-solving track record. They're the ones whose teams can solve problems without them — because they measured for capability, not just completion.

What gets measured grows. So the question is: are you measuring the right thing?

That's what we're exploring in September's Problem Solver's Dojo: Measure What Builds Problem Solvers.

What We'll Explore:

• Why measuring completion is not the same as measuring capability

• The difference between being the problem solver and building problem solvers — and how your metrics are reinforcing one or the other

• What it actually looks like to track whether your team is growing, not just performing

• How to shift from "did we fix it?" to "are we building people who can fix it?"

• What leading indicators of a problem-solving culture actually look like in manufacturing and operations environments

• How to make sustainment — not just resolution — part of how you define success

👉 Come ready to look at your dashboards differently. Leave with a clearer picture of what to measure next.