Define the Goal

Before improving a system you must state its true goal and the few measurements that show whether you are moving toward it. Any action that does not advance the goal is not productivity, however busy it looks.

Why it Matters

Without an explicit goal and the right measures, people optimize proxies, local efficiency, utilization, activity, that feel productive but do not move the system. Naming the goal turns vague "improvement" into a test every decision can be checked against.

Signals

• Teams busy and "efficient" while the system delivers no more.
• Success measured by activity or local output.
• Disagreement about what the system is even for.

Benefits

A clear target and measures that expose waste, align effort, and let you judge whether a change actually helped.

Risks

Choosing a measurable proxy that diverges from the real goal (seeking the wrong goal); many local goals that conflict with the system's.

Tensions

The easy-to-measure goal is often not the true one, and pushing a single global goal can clash with the local goals people are rewarded on.

Examples

Stating the goal as money made (throughput) rather than machines kept busy; defining a team's goal as value delivered to users rather than tickets closed.