Ask Adam: Navigating Corporate Politics and Offshore Outsourcing
I am a frontline manager of software developers and business analysts in the ERP space. Recently, my boss has been pushing for more usage of disengaged offshore partner resources. Should I be concerned with this approach, and should I push back?
Sincerely,
Concerned Manager
Dear Concerned Manager,
Your concerns are valid, and you're not alone in facing this dilemma. The push for using offshore resources, especially those who are disengaged and distant from your core operations, is a topic that needs careful consideration. Here’s why you should be cautious and proactive in your response:
The Risks of Offshore Partner Resources
Quality and Productivity: Disengaged offshore resources will lack the contextual understanding and deep integration with your business processes that your local team possesses. This can lead to lower quality work, misaligned priorities, and extended project timelines. Your local FTEs have built symbiotic relationships with internal stakeholders, resulting in a smoother, more intuitive workflow that offshore teams may struggle to replicate.
- Communication Barriers: Time zone differences, language barriers, and cultural differences can hinder effective communication. This not only slows down the development process but also increases the risk of misunderstandings and errors.
- Project Ownership: Offshore resources do not have the same level of investment in your projects as your in-house team. This leads to a lack of ownership and accountability, which are crucial for the successful delivery and maintenance of ERP systems.
- Security Concerns: Handling sensitive business data with offshore teams can pose security risks. Ensuring that offshore partners adhere to your organization’s security protocols can be challenging and requires stringent oversight.
Why You Should Push Back
Given these potential drawbacks, pushing back against the over-reliance on disengaged offshore resources is a prudent course of action. Here’s how you can approach this:
- Present Data-Driven Insights: Gather data on the performance, quality, and issues faced with offshore resources compared to your local team. Use this data to build a compelling case for maintaining a strong in-house team.
- Highlight Success Stories: Showcase successful projects delivered by your local team. Emphasize the importance of their deep domain knowledge and close collaboration with internal stakeholders.
- Propose a Balanced Approach: Instead of outright rejecting the use of offshore resources, suggest a hybrid model where critical tasks are handled by your in-house team, while less critical or more routine tasks are outsourced. This can help mitigate risks while addressing cost concerns.
- Cost Over Value Mindset: Utilizing offshore resources usually has a lower cost profile, however if time is money then there is absolutely no cost savings, as using offshore resources requires more time managing such and refining requirements, while it may take 1 offshore developer to deliver the solution, it takes 3 internal resources to manage such and that is a best case scenario, in the end it isn't cheaper, and it isn't faster.
Update Your Resume
Unfortunately, the push for offshore resources is a likely sign of larger issues within your organization’s leadership. It’s wise to prepare for potential changes by updating your resume and keeping an eye on opportunities elsewhere. Here’s why:
- Leadership Trends: If upper management is politically compromised and self-serving, their decisions might not align with the long-term health of the company or its employees. This could lead to a toxic work environment and unstable job security.
- Career Growth: Ensuring you’re ready for new opportunities can help you find a company that values and leverages the strengths of its in-house team. Look for organizations with a history of sustainable project delivery and strong internal collaboration.
- Professional Networks: Engage with your professional network to understand market trends and opportunities. Being proactive in your job search can help you land in a better position if your current environment becomes untenable.
- Remain Relevant: Do not become comfortable or content with simply managing vendors whether offshore or outsourced, given the constant-changing nature of technology you must stay relevant and to some extent "hands-on", don't let organizations use you and your unique set of skills for mere insurance policies, they will eventually find a way to replace you with a perceived lower cost version and thus getting re-acclimated and marketable after being removed from such is too significant of a risk.
Conclusion
Pushing back on the overuse of disengaged offshore resources is not just about preserving your current team's effectiveness; it’s about advocating for the long-term success and stability of your projects and your professional career. At the same time, be prepared for the possibility that your organization may continue down this path and ensure you're ready to move to a more supportive environment if necessary.
Best of luck,
Adam
Adam has dedicated over 25 years to the enterprise software development space, honing his skills and expertise in a variety of roles and environments. With a career spanning both commercial software development and the creation of internal applications, Adam has become a seasoned veteran in the ERP space. His extensive experience includes:
- Software Developer: Crafting high-quality, reliable software solutions tailored to meet complex business needs.
- Project Manager: Leading teams and projects to successful completions, ensuring alignment with organizational goals and timelines.
- Business Analyst: Bridging the gap between technical teams and business stakeholders, translating business requirements into actionable technical specifications.
- Data Scientist: Leveraging data to drive insights and inform decision-making, optimizing processes and outcomes.
- Development Manager: Guiding and mentoring teams of developers and analysts, fostering a collaborative and productive work environment.
Comments
Post a Comment