Project saboteurs

Introduction

You have just been appointed leader of a new fascinating project. Hard years working in boring tasks have paid off. You are excited before your big day: your first meeting with your client (the owner of the business) and some other stakeholders (managers and other employees of the business).

Sabotage

So the meeting starts. Relationship with the business owner is smooth and you begin to write notes about software requirements, current system limitations, technologies… You know that you’ll have more than enough information to make the first requirement document.

Then, the saboteur begins to show a despising attitude questioning the very first need of this new software for the business, doubting about your professionality or even worse telling you what you have to do. Summing up, he/she has a menacing, primitive, non-constructive critic and rude behavior during all the meeting.

You want everybody in the team but are sweating trying to stop this kind of sabotage your seeing.

This individual sees you as an enemy and has made it clear in the meeting making things harder for you. He/she will continue to make things harder during the project.

But why?

The reason this person is boycotting the meeting and hence, the project is that the saboteur is scared. Humans base their society on customs and tradition, and when something “shakes” their ground, they rebel against it.

You are a software engineer, you are more than capable of optimizing a business you fully understand, making changes and how they have been working until now. There are people that like this kind of change because they see it like progress. There are others that will resist any kind of change above all.

Are you going to say to me how to do my job?

Other kind of saboteurs have too much ego and simply don’t want to hear that they can be wrong in the way they work.

As I said earlier, our education and experience gives us the skill of analyzing process flows pretty well and can optimize them, improving the business of our client.

Nobody wants to lose the job and if you succeed in the project, they think they can be fired.

Why are saboteurs employed?

But giving that they are toxic employees, how do saboteurs keep their jobs?

On one hand, it could be because they are civil workers and they can’t be fired.

On the other hand, usually, nobody can make some tasks they do it very well, so there is no suitable replacement for saboteurs. I’m afraid you will be surprised the low level of problem solving and autonomy that most people have. If the saboteur is marginally better than the rest, he/she will remain employed for a long time.

What can be done about these project saboteurs?

They just need to feel that they are managing the situation and they are “important” during project development. What means to be “important”? Asking them about what are their needs and above all, every change proposed of their “way of doing the things” must be “for the sake of their work” or “because it helps them do some task”.

Many times they will use a tone not appropriate for a business like environment. No problem, be more polite than ever, showing that you are here for help a business. Saboteur will feel his/her intentions are being made clear and will cease his/her attitude.

An agile project management is the best solution for changing requirements. Thus it shows everybody the costs of these requirement changes. So, from third or fourth iteration they will think again before asking the owner to spend more money in a non-vital feature. Probably owner will have a chat with them and will ask them to change their attitude.

Conclusions

The best you can do is have the owner of the business on your side.

Do not accept rude comments, insults or questioning your professionality from anybody. Call off the meeting until everybody that sits bring something to help the development of the project.

Use an agile project management that shows them the cost of not behaving as a part of the software project development team. Of course, pair this agile project with a iterated bill system to make it more clear.