You Need Software Training

You Need Software Training, Just Like You Need Driving or Skiing Training: eDiscovery Best Practices

It’s a three-post day! And I could relate to both examples used by Vound Software in their post yesterday. My daughter recently learned to drive, and I tried to learn to ski last week (she fared better than I did!). So, as they noted in their post, you need software training to get the most out of the software.

In their post Add Software to the List of Things You Need Training for to Be Effective, Vound reminds us that, chances are, you probably completed a driver education course before you were approved to begin driving; in fact, in most jurisdictions, it’s required by law. And you would get instruction from a certified ski instructor first and practice on the “bunny hill” until you know how to ski proficiently (or at least learn how to stop!).

So, even though you may be thinking that “the software solution should be so easy to use that I don’t even need any training”, there are at least four good reasons you need software training. Here’s one of them:

Advertisement
Veritas

Increase ROI in the Software: Your investment in eDiscovery software (though necessary to conduct discovery effectively today) can be expensive. Proper training – to fully understand how to use all capabilities of the solution and learn how to use those capabilities as efficiently as possible – makes you more efficient and more effective with the solution, increasing the ROI your company gets out of it.

That’s a good reason you need software training. So, what are the other three reasons (and a potential fifth reason)? Find out that and more here! And please share any comments you might have or if you’d like to know more about a particular topic. Hey, even though I’m not that great a skier, I lived to tell about it!  😉

Disclosure: Vound Software is an Educational Partner and sponsor of eDiscovery Today

Disclaimer: The views represented herein are exclusively the views of the authors and speakers themselves, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Advertisement
KLDiscovery

2 comments

  1. I have been citing the following web page for nigh 13 years now, because it illustrates exactly this point about needing to have tools that are powerful enough that you’d need training for them.

    ——

    https://www.engadget.com/2009-01-02-the-death-of-lively-and-some-lessons-about-complexity.html#:~:text=We%27re%20not%20ragging%20on%20Lively%20here.%20Instead%2C%20we%27re,and%20type%20of%20tasks%20which%20can%20be%20performed.

    “If you dumb something down far enough, very few people will actually want to use it. We’re not ragging on Lively here. Instead, we’re aiming to learn from its principles and performance. Let’s introduce a new principle called necessary complexity.

    The idea here is that any interactive system has a certain amount of complexity, usually involving the number and type of tasks which can be performed. Obviously, it is detrimental if the interaction interface is more complicated than it needs to be. That just makes things harder.

    What’s a little less obvious is that reducing the complexity of the interaction interface too far makes things harder as well. Either it makes it hard to perform the tasks, or it reduces the number of tasks which can be performed.”

Leave a Reply