No option for Law Firm

If anyone wants an example of why you should blog or use twitter, read on!

Since starting this blog back in January I have built up better relationships with legal IT suppliers than I have ever managed with any “account manager”. Through blogging and through twitter I’ve managed to discuss their products directly with the people inside those companies who are involved with developing them.

An example today relates to comments I’ve made over the past month in regard to Workshares products, first about their recent 5.2 SR2 release and then about a possible protect workflow problem here.I’ve been contacted a couple of times by Workshare through this blog and through twitter (@jesbreslaw), but today I got some good news relating to two specific points I raised in the posts indicated above.

1. My comment on 5.2 SR2 – “The PDF Combine functionality is only available from the local file system!!”
2. My comment on how Protect and Autonomy iManage Send & File together could annoy lawyers.

Here’s what Kevin Docherty, Product Manager had to say:

I just wanted to clarify a quick point that you mention… re “The PDF Combine functionality is only available from the local file system!!”- I suspect that you are using the first Beta as the second Beta fully supports DMS interaction.

This is great news as I see this peice of functionality being really useful for things like Bible creation etc. Then on the second point Kevin continues:

yes, we know that this may provide a challenge to the basic Protect workflow. We are obtaining a pre-release version of Autonomy very soon and will be looking to get it set up ASAP. We’re specifically targeting Protect Workflow in the SR 3 version of Professional (Oct/Nov) so I will hopefully have some feedback for you around this area soon – and how we will be looking to cope with the multiple Autonomy pop-ups.

I’ve no idea how Workshare found the blog, but regardless I’m impressed that they took time to read and respond to their customers. More companies should follow suit and get their product development and sales staff on twitter and other “web 2.0″ technologies to get dialogue going with people who use their applications.

If you want dates for the Workshare releases I got told the following:

• SR2 Beta refresh– April 17th

• SR2 General Availability -  May/June

• SR3 estimated release – Oct/Nov

Is there any point in me introducing Twitter? It’s hit the mainstream press now, so like Facebook if you’re online reading this blog you probably have heard of the latest internet hit. But have you heard of Jaiku? My guess is probably not.

Jaiku was founded in 2006 and then purchased by Google a year later, it’s basically a “twitter clone”. It generated a fair bit of publicity last week amongst Google’s announcements that it was culling a number of it’s offerings.

Now I know Jaiku is never going to beat Twitter just like Microsoft Live Search is never going to beat Google. Twitter is now the defacto standard for micro blogging. So why then title a blog post in such a way that it indicates that there is some scope for a challenge?

The answer is in this paragraph from the Google announcement.

we are in the process of porting Jaiku over to Google App Engine. After the migration is complete, we will release the new open source Jaiku Engine project on Google Code under the Apache License. While Google will no longer actively develop the Jaiku codebase, the service itself will live on thanks to a dedicated and passionate volunteer team of Googlers

I can see so many uses for Twitter internally in a law firm. IT notifications of service interruption, legal project teams working together globally on cases using it to communicate, marketing teams communicating pitch information, you could fill a page with knowledge management use alone etc. The problem though is security. You may use Twitter now, but I bet you keep your tweets vague enough to not give any personal or confidential information away?

Now with an open source Jaiku, you can have an internal Twitter. Hosted on your own secure network. Keeping it in your own network means you don’t have to limit the content. Also with it being open source you can guarantee that soon there will be Adobe Air clients, BlackBerry clients, Mac clients etc etc

This could do for internal social networks what Twitter has already done for external!