5 ms·
Enthusiastic(and authentic) recognition. Everyone knows those tasks suck but you can still use it as an opportunity to re-enforce how critical they can be and g
by vvanders 9y ago
Enthusiastic(and authentic) recognition. Everyone knows those tasks suck but you can still use it as an opportunity to re-enforce how critical they can be and give a big kudos for whoever rolled up their sleeves and dived in.
Another nice upside of this approach is it helps re-enforce a culture of doing the right thing because we ship and don't just write code.
- ethbro 9y agoI think group recognition works excellently. Especially in terms of ensuring folks who didn't choose the ugly tasks recognize that they won't have to do them now thanks to John / Jane.
- mercutio2 9y agoMany people, especially developers, specifically hate group recognition. People who like group recognition are the easiest to support (if they’re actually good), but sadly, these folks are the least likely to actually enjoy maintenance work; enjoying group approval correlates with a desire to work on the Big Cool Sexy New, which maintenance work decidedly is not. You have to know your people, and give them support that motivates them. But that takes (gasp!) good managers.
- ethbro 9y agoI'm curious, how do you get from people who enjoy group recognition are the least likely to enjoy maintenance work? My gut is that it goes the other way around. People who desire to work on the Big Cool Sexy New are often less motivated by peers, and more by personal drive, as by definition most of their peers won't know what the hell BCSN even is. Unless the person in question is working in a 100% BCSN shop, in which case there's likely to be fewer maintenance tasks in the first place as the codebase will be fresher.