LEADERSHIP JUDGMENT CHALLENGE 007

THE PRIORITY
LIST

An AI system ranks 200 customer accounts every Monday, and the top five get leadership time. One of the ten largest sits at fourteenth: a failed implementation, a quiet customer, renewal in ten weeks. The implementation notes are in the system. The ranking weighs them lightly.

What do you do first?

THE SITUATION

The ranking worked. The account still fell below the line.

Every Monday, the company’s AI system ranks its 200 largest customer accounts for executive attention. The top five go on the leadership agenda that week. Its record is strong, and leaders have come to trust it.

The system ranks on revenue, churn probability, recent complaints, response activity and contract timing. It also holds the customer-success notes and every logged implementation issue, but gives them light weight.

This Monday, the Chief Customer Officer notices an account at fourteenth. It is one of the company’s ten largest. Six weeks ago, its implementation went badly. Since then the customer has gone quiet: fewer emails, fewer meetings, no escalation. Renewal is in ten weeks.

A proper review of the ranking logic would take four to six weeks. The fifth-ranked account is a mid-sized renewal, also due this quarter, with churn probability climbing.

The head of customer success says: “Add it.” Someone else replies: “The ranking has been right for years.”

MAKE THE CALL

What do you do first?

Choose before you continue.

A

Keep the ranking as it is.

The system has the relevant data and a strong record. One account falling below the cutoff is not enough reason to override a process that has worked consistently, and the account may still be fine.

B

Add the account to this week’s top five.

Override the ranking today. The renewal window is short, and the account takes the fifth slot, displacing the mid-sized renewal.

C

Review the ranking logic before changing anything.

Don’t patch one case. Examine what the ranking systematically misses, over the next four to six weeks.

D

Escalate the account outside the ranking.

Leave the system and the top five untouched. Assign the account directly to its customer-success owner for immediate intervention.

WATCH THE CHALLENGE

Coming February 11.

The video for this challenge publishes February 11. Check back then — or work through the situation and questions below in the meantime.

THE JUDGMENT PROBLEM

This isn’t about a mistake. It’s about what a ranking was built to see.

Nobody is missing information. The system has the implementation notes. It weighs them lightly, because the ranking rewards visible activity, measurable risk and near-term commercial signals.

What scores highest on those signals and what most deserves leadership attention are two different questions. The ranking has collapsed them into one.

Every ranking draws a line between what receives human attention and what falls below it. That line comes from the criteria, objectives and thresholds built into the system before the leader considers any individual account. Below it, an account may receive no leadership attention without anyone ever deciding, case by case, that it did not matter.

And the account you noticed is the one you happened to know about.

THE ATTENTION PROBLEM

A ranking doesn’t only organize information. It allocates attention.

How many other accounts sit below the line that nobody on the team happens to know?

Some risk looks like silence. Low activity isn’t the same as low risk.

THE JUDGMENT DIFFERENCE

What scores highest is not the same as what most deserves attention.

THE RANKING REWARDS

Visible activity, measurable risk and near-term commercial signals.

JUDGMENT ASKS

What would this ranking score low every time?

The ranking is reasonable. Whether it shows you what matters is a different question.

BETTER QUESTIONS

Before you act, ask:

01

What does this ranking reward, and what kinds of risk would it score low every time?

02

How did this account reach you: through the system, or because someone happened to know its history?

03

If this account is lost at renewal, what will the review say the ranking should have caught, and has leadership decided it accepts that kind of miss?

This isn’t about whether the ranking is wrong. It’s about what it could systematically fail to surface.

SO, WHAT WOULD I DO FIRST?

D first.

D is not the whole solution. It is the first move.

Ten weeks is enough time to act, but not enough time to make this account the test case for a system review. D protects the account now, without displacing another account from a ranking that has generally worked. Then I would examine why the account fell below the line.

None of the options is free. A protects consistency but leaves a top-ten account exposed. B protects the account today but takes a slot from another renewal and makes the ranking’s reach depend on whoever happens to notice. C addresses the structure but the account waits four to six weeks. D hands the intervention to someone without executive weight, creates a side channel, and does nothing about the next account the ranking misses.

THE LEADERSHIP JUDGMENT TAKEAWAY

01

A ranking doesn’t just organize what you see.

02

It shapes what gets your attention, and what falls below it.

03

Better judgment asks what the ranking is least likely to surface.

A ranking doesn’t just organize what you see.
It shapes what gets your attention, and what falls below it.

BRING THE CHALLENGE TO YOUR TEAM

Make judgment visible.

Judgment Challenges can be explored with your team through a private 90-minute Judgment Lab, turning the scenario into a practical conversation about where a ranked list decides what gets attention in your own organization: hiring shortlists, risk flags, fraud alerts, escalation lists and investment priorities.