Annoying requirements
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
It varies depending on the client but sometimes if you can get them to think an idea was theirs it can slip past the barriers. Or maybe present it in a way that wil lsave them money in the long term? Elaine (slightly devious fluffy tigress)
Visit http://www.notreadytogiveup.com/[^] and do something special today.
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
If he's smart, try to convince him of the better way. If he's dumb, just do it, and let them find out it won't work (don't bother with "told you so", cause he's dumb anyway).
Wout
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
I put it off as long as I can hoping they'll see reason. I recall only one time that happened; they kept insisting, so I (eventually) did it their way.
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
Refuse to do it until they give a valid technical/business reason for the requirement. This usually get you more information but sometimes you just end up with BECAUSE. After exploring all reasonably (you know the ones that won't piss the client off too much) you have to build it. Unless you have final say in the design you have to build it if it is technically possible. Remember a business reason ALWAYS overrides a technical objection, it's up to the developer to design a solution to meet the business requirements. The one time I flatly refused (a command line registry editor in VB6) I was sacked. Luckily I now have final say if a requirement cannot be justified by the client, and I have used it twice in the last 4 years!
Never underestimate the power of human stupidity RAH
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
You need to make a case. Prototype both solutions and demonstrate them. Another way is to simply prototype their solution and as you show it, hint at another solution and let them come up with it.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
The first thing you need to do is get your ego under control. I've been on both sides of the fence on occasion. Sometimes I've been on the receiving end of a client with an essential contracted requirement that requires incidental violations of laws of physics. And, I've sometimes been the technical authority representing a client with a critical requirement, facing down a stubborn developer who flatly refuses to meet an essential requirement without offering any valid explanation. The reasons for the requirement need to be talked through, and the benefits/tradeoffs of implementing something to meet it need to be discussed. This requires maturity of all participants to ensure there is a resolution that everyone involved can accept. And it also means both need to avoid the temptation of thinking of the other as incompetent/useless/annoying. Such attitudes tend to be quite visible to other parties and nobody appreciates being treated with disdain. Quite frankly some of the other attitudes exhibited in this thread ("just do it if he's dumb", stalling until they see reason, demanding justification before you try) are completely immature. An unhappy client will probably elsewhere so the developer (or his/her employer) loses business and therefore profit. In worst cases, the only ones who benefit are those in the legal profession when it all goes to court.
-
How do you cope up with this? Imagine client asks for a request which you think is useless or can be annoying for the users. You even tried to suggest something you feel is better(its just what you feel might or might not be correct). How do you manage that? Since it is 1 am here, I will sign off. I will read the thread tomorrow to see the responses. Hope I have provided some food for thought.
जय हिंद
My experience has been that this situation usually means you don't understand what is the client's real requirement. Most of the time, the client has a problem, and being the clever, experienced sort of people they are, believe they know the perfect solution. They present that solution to the developer as a requirement, not realizing that it's a dumb idea. The key for you is to recognize the situation, and figure out what the actual underlying problem is, and then come up with a solution to that. The only way to do that is to talk to them, and ask "when we do what you ask, what problem are you trying to solve?"
Software Zen:
delete this;
Fold With Us![^]