Lotus Quickr and Connections announced

I know this has been well covered already, but no harm in repeating the message!

IBM has formerly announced the two new products we have been waiting for so eagerly, Lotus Quickr and Lotus Connections.

I have recently been exploring the two quite a bit, and can honestly say they are a big step forward as collaborative tools in the enterprise.

If you still can’t wait for the 29th, and haven’t yet done so, get over to the Lotus Greenhouse and sign up!

Lotus Connections market positioning

Jake has an interesting post over on Codestore about managing large numbers of Domino based blogs.

The client is a university with about 20,000 students. They want to give each student the ability to blog.

He is asking for input regarding scalability and the use of one large database versus a large number of individual databases. This sounds like a cool project, and is something I have thought about a bit in the past. Personally I agree with the consensus and go the route of individual databases, building an admin tool and landing page as a front end.

However, reading Jake’s entry got me thinking to Lotus Connections, and it was a comment that Warren left that prompted me to write this post. The line in particular I’m referring to is:

“(and a whole lot better than Lotus Connections…)”

Now, I haven’t seen much on Connections yet, but it sounds like a cool product, and I imagine that IBM would be looking at the situation Jake raises as the ideal use scenario. Certainly for the blogging and community modules. I would expect that the blog functionality be pretty capable, including the ability to mark posts as private, and certainly managable for the admins.

Am I mistaken? Why would I rule out Connections in this kind of situation? I’d be interested to hear any thoughts on this, and the level of feature parity between Connections and the Domino blog template.

Some good details on Quickr and Connections positioning

Stuart McIntyre has posted a good post helping those of us pondering some of the product positioning of Quickr and Connections.

I particularly like this:

When used together they provide companies with unique value to address their collaboration requirements that span from formal, role-based team workspaces to informal community-driven social networks.

Things are getting clearer!

Source: Stuart McIntyre 14/02/2007: Quickr vs. Connections

More on Lotus Connections and Lotus Quickr

Since I wrote my first post on these products, there have been a few more good ones appearing on blogs.

Rob Novak has a good article on Quickr answering some of the key questions relating to it replacing Quickplace, the choices on the backend and more.

Connections is being covered by Roberto Boccadoro with his detailed description of the product and its components over at Yellow Is The New Black. Luis Suarez also has a similar piece with his own take on things.

All in all, this is adding up to some great information on the products at such an early stage.

Now when will my invite to the Lotus Greenhouse site arrive!? ;-D

Lotus Quickr and Connections

I, like a lot of people, am following the information coming out of IBM Lotus regarding their recently announced products Lotus Quickr and Lotus Connections.

This week I had an interesting conversation with colleagues on our understanding of the products at this early stage. One point that came out was an apparent overlap, particularly on the blogging front. It raises some interesting questions. How will the products integrate? How do I base a decision whether to run blogs from Quickr or via the blogging component of Connections?

With little information so far from Lotus, it is difficult to grasp the differences. The innovation coming with these products is a big thing for the enterprise. Their successful adoption will depend in many cases on the ability of an organisation to generate a culture of open knowledge sharing. Here, IBM and its Business Partners will have a crucial role in helping companies deal with this culture shift.

Interesting times ahead.