Over a million developers have joined DZone.

Acknowledgment as Motivation

Learn more about what makes software developers work harder and better at their jobs, and they will feel good about their jobs, too!

· Agile Zone

Reduce testing time & get feedback faster through automation. Read the Benefits of Parallel Testing, brought to you in partnership with Sauce Labs.

 Recently at Prairie Dev Con I gave a talk on #NoEstimates and part of the discussion centered on the practice of using estimates as motivation. Using estimates as motivation *may* be effective in the short term, but in the long term I believe it is dangerous and more likely to negatively affect motivation. As an alternative, in the talk I briefly reviewed Dan Pink's work on motivation that centers on Autonomy, Mastery, and Purpose. Have a quick look at that video if you haven’t already. Today I watched a Ted talk called 'What Makes Us Feel Good About Our Work?' by Dan Ariely that provides another angle on motivating through acknowledgment.

In the middle of the talk, he describes an experiment they ran to try and understand the role of acknowledgment in making us feel good about our work. The task in the experiment was fairly straightforward. Participants were given a piece of paper filled with random letters and were asked to find the pairs of letters on that page. For example, in "aswwhggjks", you would find the pairs "ww" and "gg". Participants were paid a certain amount to complete the first page, and then for every subsequent page they would complete, they were paid slightly less.

In the first version of the experiment, when participants handed in their work the experimenter reviewed it from top to bottom and acknowledged the effort with a simple "uh huh" before putting the paper on a pile. In the second version of the experiment, the experimenter did not review their work and simply put the paper on a pile. In the third version of the experiment, the completed work was put straight into a shredder without any acknowledgment at all.

The results of the experiment are displayed in the image - people were willing to work for much less in the first version of the experiment than in the second and third versions. In addition, people stopped working at about the same level if their work was being ignored or shredded. As Dan summarized, "ignoring their performance is almost as bad as shredding it." There is good news and bad news here. The bad news is that if you aren't acknowledging the efforts of your team or employees on a regular basis, it is likely having a negative effect on their motivation. The good news is that there are some simple experiments you can try:

  • Add regular checkpoints with your team members to thank them for some specific contribution.
  • In your regular team retrospectives, start by celebrating the great work you have done together.
  • Schedule time in your calendar to give positive feedback to your team on a regular basis.
  • Schedule in regular demos so that your team can show off how they are delivering value to actual customers
  • Pass on good feedback from your customers to the team.
  • Start using KUDO cards to acknowledge good work.
  • Buy a $2 box of brownie mix, add an egg, some vegetable oil, and bring some fresh brownies to your team as a thank you.


Thanks for reading - I appreciate it.

The Agile Zone is brought to you in partnership with Sauce Labs. Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure.

Topics:
estimating and planning ,project management ,performance ,productivity ,agile

Published at DZone with permission of Steve Rogalsky, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}