Metrics Tell a Story: Leadership Development Before Correction

Metrics tell a story, but they rarely tell the whole story by themselves.

I do not want leaders to ignore numbers. If a team is missing targets, missing deadlines, losing people, or producing uneven work, the number matters. It tells us something happened. It gives us a place to begin. Without that signal, a leader can drift into opinion, personality judgment, or whatever explanation is easiest to defend.

But the metric is not the whole story. It is usually the evidence that a story exists.

That distinction matters because many development plans begin with the failing number and never move far enough beyond it. The dashboard says performance is down, so the plan becomes more coaching on the behavior connected to the number: follow-up, pressure, reminders, and accountability conversations. Sometimes that is necessary. Standards do not disappear because we want to understand people more deeply.

Still, if the leader only reacts to the visible result, the development plan can become a more polished version of the same pressure that helped create the frustration in the first place.

In Why Effort Is Not Enough, I make this distinction: metrics at that point are not something the person has to focus on first. They are telling us the story of where that person is at a given time. I would not say that because the number is irrelevant. I would say it because the number is often downstream from belief, confidence, trust, skill, identity, instruction, and the way the person understands what the work means.

That is where the leader has to slow down.

Metrics tell a story, but the leader has to read it

When a metric goes in the wrong direction, the common reaction is correction. Find the behavior, name the gap, tell the person what needs to change, and inspect more closely until the result improves.

There are situations where that is exactly right. If the expectation was clear, the person has the skill, the system supports the work, and the gap is simply a choice not to meet the standard, the leader should address it directly.

But leadership gets harder when the metric is telling the truth without explaining itself.

A missed target may point to a skill issue. It may also point to unclear instruction, an employee who no longer believes the work connects to anything meaningful, a person who wants to grow but cannot yet see who they need to become, or a system that has taught people to protect themselves instead of take ownership.

Those are very different problems. They should not all receive the same development plan.

A metric can tell a leader where to look. It cannot tell the leader what they are looking at.

This is why I am cautious when development starts with the metric and works backward too quickly. The leader may improve the number for a while and still leave the person unchanged. That kind of improvement often depends on pressure, attention, or fear of consequence. It can move behavior, but it may not create ownership.

Development changes when we understand the person

The deeper question is not only, "What result is missing?" It is, "What does this person want, and what do they notice about who they are being as they pursue it?"

That language may sound unusual if we are used to development plans built around competencies and performance gaps. Those tools can be useful. I am not arguing against structure. I am arguing against using structure before we understand what is actually happening.

When a person explores what they want, why they want it, and why they believe they do not have it yet, they begin to uncover who they are being. The leader can support that inquiry without deciding the answer for them.

That is the part many leaders miss.

Someone may want more responsibility but believe they are not the kind of person who speaks up in difficult rooms. In that case, the development plan cannot only say, "Contribute more in meetings." That may be the desired behavior, but the person may be fighting an old identity every time the opportunity appears.

Another person may want to become more trusted but has learned to avoid visibility because visibility has felt unsafe in the past. The development plan cannot only say, "Take more ownership." The words may be correct, but they may not reach the belief underneath the behavior.

A future leader may see leadership as control, performance pressure, or political survival. The development plan cannot only assign leadership tasks. The person may need a different understanding of what leadership is before the tasks become developmental.

This is where aspiration-centered development changes the conversation.

Traditional development often starts with the metric that is failing. Aspiration-centered development starts with the person who is trying to become someone. The metric still matters, but it is no longer the source of the development plan.

That sentence is important to me because it protects both sides of the work. We do not abandon the result. We stop pretending the result explains itself.

The metric may be a mirror, not a verdict

Leaders often treat a poor metric as a verdict on effort. The person is not trying hard enough. Maybe the team does not care enough, or the manager is not holding the line strongly enough.

Sometimes effort is part of the issue. But effort is not always the source.

People can work hard in directions that do not connect to who they are trying to become. Teams can spend enormous energy correcting around misalignment rather than addressing it. Leaders can ask for ownership while the system quietly rewards compliance. In those situations, more effort can make people tired without making them more committed.

The metric may be showing the exhaustion, not the root problem.

That is why a leader has to learn to read the number with curiosity before moving into correction. Curiosity is not softness. It is discipline. It keeps the leader from reducing a person to the most visible evidence on the dashboard.

A metric can show that follow-up is weak. Underneath, the person may not believe customers want to hear from them. Low initiative might come from a team that learned initiative gets punished. Inconsistent performance may mean the person can respond under pressure but has not yet become someone who owns the direction without being pushed.

Those stories require different leadership.

SMART can become too small if we use it too early

I respect goal structure. Locke and Latham's work on goal setting shows why specific and difficult goals can matter for performance. Clear goals can focus attention, increase effort, and create a standard for action. That research is useful.

But a goal can be clear and still be disconnected from the person.

That is one reason I adapted the SMART conversation in my Labs: Specific, Measurable, Aligned, Relevant, and Time-bound. Aligned and Relevant connect the goal to the aspiration the person actually wants. Does this task connect to something they actually want? Does it help them become someone they recognize as part of the future they named? Can the person see why the work matters beyond avoiding correction?

If the answer is no, the leader may still get compliance. The person may do the task because it is required. They may even do it well for a while. But compliance is different from owned development.

Self-determination theory is helpful background here because Ryan and Deci describe the importance of autonomy, competence, and relatedness in self-motivation and integration. I am not using that research to claim proof for my framework. I am saying it supports something leaders often observe in practice: people engage differently when the work connects to ownership, capability, and meaningful relationship rather than external pressure alone.

A development plan that begins with aspiration has a better chance of becoming something the person owns. Ownership changes the texture of accountability. The leader is no longer the only force holding the plan together.

The leader still has to protect the standard

None of this removes accountability.

A leader still has to name the gap. The business still has commitments. Customers still need the work. Teams still need reliability. If a person is damaging the team, avoiding responsibility, or refusing to meet reasonable expectations, the leader cannot hide behind curiosity.

Understanding is not the opposite of standards.

The difference is sequence. If the leader starts with judgment, the development conversation narrows. If the leader starts with discovery, the correction can become more accurate.

That is why I think metrics should trigger inquiry before they become the whole development plan. The leader has to ask what the number is revealing. Is this a skill issue? A belief issue? An instruction issue? A trust issue? A capacity issue? An identity issue? Is the person pursuing an aspiration that contains transferable capacities the organization can help develop, even if the aspiration itself does not fit neatly inside the current role?

Those questions do not make leadership easier. They make it more honest.

A surface answer may be faster. It may also be wrong.

Read the story before writing the plan

When a metric moves in the wrong direction, the leader has a choice.

They can treat the number as the whole problem and build the plan around correction. Or they can treat the number as a signal and build the plan around understanding what is producing it.

The first path may create a temporary lift. The second path has a better chance of developing the person.

That is the point I want leaders to sit with. A metric can tell us something true without telling us enough. It can show the gap without naming the person inside the gap. It can reveal that performance is off without explaining whether the issue is effort, belief, clarity, ownership, trust, skill, or identity.

If we want development to become more than pressure with better language, we have to read the story before we write the plan.

That begins with a different kind of leadership question: what does this number show me, and what do I still need to understand?