Skip to main content
Steady at the Top
← All articles

How to recognize good work without sounding formulaic

Recognize good work by naming what the employee did and why it mattered. Choose a setting that respects the person’s preference, and give shared work its proper credit. Recognition sounds formulaic when the language could apply to anyone or when praise conceals another request.

Contribution-and-impact recognition is a working method for acknowledging an observed action and its useful consequence. Its grounding is self-determination theory, summarized by Ryan and Deci in 2000, which identifies autonomy, competence, and relatedness. The method is an applied writing and management practice, not a validated recognition scale.

Recognition names a contribution. Feedback helps someone understand performance and make an adjustment. A reward transfers something of value under an explicit arrangement. These can occur together, but a thank-you note does not settle compensation, promotion, or workload questions.

Apply industrial/organizational psychology, the psychology of work and organizations, to how an acknowledgment reaches its recipient. Separate the observed contribution, its consequence, and the employee’s preferred setting before choosing words of appreciation.

Start with evidence you can defend

Before speaking, identify the action you observed or verified. A leader who says an employee saved a customer relationship should know what happened. If the evidence comes from a manager, confirm enough detail to avoid crediting the wrong person or exaggerating the result.

Specificity does not require intimate knowledge of every task. You can say, “The project record shows you identified the missing dependency before the release review.” That is stronger than implying you watched work you did not see.

Check who contributed. Some work becomes visible through the presenter while other people supply the analysis or resolve the problem. Ask about the handoff before praising one person as the sole source of the result.

Avoid treating every contribution as extraordinary. Ordinary work done carefully deserves acknowledgment. Inflated language makes routine appreciation harder to trust and leaves little room to distinguish a truly unusual contribution when one occurs.

The contribution-and-impact recognition method

1. Describe the observable action

Use a verb and an object. “You documented the exception and brought it to the review before the commitment was made” gives the employee a recognizable event. “You are a superstar” offers a label without useful information.

Keep the description within the employee’s actual responsibility. If someone stepped outside the role to rescue a failure, acknowledge the action while examining why the rescue was needed. Do not make the emergency response the permanent expectation.

Name the relevant standard when helpful. “You checked the customer constraint before approving the change” links recognition to a behavior the company wants to preserve. It should not become a lecture or an invitation to praise you for noticing.

If you cannot identify the action, ask for more information. A generic note sent for speed can be less useful than a short, accurate acknowledgment after you understand what happened. Do not invent detail to create the appearance of attention.

2. Explain the consequence without inflation

Connect the action to a verified effect. Perhaps it prevented an avoidable handoff, gave a colleague the information needed to decide, or made a customer commitment more accurate. Explain the actual consequence rather than reaching for a dramatic claim.

Use bounded language where causation is uncertain. “That helped us identify the risk before approval” is different from “You saved the company.” The first can be supported by the decision record. The second usually asks the employee to accept an exaggeration.

Do not reduce every contribution to revenue. Work can matter because it improves quality, protects a control, enables a colleague, or makes a decision more informed. Choose the consequence relevant to the work rather than a fashionable metric.

When choosing recognition language, use the autonomous-versus-controlled motivation distinction in Deci, Olafsen, and Ryan’s 2017 review to examine whether the acknowledgment informs or pressures the recipient. Use recognition to inform people about a contribution, rather than to pressure them into repeating an unsustainable level of effort.

3. Check the preferred setting

Ask whether the employee prefers a private note, a team acknowledgment, or another appropriate form. Do not assume public praise is universally welcome. A preference can depend on the work, the audience, and the person’s relationship with colleagues.

Make the choice easy to express. “I would like to acknowledge this at the team meeting. Would that suit you, or would you prefer I keep it private?” Then respect the answer. Asking and ignoring the preference is worse than never checking.

Consider confidentiality. A customer problem, sensitive personnel process, or restricted commercial decision may not belong in an all-hands example. You can acknowledge the contribution privately or describe the behavior without revealing protected details, after appropriate review.

For visible CEO acknowledgment, use How to be a visible CEO without turning private life into content. Your presence can change the meaning of a small gesture. Keep the focus on the work and the recipient rather than turning recognition into a story about your leadership style.

4. Give the acknowledgment without attaching a demand

Say the contribution, its effect, and your appreciation. Then stop long enough for the employee to respond. Avoid following the thank-you immediately with another task that turns the moment into a prelude to more work.

If you need to discuss a new assignment, separate the conversation. Let the employee understand its scope, capacity implications, and authority. Past contribution does not establish consent to every future request.

Do not use praise to soften feedback so much that the feedback becomes unclear. You can acknowledge good work and later discuss a gap directly. The employee should not have to decode whether a compliment predicts criticism.

Keep written messages proportionate. A short accurate note can be enough. Elaborate prose may sound less personal if it introduces claims the recipient does not recognize. Precision and attention matter more than ceremonial length.

5. Inspect the pattern across the team

Review whom leadership notices. Are customer-facing achievements visible while maintenance work disappears? Are employees near the executive office recognized more often than colleagues on different shifts? Examine the work and access patterns before assuming the distribution reflects merit.

Use Are your incentives rewarding behavior you want to stop? to inspect incentives for unintended behavior. Recognition can become an informal signal about which actions gain status. If only emergency rescues receive attention, investigate whether prevention and reliable coordination are being overlooked.

Use How to give employees autonomy without losing accountability to connect authority and accountability. Recognize responsible use of delegated decisions, including a well-supported decision to pause. Do not praise independent judgment only when the employee happened to choose what you preferred.

Where sustained extra work appears, check capacity. Compare the exceptional effort being praised with the person’s actual resources and needs through the NIOSH description of job stress. Recognition should accompany an operating correction when the contribution required unreasonable demand.

Scripts that describe different contributions

For early risk identification: “You raised the missing dependency before we committed the delivery date. That gave the team time to revise the plan with the customer. I appreciate the care you took with the evidence.”

For an unglamorous handoff: “Your account notes made the transition usable for the incoming manager. They could see the open decisions and contact the right people without reconstructing the history. Thank you for doing that work carefully.”

For appropriate dissent: “You challenged the forecast using the current customer evidence. We changed the assumption before approving the plan. I appreciate that you made the disagreement specific and stayed with the question until we understood it.”

These are hypothetical scripts. Use them only when the described actions and consequences are true. Replace the details with the actual contribution. A precise sentence copied onto the wrong event becomes another formula.

The private-life composite

A founder drafts recognition messages from a phone during a family meal. Every message begins with the same enthusiastic phrase. Their partner asks what each person did, and the founder can explain only one of the contributions without checking.

This composite illustrates the difference between distributing praise and paying attention. The founder can pause the batch, verify the examples, and write shorter notes tied to real work. A smaller number of accurate acknowledgments is a better starting point than a larger set of invented specifics.

If the pressure you are carrying alongside routine recognition duties includes symptoms that persist or affect daily life, consult a licensed clinician; a better acknowledgment schedule is an operating change. The management adjustment here is to make attention deliberate and to avoid carrying routine acknowledgment into every private moment through a constant queue of messages.

Keep appreciation separate from repair

If an employee says the recognition feels hollow, ask what does not match their experience. They may appreciate the contribution being seen while still objecting to workload, compensation, or unequal opportunity. Do not ask them to choose between gratitude and a legitimate concern.

Respond to the concern through its proper process. A missed promotion requires a clear explanation and review where appropriate. A workload problem requires a capacity decision. Another thank-you note will not resolve either issue.

Place the acknowledgment in the wider management approach described in How CEOs can build motivation that survives hard quarters, while keeping this conversation about the specific contribution. Recognition is one management practice within it. Its narrow purpose is to make a real contribution visible in language the employee can recognize and a setting they can accept.

Before giving the acknowledgment, ask three practical checks in sequence. Can I verify the action? Can I explain the consequence without exaggeration? Have I considered the recipient’s preference and the team’s contribution? If an answer is missing, improve the message before delivering it.

Afterward, keep the work standard consistent. Do not require the recipient to display enthusiasm, repeat the story publicly, or become the company’s example without consent. Acknowledgment is complete when the contribution has been accurately named. The employee does not owe leadership a performance of appreciation in return.

Correct misplaced credit promptly

If the employee identifies another contributor, acknowledge that correction and update any public account. Do not defend the original wording because it came from the CEO. Accurate attribution is part of the recognition. A short follow-up can name the shared work without turning the correction into another ceremony.

Sources

Steady at the Top