Five Reasons Why You Shouldn’t Manage Your Own eDiscovery Environment | George Jon
The reason eDMSPs can do this much more cost effectively than in-house teams is that they share skills among many clients. Take, for example, a very important skill that I listed above: Data Architect Specialist. The role of this professional is to:
- Analyze inbound and outbound streams of datasets in eDiscovery environments.
- Identify bottlenecks that cause slowdowns and outages.
- Designing solutions that speed up processes and prevent breakdowns.
- Train system users to use the processes and tools they have integrated into the environment.
- Be on call, in case of problems they can solve.
- Check back every 6 months or so to see how things are going and to identify even more ways to improve speed and performance.
- A year later, start the cycle again.
As you can see, this skill set could be extremely valuable for optimizing performance. But here’s the thing. Most eDiscovery environments only need this level of contact a few times a year, at most.. When you need it, you really need it. But then what? What happens to a data architect who is bored because he has no interesting problems to solve? They advance. I have seen it over and over again.
But eDMSPs can keep these types of professionals busy, engaged, evolving in their careers, and constantly challenged by new problems that need to be solved. As an FTE for a law firm, for example, they would only need to work a few weeks per year. But as an FTE for an eDMSP, they could work all year round without ever getting bored. But the best part is that the salary costs, say $200,000 per year, are shared among a multitude of clients. No organization has to pay $200,000 for a part-time employee. That’s why, in the end, eDMSPs can give you better results for less money.