Discussion Locked

Problematic client!!!!!

0 helpful
19 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am a Project Manager in a software development company and am working with a client on a web application. And I do not what to do....
The client is never satisfied, whatever our team does. Always complains that the application is difficult, unituitive, does not match the original specifications, etc. Problem is, the specification our client likes so much misses major points and provides very scarce and irrelevant information about many aspects. It also shows little technical knowledge but the Project Manager on behalf of the client wishes that we follow the spec one to one. Can anyone suggest what I should do in with clients like that -- that just love paperwork, do not have much technical knowledge and foresight, and do not wish to leave anything to the discretion of the development team....

19 replies

by parsonsac

You are experiencing the problems that emerge whenever a project is insufficiently spec'd. Project specification is the single most important phase of any project!!!

I can see no other option than to follow the original specification, (with all of its omissions) and once completed the client company will soon see their project managers shortcomings

by donq

Because the "Specification" represents your companys ONLY enforcable document, AND it was originally accepted it MUST be followed to eventually insure you get paid. I would definately document "in-writing" your concerns with the current spec. and validate through registered mail your warning is received. Then do EXACTLY what the spec says, or stop until you receive a revised specifcation from your client.

You are not alone!

by xxx123

During specification phase, you can always meet with the client and suggest changes/enhancements, etc. But you cannot start construction, and then say, "Well, he hasn't a clue what he REALLY needs" and then go off and design something completely different. If the client is truly obstinate in the design phase, you can refuse the project knowing you will be saving yourself a lot of grief later on. (That's why design/spec phase is often quoted separately.)

If you uncover a showstopper design flaw, you have to stop and go back to the client. Otherwise you're stuck when he doesn't like your choices and refuses to pay.

No client has perfect understanding of the technology - - if he did, he wouldn't need you. But you have to bridge the gap, not just drive off and leave him in the dust.

by eujay

This is an interesting problem.

Does the client have a boss that you can bring into the picture ? If you bring his boss in then maybe the boss will override him.

If not then is there a way that you can make a quick and dirty version of what the client is asking for, a model if you will of what he is asking for.

If you can do this and present it as being something like what he wants then give it to him for approval. Then he himself is going to find out all about what it will not do and then he will have to come back to you asking for something different.

I would be very careful about this whole thing because if you go ahead and complete the project and give him the crappy product he wants then when it doesn't work right and/or has flaws the client may find out and will then bad mouth you for doing the crappy job he has asked for.

Please keep us posted on progress I am very interested in this.

Eujay

by terziev

You are right, we will take the blame for delivering a bad product even though we were following the spec 1:1. But you see, it is very interesting that the client is very sensitive to "following the specification" and disproves of anything that is not in line with what he has put, but when we add something essential that he missed, there are no complaints:))

Will keep you updated:)

by terziev

I forgot to mention what is, at least in my opinion, the reason for the whole mess...

The problem is that the Client wrote a specification before choosing a technology and not all of the things he has envisioned are achievable at the same time:) And then the specification was handed over to me after it was approved. So my advice to all that are reading this is to participate as much as you can in the spec development so that you are not trapped like I am in the moment. Otherwise you will have to be very creative and reach unreachable deadlines adn budgets:)

by epepke

Don't accept the specification until you are completely happy with it and the client signs off on it. Rewrite it if you need to.

by jeff.tibbitts

I can empathize, many clients are difficult to deal with for various reasons -- yours sound especially so!! But, regardless of whether the client is an idiot or a genius, they are paying you to design a product meeting their specifications and the "customer is always right"!

Advise your client where and why you feel changes should be made in writing and record their decision -- then press on! If the issues are big enough to discredit your company after development -- perhaps the decison to"cut your losses & walk away" is warranted.

by epepke

You're not a medieval serf, and the customer isn't always right.

Nobody believes that the customer is always right anyway. Nobody thinks that a customer who returns damaged goods or shoplifts is right.

The corresponding IT customer is the onewho comes up with poor specifications in order to be able to squeeze out more than they have bargained for.

A specification is, for all intents and purposes, a contract. If it isn't to your liking, don't sign off on it.

(How does one hoe roe,anyway? I always thought they used little spoons to get it out of the fish.)

by admin

The original spec is not working. Instead of "Intuitive" come up with specific quantifiable goals.

Since you already are at a difficult point, you could offer to re-write the spec so you can both proceed to both of your benefit... "We're having difficulty understanding exactly what you want, could we go over this more in detail so that we understand what you find intuitive" -which can be time intensive- or perhaps help them find another consultant. These aren't attractive, I know. You will probably take a loss on this one whether it's financial, or if you just walk, credibility- which you could lose anyway. You should seriously look at what you can afford to lose and discontinue the relationship as it is now by taking the time to re-invent it with better specs, taking the time to hand it off to a person who can help them or walking.
A personal note, I had a similar problem with hardware installation recently. Both the client and I thought we were on the same page, we weren't. I had to sit down and tell them I could not help them under the current conditions. I offered to redo the agreement, find someone else, or leave and refund their advance. They chose to redo, however, I took a loss on labor. A few weeks later they called with another job. They did not like the specs and price of the bid on the new job and were obviously trying to be vague. They also felt I was raising my cost due to the fact that I had done the previous job more inexpensively. I was bidding a fair, non-inflated price.
Needless to say, this didn't work out. No matter how "fair" you are, sometimes it's better to cut and run. You'll have to make this decision in the situation though and then make sure your specs are in order next time.

by madman1

The simple fact is you know there are going to be design flaws and second of all since the client is going to be difficult then as someone mentioned earlier stick to the original specs. Make sure the client signs some documentation stating this is exactly what he wanted and leave it at that. If he/she finally sees the light then new specs needs to be written and obviously this changes the contract IMHO which means $$. What I do not understand is why there was not an engineer/programmer involvedwith the client and company liason on this before you even began the project. Oh well, that's water under the Bridge. Good luck!

by shanghai sam

We agree that specifications are contractual requirements. One of the original customer complaints was failure to follow the specifications -- like it or not, when a consultant accepts (key word) a job, the customer's requirements are "right". If you professionally disagree, present your suggeseted changes, document the decision, and either follow the customer's wishes or "cut your losses" & walk away. Again, the consultant's decision.

I always think a customer that returns damaged goods is right. A shoplifter however is not a customer -- they are a thief.

(Unfortunatley, my typing skills are a bit rusty -- the phrase should have been "Tough Row to Hoe". The "w" key happens to be right next to the "e")

by epepke

But seriously, folks.

If you've already accepted a contract with poor specs, then you pretty much just have to deal with it.

However, the original message was asking about how to avoid the problem in the future, and most of my comments were directed toward that.

There is nothing about business ethics that require you to take a job that is not well defined. Ethics are not a one-way road. If you don't maintain your expectations of ethical behavior toward you, you will be walked on.

You have to be willing to take personal risks and get things straight up front. If you aren't, then doing this is not for you.

by ibeinnofl

Ever heard of "The Golden Rule?" It basically says "He who has the gold, makes the rules." In your case, the client is the guy with the gold. Sounds like you don't belong in the Project Management arena, which is most definitely customer-centric. If you can't deal with it, do yourself, your company, and your customers a favor -- find another line of work.

by generalist

Actually, I've heard of two versions of the 'Golden Rule'.

The version you mentioned, which is the newer one, is what I call the cynical version. It is something that people have to remember when doing work for another. Of course, that version can be taken too far when arrogant idiots think that having the gold' makes then capable of writing all the rules.

The older, more classical version, which can be found in religious teachings all over the world, essentially says 'Do unto others as you would have them do unto you' when you use the King James biblical version. As with the 'newer' version, you AND your client need to obey this rule. Many lawsuits, blacklistings and conflicts are caused by people not considering this basic rule on how to get along with others.

Personally I prefer to use the older version of the 'Golden Rule' because it already considers the newer version when you are dealing with a client. As you mentioned, the business is customer-centric and most people want a good product for their money.

by admin

It is of interest that so many people are following the one you call "newer" It is powerful, but only in the short term. The "older" one, however, is, IMHO, sustainable throughout a lifetime - or even generations. Thanks for bringing this up, I don't hear it much in the Tech world.

:)

by epepke

That golden "rule" is really a moral imperative. Like Kant's "behave as if you would approve of your behavior as a universal law" or Nietzsche's "behave as if you would be willing to repeat the behavior for all eternity."

There's an even older Golden Moral Imperative. It's "do not do to others what is hateful to you." I've always thought that one was better, because, seriously, you really don't want to do to others what you would have them do to you, and if you took it literally, the whole economy would collapse.

by terziev

You know, there is another golden rule -- when you cannot say anything nice, don't say anything. I posted this duicussion to share some thoughts with more knowledgeable people who can help me with my problem and not in order to be reproached by anyone. So I suggest you do yourself a favor and instead of posting some generalizations here, you go to another discussion where you can cotribute more.

By the way, my BA is in Business administration so I am pretty much aware of your "golden rules".But I cannot agree with you that the client is always right. SOmetimes clients do not fully understand that the combination of all things they want is unachievable.

by epepke

That's a rule that parents tell children to make them unobjectionable. It can be highly dysfunctional for adults. Most of the time, it seems, people are nice for their own benefit.

If you've read my other advice, you already know that I don't agree with the advice of mariasangria, but she does have a point.

You may not like to be reproached, but face it: you did screw up. You let the specs get out of hand. If you want to live in a world where you can screw up and not be reproached, that's very easy. Most average Americans do it. If that's what you want, then get used to bending over, because you'll be doing it a lot. Also, this is a technical board, not a support group, so you can reasonably expect people to point out how you screwed up when you ask a question here.

Or, if you choose otherwise, you can live in a world where you learn from the times you screw up. This is the world I prefer to live in. It does have its problems: sometimes you have to take a few antispasmodics for the knee. Them's the breaks.

It's extremely self-limiting to reject offensive observations. Many of the most important truths are offensive. People who try to sugarcoat them wind up lying a lot.

My view is that writing projects to spec for a client, as opposed to, say, working in a development house, requires an irreducable amount of hard-assedness during the specification phase. If you cannot bring yourself to do this, maybe because it isn't "nice" enough, then mariasangria's observations are true: you need to do something else with your time and your life.

Finally, I have to point out that neither mariasangria nor I is your difficult client. We are not the people who are making you feel so frustrated. If the goal of your posting was not to get real advice but to play Ain't it Awful or find a substitute enemy here, well, thank you for playing. There are no lovely parting gifts.

This discussion is closed to new replies.