When a good decision disappoints someone
When two worthwhile requests compete, fairness may still leave somebody disappointed. What you do next matters.
Two perfectly reasonable requests
Suppose two people in your team ask for development funding. Both have put together a good case. You can afford one course this quarter.
One proposal addresses a skill the team needs for work already committed. The other supports a colleague's longer-term ambition. You fund the immediate need. The second colleague is disappointed, and you feel worse leaving the conversation than you did entering it.
That feeling is worth noticing. It doesn't, by itself, tell you whether the decision was wrong.
A reasonable choice can impose a real cost on someone. If leadership required every fair decision to feel good to everyone affected, a budget meeting would become a séance: plenty of hopeful language, very little contact with reality.
Was the choice actually fair
Before reaching for “You can't please everyone”, examine what you did. Were the criteria clear before the applications arrived? Did both people have the same opportunity to make their case? Was the urgent need foreseeable months ago, when you could have planned for both?
Perhaps you genuinely faced a trade-off. Perhaps you made one through poor planning. Those deserve different conversations.
It also matters what kind of request you're considering. A discretionary course budget is not interchangeable with a legal entitlement or an adjustment someone needs to do their job. Calling everything a hard leadership choice can disguise a failure to understand the obligation.
In the hypothetical course decision, the defensible reason is the work requirement and the agreed criteria. It isn't that the successful applicant argued harder, or that the other person usually takes bad news well.
Say what you chose
A straightforward explanation might be: “I'm funding the course we need for the work starting this quarter. Your proposal is worthwhile, but I can't fund both from this budget. I understand why that's disappointing.”
You can discuss a later opportunity if it is real. Don't invent one to soften the conversation. A vague promise of “next time” gives you a pleasant exit now and hands someone else a second disappointment later.
Explain the decision in your own name if it was yours. “The business has decided” is a curious phrase when the business was you, at a spreadsheet, on Tuesday.
And leave room for the person to disagree. They may understand every word of your explanation and still wish you had chosen differently. Understanding isn't the same as approval. You don't need to extract approval before ending the meeting.
Stay accountable
There are good reasons to revisit a decision. New information, a mistake in the assessment or an overlooked commitment can change the answer. Being consistent doesn't mean defending an error because it already has your name on it.
There are also good reasons to let a sound decision stand. Reopening it whenever the discomfort returns can create an advantage for whoever has the time and confidence to keep pressing.
What you can do is remain available, follow through on anything you promised and check whether the consequence you accepted was the one that actually occurred. If you said you'd reconsider funding at the next review, put the review in the diary.
The colleague doesn't owe you reassurance that you're still a good person. They asked for an opportunity and didn't get it. Let them have that reaction without treating it as disloyalty, or trying to make them comfort you about the choice you made.