Leading Indicators Show Leadership Problems Before Lagging Metrics Tell the Story

At 8:03 on a Wednesday morning, a leadership team looked at a revenue report and discovered that the quarter was already in trouble.

The number on the page was accurate. It was also late. By the time revenue confirmed the problem, the causes had been active for weeks: fewer qualified conversations, slower follow-up, rising rework, and a handful of customer issues nobody owned. The team had been busy the entire time. They simply had not been watching the right signals.

That is the difference between leading and lagging metrics. A lagging metric tells you what happened. A leading indicator tells you what is likely to happen next. Leaders who wait for the final number are forced into reaction. Leaders who watch the work beneath the number have a chance to change the outcome while change is still possible.

I use scorecards because they turn that distinction into a weekly leadership habit. The scorecard does not need fifty metrics or an impressive dashboard. It needs a short list of numbers that reveal the health of the business, an owner beside each one, and the discipline to respond when the trend moves in the wrong direction.

A scorecard gives leadership an early warning

Revenue, profit, cash flow, and customer retention matter. They are also lagging measures. They summarize the result of decisions that have already been made and work that has already occurred. A leader cannot rewind a missed quarter by studying the quarter-end report with greater intensity.

Leading indicators sit closer to the behavior that creates the result. Sales teams may watch qualified opportunities, proposal-to-close rate, and days to follow up. An operations team may watch on-time delivery, turnaround time, rework, and open customer issues. A people leader may watch time to fill critical seats, training completion, or regrettable turnover risk.

The right measure depends on the promise your company makes. If you promise fast service, measure the activity that protects speed. If you promise reliable outcomes, measure the quality checks that prevent failure. If you promise a steady flow of new business, measure the conversations and proposals that create that flow.

A scorecard becomes useful when it can answer three questions before the monthly report arrives: What is changing? Who owns the number? What action will we take if it misses? If the team cannot answer those questions, the number may be interesting, but it is not yet an operating tool.

I have watched leaders add metrics whenever a problem appears. That approach creates noise, not control. Start with the handful of behaviors that have the strongest relationship to the result you care about. Measure those consistently before adding anything else.

Leading indicators reveal the work behind the result

A number by itself cannot lead anyone. The team needs to understand the behavior behind it. If sales is below target, “sell more” is not a leading indicator. Qualified first meetings held this week may be. If margin is falling, “protect profitability” is too broad. Pricing exceptions, hours of rework, or project scope changes may show where the margin is being spent.

This is where the Data Component connects to the other parts of EOS. Vision tells you which outcomes matter. People assigns the work to the right owner. Process makes the behavior repeatable. Issues and IDS help the team solve the constraint when the number slips. Traction gives everyone a weekly cadence for following through.

The connections matter because a scorecard cannot compensate for unclear leadership. A team may miss a target because the measure is wrong, the owner lacks authority, the process is broken, or the priority keeps changing. The scorecard surfaces the signal. Leadership still has to diagnose the system.

Take customer retention as an example. A quarterly retention percentage tells you what happened after customers made their decision. Weekly measures such as unresolved escalations, response time, adoption milestones, or renewal conversations give the team a chance to intervene. The leading indicators do not guarantee retention. They make the work that supports retention visible.

The same principle applies at home. If I say my family is a priority but never measure the commitments that protect connection, the statement remains abstract. A weekly date, a device-free dinner, or a scheduled conversation can function as a personal leading indicator. Numbers do not replace love. They help expose whether my calendar is cooperating with what I say I value.

A small set of owned numbers creates accountability

A healthy scorecard has an owner for every number. “The leadership team” is not an owner. A department is not an owner. One person needs to know the definition, the target, the source, and the next response when the number is off.

Ownership is not blame. It is clarity. When one person owns the scorecard number, that person can ask for resources, identify obstacles, and raise an issue before the result becomes a crisis. Without ownership, everyone can care about the number while nobody is responsible for changing it.

I also want the definition written down. What counts as a qualified opportunity? When does the clock start for response time? Which customer issues are included? What is the source of truth? Two people can review the same label and report different numbers if the definition lives only in conversation.

The target needs equal precision. A goal of “improve follow-up” creates debate. A goal of “respond to every qualified inquiry within one business day” gives the owner a standard to manage. The target may need to change as the business learns, but the definition should not change simply to make a miss disappear.

The Accountability Chart helps here. It clarifies who is accountable for a function and prevents the founder from remaining the invisible owner of every metric. If a number keeps returning to the owner for rescue, that may be a People or Process issue rather than a Data issue.

Put the scorecard where the relevant leaders can see it. Review it at the same time each week. Use one source of truth. If the number is red, do not write an explanation and move on. Put the underlying issue on the Issues List and solve the cause.

Weekly review turns data into decisions

A weekly scorecard review should be short and unemotional. The team looks at the number, compares it with the target, and decides whether the result is on track. The review is not a courtroom. It is an early-warning system.

The temptation is to debate every fluctuation. One week may contain a holiday, a large renewal, or an unusual customer event. Context matters, but context cannot become a permanent exemption. Ask whether the miss is noise, a one-time event, or evidence of a trend. Then decide what deserves attention.

A simple sequence keeps the conversation useful:

1. State the number. Use the agreed definition and source.
2. Name the trend. Compare the current result with the target and recent weeks.
3. Identify the owner. Let the accountable person explain the relevant facts.
4. Choose the next action. If the action requires deeper discussion, move the issue to IDS.
5. Record the commitment. Give the action an owner and a date.

That sequence prevents the meeting from turning into a report-reading exercise. The goal is not to admire the dashboard. The goal is to make a decision while the decision still matters.

I pay attention to the language leaders use when a number misses. “We were close” may be accurate, but it does not identify the cause. “The team needs to try harder” is not a diagnosis. Ask what changed, which step failed, what the owner can control, and what support is required. Precision creates a path forward.

The review also teaches culture. When leaders respond to bad news with curiosity and directness, employees bring problems earlier. When leaders punish the number, people protect themselves until the problem becomes expensive. The response to the scorecard becomes part of the scorecard.

Scorecards improve when leaders respect the truth

A scorecard should make reality easier to face, not easier to decorate. Leaders break the system when they pick numbers that make the company look healthy, change definitions after a miss, or add metrics nobody has time to review. A beautiful dashboard can still hide a weak business.

I recommend a quarterly scorecard audit. Ask whether each number still connects to a meaningful outcome, whether the owner has the authority to influence it, and whether the team takes action when it misses. Remove numbers that no longer help. Clarify numbers that create arguments. Add a measure only when the business has a specific blind spot.

Leading indicators also require humility. A measure can be directionally useful without being perfect. If the number does not predict the result as expected, learn from that evidence. Change the measure because the business understands more, not because the old measure became inconvenient.

The founder who waits for revenue to confirm a problem will always feel behind. The leader who watches the behaviors beneath revenue can ask better questions earlier. That shift changes the weekly conversation from “Why did this happen?” to “What are we seeing, and what will we do while we can still influence it?”

Your scorecard should tell the truth about your priorities, your processes, and your leadership. If it does, you will find problems sooner, give capable people clearer ownership, and spend less time explaining surprises that the business had already announced.

Action Items From Today

1. List three lagging results. Write down the three numbers you care about most: revenue, margin, retention, cash, or another outcome. Under each one, list two weekly behaviors that create it.

1. Choose one leading indicator to test. Pick the behavior with the clearest connection to a result. Define exactly what counts, set a weekly target, and assign one owner for the next 30 days.

1. Create a scorecard definition sheet. For every number, record the source, formula, target, reporting day, and accountable owner. Ask someone else to read it and explain the number back to you.

1. Move one recurring explanation to IDS. When a metric misses this week, identify the issue beneath the number instead of accepting a status update. Put the issue on the list, solve it, and document the owner and date.

1. Audit your calendar against your scorecard. Look at the weekly behaviors you say matter. Find one block of time, meeting, or responsibility that supports them and one that competes with them. Make one calendar change today.

1. Run a quarterly metric cleanup. Remove one number that does not change a decision. Clarify one number that creates debate. Add nothing until the team can explain why the new measure belongs.

Five Bridges Challenges

Internal — Tell the truth about one missed number. Choose a metric that has been off for at least two weeks. Write the explanation you usually give, then write the behavior or decision underneath it that you have avoided naming. Take that action before the next weekly review.

Relationships — Give ownership without abandoning support. Ask the person accountable for one scorecard number what obstacle they cannot remove alone. Listen, provide the needed resource or decision, and keep the ownership with them. Follow up on the agreed date.

Environment — Make the right signals visible. Put your scorecard in the place where the relevant leaders already work. Review it at a consistent weekly time, with the same definitions and agenda. Remove one competing report that creates confusion.

Data serves leadership when it tells the truth early enough for people to respond. Choose the signal. Name the owner. Make the decision before the lagging number forces it for you.

Inspire & Impact,

Josh