Trust Spent on a Recommendation You Cannot Explain

The packet was twelve minutes old. A ranked list, a confidence number, a paragraph that sounded like a person who had compared the files. The leader initialed the top name. In the meeting that followed, someone asked why that name and not the third. She repeated the paragraph. It was fluent. It wasn't hers.

That's not a small embarrassment. It's a trust withdrawal with a timestamp. The people in the room learned that a score can spend their standing. The leader learned that she can be asked why and have no answer that belongs to her. Both lessons compound.

The balance-sheet note is how to date deposits and withdrawals. This is the specific spend: a recommendation you can't explain, signed anyway.

A score isn't a reason

Decision support that ranks people (vendors, candidates, cases, faculty) will always arrive sounding more finished than a human first pass. That's the product. The trap is treating finished language as finished thought.

Explainability as a leadership skill is four sentences a non-technical leader will sign when someone who lives with the outcome asks why. If the only sentences you have are the model's, you're not standing behind a path. You're renting one. Rentals don't survive a journalist, a grievance or a quiet person who notices they were never in the list.

The number on the page shows that the system produced a number. It doesn't show that you understood the tradeoff. Those are different kinds of certainty. SCARF will punish the room that confuses them: status moves to whoever can recite the score, and fairness drains from whoever can't see themselves in it.

The withdrawal is immediate

You don't get to wait for the hire to fail, the vendor to miss, the case to bounce. The spend happens at the signature.

• The ranked person is treated as chosen, not considered.
• The unranked person is treated as absent, not rejected, which is how opportunity hoarding hides inside a tidy list.
• The leader's name is now on a path they can't reconstruct at 9 p.m. when the phone rings.

If you can't name who may refuse the recommendation, you also have an override problem. Signing and pausing are the same muscle. A culture that can't explain a yes won't produce a legitimate no.

This week

Pick one scored recommendation in flight, not a training example, a live one. Close the model output. Write four sentences you would read to the person it ranks, in language you would still sign on Friday. If the sentences won't come, don't sign. Either you need a person who can translate, or the path should stop.

The person remains the one who can be asked why. A recommendation you can't explain has already spent the trust you will need when it's wrong.

The five questions in the Ethical AI Leadership Decision Toolkit are built for this kind of page. Field notes continue in EI Leadership Insights.