Recognition that means something, to both of you.
A free, five-minute tool. Bring one person and one thing they achieved, overcame, or created, and it helps you draw out what they actually felt and what steps they took, then hands you three questions to go ask. They hear their own value in their own words. You understand how they work. You both come away with more.
Takes about five minutes. No account needed. You leave with three questions, not a script. Works for a teammate, a friend, or anyone whose win you want to understand.
Using this is a contribution. Tell us how it went and let us share it, and you help us make the tool better, and help the next person believe they can do this too. That is how a more connected world actually gets built, one real conversation at a time.
Most people analyze failure. Few people study success.
A missed deadline gets a post-mortem. A near-miss gets a root-cause. We are trained to take what went wrong apart and learn from it.
A win gets a round of applause, and the story of how it actually happened goes unrecorded. So the next time we need that result, we are guessing.
The strongest teams already know this. The military has run after-action reviews for decades, and the best ones study what went right, not just what went wrong. Most workplaces still only run the post-mortem on failure.
Recognition done well is not a nicer compliment. It is the post-mortem we never run on the things that went right. The more clearly you know how a success happened, the more reliably you can make it happen again.
Instead of
“Great job on the launch.”
You bring back
“When the launch landed with two people out, what was that like for you, and what did it take to keep it on track?”
Recognition you both come away from.
You both come away with more
They hear their own value in their own words. You understand how they actually work. Neither of you has to perform.
They feel genuinely seen
Being understood reaches a place “good job” never does. The specifics show you actually saw the work.
What is worth repeating becomes clear
Naming the steps they took turns a one-off win into something you can both learn from.
Three things worth knowing about any win.
You start with someone in mind and what they did. The tool walks three short steps, building on what you already know, and writes you three questions to bring back to them.
What it was like for them
What they felt, what they noticed, what they are proud of, and what made it matter to them.
What steps they took
The actual moves they made to achieve, overcome, or create what they did.
Who or what improved because of it
What got better, and who felt the difference, near and far.
Humans have always shared how, not just that.
Our ancestors did not just say good hunt. They told the story of how it went, where the blueberries were, what worked and what did not. Sharing how the good thing happened is how we learned to repeat it, and part of how we survived.
Recognition is that same exchange. When you understand how someone pulled something off, they hear their own story back, you learn how they work, and the knowledge stays in the room. That is the appreciation, not a line added on top, but the understanding itself.
Recognition, answered.
How do I recognize an employee so it actually lands?+
Lead with the story, not the praise. Find out what it was actually like for them, what steps it took, and who or what got better because of it, then say that back to them. People trust recognition that shows you understood what they did far more than a general good job. The tool above walks you through it and gives you the questions to ask.
What can I say instead of "good job"?+
Ask before you say. "Good job" is a verdict on the result. The recognition people remember names the actual thing they did: the call they made, the obstacle they got past, who they helped. You find that by getting curious first, then the thing worth saying tends to write itself. The tool builds you three questions that get you there.
How do I debrief a win, not just a post-mortem?+
Run the same curiosity you would run on a failure, pointed at a success. What was the goal, what did it actually take, and what got better because of it. Naming how a good result happened is how you learn to repeat it on purpose, instead of hoping it happens again. That is exactly what this tool walks you through.
Why does my recognition feel flat, or like empty praise?+
Most recognition skips the story and jumps to the verdict. "Great job" is a verdict. It tells the person you noticed the result, not that you understood the work. When you can name how they pulled it off, the same few words carry real weight, because they are earned.
What should I say to recognize a teammate?+
Before you say anything, get curious. Ask what it was like for them, what steps they took, and who or what improved because of it. The thing worth saying tends to write itself once you understand those three. This tool builds those three questions for your specific situation.
How do I recognize someone without it being awkward?+
Awkwardness usually comes from performing a compliment. Asking someone how they did something they are proud of is rarely awkward, it is welcome. Curiosity takes the pressure off both of you and still leaves them feeling seen.
How do I recognize someone on a remote team, or without it looking like favoritism?+
Curiosity travels well. Asking someone how they pulled something off works the same over a call as it does in the hallway, and it scales: when you can name the specific work behind a result, recognition reads as earned rather than picked, because it is tied to what actually happened, not to who you like. The more specific the story, the less it looks like favoritism.
What is validation before celebration?+
It is a Finding Good idea: understand and name what someone actually did before you celebrate it. Validation is showing you grasp the real story. Celebration without it can feel hollow. With it, the celebration lands, and you both learn something worth keeping.
Is there any science behind this?+
Some good, named research lines up with it. Feeling genuinely understood activates the brain's reward and social-connection circuits, which a generic good job does not reach (Morelli and Eisenberger, 2014). Carol Dweck's work found that naming the specific process someone used, rather than a fixed trait, builds more persistence than generic praise. And studying what went right, not only what went wrong, is how militaries and high-reliability teams have learned for years. This tool is built on that: understand the real story, then recognize it.
How do I recognize someone I care about, not just at work?+
The same three things hold for a friend, a partner, or a family member: what it was like for them, what steps they took, and who or what changed because of it. The setting changes, the curiosity does not. Start the tool with that person in mind.
Built on the Finding Good framework.
Finding Good helps teams bring generative communication into the work itself: changing how they train, how they track success, and how they set goals.
It was created by Brian Fretwell, founder of Finding Good, TEDxBoise speaker, and author of Experts Of Our Potential. After years at the meeting point of neuroscience and culture, from juvenile corrections to mining camps to leadership rooms, he built it around one problem he kept seeing everywhere: people cannot see the worth in what they already do. His work helps them draw it out. This tool is one small, free piece of it.