{"id":7328,"date":"2026-08-07T08:35:00","date_gmt":"2026-08-07T08:35:00","guid":{"rendered":"https:\/\/ryantiffin.com\/dont-just-say-great-job-name-what-worked\/"},"modified":"2026-09-09T13:39:50","modified_gmt":"2026-09-09T13:39:50","slug":"dont-just-say-great-job-name-what-worked","status":"publish","type":"post","link":"https:\/\/ryantiffin.com\/es\/dont-just-say-great-job-name-what-worked\/","title":{"rendered":"Don\u2019t Just Say \u201cGreat Job.\u201d Name What Worked."},"content":{"rendered":"

\u201cGreat job\u201d is kind, but it is rarely specific enough to help someone improve.<\/strong> Employee recognition becomes more useful when a leader names the behavior that worked, connects it to the impact, and makes the standard visible enough to repeat.<\/p>\n

That does not make recognition less human. It makes it more credible. Specific feedback tells an employee that the leader was paying attention\u2014not just to the outcome, but to how the employee created it.<\/p>\n

\n

Recognition should be specific enough to repeat.<\/p>\n<\/blockquote>\n

Employee recognition can be operational feedback<\/h2>\n

Imagine an employee has just handled a frustrated guest well. \u201cGreat job with that guest\u201d communicates approval. But it does not explain what the employee should carry into the next interaction.<\/p>\n

A stronger version might sound like this: \u201cYou stayed calm, clarified what they actually needed, and gave them a clear next step. That kept the situation from becoming bigger than it needed to be.\u201d<\/p>\n

Now the employee has usable information: stay calm, uncover the real need, and make the next step clear. Recognition has turned an invisible service standard into observable behavior.<\/p>\n

\"Candid<\/figure>\n

Use the Behavior \u2192 Impact \u2192 Repeat model<\/h2>\n

A simple recognition framework can keep praise from becoming vague:<\/p>\n

    \n
  • Behavior:<\/strong> Name what the person actually did.<\/li>\n
  • Impact:<\/strong> Explain why that behavior mattered to the guest, team, or operation.<\/li>\n
  • Repeat:<\/strong> Make clear that this is a behavior worth carrying forward.<\/li>\n<\/ul>\n