How does your company celebrate success?
How do you celebrate success with your team?
The most common answers to this include going for a meal and drinks, bringing in a combination of cakes, sweets and generally unhealthy food or giving people a paid day off.
These are all very satisfying in the moment, but are very quickly forgotten and it’s not long before everyone is back in the thick of the next project or piece of work with the success of the last one a distant memory. It is almost like saying “Thank you for delivering this – now finish your free drink, eat your free food and get back to work!”.
But imagine if the way you celebrated success was to use company resources to turn team members/ employees’ personal ideas into reality.
For example, what if someone had a great mobile app idea and to celebrate the fact that they had just played a major part in delivering a project that would bring the company £1m benefit, they were given access to a developer for a week to build their app idea.
Or what if someone had always wanted to write a short story and the company gave them access to a Copywriter for a week to help them turn their story into an ebook.
Or maybe someone had been wanting to organise a big event for one of their relatives but didn’t know where to start, so the company gave them access to a project manager or a company Events Co-ordinator for a few days to build a plan with them outlining everything they needed to do to make it a reality.
These all may sound a bit extreme but let’s think about the impact this approach to celebrating success could have.
Improved employee retention, better employee work life balance, much more positivity leading to increased productivity, the company becoming much more attractive to potential employees and graduates and increased desire and incentive to make every project a success are all potential benefits of adopting this approach.
So, what are the downsides? Well the only obvious one is the cost to the company for ‘lending out’ these resources for a short period of time and therefore a perceived reduction in output. However, why not build these costs and timeframes into the project forecast up front meaning the downside would be ‘invisible’ as it would have been factored into the overall benefits case (and would almost certainly be a very small dent in the overall annual company benefits).
Therefore, on face value and by comparing the pros and cons why would a company not take this approach or one along a similar vein? and furthermore, why aren’t they already?
If you’re company does already do something along these lines then let us all know…