Communicating and leading, one lesson a day

It is the end of a busy week at a community garden. For most of the summer, the west beds have been drying out faster than volunteers can water them. Two new volunteers studied the layout, rebuilt a clogged section of the drip line, and added a simple color marker that shows which valve serves each row. Water use dropped, the seedlings stopped wilting, and the Saturday crew finished early.

The garden coordinator notices all of this. She thanks the volunteers while stacking tools in the shed. Nobody else hears it.

That is kind, but it leaves most of the value on the table. Today's lesson is about praise as a leadership tool: not flattery, not a morale trick, and not a generic “great job.” Praise works when it tells a group which behavior mattered and why.

Gallup has asked workers for years whether they have received recognition or praise for good work in the last seven days. The answer strongly relates to engagement and retention, yet many people say no. The gap does not require a cruel manager. Praise feels optional, and optional things disappear when the week gets crowded. Strong leaders make noticing part of the work.

Useful praise has three parts. Name the specific action. Name the effect. Say it where the relevant group can hear it.

For the garden, it could sound like this: “The new valve markers and the repaired drip line cut Saturday watering by nearly an hour. That means the next crew can spend its time harvesting and turning compost.” The action is clear. The effect is clear. If the message goes in the volunteer newsletter or gets said at the opening huddle, the whole group learns from it.

“Amazing work” does not do the same job. It may feel good for a moment, but it does not tell the volunteers what the coordinator saw. It also gives everyone else nothing to copy. Specific praise is a tiny piece of instruction. It says, this judgment was useful, this action helped the group, and this is worth doing again.

The public part matters because public recognition creates standing. A private thank-you tells someone you appreciated the effort. A public one tells the group that this person's contribution can be trusted. That can influence who gets invited into the next planning conversation and whose idea gets a fair hearing. People cannot credibly announce that about themselves. A leader can give it to them in two honest sentences.

Some leaders resist public praise because they worry it will seem unfair or create competition. That concern is reasonable if praise is vague, rare, or based on favorites. The answer is not silence. The answer is precision. Praise the observable contribution, connect it to the shared goal, and keep looking for good work across the group. You are not ranking people. You are showing what helped.

There are three traps.

The first is praising a trait instead of an action. “You are brilliant” sounds generous, but it gives the person a reputation to defend. “You tested each valve before changing the layout, which kept us from replacing working parts” names a practice they can repeat. Aim at choices and effort that actually affected the result.

The second trap is delay. Recognition loses force as the event recedes. Praise delivered weeks later can feel like an afterthought or a warm-up to a request. Say it while people still remember the work. If you missed an old moment, do not manufacture a ceremony around it. Catch the next useful contribution on time.

The third trap is attaching correction. “The valve map saved us time, but the labels need to look better” is not praise. It is feedback wearing a friendly hat. If a correction matters, give it separately, often in private. Let the recognition stand on its own long enough to be heard.

Public does not mean broadcasting everything to the largest possible audience. Choose the room where the contribution has meaning. The volunteer crew needs to hear about the irrigation fix. The entire town does not. Good recognition is visible to the people who can understand the work and learn from it.

There is also a fairness question when several people contributed. Do not turn a team effort into a story about one hero. Name each distinct contribution you can actually support. Perhaps one volunteer found the blockage while another designed the marker system and the regular crew tested it across two mornings. Specificity makes shared credit easier because you do not have to flatten everyone into the same compliment.

Try this before your week ends. Find one thing someone did in the last seven days that made a shared result measurably better. Write two sentences. In the first, name exactly what the person did. In the second, name what changed because of it. Put the message where the people who work with them will see it. Do not add a request, a correction, or a speech about gratitude.

Then pay attention to what happens afterward. The return on praise is not only that someone feels good. It is that the person understands which part of the work mattered, and other people see a behavior worth repeating. The group gets a clearer picture of what good work looks like.

That is lesson twenty eight. See the useful thing, name its effect, and say it in the room where it can teach.