Comments
4 Outsourcing Mistakes Companies Still Make
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 3   >   >>
SaneIT
100%
0%
SaneIT,
User Rank: Ninja
8/27/2014 | 8:01:10 AM
2. You focus on pay rates over results
This can not be said enough.   Too often outsourcing is not about an expanded tool set it is about doing something as cheaply as possible.  That almost never turns out how it is expected to.  I cringe every time I hear "we went with the low bidder" because I know that the management of the project and the clean up is going to be incredibly high.
zaious
100%
0%
zaious,
User Rank: Ninja
8/27/2014 | 5:24:55 AM
Re: Outsourcers
Work rotation is beneficial for the emplyee (sometimes), but it is hardly beneficial for the line manager. They have to let go their star player for a rookie.
SachinEE
100%
0%
SachinEE,
User Rank: Ninja
8/26/2014 | 3:15:08 PM
Re: Outsourcers
Rotating people to increase their skill set may be a cool idea to begin with, but managers know that if you are working for a department for a couple of years and if you get transferred to a new department for the sake of new skills then that could mean a disaster. It could mean work stalling and hence work pile up. Not only that it would create delays is decisions which otherwise wouldn't have happened if the employee did not rotate. So basically there are too many factors to consider.
SachinEE
100%
0%
SachinEE,
User Rank: Ninja
8/26/2014 | 3:12:32 PM
Pay rates and potential
Pay rates are seriously low in the eastern IT sectors. Most outsourcing companies focus too hard on the jobs without knowing the background of the staff that does the work for the western based company, and this creates blame games and payscale fluctuations. If managers on both sides could communicate such differences out of the framework then that would be very helpful.
TerryB
100%
0%
TerryB,
User Rank: Ninja
8/26/2014 | 9:44:46 AM
Re: Outsourcers
Thanks for clarifying @jjobe. I did miss the point they were doing the architect work. I also see you are talking about a "big data" project, which is way outside the scope of what small companies like mine have to deal with. I'm not going to sit here and tell you I'm an expert in that world.

Thanks for sharing your experience and good luck sorting things out with your outsourcer.
Shane M. O'Neill
100%
0%
Shane M. O'Neill,
User Rank: Author
8/25/2014 | 6:10:01 PM
Re: Pricing
Yes Lorna, the analysts I talked to say hourly pay rate is inefficient, and they encourage pay per job or based on certain results. Or maybe they'll do a lower hourly rate, with a big bonus if the outsourcer reaches a goal (i.e. 100% Web uptime during a retailer's busy season). But this is easier said than done because business outcomes are hard to predict. So companies fall back on hourly rates because it's the standard.
jjobe323
50%
50%
jjobe323,
User Rank: Apprentice
8/25/2014 | 4:24:57 PM
Outsourcers
TerryB, no offense taken.  As mentioned, when I started out in this career, we coders did it all.  Then our profession matured; some prefer to count the leaves on the trees (coders) & some prefer to ensure the forest is healthy, optimally thriving, & all the bits & parts are peaceably coexisting.

If I may, I think you might've missed the message.  Our implementation time has skyrocketed because we've outsourced the architect role along with the coding.  It isn't just that outsource teams DON'T want to abide by data/database design standards, it's that their failure to do so has resulted in their creations being unimplementable -- we won't even get into the tonnage of resources necessary to make these abominations functional for users.

If they HAD followed standards, the geometric increase in the time it now takes for our technical team to trot the new app out for the users to actually use would NOT be happening.  We know this because we know the entirety of the hardware, software, & communications architecture of the organization & work in concert to keep it humming along as best as we can -- they don't.  When standards are NOT followed, we have to create new & unique techniques for implementing & connecting everything up.  These new & unique techniques create unnecessary complexity which -- I don't know about your shop, but before outsourcing we were doing our best to simplify -- is contrary to both the demands of our executive leadership & industry best practices.

I've been reading a lot lately on the way(s) large companies handle 'big data', & the level of analysis & coordination (read:  data administration & architects) required to keep the wheels moving, & I think if folks believe it's the coders who are doing all of that, those folks are naïve at best & deluded at worst.

No offense intended, TerryB.
Laurianne
100%
0%
Laurianne,
User Rank: Author
8/25/2014 | 2:45:59 PM
Re: Outsourcers
"I'm not sure people are built to do the whole thing anymore because, like the @jjobe said, you just don't see it all outside the smaller companies. Everybody has to be a specialist today." Does this ring true to you too, readers? What happened to rotating people to broaden their skill sets? Are CIOs talking about it but not doing it?
TerryB
100%
0%
TerryB,
User Rank: Ninja
8/25/2014 | 2:32:11 PM
Re: Outsourcers
I would add BIG companies, Laurianne. There are many like myself who have spent our careers at $30 to $100 million annual revenue companies who perform the Architect to Coder role. These companies can't afford big IT teams. One guy to write code/support ERP and 1-2 to do infrastructure admin. That's your IT team.

We were Agile long before it had a name. Actually, it did have a name. Rapid Prototyping, now just considered a small part of the whole Agile process. I saw very little need to write a business requirements document to myself after interviewing users. You can save a lot of time and money by getting right to the code.

But you have to be good at all roles to make it work. If you talk over users head in Technese, it won't work. If you don't know how to design the application for proper scale and other things like that, it won't work. And most importantly, if you write terrible code it won't work.

The question I have anymore is whether Comp Science programs are producing these kind of people anymore. You seem to either get the super techie Java coder or network hacker or the high level analyst type person who slides into these Architect roles. I'm not sure people are built to do the whole thing anymore because, like the @jjobe said, you just don't see it all outside the smaller companies. Everybody has to be a specialist today.

Glad to hear Netflix gets it.
Laurianne
100%
0%
Laurianne,
User Rank: Author
8/25/2014 | 2:15:56 PM
Re: Outsourcers
Terry makes some good points here re agile. This whole conversation wouldn't happen at a company like Netflix, which has essentially erased the wall between IT and biz ops. Most companies are not anywhere near that big of a culture leap, however.
<<   <   Page 2 / 3   >   >>


Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest, Dec. 9, 2014
Apps will make or break the tablet as a work device, but don't shortchange critical factors related to hardware, security, peripherals, and integration.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
Join us for a roundup of the top stories on InformationWeek.com for the week of December 7, 2014. Be here for the show and for the incredible Friday Afternoon Conversation that runs beside the program!
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.