Recently, I wanted to add a personal note to a gift I had obtained for one of our Guest Relations Executives.

The gift was connected to a promise I had made around a specific operational objective.

In the note, however, I wanted to acknowledge something broader: her efforts, her care for the facility, and the concern she showed for the center’s well-being.

The original promise gave the gesture a reason. It did not capture everything I wanted to recognize.

That distinction matters in leadership.

A particular result may attract our attention. The contribution surrounding it can be easier to take for granted.

Reliability can become background noise

Management attention naturally follows problems.

An incomplete task needs intervention. A complaint needs a response. A mistake needs correction. An unexpected absence requires a change of plan.

Dependable work does not always create the same demand for attention.

It simply continues.

Over time, a reliable employee’s contribution can become part of what the manager assumes will happen.

We notice the interruption immediately. We may say very little about the consistency that preceded it.

For the employee, that can mean hearing detailed feedback whenever something goes wrong while receiving little indication of what management values when the work goes well.

Make appreciation as specific as correction

Leaders often know how to explain a shortcoming precisely.

We can identify what happened, what should have happened, and why the difference matters.

Recognition deserves the same clarity.

“Good job” is pleasant, but it leaves the person to guess what earned the acknowledgment.

A more useful approach names three things:

  • The contribution: What did the person actually do?
  • Its value: Why did it matter to the team, customer, or organization?
  • Its consistency: Was this a single result or part of a dependable pattern?

That contribution might be careful coordination, reliable follow-through, or noticing an issue before someone else has to intervene.

These are examples of professional value that can become almost invisible when they are consistently present.

Naming them makes your appreciation understandable.

Acknowledgment and standards belong together

A contribution can be expected as part of someone’s role and still deserve acknowledgment.

Recognizing it does not change the expectation.

It tells the employee that you see the care and judgment involved in meeting it.

The same person may also need corrective feedback in another area. Appreciation and correction can both be accurate.

This requires specificity in both directions.

Recognize the work that deserves recognition. Address the behavior that needs improvement. Neither conversation needs to become a verdict on the person’s entire value.

Look beyond the people who attract attention

Some contributions are easy to see because the employee regularly presents them.

Others happen quietly, within routines that management rarely examines unless something fails.

Leaders need to pay attention across the team.

Otherwise, recognition can follow visibility or personal familiarity more closely than actual contribution.

The question is what the person’s work adds to the organization and how consistently they demonstrate it.

That keeps appreciation connected to evidence.

Make recognition part of how you lead

In my example, a gift created the occasion for a personal note.

The underlying leadership habit can be much simpler: notice a contribution, explain why it matters, and acknowledge the person responsible.

A conversation or a thoughtful message can provide that clarity.

The point is to make sure your team hears what you value with the same precision they hear what you expect.

Reliability should make someone easier to trust, without making their contribution easier to overlook.

When did you last tell a dependable employee exactly what you value about their contribution?