To recap, those seven risks are:
Risk 1: High Hourly Cost
Risk 2: Time Zone Differences
Risk 3: Not Agile Enough
Risk 4: Language Barriers
Risk 5: Culture Barriers
Risk 6: Knowledge Transfer
Risk 7: Questionable Code Quality
In this blog post, we’re going to discuss the 6th risk of outsourcing: a lack of knowledge transfer.
The State of Outsourcing
In outsourced projects, many companies are used to one standard model for outsourced staff: time and materials. In this model, the high-level manager is typically heavily involved in the staff resourcing process, including who is needed, what skills are needed, and which projects said resource could add value to.
With many projects to manage with many internal and external staff across consulting firms, managers often face overwhelm. Tasks like documentation as the project goes gets left by the wayside for more important tasks. And when outsourced consultants leave or projects wind down, projects often end up undocumented. This causes knowledge to virtually walk out the door.
The knowledge loss is especially painful when a project has to stop unexpectedly for budget reasons. In an economic jolt like the world saw in 2020 with COVID-19, there was not time for many projects to wrap up and document projects appropriately. For those organizations, projects had to stop immediately to preserve cash flow. How many projects had progress and knowledge which simply walked out the door?
This is a solvable problem.
We’ve been in the business for 20 years now, and we knew there had to be a better way to address the problem of knowledge loss because of lost resources or “ramping down” projects. We also knew that often, projects eventually do “ramp up” and restart. Why not preserve your project knowledge for the inevitable restart?
This knowledge problem is why we developed AptudeFlexTM.
AptudeFlexTM is our solution to the knowledge transfer problem. This model is a nearshore/offshore project organization that contains costs and encourages speed while also preserving project knowledge.
How do we do it? It’s possible because in this new model, maintaining knowledge is built into the project team design. Instead of sending you individual team members, we include a Project Lead in every engagement. This Project Lead keeps all of the project information in secure documentation vault so that nothing is lost when you have to ramp down.