Serendipity and Learning

As the sessions progressed and we spoke about appreciation, we asked the group - so what exactly are you appreciating someone for? And came the reply: Ownership Responsbility Accountability Problem Solving Planning Prioritizing Focus and so on. If the behaviour is identified correctly, the person might go back with a feeling, "this is what I need to repeat" or "this is my strength" and so on.  And we also heard - Communication, Collaboration, Helping and Timely Delivery. What is the problem with these 4 words? Communication and Collaboration are too vague and dont leave the person with something tangible.  Helping, unless it can be measured and quantified is often a lazy term to be used when appreciating or justifying your time.  And Timely Delivery is almost always an outcome - it is never the cause of appreciation. So, the next time you catch yourself using these vague words, pause and think, exactly what are you appreciating?

 Worked with a bunch of talented technologists over the last few days. And gave them an exercise "Appreciate an intern" The majority of the responses were along the lines of "great job, good job". Some of them were "good job, great job" with a disclaimer. Some found it difficult to appreciate (is there any reason to appreciate?). Fairly common - I have written about this in my book as well - but what is funny is that they are saying this because they have received appreciation in much the same way.  So, we worked from there and asked - what is wrong with this? And they all got it right.  What is the purpose of appreciation - and they got that right as well.  If you know that this sort of vague appreciation is not helping the team, why are you not doing it the right way? And. how are you appreciating your team?