I’ve been reading a bit on Office 2016 this week and getting interested around their real time collaboration on documents using any device, true mobility (meaning ubiquity not device type). The challenge for legal here is the DMS (document management system), how does this fit into the picture?
It feels we’re on the cusp of change here, like the shift in DMS when Windows 95 and Word came online, out went stand alone DMS desktop apps and in came integrated Open, Save etc within Word. What we need now is a DMS that is fully aware of Microsoft’s emerging ecosystem to allow us to take full advantage of the new features of Office 2016. Ignoring Windows 8 and, to a large extent, Office 2013 (by ignore I mean taking advantage of the new systems rather than compatibility) was fine, most law firms skipped these, but Windows 10 and Office 2016/365 I think will be different.
You get the feeling this is no longer just about access on mobile devices, but something more fundamental. It’s ubiquity of access to what you want to do. Working wherever, whenever, on whatever. I’m sure for law firms Microsoft Office will still remain the core to this, as will the need for industry strength robust DMS’s. But the the next generation DMS needs to swim faster with the Microsoft Office tide in true document mobility rather than just constrain itself to addressing iPad access and being in the cloud.
Maintaining a good electronic file in the DMS is key but it can not afford to be at the expense of efficiency in creation of what is part of the core business, the legal document.
RT @planty: [blog] The future of document management? : http://t.co/kbxuDZ6JD7 #LegalIT
Legal Technology: The future of document management? http://t.co/K4JJhTOyt1 via @planty #DMS
That distinction between Version Control and change tracking is one I always felt was troublesome. I’ve lost track of the number of times I’ve had to explain to users that they are different things that have to be managed in parallel (i.e. never meeting).
It would be great if DM products could become aware of change tracking data in a document and adapt their behaviour. If I spin out a new version – should that automatically accept all changes in the prior version? Should DM be prompting for a new version when the degree of change passes a threshold? How about when a second user starts making changes?