Slashdot Mirror
Improving Company Morale?
Undaar asks: "I work as a developer for a web development company. We were pretty hard hit (as were many companies that do what we do) by the "economic down-turn". The company went from over 500 people to under 200 in under two years. It's more stable now, but people are consistently laid-off. Consequently people feel like they always have to look over their shoulder to avoid getting fired. Most lunches are spent complaining about lack of enjoyment/challenge from the job and the fact that upper-management seems not to understand what we do. Employers: what have you done to improve employee morale in your company? As an employee, what can I do to improve the morale in the people I work with? How can I make my work environment more enjoyable? What kind of constructive suggestions can I take to management so that they can help improve the situation?"
People that are happy at work tend to be better workers, so letting them use the internet and phone for some personal business during work can be a "good thing." That's not to say they should be allowed to surf for porn all day, but looking a few websites outside of business during 9-5 can help.
Also, be flexible with work hours. Not everyone needs to work the same 9-5. Let departments figure out their own policy and be flexible with workers.
Whores. Lots and lots of whores.
And don't be stingy with the cocaine, either.
God invented whiskey so the Irish would not rule the world.
It's gonna be like this, in our job market at least, for a while. Hopefully not too long...!
"Firings will continue until morale improves"
;)
- The Management
Sorry, couldn't resist
-- Gxis! Ed.
Two years ago I wrote this: Management Techniques of the Bottom 95% of U.S. Corporations.
:)
Just take all the advice and reverse it.
I work for a software dev company down
here in O.C. It's the same way here.
The way I relieve my stress is applying
for better jobs and talking more sh!t
about management and their crappy decisions
that landed up the company in this situation.
what have you done to improve employee morale in your company? As an employee, what can I do to improve the morale in the people I work with? How can I make my work environment more enjoyable?
I left and went to another company with people that are happy. Much happier when I recognized that I couldn't steer a ship from the White Star Line with a paddle. Just not possible.
If the company intends to screw everyone after finishing a couple pieces to make a liquidation plausible, then it's pretty cold to try to improve morale if you know something horrible's about to go down.
#1 *ALWAYS LOOK FOR A BETTER JOB*.
That is, until you find a job where you don't feel you have to look over your shoulder and wonder why management doesn't get it. When management doesn't get it, there's usually no way to fix it. It becomes entrenched in the fabric of the company.
There is only one way for such a company to change--promote from within. This brings up the people who already understand the business PLUS understand the real-world problems faced by the little employees. But such companies rarely do this. They usually hire outside people who have no clue as to what goes on day-to-day. And they keep crapping on their own employees.
I really recommend looking for another job. If jobs in your area are scarce, then think about moving. Being flexible always provides better opportunities. I know the job market is tough right now, and I would not like to be looking for a job. But I've been in that situation many times. And there is not much hope for this type of a company. Unless they promote from within and start investing in their current employees, rather than try to find the next replacement manager who is going to solve all problems, there really is no hope.
Also, all employers should have incentive programs that are based on performance. If your employer does not offer such incentives--even something as little as free movie tickets for the top-performing departments based on measurable results (like lines of checked code, or # of support issues resolved and verified)--then it is another sign of problems with management.
---gralem
No, seriously. That really helps at my company. Granted, it's only a small company of around 30 people, but every last Friday of the month (and occasionally others) they bring us beer and sometimes margaritas. Everyone hangs out in the kitchen and lets off some steam and it really does help. There's usually leftovers too, so my friend and I sneak back there about 15 minutes before quitting time on other days and have our own little party. Several times the owners have walked past on the way to the bathroom and occasionally they join us.
I read an article about 10 years ago which was about some guy in Brasil, I think it was, whose rubber company was about to go down the toilet financially. So he went to his workforce and said "Here's the situation - we're up shit creek financially, either I make half of you redundant, or we take half pay, until the situation improves - you decide" and put it to the vote. The workforce apparently decided on the half pay option, but productivity soon improved and they could afford to pay their old salary. The guy went on to experiment with introducing worker democracy on a wide scale - salaries, job descriptions etc. and apparently the company became very successful. I've always thought that sounded like an interesting idea, has anyone else heard of this?
I reserve the right to be wrong.
You can't compensate for customers that don't buy anymore. But you can give the company some kind of purpose - so that people don't feel lost anymore.
A manager could redefine the company so that people see a future for it. It could specialize. People could get trained so that a department becomes better and better. Such a specialization could even help when the layoff go on, because it will improve the chances for a new job.
Even a low level employee could help building such a view. Try to find collegues gor exchanging ideas and build your own "center of excellence". With a sense of purpose and collaboration even mediocre employees can achieve good results - provided the motivation is there.
Treat your people like professionals, not children. Tell them what you need them to do by when (set reasonable expectations, not impossibilities), tell them what their assets and resources are, and then leave them the hell alone to work. Don't hold enless status meetings, don't hassle them about what hours they're working, etc. If someone's struggling or not doing their work, you'll have to deal with that, but don't treat that as the default situation.
My last "bad" company was constantly under deadline pressure. My development VP responded to this my having daily status meetings, wasting an hour a day restating what was happening and getting status info that he could have gotten automatically if he'd just learned to use the damned change tracking system. They'd also give you shit if you tried to go home before 9 PM (even if your work was done; you should be "testing or something"). What did I learn there? Treat people like irresponsible children and that's how they'll act.
So, basically, don't overmanage and don't be a dick. Treat your people with respect that you'll get it in return.
There's one more thing I'd suggest, but in my experience this is either something you're good at or something you're not: I'm a firm believer in team building, but in an informal way -- when you go to grab lunch, ask your people to come with you. If you're going to grab a beer after work, invite your people along. In my experience, this works great and has a lot better effect than going to Dave & Busters once a quarter or something.
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
Our company's engineering department runs an annual "coding contest" with a nice prize or two. Last time, teams of two had two days to build the fastest-running solution to a series of problems.
It sounds kind of gimmicky, but there's apparently nothing like a little competition and a prize to get the software engineers' blood pumping. It was really all the discussion about the problems before and after that was so great... it did a lot to get different groups of people talking like they never had before.
It worked brilliantly as a team-building exercise for engineers. Heh, and maybe it helped the management spot the engineers crazy enough to spend the time on the contest, and win.
Having problems with negative talk during lunches?
Get rid of the lunch breaks! If your local labor laws won't alow that, then just make sure each employee has a different lunch time. You may have to vary start times to fit them all in, but that is why the day has 24 hours.
People complaining around the water cooler?
Remove the water cooler! If the local health laws require a source of water, then intall a money collection device. People will think twice about gathering around for a BS sessions if it costs them $.25 a swallow.
Negatiove E-mails making the rounds on your corporate network?
Are their computers REALLY needed?
Isn't web development really more of an artistic thing? I think only one person would really need to have a computer, the rest can just draw there ideas on paper with crayons and submit them to the guy with the computer for entry. And those silly PHP or Perl monkeys spend WAY too much time changing code, tweaking , degugging and stuff. I think most bugs are there because they are not careful or they are poor typists. You could hire a touch typists from you local high school to enter all their code for the day in the evening. Tha way they would be sure to be accurate the first time. Your empyees will be so busy they won't have time to have morale.
You are correct in your assumption that lay offs cause bad morale. NEVER LAY OFF EMPLOYS! Alway make thier job so horrible, so degrading, so painful that they just quit. It will save you a bundle on unemployment fees and severence packages. If you planned ahead you are allready located in an area like Utah, that has a horribly depressed tech sector so a few employees will stay because they know that the only other oppurtunity is flippiung burgers at McD's.
~Z
Or, if you must lay off, act like you don't want to do it.
I've been through or in six rounds of layoffs at four different companies since I was an intern in '98. The very best handling I've seen was when I was with SGI (the company formerly known as Cray at the time) as an intern.
First, you could tell that the boss genuinely hated, hated laying off her people and felt like she'd failed them somehow. Second, when the layoffs actually happened, she held a meeting with the survivors to tell us about it so we didn't hear it through the grape vine. Finally, the department took the whole afternoon off. We had the option to go home, but instead we grabbed some beer and a couple of pizzas and went to a local park, played frisbee and hung out (the people who'd gotten laid off were invited too, which I thought was classy).
At my last company, they laid off like theives in the night. They'd call people in out of the blue, then send out an email apparently designed to scare us all into working harder and longer. One time, we laid off a dozen people and the CEO's wife (who was executive something or other) went out and bought a new Lexus the same day. It's amazing nobody took an AK-47 to that shithole -- they definately had it coming.
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
First, I agree with you totally. However, beoynd the web development/+5 years java experience/visual basic etc. etc. market, there exists a seedy underbelly to the IT world. That is the land of Legacy Systems.
There exist systems so large and arcane, that it takes a developer the better part of a calendar year just to understand some basics of how the system works (and I've seen others struggle for longer). There is ADA. There may be FORTRAN. And there is a whole lot of assembler.
These are systems that have their own operating systems written on top of the operating system. These have components that average 100,000 lines of code each- with another 100,000 lines of code for the test harness. Now multiply that by 12 support components. And we haven't even gotten to the actual APPLICATIONS that run on top!
For projects like these, management does have to watch their back. They don't have lots of money to keep useless developers on, but once a new project ramps up they say 'oh, we need developers who have a lot of experience with our system' hahaha! Hire back those guys you fired!
It is companies like these (think: big ol' gov't contracts) that have to play this dancing game of shelling out some money for pizza every now and then to keep people happy because if they let go of everyone now (or piss them off enough so they leave), they won't be able to staff up in time when the new projects come, and they won't be able to complete the new projects (because they are aggressively scheduled) and they never make a dime on new projects again.
In the future, I would want to not be isolated from my friends in the Space Station.
And don't take away the casual dress policy (if you have one). Nobody wants to have to wear a damn tie just to sit behind a desk all day. It makes no sense.
I was in a healthcare-related tech company that went under and in the last couple of months, you could see it coming. The bosses had no clue what they were doing and wanted all of us smaller people to come up with AND execute the big ideas.
Maybe the business should offer some info on how to make a great looking resume.
...All I can say is that my life is pretty strange...
My boss allows me to work from home on Mondays and Fridays. I avoid a long, stressful commute to work, and I save 40% on gasoline. Overall my productivity has increased, and I feel better.
This is soooo true. I have flex hours, I can work 6am-2pm, 2pm-10pm, or 9-5. I can work at home, or my office, thanks to things like a VPN and Avaya IP Softphone.
When your work load starts to be equal to that of 2 or 3 (or more!) head count, and you know that if you push yourself that you can do it... there are a few things that happen: 1) you realize that doing this work will save your job for the months to come so you do it, and 2) you realize that your boss doesn't really care if you sit in an office or the recliner in your home... as long as the work gets done the boss will be as happy as pig in shit.
--------
Free your mind.
Most lunches are spent complaining about lack of enjoyment/challenge from the job and the fact that upper-management seems not to understand what we do.
Welcome to every company everywhere.
It costs approximately $10-15k (before you spend dime one in salary) to hire your average full-time employee in America. (This is an average, not a locked-in-cement dollar amount... It includes advertising, agency efforts, the manager's time, the HR manager's time, how much time it takes to sift through 2,000 resumes for a $22k per year helpdesk job, any training they may need to provide to get the new guy up to speed, drug test, background check, reference check, etc...)
Given this fact, in the long run, it costs MORE to have high turnover in a company than you could ever spend on treating your staff like human beings... I'm not talking about pool tables and six-figure salaries, either. I'm referring to simple things like flex-time so people can actually see their kids and have interests in their lives besides work.
It seems to me that any company operating under this "Who gives a shit about you?" theory should be avoided... Sadly, in this employment market, the talent (that's us) doesn't have the option of voting "nay" to shitty employers by walking off to other jobs.
I am quite fortunate that my new employer is a private (profitable) corporation that doesn't have to whack $1,000,000 out of the budget every five minutes to meet short-term proft forecasts and prevent stock price fluctuations. My former employer made $36 billion in PROFIT the year they laid us off. Sorry, but if you have to fire 5,000 people one quarter, then need to have a "massive hiring drive" the next, that is short-sigthed mismanagement by drones in suits who put their 401k balances ahead of the company's long-term stability and reputation.
It is easy to say "We can cut 30% out of tech support and still field the same number of calls" but "# of calls" is not the same figure as "# of calls handled satisfactorily." As the quality drops, long-term sales prospects of the company's newer products slowly evaporate as CIOs and IT Managers say "Why the hell should we deal with those slow/incompetent jerks, when XYZ Corporation still offers good service?"
(Ever spend big money with a vendor after their "support staff budget cuts" led to lousy service? Me neither...)
Sadly, I'm afraid you're correct that we're going to have to deal with this sort of idiocy for a while longer... It is amazing to me that in strong economic times, managers complain endlessly about their "free agent" employees, louldy wondering where "loyalty" went?
Then, in the down times, selfsame managers do their best to shit all over said employees... Perhaps if employers didn't (ab)use their power over their employees in a lousy employment market they wouldn't be so eager to jump ship at the first opportunity.
Who did what now?
If things are bad then trying to raise morale is nothing but an attempt to deceive employees. To try to convince them things are OK when they're not. But employees aren't so stupid. Nothing tells an employee that their company is in trouble more than morale boosting exercises from management.
Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
Flexible work hours and an open plolicy regarding internet and telephone use is a very good policy, but the absence of this type of policy is a symptom of a deeper problem within corporate "culture," by that I mean the treatment of employees like any other "just-in-time" business resource.
Many companies today layoff and re-hire (euphamistically called "contract hire") employees as they're needed. Contract prices today are generally no where near where they were a few years ago because of the surplus number of contract workers and the new rage to outsource work to drastically cheaper overseas labor pools. Corporations spent the 80's and 90's trying to convince people that it really was in their best interest to function as resource units, even suggesting that it put the individual worker in the driver's seat, but in realitiy of course it was always in the corporations best interest. An excellent book on this subject is Thomas Frank's One Market Under God which chronicles the enormous PR and marketing resources expended by big companines to cultivate thier self-serving pseudo-populist image. Great insight also into the backgroud behind all those MCI and IBM commercials featuring throngs of third world looking people and the proverbial work-at-home CEO mom. Does Microsoft really stand in awe of us? I don't think so.
Few people are doing well contracting today. Employers need to realize that paying employees well and not treating them like children, indentured servants or worse as a simple "resource" like computers or other equipment but instead like fellow human beings, is the best way to make everybody happy and productive.
I agree with the internet and phone use for personal business. Most of the time I have to take a vacation day to compelete such tasks and no work gets done. On the flex hours, I would agree to a degree. In the past I have had a question for someone only to realize the that person would not be at work for another two hours (or has already left for the day). But I do not have a problem with 30 minutes to maybe an hour. 30 minutes can drastically affect commute time because you are no longer in sync with everyone else.
Peter Gibbons: So I was sitting in my cubicle today, and I realized, ever since I started working, every single day of my life has been worse than the day before it. So that means that every single day that you see me, that's on the worst day of my life.
Dr. Swanson: What about today? Is today the worst day of your life?
Peter Gibbons: Yeah.
Dr. Swanson: Wow, that's messed up!
Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
Taken from Fuckedcompany.com in Dec. (Jo Anne was soon fired afterwards, go figure).
From: Jo Anne Miller
To: Gluon - Site - All
Sent: 12/6/2002 3:03 PM
Subject: Commitment Message from the ALL HANDS MEETING
Importance: High
As those who were present at the All Hands Meeting this morning already
know, I am seeking the PERSONAL Commitment of everyone at Gluon to the
Release 2.1 development schedule. I expect a return email from all the
staff to tell me if they can step up and make the commitment to DO
EVERYTHING IT TAKES, INCLUDING POSTPONING DECEMBER VACATIONS to hit the
2.1 ready for field trial milestone of January 20, 2003 and ready to
deploy milestone of February 21, 2003. I also need to know if you will
volunteer to be here the week of December 23-27 and Dec. 30-Jan. 4.
Please consider this decision carefully. Don't say yes if you don't
believe that you and your fellow Gluon teammates can make this happen.
Don't say yes, if you aren't ready to find bugs, fix bugs, document the
product and get this ready to go out the door. Don't say yes if you are
too burned out to look forward to continued late nights, long hours and
stretch milestones.
Now more than ever, the Gluon team must have the start-up/do whatever it
takes mentality. If any of you are not of that mentality anymore, have
personal/family issues that prohibit you from making the full
commitment, please tell me that as well and I will do whatever I can to
assist you to find a job outside of Gluon.
I am attaching the four key slides from the all hands related to our
commitment to refresh your memory of what is required and why.
Looking forward to hearing back from everyone
Jo Anne Miller
Gluon Networks, Inc.
5401 Old Redwood Hwy.
Petaluma, CA 94954
707-285-4001
www.gluonnetworks.com
www.bleepyou.com
Enjoyment and challenge on the job is not something that is pointed out to you; it is something you must find for yourself.
:-7
This sort of presupposes that such oportunities/challenges exist in your work place. Their are environments, typically only in small businesses, where management is so clueless that you can actually find yourself in hot water for proposing ways to get the company out of the IT shithole you're in.
Case in point: I'm currently working for a bookstore at a university. A few years back we purchased a point of sale and inventory management system. The product we purchased so poorly developed it's egregious. In many instances it just doesn't work, and where it does work we have to go through so many hoops to get it to work, it would be better ditching it altogether. Now, this product also has various web services that are meant to run on our AS/400 server. They allow our customers to perform various activities such as: order a textbook, reserve a textbook, request a textbook adoption (for faculty), and so on. Now, as with most of the products supplied to us by our vendors, these products barely work. This is exceptionally damaging to us as an institution as these are programs that our customers interface with directly. So, I have recently proposed an alternative to management. That we set up a linux server running mySQL, apache, and PHP. We could then create web applications to replace the faulty applications we are now using.
I've spent quite some time with this proposal: In fact it's turned out to be forty-some page memorandum, complete with research and estimates on how this change would effect our company.
Now, here's the kicker. Management turned out not to be interested in even looking at the proposal. It seems he's more interested in protecting his image than the company. We've spent over a quarter million dollars on equipment and software alone, not to mention outrageous support fees. He's expressed the opinion that since we've invested so much into this product already, he can't just back out now. You see, it would make it look like he made a bad decision. Not just a bad one, but a very costly one. Since the University is considering outsourcing the bookstore, it is important that his image remain intact. Even if it means that we can barely funciton.
So, for the time being I am stuck with: Data entry, employee training, finding workarounds, and writing shitty reports and query utilities with Visual Basic (the only thing I've been able to use out of concern for future maintenance--it has to be able to be modified by Joe Random Coder). Damn it. I swear, it seems like nothing I do will actually have any impact. Why, then, should I care?
FYI: I am a graduate student studying mathematics. I've been with this bookstore for 5 years now. I was hired as an undergraduate student studying Comp Sci. I am now working full time and have education benefits for me and my wife, which is what is keeping me with this employer. And yes, I am at work now.
Do I contradict myself? Very well, then I contradict myself, I am large, I contain multitudes. -- Walt Whitman
I worked a summer job in a laundry. One day midweek, I looked up from the %meaningless task% I was doing to see the owner of the entire chain helping fold sheets.
I asked how often he does this, to which he replied "Whenever I feel like a change".
The girls on the line really liked it. He didn't have his own table at mealtimes, didn't have his own parking space, and you could call him "dave".
Ace fella. And even though the job was shit, most people were happy at it.
yes, www.dotcomforwardslash.com is my real URL.
Memo to management:
1. I want to be left alone to do my job. No OSHA training (I can use a fire extinguisher without any explanation from the "Risk Manager," thank you), no safety training (I could not care less about the MSDS sheets - I'm in an office, for God's sake), no sexual harassment/sensitivity training and no drug awareness in the workplace meetings. Do not waste my time on bullshit meetings/classes that have nothing to do with my job.
2. I come in early, work late and work on weekends. If you see me leaving or arriving outside of my scheduled hours, don't worry about it: you're way ahead on the deal.
3. If I can only use my email or web connection for business use, fine: quit allowing people to send broadcast emails about Relay for Life, Blood Drives and Girl Scout Cookies. Either it's for business, or it isn't. Don't allow other people to clutter up my mailbox for "good causes" if I can't send/receive jokes.
4. I am low maintenance, but is it too much to ask that you *not* turn off the fucking hot water heaters and ac units to save money at 4:00 pm every day? Some of us work outside normal hours.
5. If one of my cow-orkers misbehaves, I expect that he be punished. I do not expect that new policies be put in place that have the effect of punishing those of use who did not cause the problem to begin with.
6. Don't lie to me. I'm a big boy, I can handle the truth.
7. Don't get mad at me when I tell the truth.
11 things developers can do
(not in any particular order)
1) Read "Code Complete" and "Design Patterns". Others will be thankful... trust me.
2) Have pride in what you do. Programming IS an art. It requires talent, practice, motiviation, inspiration, creativity, and experience to write good code. Know your craft.
3) Eliminate the KINGDOMS on your team. That is, one person should not solely own one part of the system... hence a "king". Make sure at least two people are knowledgeable about one part of a system.
4) Utilitize tried-and-true design patterns. These are your brushes and your paints.
5) Be politically aware in code reviews. Take constructive criticism constructively and remove your ego. If a reviewer is suggesting that you make a minor change, and the change doesn't harm anything... DO IT. Being inclusive of others' ideas in your code will make everyone happy.
6) When reviewing other people's code, don't be superficially critical. Programmers have different styles. A car, on the outside, may not appeal to you, but it doesn't mean that it isn't a well built/designed vehicle.
7) When designing (or refactoring) portions of code, have design reviews (informal or formal) with at least one other developer. Bounce all your ideas and thoughts. Get ideas and thoughts in return. Use your whiteboard for goodness sakes. That's what it is there for.
8) Praise other developers when they do well. Programmers need to know when they're doing good as well as bad. Programmers appreciate praise from other programmers more than they do from anyone else.
9) When you have to be critical of someone else's code, be constructive. Apply honesty with a feather... not with a sledge hammer. Instead of saying, "What the fuck??? You're not threadsafe and possibly creating multi-tons."... say... "Do you think that synchronizing this singleton might work here better... so we're threadsafe?"... for example.
10) Be consistent in your code. It makes your code more easily maintained by others.
11) Document. Please write comments. Don't be so egotistical to think that your code is self-documenting. Even in COBOL and Eiffel... the two most verbose languages on the planet... this isn't the case.
My last job (incidentally, 70 weeks ago, unable to find work since) required me to relocate 3,100 miles from the Right coast to the Left coast, to work for them, leaving a very stable job behind. A week after I got there, my hiring manager was fired, along with 76 other people. We were 250 people at the time.
Over the next 14 months, we went through 5 rounds of layoffs, including the last one which liquidated my entire department, leaving me as the only person standing. Even my boss was let go.
In 18 months time, we had gone from 250 people to 30, and were on our 4th CEO. All three founders had resigned, two failed merger deals (one with a company that just recently bit the dust themselves), two sexual harassment suits pending against the first CEO and his team, and it only got worse from there.
We originally had free vending machines, but those were soon turned into pay-only machines. The senior management team had free parking in a mostly-empty garage space, and we had to pay $20.00-per-day to park across the street. The middle-management groups were internally promoting themselves, laying off more and more people, and making the remaining people work longer and longer hours, for less pay. We were earning (as developers) roughly 1/4 of what the managers were earning at the time. They were working 4-day weeks, 5 hour days, feet up on the desks, while we were camping in the offices overnight sometimes to meet customer deliverables.
Every day, people would come in wondering if "..they were next". That's not a nice way to come to work, not wondering if you're going to lose your job, but when.
In November 2001, I decided to pack up my things, and resign. The company wasn't going to survive a 6th round of layoffs, and now with the board in control, they had changed direction, completely tarnishing their name with the Open Source community. I moved back 3,100 miles to the Right coast, and haven't been able to find a job since (yes, it's incredibly tough out here).
After I left, they worked on a product, and after the remaining developers completed version 1.0 of the product, and delivered it, they were all fired, en-masse.
How's that for morale for you?
A couple of simple rules have always helped me with the morale of my team. If morale is poor, I nearly always point at one of these things and realise that I/my company is not doing it: 1. Clear, achievable deadlines
2. The best tools and equipment for the job (within reason obviously)
3. Insulation from the most insideous company politics and hopeless project managers.
4. Wages in the upper bracket of the industry for each role
Never, ever lose a file again. Ever.
Aww, you hate your job?
There's a support group for that. It's called everybody, we meet at the bar.
See you there!
My mom says I'm cool.
As a currently very happy employee myself, I can tell you what specific conditions exist at my job that make me happy. Most of these conditions are a function of the job being A) unionized, and therefore solid with good benefits and a living wage, and B) in government, so there is a well-thought out bureaucracy in place to keep things running smoothly. BUT, the specific happiness inducing effects shouldn't be too hard to replicate in private industry -- IF the bosses want them to be. So, as a public service message from moi, here are the factors which lead to happiness:
1. Pay your employees a living wage, and AT LEAST give them medical and dental. Note that this doesn't mean you have to make them rich! But if you're not paying them at LEAST in the 40K range, they're going to be too busy worrying about getting their rent money together, to worry about YOUR work. In places like NYC or Boston, better make that 60K or your employees will be living in cardboard boxes.
2. Don't breathe down your employees' necks. Where I work, the bosses leave you alone as long as you produce. So, if your employees aren't missing deadlines, leave them alone and let them do their stuff. When managing programmers (as with herding cats) less == more. Just tell them to keep you posted on their progress, at least once a week (say, Friday before COB). If you need to find out how something is doing, ask casually (this is good because it shows interest and lets the programmer know he's not forgotten). The trick is to LET the programmers produce instead of trying to force it. You'll find they come to YOU to tell you how things are going, because people like to talk about what they're doing. And they'll like you more (this does matter).
3. Don't be anal about when programmers come and go. We're not the most precise people when it comes to getting up in the morning, or going home at night. We may get in a half hour late and leave two hours late at night -- you get a free hour and a half, and we barely notice. But if you enforce business hours, we get pissed and come in and leave on a much more exact schedule.
4. Casual dress code. This means, generally, something comfortable but tasteful, like jeans and a polo shirt. Don't enforce the whole "dockers and sky blue shirt" thing (god, that is SO over), or (worse) suits. If you're uncomfortable, you're worried about stretching your shirt collar, not coding that loop. This doesn't mean you have to let them walk in in a kilt and a see-through rubber shirt, either. But, let them be comfy.
5. Cubicle decoration (within the limits of good taste) should be encouraged. A cluttered, chaotic cubicle is a happy, productive cubicle. A pile of paper on a desk is a sign of activity. Don't sweat stuff like this.
6. Coffee. Lots of coffee. Don't skimp on the sugar and half-and-half, either, or no one will drink the coffee and that's like no coffee. Any old coffee pot will do as long as the coffee is a reasonable, good brand and when people notice the pot is empty, they can set a new one on to brew. I can't stress the importance of caffeine and sugar to programmers enough. They WILL find ways of acquiring it; if you don't supply it, they'll be taking breaks to make coffee runs. Which do you prefer; three minutes to fill the mug at the office coffee pot, or fifteen minutes to walk a block to the Starbucks, with you playing Spy Games to figure out who's going where and when?
7. When nothing serious is going on, let the programmers do pilot projects that will eventually be good for the department. You can direct this a little; if you know, say, that you're going to be using some specific set of email tools, mention it to a programmer who isn't too busy and ask him to fiddle around with it and see what he can make it do. Then, keep the source code around for when the project ramps up. Remember: idle hands are the devil's playthings.
That's about all you have to do, really, to keep people happy. Leave them alone, let them do their thing, keep up the supply of interesting things to do, don't push them unless you really have to, feed them lots of coffee, and let them dress comfortably.
Farewell! It's been a fine buncha years!
Welcome to every company everywhere.
Actually, that's not entirely true. To the original poster's questions:
Employers: what have you done to improve employee morale in your company? As an employee, what can I do to improve the morale in the people I work with? How can I make my work environment more enjoyable? What kind of constructive suggestions can I take to management so that they can help improve the situation?
Here's what I've learned in my brief time spent on this earth about management and leadership. I've learned most of what I know from real-world inferences derived from what not to do. However, I have read a fair amount of leadership, management and sales literature (it should probably be said that I'm a software engineer by training/trade). I've found it boils down to a few things along one main theme:
You've probably already spotted the theme here: people, people and people. Unfortunately, if upper management doesn't buy into this, you're fucked. There's very little you can do (unless you're in a leadership position yourself) to combat this.The best you can hope for is to be laid off so you can collect unemployment while you search for a new job. Think of it as bozo cancer which has metastasized. If you are in a position of leadership, here's some things you can do:
moto411.com