Enterprise 2.0 and ROI : forget the “whether” and focus on the “how”.

Summary : even if the concep of ROI, in its traditional sense, hardly hardly works for enterprise 2.0, overlooking the question of tangible benefits tha should be expected is impossible. But the reasonnings on this issue suffer from a noticeable bias : technology is assessed in the current context while it needs organizational and management changes to deliver its effects. So there are few chances to have a solid demonstration if the focus is kept on the existence of ROI without a joint reflexion on how to make it happen.

The ROI of Enterprise 2.0 is interesting because it’s at the same time unavoidable and a problem that’s impossible to solve without rethinking the whole paradigm of value creation.

First, I’d like state something. I’m using the word ROI because it’s the one we all use to discuss this point while I think that “measurable improvement” would be more relevant.

Then, I’ll start with a metaphor. If a logical and rational thinking makes us deduct that an engine is the best solution to make a car move and that, despite your car has one that works, your car don’t move when you accelerate, it may mean two things. The first is that ou forgot to shift the gear box on the right position, the second is that it’s not connected to the transmission. Instead to trying to fix the engine or throwing it away, what needs a fix is the transmission.

Then let’s talk about ROA (return on assets). The number is well known but John Hagel recently reminded it to us : it has dropped to 25% of what it was in 1965 while people’s productivity has been skyrocketting in the meanwhile. Conclusion : that’s not employees that don’t pedal fast enough but the organization that struggles at turning their effort into value. So the solution is not to blame employees and put even more pressure on them but to rethink the way work is organized and people are managed.

Now, have a look at new ways of doing things and the tools that support them. Anyone with few objectivity understands that the easier it is for employees to access resources and expertises in a fluid way that helps to save time, the quicker problem solving and the better made decisions made will be. But since this system is hardly systematizable, organizations keep their old way of doying things. What means telling the cyclist to pedal harder and harder while the chain is broken.

So the true question about ROI is not to know if it exists but how to turn a potential into actual benefits. This is not about social media or behaviors (even if it will play a part) but about “plumbing”.

That’s exactly what I wrote a couple of years ago about strategy maps and intangible assets :

• Value creation is indirect : intangible assets don’t create value by themselves, but through their use in business process.

• Value is contextual : the value of intangible assets depends on their alignment with strategy

• Value is potential : if business process don’t use those assets, their value remain potential and can’t be fully realized.

• Assets are bundled : intangible assets have to be use in conjuction with tangible assets.

So it’s logacally difficult if not impossible to demonstrate any kind of benefit and, most all all, to measure them, if the question of alignment has not been tackled and if processes have not been designed or fixed to actually rely more on intangible assets.

Organizations have to forget the old principle according to which tools ahave an endogenous value : the value of social tools is exogenous and can’t be delivered if tools are not used in the context of adapted processes.

So there are chances we keep on discussing the ROI of Enterprise 2.0 again and again for years if the focus is kept on “whether” it exists instead of “how to deliver it”. Even people who are convinced and don’t care about the “if” shoud care of the ‘how” that ensures that processes will be able to turn the potential into tangible benefits.

As my good friend Luis Suarez rencently wrote, we should learn to work smarter, not harder. Lett me add : provided we avoid to pedal better but in emptiness.

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.

Enterprise 2.0 and processes : what are we talking about ? (and why…)

Summary : the business process issue recently burst into the enterprise 2.0 world. Sacrilege for some, pragmatic approach without which no value will be created for others, it seems we’ve reach a tipping point. But what are we really talking about ? It’s not about turning unstructured activities into processes but to make it serve processes without distorting it. Then, if we define process as a set of tasks that gives structures to production, it’s important not to mistake what processes applied to some kind of activities should be with what businesses have been used to do for decades. It’s about production as it should be and not as it is today. That said, knowing why this approach is emerging matters too. There are many reasons to that and they are inequally worth but it does not matter : even if many things have to be done out of the process field, this issue will have to be tackled one day or the other. It does not matter anyone wants to change them, keep them unchanged or break them down : they can’t be overlooked.

Big agitation in the small enterprise 2.0 word : since some people at the last Enterprise 2.0 conference suggested that business processes had to be taken into account this topic has become very trendy. Salutary brainwave for those who see there the evidence that enterprise 2.0 is not a funny gadget disconnected from reality and unable to deliver any measurable benefit, crime of lese-majesty for those who see a horde of hungry wolves entering a house full of little red riding hoods.

Cela fait plus d’un an que je milite en faveur de cette approche (ou en tout cas de ne pas refuser de l’aborder et être dans le deni permanent) et je ne vais donc pas me priver de commenter la chose.

What are we talking about ? (Or the story of a big misunderstanding)

The word process is so scaring for some that they run away as soon as they hear it without even listening to the rest of the sentence. It’s not about turning informal and unstructured dynamics into carve-ups but making sure all the energy goes in the right direction. As I said earlier, serendipity is a very limited model for value creation and I find legitimate that businesses want channel what looks like chaos to them. As Rex Lee brillantly wrote recently :

Enterprise 1.0, would suggest that only specialized, trained individuals with the resources knew how to find pearls (i.e. where to dive, specialized equipment, knowledge on how to abstract the pearl from the shelled mollusk, etc.)

.
Enterprise 2.0 suggests that we can simplify and remove some of the “specialization” barriers to enable more people to search for pearls.

Enterprise 2.1 would suggest that rather than “serendipitously” finding pearls, that we coordinate our efforts to actually create pearl farms.

The purpose of any business is to create value and to do so it tries to optimize its production. Nothing shoking here. So sets of tasks are defined in order to make things more predictable, manageable and cost efficient. It often ends with a very rigid result and that often is the main point of friction.

In a manufacturing world, where production flows are tangible and can be normalized, rigidity is well adapated, exceptions to the rule being very rare. In a world where people work on knowledge, continuously solve problems, exceptions are the new normality and rigidity only works in a few cases. [Read more...]

Putting conversation into processes

Summary : nowadays, people need to continuously solve problems to execute business processes. To do so they need a quick and easy assess to knowledge. But knowledge needs stimulis to be expressed, what seldom happes out of conversational logics. Traditional processes need to be enriched with a social layer. On top of that, business processes are the smallest common denominator upon which an enterprise 2.0 dynamic can start without having to deal too much with cultural issues because it brings a focus to what makes sense for anyone : solving actual issues they face while they tried to achieve what they are evaluated on.

There are many ways to deal with the articulation of enterprise 2.0 dynamics with business processes. Here’s the presentation I made at the Enterprise 2.0 Forum in Milan in June.

And here are some explainations… [Read more...]

How to understand and position enterprise 2.0 in the real enterprise

It’s time to sum up all the thoughts I had these last months. I tried to start from both the concerns expressed by C level managers asking for a global vision and ground managers who needed a “hands on” vision because they don’t have time to waste to try to understand such nebulous things. Having to focus on day to day delivery and short term objectives, many see such a fallen-from-the-sky (and on their head) gift as a source of misunderstanding and discomfort.

These concerns are not surprising at all : what is it, what does it bring, how does it work, how to position it and integrate it in the organization as it is today… Talking about a new discipline, lots of things were learnt from early adopters who worked on a “try / fail / improve” model and, in so doing, helped to build a knowledge and know-how corpus. As a matter of fact this corpus was build upon failed and successfull implementations that helped to refine some presupposition that were prevailing at their beginning. The whole helped “followers” to benefit from these experiences.

But we still have to be aware that that’s not by saying “that’s that, that’s not that, one must, one must not” that things will improve. Businesses need to undersand the path that lead to these conclusions to make them theirs, and we all know what happens when one content himself with copying a result without understanding what reasonning often leads to  : lack of self-confidence, fear of the unknown, defensive attitude….then failure.

Rather than proposing an attractive future at the end of a vague road, let’s start from what actually exist to build the future. This will also help to explain the “why”, relying on what can be learnt from past experiences.

[Read more...]

You want your employees to be more “social” ? Rely on their selfishness

Among all the projects that have a “2.0 label”, it’s possible to make a distinction between those that are mainly about social networkings and those that aim at bringing traditional office applications on the cloud. Each kind addresses specific needs and has its own barriers.  In one case it’s about changing the way people work, in the other it’s about making them use their browser instead of their usual desktop application, what makes me say it’s more about Office 2.0 than enterprise 2.0. In both cases, getting over IT depts’ reluctance is everything but trivial, Office 2.0 seems to be less sensible on an adoption side since it does not impact people’s behaviors that much : they will still write docuemtns, fill spreadshits, but in another interface (but I’m not saying that’s easy !) I’ll also add that applications like Google Docs makes it possible to make giant steps in collaboration (or rather co-building…). All the people I’ve that who once worked on both kind of projects told me the same thing : “Office 2.0 is simpler (or less hard) than enterprise 2.0. But collaboration matters in Office 2.0 too, even if less developped than in Enterprise 2.0″. Understanding what that means may be of some importance.

Who would accept to make everything he writes on his word processor public ? No one. In the other hand, starting a work on one’s own and invite people to collaborate as and when needed because some help is needed, because it’s better to ask a specialist to write a specific part, because proof-reading is needed or because the manager needs to know how things are going on without getting a daily report makes a lot of sense. One starts on his own and widens the scope of the human, social and knowledge capital that is used he can’t do more, when he realizes he won’t be able to deliver on time or when he faces his limits. I think that enterprise 2.0 has a lot to learn from that, most of all on the adoption side. What drives collaboration is “me, the goals I’m assigned, my tasks, my issued”, and if we want to bring people to the logic that will make them help their colleagues, they first need to understand how this logic will serve them. Then for the same reasons they bring themselves to “invite” people on their Google Docs, they’ll initiate the famous conversations that are so important in the 2.0 culture.

That’s the evidence that, for 99% workers, things are not social by nature but by need. Everything starts with a (personal) taks, with (personal) limits that are faced and with the need of making all these things “social” in order to get out of the situation. Such a logic can lead to a systematic sharing not because people want to share but because they realize they have to. Conversely, any systematic sharing that would not be the result of this reasonning would be against people’s nature and causes apprehension.

What conclusions can we draw ?

[Read more...]

Enterprise 2.0 : adoption through social routine

Nearly everydody now admits that the only way to make a social software project succeed (and make people adopt the new tools) and be a source of value is to link it to the core of employee’s day to day job and life. What implies some attention as to be paid to a few trivial things as BPM, worflows, processes…

This does not mean that what exists has to thrown away. There are things that has to be made such a way, tasks that have to be made in a certain order, steps that has to be followed in order to make operations under control, for quality reasons, in order to avoid leaving in a world of approximation. Changing how things are done does not mean changing what is done.

The challenge of any enterprise 2.0 project is not to get rid of all these things but, on the contrary, to find its place inside. Studying the way everyone’s job is done does not mean it has be changed but facilitated. How ? By allowing people to rely on collective, social logics when it’s getting hard, if not impossible, to achieve a good work on their own? (Have a look here too).

So things are not (and above all in the begining) to rethink processes (most of all when they’re mission critical) but to widen their bandwith and increase the knowledge capital they use. That’s what enterprise 2.0 is all about.

[Read more...]

People Centric Organizations ? Not that sure…

One of the most common thing we can hear about enterprise 2.0 is that “it’s about people”. Even if it delivers a meaningful meassage, it brings more questions than it solves, leaving enterprises into doubt, if not in fear. I’m not even sure that everybody agree on what it means at the end. “It’s about people” is a bit like the “enterprise 2.0″ word : vague enough to gather many people, not defined enough to provide a framework for action.

What businesses may undersand is “power to people”, “people matter more than organization”. At the end they see a real threat to essential concepts such as organization/objectives/discipline/work. I think it’s a huge misunderstanding : it’s not about the cult of the “individual kingé” but about optimizing the way it’s used as a resource. That does not prevent from having an human vision of business, to value and give consideration to people, to help them develop and improve. But the main objective, let’s be honnest, is to make people give their best, to be sure that no talent or expertise is left unemployed. That’s the macro level. (Those who want to know more about the “union risk” must refer to this post by Oliver Young).

At the micro level, it’s considering people as the engines of the organization. And their knowledge and social capital as the fuel. A new kind a fuel that can’t be stocked, replaced or substitutable and which combustion is uncertain. By “uncertain”, I mean that it delivers energy when it wants, and decide of its energetic power according to its current mood and state of mind. That’s a big change, considering the times when companies owned the engine or the fuel. That’s the reason why things like motivation, sense, engagement, are more important than ever. So, “it’s about people” means that people are the factor that limit any change or transformation project. More, it’s a factor no company can’t do without. Even of some understand than once things are implemented, they’ll be able to take the most of everyone, it’s also important to understand that working on the human parameter is key to achieve anything, how great and fantastic social media tools can be. Culture, that is a point that many try to dispose of because of lack of courage, remains essential.

Then comes “User Generated Content”. Many businesses fear generating monsters, that’s to say the uncontrable popularity of employees trying to overpromote their own status, what would go against the seeked efficiency. With hindsight, experience shows that people are not the entry point to new practices but are only the fuel. Except for CxOs or recognized experts, people don’t focus on other people as such but because they are relevant from a business viewpoint. And that changes many things. A good example is Google wave: it’s the subject that aggregates people, that determines who has to be involved into a wave. That’s the same of every social tool : it’s all about outputs and people only exist through their ability to contribute to a given output. This shows the limits of personal branding strategies in the workplace. Anyway, what has to be understood is that it’s not a “people vs process debate”, on the contrary it’s about taking the most of people while following processes.

People are engines, essential, and deserve all our attention. But, at the end, in a corporate 2.0 context, they are not central points round which everything revolve but only exist through their ability to bring an added value. The “It’s about people” word is not absolute but has to be contextualized according to the expected outputs.

Even powered by people more than ever, enterprises are still objective driven productive organizations. We all should remind this.

capital informationnel, capital social, engagement, Entreprise 2.0, Management, medias sociaux, motivation, people-centrism, personal branding, process, Ressources Humaines, sens, social-media, syndicats, ugc

Is Netflix the right example of enterprise 2.0 ?

Netflix recently issued a 128 slides document explaining their culture, their organizational model, their management and the way they work. It attracted a lot of attention and  advise you to read it before carrying on.

View more presentations from reed2001.

According to many people, Netflix issued the reference enterprise 2.0 manifesto, or rather the management 2.0 manifesto.  What may we think of it ?

[Read more...]

Enterprise 2.0 : the truth is in the middle

As you may have notices in my latest posts (and it will continue in the future ones), questions related to enterprise 2.0 (the name does not matter, it’s one more evolution process as there were already many in the past, and a new name for many olds things), it’s not a matter of break but a matter of moderation and articulation.

- this is not a Gen Y vs Boomers debate, two generations that are very similar. The tipping point maybe on the intermediate generation, the X.

- that is not a debate about traditional tools vs new tools, but about the need to articulate both where it makes sense, according to the need for producing efficiently. The the example proves it : the technical part of enterprise 2.0 is often built by linking new tools and the old ones that the basis of every corporate IT infrastructure.

- It’s not a debate about new vs old ways to do one’s work. It’s a focus on what structures businesses with a concern for giving more flexibility and the ability to mobilize more relevat resources where and when it’s needed. The whole while ensuring that socialized activities provides a direct return to the core business.

- It’s not something that is done in the back or agains traditional corporate functions but by reconciliating them.

- It’s not about taking from managers the visibility on their staff’s work but providing them with tools in order they should not be submerged by information that prevent them from doing what they’re good at. On the contrary it’s about making them able to focus on what matters to them (helping their staff to reach their objectives) while still having the ability to have an overview on their work when they want and not being a victim of continuous information overload.

- It’s not a qualitative social capital vs measurable financial capital debate, but about using the one to serve the other, and really improve the way value is created and traced through this process.

- it is not a debate between upholders of a new vs an old world, but the search for a zone of convergence where both will work in synergies.

- it’s not a debate between internal and external practices, but about bridging the gap between both.

The list could be more longer. Anyway, it can be summed up in one sentence : start from what exists, be moderate, articulate. And remember that all businesses are different : nothing can be done that won’t be accepted by all stakeholders, culturally, technically and organizationally. Even the “E2.0 rockstars” started this way.

So stop having an exclusion approach and start finding the right middle that fits every different business.