View from ThinkDox

"Friends, Romans, Countrymen, lend me your ears, I came not to praise Caesar but to bury him..." 

So a while ago, I sang the praises of Laserfiche 10; in my opinion a re-boot dearly needed as the ECM landscape fragments – and it was great for a re-boot. It provided a new UI along with basic operation analytics. All of these things lowered the barrier for on-boarding new users for existing clients. We have yet to hear any complaints regarding LF10.

That of course was until 10.1 came out yesterday. Where LF10 fixes problems for existing clients, 10.1 is meant for those still looking for ECM or EIM. It is a product that ThinkDox as a VAR is really looking forward to offering to our new and existing clients.

So in reference to the quote at the top- forget all those nice things I said about 10....I really meant you should be excited about 10.1.

Highlights

Our live update via Twitter:

LF101_TD_twitter.png

The biggest reason to love 10.1 is the Business Process library. This is a set of 40+ processes that take advantage of Laserfiche forms to reduce the pain of capturing information and organizing it. These templates provide a starting point for any organization looking to reduce the complexity of their digital processes.

Not only are the processes broken down by business goal but also by most likely work group and industry. As a VAR I can’t tell you how much effort this will save clients attempting to maximize their system but lacking a full business analyst. It also is a game changer for implementations where are large part of the issue is simply identifying a starting place for their HR process(es) or as many clients have put it “What does a digital purchase order process look like?”

Practically, for those still evaluating their options with respect to products it gives me the ability to reduce the implementation time and cost by providing a grocery list, and focusing the team’s attention on configuring the best practices for processes on Laserfiche rather than designing the process from scratch and providing customized solutions. 

Does this mean there is no customization? No it still will neede to be configured to the user and repository needs of each specific system but it provides a starting point. As a person who believes in the value of standardized and continually optimized process (i.e. Kaizen methods) this is a great point for cutting through the initial concerns. 

Have questions? Feel free to contact us and we can provide you more information.