TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPassBlogs
Home  >  Detail: The Secret Ingredients of High Morale



A StickyMinds.com Original
Article Picture
The Secret Ingredients of High Morale

By Esther Derby

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: Jessica and Sean have just attended the company spirit meeting, and they’re feeling a little dispirited. What does it really take to build morale? The answer is both simple and difficult. Learn the ingredients of morale as identified by a group of experts--a project team that may be a lot like yours.


Infosys
Jessica and Sean scowled as they headed back to their cubicles after the company spirit meeting. 
 
“I can’t believe they wasted two hours of our time with that award ceremony and that stupid pep talk,” Jessica said. “Talk about de-motivating. Morale is bad enough around here without wasting our time.” 
 
“Yeah,” said Sean. “It was like the Oscars for the never-done-nothing crowd. I can’t believe they gave out those hokey certificates. If they really wanted to build morale, they’d stop changing priorities every two days and let us get some work done.” 
 
“When pigs fly,” answered Jessica. “I’ve got to get back to work—I’ll be here ‘til midnight getting everything ready for the build.” 
 
As Jessica and Sean turned down the hallway, Ted, the manager, peered around the corner to make sure the coast was clear. He hadn’t intended to eavesdrop, but he’d just heard an earful. “Do they really think managers are that clueless?” Ted wondered. “I always thought recognition and team spirit helped morale—that and a big pay raise. But maybe I’ve got it wrong.” 
 
Ted may have been hearing something new, but we can’t be too hard on him. Recognition and rah-rah have been the conventional wisdom for building morale for a long time. Unfortunately, there is no quick fix. Cheerleading is no substitute for the hard work of helping solid morale grow naturally. 
 
If you’re a manager or a team lead and you really want to improve the morale on your team, take heed of this list—it’s inspired by some real experts on what it takes to build morale in software teams. Who were these experts? They were “actual people” on a software team. 
 
Keep Workload Reasonable 
If your team is being asked to “do more with less” (and who isn’t these days), it’s time to set priorities and decide what not to do. You can only do it all if you don’t care what “done” means.  
 
Set a Sustainable Pace 
A forty-hour week will do wonders for morale. Enforced overtime will not. The more overtime people work, the less productive they are. 
 
Avoid Multitasking 
Assigning people to work on several projects at once creates the illusion of progress. In fact, multitasking slows down progress. Most people are motivated by a sense of accomplishment—actually finishing something. Multitasking works against a sense of accomplishment because it takes longer to finish everything. 
 
Articulate a Clear Mission for your Group 
People want to know that they are working on something worthwhile. Even if you’re not in control of the company mission or product mission, you can articulate a mission for your group. Perhaps your group’s mission is to “Provide accurate and timely information to management about the quality of the product,” or “Create inviting and easy-to-navigate documentation that enables our customers to access all the features of Widget Master.” Say it. Document it. Then stick to it. When you’re deciding on goals and how to achieve them, ask yourself and your team “How will this action help us meet the mission of our group?” 
 
Set Clear Goals 
A mission tells the big story—why your group exists. Every group needs goals—specific, time-bound, achievable goals. Your group’s goals may relate to a release, a project, or a service level. People will push towards the same direction when they know what that direction is. Muddy goals make it hard for people to focus their efforts, which hurts morale. 
 
Set Clear Priorities 
Shifting priorities undercuts morale. People don’t like to throw away the results of their hard work. Switching priorities can have the same effect as multitasking—nothing reaches completion. Change priorities often enough, and people will view the newest priority as “flavor of the day.” The reality of business is that external events may dictate changes. Iterative development, with its three-to-six-week sprints, is one of the ways to manage for accomplishment in a shifting environment. If your organization can’t hold to one set of priorities for three weeks, it’s going to be hard to make forward progress in any direction. 
 
Remove Obstacles 
This is one of the most powerful morale building tools in a manager’s toolkit. Find out what’s getting in the way and work to remove the impediment. When people see their managers are making it easier for them to work, morale goes up. Managers can’t always remove every obstacle. Let people know what you’re trying, and be honest if you can’t fix it. 
 
Don’t Over Specify  
Give people the goal, set them in the right direction, and let them decide how to get there. People will come up with a surprising number of creative ways to achieve the goal. Telling people both what to do and how to do it stifles morale, and defeats productivity. There’s only one thing more de-motivating than over specifying the goal and the method: over specifying the method, and not articulating the goal. 
 
Deal with the Un-jellers 
It’s hard enough to build software without someone actively working against the goal. It’s a manager’s job to field the best team possible. If there is a person whose interpersonal skills are making life hell for the rest of the team, deal with it. Sometimes that means moving someone off the team. Never underestimate the impact that an un-jeller will have on the team. 
 
Negotiate Reasonable Deadlines 
We all know that we don’t always get to choose the release date. If you’re stuck with a hard date, prioritize the requirements and negotiate scope. Knowing from the get-go that the schedule is impossible to meet is not very motivating.  
 
If you’re stuck with a hard date and a hard scope, talk to your team. Tell them you want everyone to work as hard as possible (but not overtime) and that you have serious concerns about meeting the goals even if everyone does their best. Ask the team if they have any ideas on how to make the project work. Knowing that you recognize the situation the project is in will help the team remain focused and energized. Working reasonable hours is a better strategy for reaching goals than going on the fabled death march.  
 
Pep talks, contests, and certificates won’t build morale. They can be fun when things are going well, but when your team is in the pits, they contribute to cynicism, which widens a chasm between practitioners and management. There’s no short-term fix or magic formula for boosting morale, but old-fashioned, effective management may just do the trick.


About the Author
Esther Derby helps teams start projects on a solid footing, assess the current state, and capture lessons learned. She also coaches technical people making the transition into management and is one of the founders of the AYE Conference (www.ayeconference.com). You can read more of Esther’s musings on the wonderful world of software at www.estherderby.com and on her weblog at www.estherderby.com/weblog/blogger.html. Her email is derby@estherderby.com.

Back to Top
 

StickyMinds.com Weekly Column From 11/03/03 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Geordie Keitt 11/20/2003

I have a question about "Don't Over-Specify". I get lots of good but naive suggestions from my testers. These suggestions are the beginnings of real improvements in our process, but require some changes to become really useful. One came today, actually, from a tester I want to encourage to contribute more ideas. I felt badly asking her to implement her idea, but not in her original conception (because if she did it wouldn't work). It can be difficult to strike a balance. I tried to emphasize that it was a great idea, and it just needed a little more content to make it really take off and work. She still looked crestfallen.

 
 
Comment:    
by Elizabeth Knight 11/6/2003

From perspective gathered on both sides of the peon/lead line, I'd add that it's important for leads to put their money where their mouth is when it comes to all the principles expressed in the article. It's my observation that there are no shortcuts to respect, and no shortcut ways of expressing it. Furthermore, nothing gets up the nose of the average serious professional more than being fobbed off with lipservice and cheap Cracker Jack prizes or instructed to feel themselves valued when management actions blatantly express the opposite. People resent being treated as if they were stupid, and they don't work well or happily for leaders...Read On

 
 
Comment:    
by Rodger Drabick 11/6/2003

Hi, Esther. Neat article. No new information; I've been around too long, but well-organized and well-phrased. A couple of thoughts: 1) relative to "Avoid Multitasking", one of the big problems I've seen with multi-tasking is the impact of switching from 1 job to another, and especially if it has to be done asynchronously. A person can easily lose half-an-hour in this "switching". And then, of course, you have to switch back. 2) "Set Clear Priorities", of course you'll set your priorities based on a Risk List which you've developed with your team 3) "Remove Obstacles", this should be one of a manager's main jobs, I believe.

 
 
Comment:    
by Neal Gamache 11/5/2003

A point I was suprised to not see in the article was ensuring open avenues to career advancement and career goals. Perhaps this is the "big paycheck" of the traditional wisdom, but I found that morale suffered incredibly at a company I once worked for as entry level employees began to realize that they would never be promoted out of entry level--not because of their skills, but because outsiders were always hired for the higher level jobs. It's not simply a question of salary--people expect their skills and responsibilities to grow as they stay with the company, and when that doesn't happen a feeling of hopelessness and resignation can set...Read On

 
 
Comment:    
by David Lanouette 11/5/2003

As a developer, one of the biggest motivators/demotivaters I've found is the level of quality that is accepted on a project. Almost always, the higher the level of quality that is expected, the higher the morale level. This effect also can be seen at the company wide level. If a company generally produces high quality products, the employees are happy campers. Companies that produce mediocre products have disgruntled and unmotivated employees. Otherwise, I think it is a great article. It is about time somebody start voicing what those hiding in the cubes have always known - motivation is not easy and most managers/companies get it...Read On

 
 
Comment:    
by John Morand 11/5/2003

I thought the article was good except for this statement “I always thought recognition and team spirit helped morale—that and a big pay raise. Unfortunately, pay raises are meager, if they are even given these days, and that is very difficult to counter when people don't feel they are being rewarded for working hard. And I am sick of hearing management say "Well, at least you have a job". Wait until the tide turns again, and see how fast workers run from a company where they were not at least treated reasonably during tough times.

 
 
Comment:    
by Frank Patrick 11/4/2003

One thing that I've observed over the years is that while many think of high morale as a prerequisite for team performance, the reverse -- the ability to perform and to achieve something is the best source of high morale -- is equally valid. Morale is an effect as much, if not more, than it is a cause in an organization. Interesting that most of Esther's points are about setting up an environment that allows one to perform.

 
 
Comment:    
by Matthew Heusser 11/4/2003

I'm not sure what I think of this article. On the one hand, the author might as well have said "Read Rapid Development, Peopleware, and Mythical Man-Month." Then again, this article is probably pointed at people too "busy" to read those books, or who have never heard of them, or who would never admit they have something to learn. Overall, it's got some interesting points, the but the author doesn't have to take the time to develop them. (Each individual point is probably worth an article or two) If you found value in the article, I would suggest reading the books I reference above. (Matt Heusser)

 
 
Comment:    
by Udhay Kumar Ramamurthy 11/3/2003

Hi! Sometimes, the senior personnel does the Appraisal for the people and it happens to be like College/School where few students do their work just because they are scarred of their professors and HODs. And in this case, since Appraisal tells about the Salary, Hike and promotion, the amount of fear(may be strong word here) within the employee increases. I feel the morale decreases there. Whats your advice for both the parties in this case? Thanks. With warm regards, Udhay.

 
 
Comment:    
by Gene Fellner 11/3/2003

One common demoralizing influence is rumors. "We're going to be outsourced." "The company is going to merge with its biggest competitor and the result will be overstaffing in IT." "There will be no bonus this year." "Project XYZ will be cancelled." If you have good rapport with your staff, you hear these rumors too. But since you're a step above them in the hierarchy, you probably know more of the truth. Use that advantage to dispel or clarify rumors. No matter what the truth is, most people are more at ease knowing they have the facts than wondering whether gossip is true. Once in a while an ominous rumor is real but you've been directed to...Read On

 
Back to Top



 
Ads By Google
What's This?
 
 



Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2010 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


ThoughtWorks




STAREAST 


Better Software Conference