i came up with an idea what i may do when i come back to switzerland in october.. read on to see my mail i sent to etg (the team i lead at kpmg consulting)
working in thailand has opened my eyes to some things we might consider doing in switzerland.

i lead a team of 4 young thais (all 24) that have finished their it studies. their skill set varies greatly, the best of the bunch is like 3 times more productive than the others. furthermore, while they are all quite dedicated to their work, they need some help in the architecture, structure and organization departments.in other words, they need guidance. providing guidance and technological insight is something where etg is quite strong already, and where etg has a lot of potential for the future. i think you would agree with me that all of us have a far better understanding of technical issues than most consultants. this enables us to leverage in projects like the cs project, with great success.

in an ideal world, every project would be well designed from the onset. there would be specifications, a good architecture,coding standards, reuse of code and patterns, to name but a few.unfortunately, these important goals always come second or third in priority. the first and second priorities are usually cost and time to market (or vice versa). this is why we often get bullied to develop using a quick & dirty approach. this always turns out to be dirty only, but never quicker than with a rational approach.

the crucial question therefore is: how can we achieve goals 1 & 2 without sacrificing the other goals?

first, cost. while we are generally a lot cheaper than consultants, we are not that cheap, either. compared to thailand, where one developer can be had for 40 swiss francs per day, that is. compared to that, typical etg costs would be more like 320+ swiss francs per day (salary & some side costs) and, there is a (for our purposes) basically infinite supply of young thais with the necessary technical background.

second, time to market. having a 13 hour work day, instead of a 8 hour work day, would increase output by 50%. of course, nobody wants to work that long. he would not have to, because we would make use of the time difference between thailand and switzerland (5 hours during summer time, 6 hours during winter time). the 50% figure is way too optimistic, of course, but i made it more to make a point than to be accurate.

i could go on and on for many pages, but i think you’ll grasp the basic idea. outsourcing some work to thailand may do us a lot of good.

of course, to make something like this work, we would need a world-class virtual company. communication flow is crucial. it must be very easy to share work results with our partners in thailand, and there should be instant access to technical knowledge on the other side.

needless to say, we need such an infrastructure anyway to set us apart from old, inefficient, monolithic companies (like kpmg) read www.cluetrain.com for some good laughs on that topic..

what would our role be in such a deal? we would do what we do best, or rather, what we strive to do best:

giving technical advice, coming up with new ideas, creating good architectures. being somewhat relieved from priorities 1 & 2 would make it much easier to create REAL good software. and it would be a lot more interesting, too, because we would automatically source out the boring, repetitive work to our friends in thailand, and focus on adding value for the client.