Recognise This! – You can never get – or give – too much recognition.

I am pleased to announce that I recently became a first time father, to twin girls! I am exceedingly excited and thankful that both are beautiful and doing extremely well.  While I knew I’d feel an emotional bolt at first seeing them, what I really was not expecting was the wave of emotional bolts that came as a result of the congratulations and well wishes from family, friends, and colleagues.

Indeed, it was a massive wave of well-meaning, genuine, heart felt best wishes.  But, what is especially meaningful to me are the words of wisdom and advice that were provided, too.  These words have been repeating in my mind continuously, as I think through the fuller meaning of each one. Here’s an example of these indispensable gems I shall treasure forever (in no particular order):

And then also the literally hundreds of congratulations, WOW, OMG, ohhhh, best wishes, fantastic, ridiculously cute messages that filled my e-mail, voice mail and text message box.

All this made me think of a question I get often in workshops – “Can you ever get too much recognition?”   I just got loads!   And you know what? I am now more sure than ever that you cannot get too much recognition.

Each and every message of congratulations, encouragement and support has resulted in a warm glow to all of us in our new family.  Ensuring this is that every message is heartfelt, genuine, and thoughtful.  Apply the same to recognition at work, and you can never give too much of it.

And the final words of advice from my consulting team:

A final note: Readers may have noticed a more infrequent pattern to my blog posts as of late. Now you know why! I remain committed, however, to sharing the latest research and news about employee recognition, engagement, performance and motivation through Recognise This!, though the frequency of my posts may remain a bit more inconsistent in the coming weeks.

Processing...
Thank you! Your subscription has been confirmed. You'll hear from us soon.
ErrorHere