How-to: Give Specific Praise That Lands
Generic praise feels nice for three seconds and teaches nothing. “Great job” is polite fog. Praise that lands names what someone did, why it mattered, and what you want them to repeat. It builds a culture where people know which behaviors create value, not which personalities get liked.
Time box: 3–5 minutes to draft and deliver one piece of specific praise (live, Slack, or email). If you need a longer celebration, still open with the specific line so the room knows what “good” looked like.
Use this from the Individual Contributor hub when peer recognition matters, and from the New Manager hub when you are building trust on a new team. Public praise belongs in team rituals; private praise belongs when the win is sensitive or the person prefers quiet recognition.
When to use / when not
Use when:
– You observed a concrete behavior or outcome worth repeating
– Someone took a smart risk, helped a peer, clarified a messy decision, or raised quality
– You want to reinforce a standard before review season
– A quiet contributor did high-leverage work that others missed
Do not use when:
– You are buttering someone up before bad news (they will notice)
– You did not actually see or verify the work
– Praise would expose confidential details (customer, deal, personnel)
– You are praising speed that created hidden debt you will later criticize
Praise is not a substitute for fair pay, clear goals, or addressing harm. It is a precision tool inside a healthy system. For formal recognition programs, follow how HR works.
Prep
Before you speak or type:
- Behavior: what they said or did (observable)
- Context: meeting, doc, ticket, customer moment
- Impact: on customer, teammate, decision quality, risk, or timeline (use real outcomes you know; invent nothing)
- Audience: private, team channel, or all-hands
- Ask to repeat: optional one-line “please keep doing X”
If the win crossed teams, a short note that CCs a partner manager helps how departments work together without stealing credit.
Steps
- Catch it close to the moment (same day if possible). Delay turns specifics into vibes.
- Write the three-part line (2 min): behavior → impact → ask-to-repeat.
- Choose channel. Private for introverts or sensitive wins; public when you want the team to model the behavior.
- Deliver without a sandwich. Do not glue criticism onto praise in the same breath.
- Optional amplify. Forward to their manager (if you are a peer) or mention in the next 1:1 so it shows up in reviews.
- Log lightly. One line in your notes helps performance drafts later without turning praise into surveillance.
Managers: balance who gets praised. If only the loudest demos earn airtime, you teach the wrong game. Directors can use the Director / VP hub lens to praise cross-org glue work, not only heroics.
Script (what to say / send)
Live, private:
“In standup, when you flagged the dependency risk before we committed the date, we avoided a slip. Please keep calling those early. It helped the whole plan.”
Team channel:
Calling out [Name]: on the [project] handoff doc, they added the owner + date + risk section before the review. That cut fifteen minutes of confusion in today’s meeting. That’s the standard for cross-team handoffs.
Peer to peer:
Thanks for rewriting the customer email last night. Leading with their constraint and offering two options made the thread decidable. I’ll mirror that format next time.
Manager to report (email or doc comment):
Specific praise on [deliverable]: the executive summary named the decision, options, and recommendation in half a page. Leadership could decide in the room. Keep that structure for decision memos.
If they deflect (“it was nothing”):
“It wasn’t nothing to the people who needed it. I’m naming it so you know what to keep.”
Public all-hands version (short):
One behavior worth copying: [Name] brought a pre-read with a clear ask. We decided in twenty minutes. That’s how we respect each other’s time.
Output artifact
Praise note (copy/paste block):
- Person / date / context
- Behavior (one sentence)
- Impact (one sentence)
- Ask to repeat (optional)
- Channel used (private / team / leadership)
Keep a personal log if you manage people so review season is not a scramble. Do not publish private praise logs broadly.
Watch-outs
- Personality labels. “You’re a rockstar” is empty. Name the work.
- Only praising crunch. If you only celebrate midnight heroics, you incentivize burnout theater.
- Credit laundering. Do not praise a manager for an IC’s work without naming the IC.
- Public embarrassment. Some people hate spotlights. Ask once about preference, then honor it.
- Praise as manipulation. If every compliment precedes a request, trust dies.
- Ignoring cross-functional partners. Sales, finance, and ops wins often sit outside your standup; learn enough from how sales works and finance for non-finance managers to recognize real contribution.
- Empty company values shout-outs. Tie the behavior to the value with an example, or skip the slogan.