Better collaboration does not mean better results for the organization

Summary : when we try to explain the new way of collaborating that’s expected in the workplace, it often looks like a lot of flows and interactions that has to form around every employee. But that’s overlooking one essential point : context. If interactions flows around employees, employees are organized around a production flow that aims at turning a request into a solution or answer. That’s the difference between collaboration to meet one’s goals and collaborating to create value. That’s essential because it makes us put individual actions into perspective and measure their usefulness and added value not in relation to the person performing them but to their contribution to the production flow, even if intangible and made of information. Conclusion : the value of any collaborative system does not rely on generic approaches but has to target the weakest link of the chain. The latter is not only weak because of the lack of collaboration tools but also because of organizational constraints that are peculiar to him.

Let’s take a few minutes to wonder about the sense, the goal of one’s activity in the workplace. We collaborate, exchange, solve problems (more or less efficiently)…but it’s only the micro part of a wider system. We tend to focus on individuals who “should” and “need to” without paying attention to their context.

At the beginning there’s an input, a request. It cames in the form of a simple question, a request to get a deliverable, a problem to solve. This input needs an output in return, that may be an answer, an operating model, a methodology to apply. If we have a closer look it appears that the whole organization is working this way, the input being either ‘can our product do such thing”, “how to fix this machine”, “what communication plan for our new product”, “designing our new intranet” or “how to hire someone with such or such skills”. It comes from someone who can be called customer, who can be either internal or external.

What does happen when this input is sent ? There are two possible situations : either it exists a methodology/process/procedure to manage the input or not.

In the first case we have a linear intangible flow with defined steps (creation, problem solving, design, validation etc…). Each of these tasks needs specific actions that themselves need information, knowledge, experience, expertise that that the owner of the task seldom have. If he can identify the right information/resource, he’ll use it to create/design/decide as fast and good as possible. If not he’ll do with what he has and push the work to the next person in the chain and so on until the final deliverable is issued, what is the output. Behind something that looks linear we have, in fact, a something that quite different and looks like a network even if, officially, things are supposed to be linear.

In the second case, the person that receives the input has to manage to find the way to process the input before starting to work. So he immediately falls into a network logic that, in the end, looks like the result of the previous case with on difference : there was no predifined role.

Let’s call “flow” the processus that ensures the transformation of the input into output (solution, answer), should it be linear or not. What is the major and most legitimate concern for any business ? (note that even if the matter that is transformed and the role of humain being has evolved, the problem has been the same for ages).

Improve both the output (that impacts created value and revenue) and its pace (productivity). Not more not less. But that’s already a lot.

Now, let’s find what’s needed to meet this goal. [Read more...]

Customer service : avoid being the victim of you social media success

Summary : while some businesses are puzzled towards the lack of success of their customer service initiatives on social media, others are trying to find solutions to face the increase of contacts and interactions. Hence the hasty conclusion that social media don’t scale. That’s a big mistake. The only fact that the point of contact is overloaded shows that the media scale. What does not is the bandwidth of the system that prevents from processing all customers requests. This limit is not peculiar to the media but to the processus it supports and that can only be removed by organizational actions. The capacity of the point of contact, should it be called community manager or anything else, can be improved by adding more resources, improving the system, redefining people’s tasks and, most of all, refocusing on exception management.

I often say that organizations that use social media for customer relationship purposes split in two groups : those that won’t take any benefit from it and those that will be overwhelmed with their success. In both cases, things have to be made to improve the situation.

• Those that don’t benefit from their initiative : poor understanding of customer expectations, interaction refusal,  absence of a service logic in communication activities.

• Those that are victim of their success : their understood what was the good positioning, had the right proposition of value for their customers…and were so successful that they can’t keep up with the load, what prevent them for keeping their promises and, then, creates a deceptive feeling among their customers that spreads and harm their reputation.

Today, I’d like to focus on this second group.

To find themselves in such a situation that can be described as a “rich people problem”, these businesses understood that beyond community management they had to have a processus approach. Since they offered an actual added value, they met their audience. But, either because of an exceptional event or a linear increase of the workload, they can’t keep up with their commitment anymore.

I’ve been observing something for a couple of months : many organizations that are successful with external facing social media initiatives realize that the internal organization has to be aligned too. Community managers (or whatever you call them) need to interact with internal resources to find solutions to customer problems what implies they can identity and mobilize them. So it’s an expert location issue. If tools and organization don’t make these actions possible, community management becomes a bottleneck where problems pile up without being solved. In conclusion, a scalable channel was used to replicate the same kind of bottlenecks that exist on the traditional channels they were supposed to make up for.

Should iy be executed in a linear or networked way, a processus has a constraint : its bandwidth, determined by the step that at the lowest processing capability. In our example, community management is the constraint of the processus. Said in other words, improving anything in the customer service processus will be without any effect and won’t change anything for customers since the limit is the community manager(s).

Like many airlines, British Airways is using twitter to solve customers problems. Everything works well in normal times but when snow begins to block european airports the switchboard explodes, as this tweet from R. Ray Wang mentioned :

In fact I think that this conclusion is a mistake : this is not the media that doesn’t scale but there a bottleck that limits the scalability of the processus it supports. The only fact that they can’t keep up with tweets is a proof that the media scale, since the amout of incoming messages exploded. What does not scale is the processing.

[Read more...]

Does your enterprise social network really make you more productive ?

Summary : one of the most frequent arguments used in favor of the implementation of an internal social network is productivity improvement through the ability to access and mobilize resources more easily. While that’s an undisputable truth at the individual level (and provided the tool is used by enough people), it does not mean that the company is made more productive : optimizing tasks and optimizing the chain of tasks that lead to the final deliverable, what is the only thing that counts, are not the same thing. So, companies will have to consider their whole production processus and identify their bottlenecks that prevent the chain from taking the most of local improvements.

One of the promises that usually come with a social network (and even with “anything 2.0″) is that some time will be saved. Since, in order to deliver the expected results, people and knowledges have to be put together in order to make progress along a processus, the more these resources are available and accessible, the faster problems are solved, solutions are found and the better decisions are.

So, here’s a very usual indicator : if any employee losts 38 minutes a day to find information, documents or people, if he can save 5, 10 or 15 minutes a day, it means x minutes a week, y minutes a year, what can easily be turned into money. By saving 5 minutes a day, your employees will make you save billions every year.

Hearing such a thing, and even if the promise is seducing and the logics credible, many managers feel there’s something wrong and they’re often right : 5 minutes saved every day, or even 30 may equal to…no saving for the company. But we must not throw the baby out with the bathwater : it’s possible to deliver the promise provided we focus on the right thing.

5 minutes saved at the employee level are…saved at the employee level

So imagine that an employee can save these much-touted 5 minutes a day ? Does it mean that he’ll be productive 1/2h more a week ? 5 minutes is the time for a coffee  break and there are many chances he will use the time he saved for his own purpose. He may also use it to cool off, knowing that even unconsciously he’ll adapt his pace to deliver at the due date. So if he realizes he can save time on some tasks there are many chances that he’ll take advantage of that to slow down or start later. I don’t even mention the case when these five minutes are 20 times 15 seconds…

Of course that’s a positive thing for the organization if employees can cool off, take the time to discuss etc… But that’s not what they were expecting at the beginning..

Optimizing tasks is useless

In fact, the whole value proposal relies on the optimization of a given task : search (whatever people are looking for). Yet, search is only one task, even a sub-task, in a more global processus.

Finding the right information or the right person helps to achieve any assigned task faster. So they can start the next earlier and so on and, at the end of the week, they would be more productive. That’s good for their individual evaluation and they’ll even be rewarded. But what’s the benefit for the organization ? None. The organization may even lose by rewarding people for something that did not change anything.

Generally, people are a link in a much longer chain. The task one achieves is necessary for another to start his part of the work and so on. If the first does things faster but the one who have to carry on or the manager that has to validate are not able to react as fast, some time will be saved for one employee but nothing will change for the company because the overall performance of the whole processus won’t be improved and, at the end, the client (internal or external) won’t be served faster. The only consequence of one employee being more productive is more files, emails and to dos for the others. That increases the pressure on the othere, brings more confusion, make things more complicated because they have to re-priorize things continuoulsy and disperse. In the worst case they’ll try to increase theyr own pace to keep up the with other’s and make more mistakes.

Optimizing people’s work at an individual scale seldom brings the expected results if the processus is not rethought and limiting factors, bottlenecks are not dealed with. It implies individual needs and actions are seen as understood as a part of a longer process that is sometimes formalized, sometimes informal (so to be identified).

It reminds me of a situation I had to deal with a few years ago. A manager was complaining that, despite of all the many undertaken efforts, the productivity of his team was not improving. Of course, he was thinking that employees had to be blamed on for that while the whole staff was close to explode due to the impressive amount of work they had to do and the high level of pressure. At the end, it was made clear that, since the manager had to validate all the files his staff has worked on before pushing it to another team…he didn’t have enough time to deal with all his team was producing. All the efforts the make the team more productive were dashed because he didn’t paid attention to his own role in the processus.

Understanding the whole processus is mandatory

So, it’s easy to understand that, once people’s day to day work has been explored with them and that some new practices that may make them more efficient, productive, have been identified, it’s important to think it as a part of a more global chain, to understand what one’s job serves (and whom), and look for bottlenecks. These bottlecks limit the overall performance of the chain and are often people at the center of a network (even informal), those most of the information has to go through. So they may be managers.

Then, each case has its own story, context and solution. Maybe the decision making process is not relevant, maybe an “a priori” validation is not necessary since corrections can be made afterwards when needed, maybe this part of the job can be handle by other people, maybe the only fact he can access his business tools while away from the office would be enough, maybe the “innovation board” does not meet often enough to deal with all the ideas that are submitted….

“Anything 2.0″ can make many things more fluid but won’t solve the bottlneck question that bridle “anyhting 2.0″ and prevent it from bringing significant performance improvements. Now it’s up to HR and managers to deal with that.

Finally it’s a very old debate that is much older than enterprise 2.0, it’s all about the pursuit of a local maximum vs. a global optimum.

Anyway, measuring any link of the chain is often misleading : what has to be optimized and measured is the whole chain.

Managing attention : a key challenge for the future of businesses

I’ve been willing to tackle this topic for a long time and seing Julien le Nestour‘s presentation at the last Enterprise 2.0 forum made me feel it was high time to put my thoughts in words.

Facing an increasing amount of information and considering the time we need to peruse, process, generate it, time is a key factor. In fact, even ignoring information takes time. But, on the other hand, I’m convinced that the assertion that we’ve reached a point of no return, that we don’t have time anymore to deal with more information is wrong. We don’t have a time problem but a prioritisation one. The point is not to have less accessible information but a better qualification of the information that’s pushed to us (the rest being accessible,findable in case of need) and a better hierarchisation to be able to handle what matters first.

These prioritisation and hierarchisation issues matter even more now that many enterprises and vendors realize that providing users with a unified collaboration context (ie the “unique customized home page” or “unique activity stream”) will be a major issue in the upcoming months. In the general public web we already saw a first attempt with Google  Wave : a service with a really impressive potential that was quickly deserted by those who were supposed to be its power users, those who had to centralize a large amount of information feeds in an unique interface and for whom prioritisation and hierarchisation were the missing feature. On the business side and according to what I saw at Lotusphere, Lotus Notes is also heading this way and I bet that the success of this new approach will highly depend on how the product will handle these issues. If it doesn’t…

So we have to identify some objective criterias for prioritisation. To make it simple, we can say that prioritisation depends on the value created while handling the information. For instance, spending one hour to answer a colleague who needs some information to handle a strategic activity or task is more important than spending one hour to read emails (or anything else) that are nothing but “for your information” emssages.

The same logics applies when trying to introduce a new tool in a context where the ROI is known for being very hard to get. So, Julien showed us of Schlumberger used another indicator called ROA (Return on attention) that helps to evaluate how a new tool is worth according to the value of the time of the user, the number of occurence of a given task and its criticality in a given use case (ok…I simplified it a lot).  This allows not only to easily justify a new tool according to its benefits compared to the current situation but also to take into account the importance of things like ergonomics in an arbitration thats supposed to be economical. As a matter of fact, maybe the best enterprise social software platform on the market has a blog feature but if the interface is so boor that the time people will spend to understand and use it will not be justified by the benefit in return, it’s better to take a tool that’s less “prestigious” but that will be easily used by anybody.

There’s also one more layer of complexity. Prioritisation is not only a matter of individual arbitration but a collective dynamic. I prioritize according to my own benefits and objectives, the anyone who sends me information prioritizes according to is own objectives. What can be strategic for one may be trivial for the other. So it’s important to have some “nice behaviors policies” (think about the other, wonder what is necessary…) and some arbitration mechanisms (when should I help, when should I say no…)

All these questions have to be tackled when tools are implemented, in the change management process and, beforehand, by vendors who won’t be able any longer to afford building bottlenecks and let users sort them out. These bottlenecks are a key issue in enterprise performance and have to be tackled in a systemic and coherent way by tools, business practices, management and organization.

Since real time seems to be a very trendy topic now, understanding its limits according to prioritisation issues may be quite useful.

I’ll conclude quoting Julien Le Nestour : attention is now a key resource, it’s scarce and constrained so its use have to be optimized in priority, even before funding.

Email, hamsters and bottlenecks

A few weeks ago, I was a part of a panel intiatied by Yann Gourvennec,  with Vincent Berthelot and Emilie Ogez. At the beginning there was a book , The Hamster Revolution: How to Manage Your Email Before It Manages You that caught Yann’s attention. So he gathered a few “experts” in order to discuss some of the traditional email related issues. I’m not sure sharing the video is very useful since it’s all in French without subtitles, but I’ll take advantage of it to explain some of my thoughts, what we said and what we didn’t say..

So let’s start.

[Read more...]

When does the value of a “social object” have to be measured ?

Let’s be clear, I’m talking about value, not about ROI (although the one is a part of the other) and about “social objects” in the large sense of the word : everything that can exist on a social platform, when using social software. It may be a content, an information specially generated, an information shared from elsewhere, a mark given to any contribution, the contribution to a collaborative work…but also the time taken to do so, the attention mobilized while the person may have had something else to do at this time etc…

Behind the everlasting discussions about ROI stands, before all, the question of the value. Does what is done have value, and what value ? In which ways an information and the time needed to publish it can have any value ? You’ll notice that it turns the ROI question not into something about tools and contents but into something wider made of tools, contents, resources and …the context in which the information is used.

That is a point that is often forgotten : it’s the context that determines values, it’s its limiting factor, more than the intrinsic value of the information itself. An insignificant information may be very valuable at a given moment for a given person even though thousands people will have nothing to do with it. On the other hand, a capital information have no value if nobody uses it. It takes us back to a reflection I’ve had a long time ago about strategy maps : intangibles have no intrinsic value but their value depends on how it’s used.

Talking about an enterprise context, let’s make it clear that “value” means the ability to turn information into money.

So the point, not that trivial, is to know when value has to be measured.

[Read more...]

I’m a bottleneck…but I try to improve

I wrote “I”…as I could I written “us”, “you”… a little story that’s, of course, imaginary. Any similarity whith any existing situation or people is accidental.

Finally, I did it well. Slowly, step by step, I climbed up the company’s hierarchy and took more and more responsabilities.

Today, I’m managing a large team. I’m responsible for my team’s results so I take care of everyhting and do my best to keep everything under control. Nothing is done without my approval. And nothing can happen if I’m not informed. As time went by I become a little less directive, more mature. I know that giving orders and setting objectives is not enough. So I’m trying to do make myself avaible to help my staff, to help them to carry on.

I also have many internal responsabilities. On many strategic fields, nothing is done without consulting me. I’m involved in many internal think tanks, advisory groups. The company does nothing until such a group has spent a long time thinking about what has to be done and how.

I don’t even mention the relations with key clients and partners, which is my exclusive domain.

That’s not easy everyday. The people I’m in contact with are as busy as me. It’s very hard to find a moment to discuss together, to make the decisions that break deadlocks. And this can’t be done by email. It’s even worth with internal meetings, because we have to deal with the schedules of sometimes ten or fifteen very busy people. What a pity : most of times, only five are really active, the other being a part of the decorum. Sometimes I’m one of the five. Sometimes I wonder what I’m doing there. A short report would be enough, just to let me know what has been said and decided.

In short : I’m responsible and essential. Nothing can be done without me. So you can imagine how much money my company makes thanks to me.

Humm… I have to admit that sometimes I’m doubtful.

[Read more...]