With these people I've encountered, I was able to see different type of clients based on how they carry themselves during each meetings. Here are some notable characters that I'm sure some of you have already encountered.
Take note that most of the meeting I'm attending are programming and technical related.
Different Type of Clients
- The Old School
These type of clients are really common. Often, they are characterized by a person on his forties, fifties and above, but not all. Some of them are just old fashioned who hates technology.
These type of clients have lesser trust on technology. They believe that all their files should always be protected yet they want them to be online. Sometimes most of the complaints come from them. It would either be "I don't understand what you are saying" or "It's not friendly", worst is, "I didn't get it".
There are also cases where in they will complain for things that doesn't match your job description. From my experience on web developing, most of them doesn't even know the meaning of "browsers".
- Mr./Ms. Know-it-All
These are the types that act as if they know more than the developer. Well, basically, they should really know what they want but to go beyond what the developer use and asks things based on the books is something that really irritates me.
They'll often asks for the language that will be used, the parameters, the safety measures that we'll be using, even the specs of the server or where it is located. Though I think these items are really important to ask, I'm pretty sure that soon enough you'll encounter a non-techie person asking you these things just because "they want to ask" and show that they know something -- and that is the point why I hate them.
- Mr./Ms. Don't-Know-Anything
These people will often seek for your help to do a project they think they need, most of the time they're requests comes with the word "something like this...".
Often times, idea comes from a site or place they saw somewhere over the Internet and think that it's good. The problem is, they don't even know how it works nor the business idea behind it. All they can see is the flow of cash they can earn once they have done it.
What I really hate about these type of clients is they are passing the brainstorming of the business model to developers like us. Correct me if I'm wrong about this, but I think it is not included in a programmer's job description, rather, it is something that should be provided by the client to programmers and developers so they should have an idea on how to approach the project.
- Feeling Close
These type is one of the worst clients in my opinion. They are the ones who want to work closely with the developers even though they also belong to the "The Old School" types. They always check from time to time the things that you are doing, and watches you with your every move.
Though business wise, these types are really important too, the pressure that it gives to developers like me is simply one of kind that makes it harder to think. Developer need time to relax too and having these kinds of clients make me sick -- literally.
- The Man From The Other Side
Most of the time, you'll encounter clients from the other side of the world. Ever heard of the song "Jet Lag" by Simple Plan?
One of the issue stated there is the difference in time zone. Adjusting your time depending on their time zone is sometimes irritating. In my experience, since I'm a full time programmer who works for eight hours in a specific schedule, I really hate it when I need to ask them something. Usually I will send them an email at morning and they will answer the next day.
This often cause an issue with the speed of development, well, unless if you are the type of programmer who knows how to decide for yourself without consulting the clients.
Well these are just some of the clients I have dealt in my four years of work. There are more types than these but basically these are types that are remarkable and very common in my opinion. Actually, these types are common too in other industries aside from software development, worst is they come in different ages and forms!
How about you? Which of these clients have you encountered?
Categories
aw. naka relate ako :D
ReplyDeletemarami pang iba-ibang klase niyan :p
ReplyDeleteHahahaha..
ReplyDeleteSo humorous that you "dislike" almost all of them. XD
May mga clients nga na nagdedemand for something na d naman ksali sa job description or career mo.
I've known some who asks me to do web designing, logo making, etc. - which is d ko naman talaga field. But because computer-related daw course ko, they're assuming that yakang yaka ko daw.
Worst was when I had a friend who asked me to repair her mobile phone xe daw IT ako. XD
very true.. naexperience ko rin yan.. hahahaha
ReplyDeleteWell described by you.... it was too humorous. i have also some kind of clients but i could successful to handle them anyhow. But really i liked the post.made me too laugh.
ReplyDeleteI have a similar call center-related post...
ReplyDeletehttp://neilyamit.com/blog/2012/february/types-of-pinoy-call-center-agents.html
What I hate most is the "Ms/Mr Know-it-All" who do they think they are?
ReplyDeleteana maka-encounter din ako ng mga ganito ^_^
ReplyDeletehehehe.. mas ayoko lalo yung magtatanong sila ng mga bagay na "akala" nila ay related sa usapan... :))
ReplyDeletesoon enough :p
ReplyDeleteWhen people say that they want "something
ReplyDeletelike this...", most likely, these people are asking some insights from the
developer itself. While it is irritating that the scope is "something like
this...", you, as the developer, can also take the role of a consultant,
and share your ideas with them.
You might possibly do not want to take such role, but it can really improve
one's growth in the company. They are showing this to you because you are
"the expert" in that scenario. What I do typically with these people
is that I don't tell them that "This is difficult to do.". Instead, I
explain to them what does this "something like this..." works and if
ever they wanted to add that feature in the system, I typically provide a rough
assessment and effects on the current timeline and budget, with the help of the
project manager. The scenario works this way:
Client: Hey, I would like to ask you something and it seems this may be helpful
to add in our project. Something like this...
Me: Oh, this is really a cool one. This works like this...
Client: Amazing, let's try to add this feature in our system.
Me: Sir, if we add this to the project, as per assessment, the following
conflicts in our timeline may happen... *blah blah blah*... and may cause us to
be delayed. If ever you really need this, this may be part of a change request
and change request may mean additional costs.
As simple as that. You have helped the client understand what "something
like this..." is and also warned him that this means costs, in a nice way.
It's still part of your "software engineer" job title/description.
And sticking with your job description only is a red flag to management (if you
are working in a consulting firm). This also varies from company to company.