Truthfully though, I think this story shows a couple of really important points.
Recognize that mistakes happen
The importance of two-factor identification
The importance of taking action as soon as you realize the mistake
The importance of getting the technical folks involved immediately instead of hiding it
It’s not normal for us to be using a platform that works one way, then changes and works another way two weeks later, but that is absolutely the way the Agile development is going to happen. The decision to change will be pushed by the business case for making the change, eDiscovery will be a second thought, if a thought at all.
That means two things in my mind in addition to the things Greg lays out in his post below.
1. You have to test, test, test. Constantly. You have to stay on top of new features, old feature changes, undocumented changes, etc.
2. The legal industry as a whole is going to have to get a lot more comfortable with “good faith efforts” being a little more of a gray area as these changes get made. What we could collect easily before, may require a lot more time and effort today, or it may not be possible today because of a bug in a recent update.
It’s going to happen. Whether you want to talk about M365, Google, cloud document management, cloud review platforms, or even cloud backups. Things will happen beyond our ability to control them, and those things will impact eDiscovery. Are we going to be OK accepting that?
This is the danger. As someone who spends a lot of time working with M365, and with clients trying to manage those environments, apps are one area that scare me a little. This is one reason, as people get so used to apps being available and pushed out by their M365 admins, they stop being…
Look, we’ve always had this issue in the eDiscovery space, in order to put data on hold, and collect it as part of a lawsuit, someone has to be able to access all of it. That means there has to be an account somewhere with unlimited access to both search, and collect, tons of data from your environment, as necessary.
As important as having the ability to do that when faced with litigation, there is also the danger inherent in having an account, and tools, with that level of access.
This week, Microsoft announced some new features coming for Teams, including some specifically designed to help employees maintain some stress management and avoid burnout. Things like a virtual commute, and a partnership with Headspace for meditations.
Which is interesting for a business collaboration tool, right?
I guess I could see this happening. Teams or Slack chats are real-time, people feeling angry might be tempted to voice their unfiltered opinions on them, much like we see on Twitter, etc. “If workers don’t feel they have a voice on serious issues, resentment can build, turning channels ugly. At the end of the…