How do you recognise someone for taking initiative?

Name what they did and why it mattered, and be explicit that nobody asked them to. The unasked part is the whole point: work that appears on a plan gets credited automatically, and work that does not has no record at all.

Why does initiative go unrecognised?

Because nothing tracks it. There is no ticket, no sprint commitment and no line in a review template. The only mechanism that makes unassigned work visible is somebody choosing to mention it.

Should you recognise initiative that did not work out?

Usually yes, if the judgement was sound. A prototype that answered a question and got abandoned did its job. Recognising only successful initiative teaches people to attempt things that were already safe.

What if the initiative created work for others?

Say both things, in that order, and separately. Thank the intent, then have the coordination conversation another day. Combining them reads as criticism wearing a thank-you.

Is initiative the same as going above and beyond?

Not quite. Going above and beyond is usually more of an assigned thing. Initiative is doing something that was on nobody’s list, which is why it is easier to miss and worth naming differently.

Recognition messages

Recognising Initiative at Work: 10 Message Examples

Work nobody asked for is the easiest kind to overlook, because it never appears on a plan that anyone is tracking.

Nothing tracks it

Assigned work leaves a trail: a ticket, a sprint, some line in a review. Somebody who spends a Friday on a prototype nobody commissioned leaves nothing behind except the prototype.

Which means initiative is credited only when a person deliberately says so. In its absence the reasonable conclusion for the doer is that it did not count, and they stop.

Credit the judgement

The temptation is to thank the effort, and effort is the wrong target. Somebody who spends a week on unassigned work that helped nobody has been busy, not useful.

What deserves the message is picking correctly: the right thing, at a moment when nobody had noticed it needed doing.

10 messages you can send

You rewrote the deploy script because it annoyed you. It annoyed everyone. Thank you for being the one who did something about it.
Peer, unprompted fix
Acknowledges the shared frustration and who acted on it.
Thanks for booking the session with support before we designed anything. That was not on the plan and it changed the plan.
Manager, on process
Credits a decision with a visible consequence.
Ines noticed we had no way of telling whether the feature was being used, built the tracking in an afternoon, and now we know it is not.
Manager, uncomfortable answer
The finding is inconvenient, which makes the credit sincere.
You started the doc nobody wanted to start. Everything since has been an edit to it, which is much easier than a blank page.
Peer, on starting
Names the specific difficulty of going first.
Thank you for asking whether we should build this at all. It was the right question and it was not your job to ask it.
Manager, on scope
Recognises a question that risked being unwelcome.
Tom spent a Friday on a prototype nobody commissioned and it answered a question we had been arguing about for a month.
Peer, on prototyping
Ties unasked-for work to a stuck decision.
You fixed the flaky test instead of retrying it. Six people were retrying it.
Peer, small but real
A tiny act with an obvious multiplier.
Thanks for taking over the customer thread when you saw it going badly. Nobody had asked you to watch it.
Manager, on attention
Credits noticing, which precedes acting.
Nour wrote the onboarding checklist after her own onboarding was rough. Two people have started since and neither of them noticed anything was ever wrong.
Manager, on fixing forward
Frames a bad experience turned into a fix for others.
You told me the plan would not work before we started rather than after. That saved a fortnight and probably an argument.
Manager, on early warning
Prices the timing, which is the whole value.

What makes one land

Credit the judgement, not the hours. Initiative is about picking the right thing to do, and thanking the effort teaches people to do more of anything.
Say it in public. Unassigned work has no ticket, no owner and no record, so a message is the only thing that makes it countable.
Recognise inconvenient findings. Somebody who builds tracking and reports that nobody uses the feature has done you a favour that is easy to resent.
Thank the question as well as the action. “Should we build this at all” is initiative even when the answer is yes.
Watch for the person who always does it. Initiative that is never acknowledged converts into quiet resentment faster than most things at work.

Questions people ask

How do you recognise someone for taking initiative?: Name what they did and why it mattered, and be explicit that nobody asked them to. The unasked part is the whole point: work that appears on a plan gets credited automatically, and work that does not has no record at all.
Why does initiative go unrecognised?: Because nothing tracks it. There is no ticket, no sprint commitment and no line in a review template. The only mechanism that makes unassigned work visible is somebody choosing to mention it.
Should you recognise initiative that did not work out?: Usually yes, if the judgement was sound. A prototype that answered a question and got abandoned did its job. Recognising only successful initiative teaches people to attempt things that were already safe.
What if the initiative created work for others?: Say both things, in that order, and separately. Thank the intent, then have the coordination conversation another day. Combining them reads as criticism wearing a thank-you.
Is initiative the same as going above and beyond?: Not quite. Going above and beyond is usually more of an assigned thing. Initiative is doing something that was on nobody’s list, which is why it is easier to miss and worth naming differently.