Your common sense is not my common sense
A friend of mine was in Jakarta for an IT project which was for a Japanese client (different client from the one I was ‘serving’). From what he told me, the entire project was a total mess…maybe worse than the one I was involved in.
First, the client didn’t know what he wanted and kept on changing the requirements. Second, when the project has been ‘completed’, the client scolded my friend and his team for being useless because they have no common sense and kept giving him things that he didn’t want. According to him, my friend and the team should just use their ‘common sense’ in order to know what kind of business processes the system should cater for. Hmm…no information….so they have to use their common sense to get those information……..does that mean he’s asking them to GUESS what the system should have?
Now now now…don’t you think this kind of situation sounds pretty familiar? A lot of clients actually expect the consultants/programmers or anyone they’re paying their money for, to have the right common sense and to come out with whatever they want WITHOUT asking them. This is possible, if there’s someone in the team who can do mind-reading. Otherwise, it’s impossible.
This is because each company has its own unique business processes and no matter how much we try to use our common sense, it’ll be very hard to ‘predict’ or ‘guess’ which is actually the correct one. The best solution here is to suggest to them your ‘best practices’ if they don’t have one….and if they do have one, get it from them without making any wild guesses. That’s the best we can do.
Because at the end of the day, you will be surprised that some companies have really weird business processes…..processes which don’t make sense at all and processes which make your wild guesses look childish.
So now you tell me, do you still want me (or my friend, or anyone you’re paying to work on a project) to use my common sense ……..or do you want to minimize the time I spend on guessing, and tell me right away what are your business processes? Remember that your common sense might not be the same with my common sense.
Decide now, and don’t blame me if your decision makes you lose money though I’m pretty sure you will. Hahah. Because the ‘blaming’ and ‘flaming’ are part of the deal after all


Hmm… did your friend’s team practice any form of risk management? These things are often avoidable if the project directors did their jobs properly. During my time, the lack of sign-offs can precipitate our withdrawal from a project because of how project margins cannot be assured. In fact, 2 to 3 out of 10 projects we analyze did not make it past our risk filter.
Damien Tan
27 Feb 09 at 9:01 am
I agree with Damien. The starting pint should have been a signed off document listing the specs and the expectations. I suppose even after this, there may be changes in mind etc, especially from a client who does not really know he wants.
moreincome
28 Feb 09 at 9:22 am
@ Damien
I doubt they have those kind of things. And the company is pretty desperate for project ….any kind of project. Thus, it ended up this way. From what I heard, the client has yet to pay them even after all the functionality has been delivered (with some bugs here and there….but well, there’s no bug-free system in this world esp on the first day).
@ moreincome
The correct way should be with the signed document but in this case, there isn’t any. That is why all I can think of now is to suggest my friend to use the iterative approach used in most lightweight projects….but well…maybe my suggestion came a little bit too late?
Alvin Lim
28 Feb 09 at 10:34 am
Ok.. Your friend is worse off than us.
Quite hard to crack the Japanese… No matter how much risk management we put in, they seem to take it and throw it out the window.
Angie Tan
3 Mar 09 at 2:22 pm
@ Angie
Maybe it’s a difference in culture…so we cannot really understand each other?
Well…that’s from the positive side of thinking. LOL.
Alvin Lim
4 Mar 09 at 9:37 am