Choose public praise when the contribution is appropriate to share and the recipient is comfortable with the audience. Choose private praise when they prefer discretion or the context is sensitive. You can also combine a personal thank-you with an agreed, factual project credit. Being valued and becoming the center of attention are different experiences.
A team meeting, an email copied to a manager, and a company-wide announcement are all public to different degrees. Before celebrating someone, decide who needs the information and what the employee wants others to know. “Praise in public” is useful advice in some situations, but it should not override individual preferences or confidentiality.
Public vs. private praise: a quick decision table
| Situation | A useful starting point | What to check |
|---|---|---|
| A routine contribution with known preferences | The person’s preferred channel | Keep the description accurate and proportionate |
| A first-time shout-out for a new teammate | Ask privately first | Audience, wording, and whether they want to speak |
| Work involving sensitive customer details | Private thanks or an approved general summary | What information can be shared |
| An achievement that needs career visibility | Agree on a factual credit in the relevant record | Avoid confusing privacy with invisibility |
| A team result with several contributors | Credit the team and name distinct contributions | Verify who actually did the work |
| Praise following a difficult personal period | Private conversation | Let the employee decide what personal context stays private |
1. Ask about the specific audience
“Are you okay with recognition?” is too broad. Someone may welcome a written credit in a project update while disliking an unexpected speech at an all-hands meeting.
Try: “I would like to mention your work on the handoff checklist in Friday’s team update. Is that okay, and is there anyone else I should credit?” For a larger audience, ask again when the context changes. An agreement to a team message does not automatically cover a public social media post.
Gallup advises individualizing recognition, including whether the person prefers public, private, written, or verbal acknowledgment. Use the question as a normal management habit rather than guessing from someone’s personality.
2. Separate acknowledgment from a surprise performance
Being thanked in a meeting does not necessarily mean someone wants to explain the project on the spot. Let them know whether the recognition includes speaking, answering questions, being photographed, or appearing in a recording.
A short written credit can be enough: “Casey documented the escalation path for the new service.” If you want a demonstration too, arrange it separately. Give preparation time and a clear scope.
If a person declines the spotlight, acknowledge the preference without framing it as a lack of confidence. “Thanks for telling me; I will send you a note instead” keeps the focus on their contribution.
3. Remove information that is not yours to share
Praise can accidentally disclose a customer’s issue, a confidential project, an internal dispute, or a personal circumstance. “Despite everything happening at home” may sound supportive to the speaker while revealing information the employee never wanted shared.
Describe approved work details instead. If you cannot safely explain the achievement to the proposed audience, thank the person privately or ask the appropriate owner for an approved summary. Do not turn a recognition message into a workaround for access restrictions.
Even internally, use the smallest relevant audience. A manager may need an accurate contribution record without the entire organization receiving a detailed account of an incident.
4. Check the contribution before naming the hero
A final presenter may be easier to recognize than the people who prepared data, checked dependencies, or maintained the runbook. Ask who contributed before writing the announcement.
For a joint result, say: “Avery prepared the test cases, Morgan checked the access requirements, and Robin coordinated the handoff.” Keep the team outcome distinct from each person’s role. Avoid implying that one person did everything.
If someone corrects the credit, update the same record or audience that received the original message. A private apology does not fix a public attribution error. For a missing-credit problem, see what to do when a coworker takes credit for your work.
5. Avoid making praise a ranking of everyone else
“Finally, someone here knows how to take ownership” praises one colleague by insulting the rest. It also makes a vague claim that is difficult to assess. Name the useful action directly: “You clarified the unresolved approvals before the handoff.”
The same applies to broad labels such as “the only reliable person on this team.” They can create an unwanted expectation that the recipient will accept every emergency. A good shout-out does not assign permanent extra work.
If a process needs to become standard, discuss it as a process decision: “Let’s add that approval check to the shared checklist.” Keep that discussion separate from comparing people’s worth.
6. Make private recognition useful for future reviews
Private praise should not leave a person’s work invisible to the people evaluating it. Ask whether they would like a factual contribution included in a project recap, one-on-one note, or performance discussion.
For example: “Would you prefer a private note, or may I also include your role in the monthly project summary?” The summary can credit the work without retelling the personal conversation.
This is particularly useful for remote colleagues and ongoing maintenance work. Keep records of actual contributions rather than relying on who was most visible in meetings. Our guide to workplace visibility without self-promotion explains how to make the work understandable to others.
7. Let the thank-you stand without a new request
Ending a shout-out with “So you can take the next weekend shift too” changes the meaning of the moment. If you need more help, make a separate request with its own scope and capacity discussion.
When private praise is more appropriate, use a simple message: “I noticed how clearly you documented the remaining questions. It made the handoff easier to review. Thank you.” Use only outcomes you can support, and do not attach a demand for gratitude or a particular reaction.
If you are receiving unwanted public attention, try: “Thank you for recognizing the work. For future acknowledgments, I prefer a written note or a brief project credit rather than being called up to speak.”
Frequently asked questions
Is public praise always better for motivation?
No. Preferences, audience, and context differ. Ask how the person wants the contribution acknowledged instead of assuming that more attention is more rewarding.
Should I ask permission before every thank-you?
An ordinary private thank-you usually does not need advance discussion. Check preferences when expanding the audience, sharing sensitive context, or creating an unexpected speaking or publicity obligation.
What if someone prefers private praise but wants promotion visibility?
Agree on an accurate record for the relevant decision makers. A factual contribution in a review or project recap can support visibility without a surprise ceremony.
How is choosing an audience different from choosing the wording?
The audience decision concerns who sees the recognition and how the employee experiences it. The wording still needs to be truthful and free of hidden obligations. Read praise vs. flattery at work for that separate question.