Tom's latest eBook has been released on Amazon: "The 7 Myths of IT Integrations". Tom is also a Program Director for a large Midwest corporation and has been an adjunct faculty member at Walsh College. He has managed global web initiatives, data center moves and large multi-million dollar programs.
Symphonies are beautiful and complex pieces of music. At the hands of the masters, such as Mozart and Beethoven, complex arrangements would be drafted by hand over the course of several months (if not years). In today’s competitive environment, Mozart would have done well to delegate major sections of his scores to outsourcers to help him deliver his art faster to the adoring public. But when have you outsourced too much to the point that you are no longer in control of the total product?
IT has historically been the department near the beginning of the outsourcing trend. Just like trying to preserve the integrity of the music, how does an IT department best utilize an outsourcing strategy to truly be successful? How much can you really delegate and what key pieces should you keep on your side?
The best approach is to break the functions of an IT organization down and determine which candidates can be packaged and outsourced.
It’s best to outsource:
1. Operations
This is a perfect outsourcing situation. Stable applications and infrastructure that just need careful watering, feeding and enough technical know-how to fix the systems quickly and correctly when they have problems. If expectations are clear from both sides and you have clearly established service level metrics, this portion of work can be outsourced quickly. Keep a
"This planet has - or rather had - a problem, which was this: most of the people living on it were unhappy for pretty much of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movements of small green pieces of paper, which is odd because on the whole it wasn't the small green pieces of paper that were unhappy."