How do I recognize skill growth without relying on vague praise?
Quick answer
Name one observable change in how the person handled work, connect it to the skill they have been practicing, and describe its effect. For example: “Your latest handoff included the decision, open question, and next step in one place; that shows growth in documenting project context and helped the next person continue.” Praise the work you observed, not an assumed personality trait.
The question, the details, the next step.
I want to recognize someone who has been working on a skill, but “great job” feels too vague. How do I make the praise specific without sounding like I’m evaluating their personality?
Describe an action or change you observed, name the skill it demonstrates, and explain why it mattered. Keep the statement about the work, not a presumed trait such as “you’re naturally organized” or an unverified motive.
Try this builder:
“On [specific task or occasion], you [observable action or change]. That shows growth in [skill]. It helped [specific effect].”
For example, if these details match what you observed: “In the latest project update, you separated confirmed decisions from open questions. That shows growth in concise written communication, and it helped the group see what still needed a decision.” This recognizes a contribution without making a general claim about the person.
How can I show that it’s growth, rather than just describing one good result? I don’t want to pretend I know exactly what they did before.
Use a before-and-now comparison only when you have a real basis for it, such as an earlier draft or a change you noticed across several pieces of work. If you can’t support a comparison, describe the current example and say it demonstrates the skill; don’t label it a change.
If you reviewed both versions, you could say: “Compared with the first draft, this revision groups related points and puts the recommendation first. That shows progress in structuring written updates, and it made the main takeaway easier to find.” If you saw only the revision: “This revision groups related points and puts the recommendation first. That’s a strong example of structuring a written update.”
Keep the comparison narrow. One improved report doesn’t establish that every report has changed, and you don’t need to quantify progress.
What if I know the person has been practicing a particular skill, but I’m not sure how to connect the action to a meaningful effect?
Name the practice goal only if you know it—for example, because the person told you or it was agreed together. Then connect the observed action to a result you can point to. The effect can be modest: a clearer handoff, a question surfaced earlier, or a decision recorded where others could find it. Don’t inflate a small benefit into a claim about the whole project.
Copyable version:
“Since you’ve been practicing [skill], I noticed [specific action in specific piece of work]. That’s a clear example of [skill in use]. It helped [observable effect].”
Hypothetical example: “Since you’ve been practicing meeting facilitation, I noticed that in Tuesday’s planning discussion you summarized the two options before asking the group to choose. That’s a clear example of guiding a discussion toward a decision. It helped the group respond to the same choices.” Use the final sentence only if the effect is genuinely observable; otherwise leave it out.
Can you give me a quick check before I say it? I want the recognition to feel genuine, not like a formula.
Use the builder as a prompt, not a script. Before sharing, ask: What did I see or review? What skill does that action show? What effect can I honestly describe? If the comparison, skill goal, or effect is uncertain, narrow the wording rather than filling the gap with a flattering guess.
A concise version is: “I noticed [action] in [specific work]. That demonstrates [skill]. It helped [observable effect].” You can also make it conversational: “I noticed you [action]—that’s a good example of [skill]. It made [effect] easier.”
Specificity needn’t sound like a formal review. If you want to encourage continued practice, add a separate invitation: “Would you like to keep building on that in the next [task]?” Avoid implying that one success proves mastery.
A practical checklist
Identify the specific task, moment, draft, or contribution you observed.
Describe the action concretely rather than using a general label.
Name the skill; mention a practice goal only if you know it.
Compare with earlier work only when you have a reliable basis.
State an observed effect, or omit it if uncertain.
Remove unsupported claims about personality, intent, or mastery.
A few more useful answers
Should I say “I noticed” if I heard about the work from someone else?
No. Be clear about your basis: for example, “I heard about the handoff from [colleague]” or “I reviewed the update.” Don’t present secondhand information as something you personally observed.
What if I can’t identify a measurable result?
A specific action can be worth recognizing without a measurable outcome. Describe what the person did and how it illustrates the skill, and leave out an impact claim you can’t support.
Can I use this wording in a written performance review?
Yes, as a starting point: include the relevant work example and keep comparisons or conclusions within what you can support. Follow your workplace’s review format where applicable.