Preparing to Roll Out CT Summation iBlaze 3.0

I was working this afternoon on a demo I’m doing tomorrow to a group of attorney’s and paralegals. We had discussed a couple of months ago doing a sort of “show and tell” of ways we could try and make their lives easier by changing some of the workflow within our document review platform, Summation iBlaze. At the time, I didn’t quite realize that we’d be rolling out the upgrade to 3.0, so while I agreed to do the show and tell, I actually wound up delaying it a bit so that we could not only discuss ways we could customize different types of cases, but also preview the new features in 3.0.

As I was looking back at my notes from previous meetings, one thing that jumped out at me was how many of the new features are direct fixes for things they had been complaining about. My folks dislike the way menu and toolbar options change based on what tab you have in focus? 2.9 introduced a new UI, with a secondary toolbar on each of the tabs. They complained that it’s hard to find which documents had been redacted, now there’s a field in the database for that. They complained that there’s no way to verify duplicates, there’s a field to hold the MD5 Hash for each file now. They complained that it was difficult to keep track of whether a document had been produced already, and what it would have been produced as, now there’s an easy right-click option to show a document’s production history, they complain about working with native files and waiting for applications to open, there’s a new near-native viewer.

Now, don’t get me wrong, there are still some things to complain about, and I’m 99% sure, even with the new enhancements, that some of my users will find something to complain about, but I have to say that as I look at the big “pain areas” when it comes to using Summation for them, the company definitely has responded to make the experience better. That’s a big part of why I want to get this update rolled out, so we can move past these areas and start addressing workflow issues that are causing pain as well.

For all the shortcomings that iBlaze may have, it’s nice to know that they are listening and making efforts to improve!

Follow these topics: LitigationSupport