Curse of the IT prima donna
Summary: Prima donnas -- folks whose apparent skill is matched only by their poor attitude and arrogance are a plague we tolerate only out of necessity.
IT failures don't happen magically out of thin air. No, failure is a team sport that usually involves unspoken complicity among both management and the ordinary folks working on a project. In other words, there's plenty of blame to go around in most failures.
Although we often focus on management as major contributor to failed projects, sometimes disruptive or agenda-ridden team members are primarily to blame. As an example, read this Dilbert cartoon:
A benign and reasonable executive applies budget savings from one completed project to a second that is still in-progress. The person managing the completed initiative throws a hissy fit, is unwilling to share her budget, and even resists helping the troubled project.
THE PROJECT FAILURES ANALYSIS
We all know project prima donnas -- folks whose apparent skill is matched only by their poor attitude and arrogance. These self-serving people are a plague we tolerate only out of necessity.
Here are three tips for dealing with prima donnas on your team:
1. Evaluate your level of dependency. Before anything else, you must determine whether the prima donna is irreplaceable. Most often, we tolerate prima donnas because it's a hassle of replace them, but sometimes he or she is critical to your project's success. Before taking action, it's absolutely essential to gain an accurate understanding of the prima donna's precise role and importance.
2. Learn from the great ones. If getting rid of the prima donna risks harming your project substantially, then there’s little choice but to leave the person in place. We may not like the pretentious genius programmer down the hall, but if he genuinely saves our bacon then you can’t cut him loose.
More importantly, if the person really does possess incredible skills, then ask their advice on accomplishing your goals. Consider yourself fortunate to employ such a skilled person and do whatever is necessary to take full advantage of their skills -- which includes swallowing your own pride.
Be aware that some prima donnas are actually honest truth-tellers who have no agenda except helping you; protect those rare souls as hidden jewels.
3. Dump the pretenders. Most prima donnas are a legend in their own mind but actually fall short in reality. Their negative and self-serving behavior is a destructive force that hurts teams and damages projects. I suggest taking thoughtful steps to rid yourself of these unpleasant folks.
My take. Project success comes from good people who contribute to a team effort. Managers have a responsibility to create the right team environment, which includes selecting the best people and ensuring a healthy team dynamic. Prima donnas are a scourge on the face of projects and should be removed at the earliest reasonable time.
[Photograph of Dame Nellie Melba from Flickr Commons.]
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback
waiting until it's too late
<b>Prima donnas are a scourge on the face of projects and should be removed at the earliest reasonable time.</b>
I've seen far too often people dropping the ball on projects, only broaching the subject of removing prima donnas until the project had essentially reached the point of no return.
Your post offers sound advice for those unsure about what to do--and when to do it.
What if it's management?
create holes and let them walk into them with upper management watching
You're *that* guy?
That gets noticed by upper management as well, then you get promoted out from under the ineffectual boss.
That's a much less passive aggressive way to approach it.
RE: Curse of the IT prima donna
An exec would have to ask why Alice was able to do her project under budget while Ted's is overbudget and needs help.
We interpret differently
RE: Curse of the IT prima donna
However, in some specialty areas across IT we still see some of them from time to time. I would agree with your recommendation that such types are basically necessary evils sometimes, you have to weight their value skill wise versus their overall negative impact on morale. I would suggest signing such individuals to short, defined contract stints. Keep them around for too long and the poison starts to outweigh the talent.
Great advice
Excellent advice on keeping these folks to a short leash using clear, specific contracts.
Thanks for commenting.
This kind of thinking is responsible for organizational failures
consider their desire to work with equally-competent
people to be "not being a team player"? That's the big
failure here.
In your Dilbert example, you're saying that you honestly
believe that the problem is with the woman who finished
her project on time and under budget? Get rid of her? Not
numb-nuts Ted, the "serial failer" or the impotent boss who
doesn't have the guts to fire Ted and fill his position with
someone who's any good?
The woman who is good at her job, who is unfortunately
stuck in with this jackhole as a boss, and surrounded by
mediocrity should feel compelled to "help" Ted (i.e., do his
job for him) so that she can "be part of the team"?
No.
The solution is simple. Get rid of Ted, and other under-
performers, including the boss who can't tell the difference.
Raise the stakes to sink-or-swim for the performer by
surrounding her with people who are as good or better. If
she is a whiner with an agenda, that will become obvious. If
she is a winner who wants to be part of a winning team,
she'l thrive and excel even more.