The best recognition I ever gave was four words long. No ceremony followed it. That was the point.
One of the people on my team was selected for her first command. I heard the news, found her, and said four words: “Congratulations. That’s awesome news.” Then I went back to what I was doing. No speech. No announcement to the room. No photo. That was the entire recognition moment, and it was exactly the right size.
Most leadership writing about recognition argues for more of it — more ceremony, more visible gestures, more structured programs to make sure good work gets seen. I want to make the opposite argument. The best recognition I have ever given or received was small, immediate, peer-to-peer, and over in ten seconds. The ceremony is usually not for the person being recognized. It is for the person giving it.
What the four words actually did
Notice what those four words did not do. They did not explain why the selection was deserved. They did not recap her accomplishments for an audience. They did not turn the moment into a lesson for anyone else watching. They simply confirmed what she already knew — that the outcome was real, that it was good, and that the person telling her so meant it without performance.
That is the whole function of recognition, when you strip the ceremony away: confirming to someone that their work produced a real outcome, in a moment small enough that the outcome stays the center of attention rather than the leader delivering the news.
Why ceremony gets in the way
Ceremony redirects attention. The moment a recognition becomes an all-hands announcement, an award, or a speech, the audience’s attention splits between the person being recognized and the person doing the recognizing. Whoever built the ceremony gets some of the credit for building it. That is not automatically wrong — there are moments that call for public celebration — but it is a different transaction than recognition, and conflating the two costs something.
I have sat through employee-of-the-month presentations and all-hands shoutouts that were, in structure, more about showcasing the leader’s generosity and the organization’s culture than about the specific person’s specific work. The recipient stands at the front of a room, visibly uncomfortable, while someone else narrates their accomplishment back to them in front of an audience they did not choose. That is a performance of recognition, not recognition.
Peer-register recognition does not have that problem, because there is no audience to perform for. It is one person telling another person, plainly, that something real happened. The absence of ceremony is what keeps the attention where it belongs.
How to apply this
The next time someone on your team earns recognition, resist the instinct to make it bigger than it needs to be. Say the smallest true thing you can say. Then stop talking. Do not follow it with an explanation of why you’re proud, a story about their growth, or a segue into what’s next. The moment does its job precisely because it does not linger.
This is harder than it sounds. Most leaders feel an instinct to fill the silence after good news — to make sure the moment lands, to make sure their own reaction is visible. Resisting that instinct is the actual skill. The four words worked because nothing came after them.
The standard underneath it
How a leader responds to someone else’s success is itself a standard — enforced consistently or tolerated inconsistently, the same as any other daily practice. A leader who makes recognition about themselves, even occasionally, teaches the organization that success is an occasion for someone else’s spotlight. A leader who keeps recognition small and immediate, every time, teaches the organization that success belongs to the person who earned it.
What you tolerate, you teach. What you enforce, you build. That applies to the daily standard of operations. It applies just as directly to the daily standard of how you respond when someone on your team does something worth noticing.
Scott Pleus is an operating executive who has built his career on a single conviction: an organization’s confidence in its own readiness is only as good as the last time someone actually tested it. If nobody told you your numbers were good, would you still believe them? That conviction was forged over three decades of command in the United States Air Force, retiring as a Lieutenant General and the longest-serving Acting Vice Chief of Staff in the role’s 79-year history. His command experience is the civilian equivalent of running large, high-consequence operations at every level of scale — from a single division, to a joint international operation, to the number-two position in a 680,000-person global organization. In every one of those roles, the product was readiness, and there was no such thing as a plausible excuse for being wrong about it. His standard, in his own words: accountable, not responsible. That is the experience most executive backgrounds don’t have, and it is what any organization needs when it wants to know — not hope — that it can perform under pressure. Early in his career, he noticed something worth learning from: a self-assessment that had never once produced a failure. Rather than take that as good news, he treated it as a signal that the test itself needed to evolve. He built a new version of the check — one that measured real readiness instead of rehearsed readiness — and kept refining it, even when the organization pushed back, because he was committed to the standard underneath it, not just the version of it that was easiest to pass. That same instinct shaped how he led. He made a habit of showing up unannounced, not to catch anyone, but to see the organization as it actually ran day to day — and to ask the one question a prepared briefing never answers. That habit paid off when he inherited a struggling unit: he gave its two senior leaders a clear deadline and clear ownership of the turnaround, and in sixty days, the unit had rebuilt the standard for itself. The stakes in his operating environment left no room for a wrong answer — there was no version of a readiness failure that was merely inconvenient. That is precisely why the discipline transfers: an executive who has enforced a verification standard with zero margin for error brings a rigor to operating risk that most executive backgrounds never have to develop. Trust what’s tested. Not what’s told.
