Motivation

I recently received one of those lovely (and I mean that) emails that tells you you're special. Like most of them, however, it's only goal seems to be propagation. This one goes something like this:

"If you've received this, it is because someone cares for you...
So please, tell the people you love and care for, before it is too late.

If you do not send it, you will have, once again passed up the opportunity to do something nice and beautiful. If you're 'too busy' to take those few minutes..."

Though it purports to praise, the receiver gets the message that they don't do nice things because they are too busy.

Now, what if, instead, it said this:

"So please, tell the people you love and care for, before it is too late.
The more people that you send this to, the better you'll be at reaching out to those you care about. "


How does this relate to quality? Because quality software is not just about the end product, but the motivation to create quality software. Many of these emails touch us because we need to know that people appreciate us. In the case of software development, those with the responsibility of making the schedules and testing the software need to be aware of the impact of 'how' they communicate to those who create the software.

Next time a project manager is determining the schedule for the next release, avoid phrases like 'never hits the date anyway' and 'It is just a minor addition'. (I have a whole list of forbidden words I'll post soon.) Next time a tester needs to report a bug, listen for the developer's response and tailor the next test and report for how the developer receives your communication.

I have seen teams with a reputation of chronically late delivery and bug laden code turned around because of good communication.

Just remember to avoid compliments that have threats and putdowns imbedded in them - undoing the good that they are intended to accomplish. These insidious messages wear us down. Who knows? Maybe they account for the industry statistic of computer professionals changing jobs every 3 years. Doesn't that lead to a brain drain, denying us the quality of someone very knowledgeable staying with the product?