Understanding social messaging concept and tools

Summary :enterprise social messaging is much more complex to understand that a simple enterprise Twitter. It’s about articulating flows, value creation, usage in a very constrained environment. While there are lots of solutions providing social messaging functionalities, the concept is still hard to get for organizations that still lack keys for understanding. A situation that may change with the recently published study from N:Sight Research.

At first sight, social messaging is a very simple thing. A tool allows people to publish status updates and follow updates depending on the publisher or the topic. In short, that’s enterprise Twitter.

Beyond this shortcut that simplifies the concept, relies a complexity that organizations are still struggling to get. Behind principles that look quite simple relies the need to articulate all these things with business goals, workplace constraints, make it support usage scenarios that make sense. At the end, organizations find themselves having to choose between a large number of solutions with using criteria that are not only functional but may take into account the articulation of functionalities and sense and a business context.

N:Sight recently issued a comprehensive study on social messaging. It consists of a very clear analysis  of business needs, what it means in terms of usage and functionalities and ends with a benchmark of 14 vendors based on these criteria.

This study will help organization to understand what it’s all about, determine their assessment criteria and benchmark a wide range of solutions.

Here’s a management summary. The full study can be purchased here.

 

The end of Google Wave : both something logical and a half-truth

Summary : Google announced the end of Wave last week. Beyond the logical deception of those who adopted it and believed in it, many lessons can be learned from this project, most of all about the almost systematic failure of communications tools that don’t integrate with business contexts and processes. Anyway, maybe the deep nature of Wave was to be a software layer instead of a standalone product.

Google announced Wave was dead last week. According to their words :

But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects.

Since any downside has its upside, let’s try to find what can be learned from this adventure :

1°) Too good too early ?

Maybe Google was too early. That’s, in fact what Michael Arrington suggests and that’s surely a part of the explaination. That’s neither the first nor the last time such things happen and what happened to Apple in the late 80s/ early 90s should remind us that it can heppen to any company, that it may be harmful, but that it’s possible to recover from it.

2°) An half-cooked product

That’s the impression Wave made in the first times after its launching. Of course, it was continuously improved but it was too late to get the first deceived users back because they had other concerns than testing “one more tool” waiting for it to become usable. The worse thing in this story being that these users were supposed to be the power ones who should have lead the adoption. Fail.

On the other hand, Wave has been a very instructive experience because it demonstrates the limits of a powerful and rich stream : its lack of usability. I’m sure that many vendors that had similar things in project learned the lesson. We’ll discuss that in an upcoming post.

3°) Wrong positionning

Albeit powerful and rich, Wave was not, like Google Apps, Gmail and many other services, something anyone can master and understand quickly. To some extent it was rather an enterprise application, even if it doesn’t mean this positionning would have made things easier. Anyway, it was more a collaboration tool than a communication tool. On the web people communicate because they want and happen to collaborate by luck, in the workplace they collaborate by need and that may have made it easier to find the right early adoptions there.

[Read more...]

Freemium and enterprise software : frustrate the right person !

The freemium model, that is everyday more popular on the web, is now entering the world of enterprise software. What is it about ? Allowing people to use a software for free, with basic functiunalities that are enough for a minimal use, while proposing a premium version, richer, paying, and try to make most users switch to the latter once they’ve experiencied the free one.

The secret of the switch : make users feel they could do even more if they decide to use their credit card and pay. In fact it’s not a business model but a marketing tactics that leverages frustration. Has a good friend of mine often says : “that about showing a very small parts of one’s pants to give others ideas they didn’t have at the beginning”.

So this model in entering the enterprise with the same logic : allowing to start with simple usages for free and betting that, discovering everything that would be possible, organizations will switch to a paying version to host more users, have more functunalities which interest takes time to emerge etc…

Copying a model sometimes works…but translating it is better.

An easy way would be to apply the model that consists frustrating users who will always want more.. But a fundamental difference exists : when I’m on linkedIn or Flickr, when I want to go further with a service, I weight the pros and and the cons and if I come to the conclusion that’s worth the price, I take my credit card and I pay. But is the same in the workplace ?

Allowing people to upgrade themselves ? Unthinkable and not serious. Not only I can’t imagine that people would pay for what’s a corporate responsabilité but, more, I don’t think that enterprises would tolerate that users won’t be able to benefit from the same functiunlaties not depending on hierarchy but on their own will.

Thinking that people will ask their employer to upgrade ? Bad idea because frustration will be pushed from the end user to the administrator, the first not knowing what’s the cause of the limitation. More, nothings proves that, even if bombarded with requests, the administrator will be able to change anything since he doesn’t have the financial power. And I don’t imagine the administrator explaining that “we’re using a free version and don’t want to pay a cent to make users have more functiunalities”.

Conclusion : the frustration logics works when it impacts the person who can decide and pay or, sometimes, to someone who directly reports to him and can convince him with tangible arguments.

When you want to frustrate a decision make, you have to choose the right limitations. It will be more about scalability, number of licences, integration with existing tools than about practical things that improves the user experience but which benefits can’t be understood by people that have not the same use of the tool. On the other hand, frustrating the users by showing him everything he would be able to do but is impossible at this time is useless and even counter-productive. End users should even not be aware of the limitations, the risk of seeing them puting the tool in quarantine being very high.

When the freemium model is applied to enterprise software, it’s important to know who’s the right person to frustrate and decide of the limitations according to that. On the contrary, frustrating someone who does not have the power to pay to improve his experience is more than pointless: it’s dangerous.

Is Saas the future of your corporate IT ?

This is one more question that haunts many people’s night. More serioulsy, if it doesn’t make people stay awakened all nights long, it creates debates and brings some confusion that doesn’t help businesses to move forward. As a matter of fact deploying any solution is not that easy when one still have many infrastructure related concerns.

So, let’s try to get cleared idead about what’s going on.

Which debate ?

To make it short,  while companies have been used to host their information system on their own infrastructure are facing the emergence of an alternative solution, called Software as a Service, that makes possible to deliver applications through the internet, using services that are not hosted by its IT dept anymore but by external providers. The debate could be simple (I manage everything by myself vs I let others dealing with the issues and I pay for for service) but there are security and privacy concerns that are not trivial. Concerns that are legitimate even if, sometimes, the answer is simple, in a world where old habits have a very heavy weight.

[Read more...]

The future of cloud computing is not necessarily outside the firewall

Discussing wheter companies have to keep their information systemes within their walls or host it, wholly or partly, outside is a central issue.

The Saas or “cloud computing” logic majes sens. The time has come to take away the sacred aura of what,  as Nicholas Carrs  wrote in The Big Switch, is becoming as banal as electricity or running water. Plug, use, unplung. Nothing more. It’s a service like any other and the software + hardware duo is not a sacred cow anymore in people’s life. So why should it be so at the office. Today it’s nothing more than a simple computer and nothing more than software, it’s a part of my everyday life and the only thing that matters is that it does what I expect it to do. I don’t care how it’s done or whether my favorite software is on the net net or on my hard drive. Employee’s computers have shifted from a strategic good to a common consumer good.

[Read more...]

Is multitasking dangerous or a myth ?

Multitasking is a big issue for both people and organization. It’s the (presumed and made essential) ability for someone to do many things at the same time. The social media phenomenon and the increasing number of information flows people are exposed to are making this concern more and more central.

I’m afraid that, behing th multitasking question, hides a fundamental and dangerous erreur that may make us lose sight of what matters.

Human beings are not fully multitask. We can fully do ony one thing at the same time and it will last for years even if I can admit that in a few centurys our skills will surely imprve. Even Digital Natives are not more multitask than others.

Being multitask and being able to switch from one thing to another are often mistaken. New generations (but many other too) can quickly shuttle between two tasks, what is sometimes seen as being multitask. These people are able to transfer attention and energer between two things, what does not mean they adress them jointly.

But we also have to assume that, when attention is continuously transfered from one point to another, it loses intensity and the more multitask people are the more errors can be found in the tasks they achieve. If you need to be convinced, please read this note .

Some may find it disappointing since  because they used to see in multitasking the response to many concerns about productivity. But it’s not that bad : the impacts of multitasking would not all be positive. I already mentioned the risk of an higher failure rate. But there’s also another point : the impossibility to respect due dates. Imagine three tasks, A, B and C, whose duration is 10 (minutes, hour, days… ).

If they are carried out in a raw, the first will be achieved at H+10, the second at H+20, the third at H+30. Now imagine they are carried out in a fragmentary way, on a 5 minutes slot base. The result will look like that :

image-28

I didn’t even take into account the time needed to re-focus on each task. Maybe it can make it possible to finish a task earlier but, on a global scale, it doesn’t help people to save any time.

People are overwhelmed by signals and information that force them to try to multitask. At the end, it only lowers their productivity although communication tools are supposed to help them improve it. That is not becaue a message is received that it’s treated, and everyone has his own prioriies. But, obviously, those who send messages and those who conceive the tools that carry them, seem not to be paying any attention to that.

Being exposed to a lot of flows that condition their work, employees need to take leadership upon tools and to maser channels instead of being under a waterfall. By the way I like the analogy that consists of saying that a multi jet shower is something pleasant while being under a waterfall hurts.

The response to this issue has two sides

• The first is behavioral : employees have to learn how to turn flows off and achieve a task without being interrupted.

• The second is rather technical: tools employees are provided with must allow them to master flows and not to be their victims anymore. They must be able to priorize some, put some on hold, reroute some others and make things in order to ” if information is relevant it will find me…if not it will wait”. In brief, tools will have to make it possible for people to build their own information supply chain, whose timing, rate and content will be under their control, starting from a information marketplace, a kind of marshalling yard. A major issue for the software industry where social software will have to play its part.

I’m more productive when I get rid of the tools I use

After a long reflection I realized that the tools I use were the cause of a high level improductivity. And that the others gives me incredible services.

Try to pay attention to this in the upcomming days. Try to take some distance on your own experience, listen to your colleagues, you friends, and I’m sure you’ll draw the same conclusion.

When someone talks about “using” a tool or when you feel you’re using one, it means there’s a problem somewhere : the simple fact to be conscious of using someting creates a kind of disruption in our work, needs an effort. In brief : our efforts are not about our work anymore but about using tools that are supposed to help us doing our job.

[Read more...]