The Offshoring Blind Spot: How Poor Systems Cripple Profitability
Advisely PartnerI wholeheartedly agree marklewin1 - a sub-standard process can really cripple efficiency, especially for offshore teams. I noticed you referenced paraplanning as staying onshore in your example. In my experience, I've seen good success with offshoring the tasks you've outlined (data collection, implementation etc) but paraplanning tends to break down offshore.
Curious to hear your view - would you agree it's best kept onshore?
Hi Tamara, apologies for the delay in responding.
In practical terms, successful SOA construction (paraplanning) can take time, largely due to the challenges of training offshore staff to a level that meets the practice owner's standards in this highly technical area.
What I’ve observed is a common trend: many Australian businesses are comfortable offshoring administration and data entry, but they often stop there. As a result, SOA construction is frequently kept onshore.
That said, I’ve personally seen offshore staff produce high-quality SOAs when given the right training and support. Just as I’ve heard many reasons why a practice won’t offshore at all, I’ve also heard a wide range of experiences, both positive and negative, when it comes to outsourcing SOA production.
This all comes back to the fact that offshoring is a strategic decision. It must be made with a clear understanding of the task at hand, the time it will take, and the resourcing required to properly invest in making it work.
Mark
Recent Discussions
Related Content
