My day job is working for a software & hardware OEM with both in-house design centers in the UK, India & China as well as ODM relationships in places like Israel & Taiwan.
The level of overhead introduced with time-zone & distance has proven highly detrimental to many of the programs I've worked on. There are tricks & techniques to communicating design over distances & languages, however, in the end its an extra constraint at the cost of producing the best design possible. After 12 years of designing within an increasingly 'outsourced' business model I've concluded that flat-world thinking cannot be applied within a particular silo, in my case development. It will work when manufacturing is in one country, finance in another location etc... it does not work when you have 'low cost' implementers following high level architecture from 7500 miles away, everyone under the banner of development. Also, somewhat anecdotal as I dont have too much experience consulting, I have worked from a wed 2.0 company on the west coast, I'm in Boston, and that too has proved difficult at times. At a high level its quite easy to wade in to a design and make progress, but when it comes to crossing the t's and dotting the i's there is nothing better than being in the same room as those who implement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=27477 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
