Relative advantage : what value does it bring ?
Compatibility : how much effort to transition to this innovation ?
Complexity : how much learning is required to apply it ?
Triability : How easy is it to try the innovation ?
Observability : How visible are the results ?
None of these intangible assets (human, organizational and informational capital – i.e databases, Information systems, networks, technology infrastructure) has value that can be measured separately or independently.
Mc Afee still recommend to build some kind of business case with the following elements
People make relative evaluations
Reference point is status quo
People are loss-adverse : a prospective loss of X is 3 times more painful that a gain of X is pleasurable.
These elements lead to the fact that we value what we have far more highly that what we could have instead. The result is what Gourville calls the 9x effect : people rate what they have 3 times more than their actual value and prospective items three times less than what they’re actually worth. A new item must therefore be at least 9 times better to justify the (perceived) effort required for the adoption.
As a result, McAfee quotes Gourville and recommends not to oversell the collaborative platform and make it clear that the adoption will be a long phase.
The objectives is to help them realize that these tools are the root cause of many of their daily work frustrations
So a 30 days trial might not be enough to see the full benefits of such solutions. However it can still proves how easy it is to use them.
A good strategy to make the results visible is to locate some teams of social networks enthusiasts (IT or HR departments might be a first good guess). And start to deploy the solution on such narrow teams.
In a transparency and observability purpose, it might be a good idea to monitor the knowledge workers perceived value of their tools and measure the progress. Preparing a questionnaire with a set of questions around the subject of collaboration, innovation, productivity and knowledge management could be a good starting point.
factors that differentiate successful Enterprise 2.0 deployments from unsuccessful ones
things that are especially important to get right in order to succeed with E2.0. Italics denote difficulty— aspects of technology, initiatives, and culture that seem to be particularly hard to get right.
I’ve had for some time now the vague sense that the iPhone, Twitter, Gmail, Googling, Facebook, Wikipedia, Delicious, and other runaway successes are trying to tell us something about how we want to use technology in our lives and in our work, and if we enterprise technologists listen carefully we’ll hear what that something is.
I started jotting down some comparisons based on what I’ve seen, read, and experienced for myself, then realized that I was identifying patterns
I’m dividing my 2.0 vs. 1.0 comparisons into two groups. First is a set of patterns where 2.0 is just better than 1.0
Second is a set in which 2.0 is an alternative or addition to 1.0, not a replacement for it.
the primary goal of enterprise IT is not to delight users, but rather to increase the value of the company. But do these two outcomes have to be in conflict?
The biggest challenge will probably be to get corporate technologists (a group that includes IT departments, vendors, and consultants) to stop thinking like monopolists that can dictate tools to users with great confidence that, because of the lack of alternatives, they’ll get used.
I can think of four negative consequences of ignoring these patterns and continuing to act like a 1.0 enterprise technology monopolist.
enterprises will deploy technologies that are disliked and/or not used
employees will use ’stealth IT’ and any knowledge / information captured therein will not be retained by the enterprise
employees and customers will leave because of their frustration with poor enterprise technologies
the enterprise will be handicapped or crippled – less productive, innovative, collaborative, agile, ‘wise,’ foresightful, insightful, transparent, clear than it could be otherwise, or than its competitor is.
Il y a une véritable conduite du changement à mener et tout ne peut pas changer en un jour. Il s’agit de trouver vos champions qui vont apporter leur énergie au projet et vous aider à faire changer les choses.
Même s’il ne faut pas sous-estimer le potentiel d’une expérience lancé dans un service ou une direction et qui finit par faire tâche d’huile dans l’ensemble de l’entreprise. Mais dans ce cas encore, cet élargissement n’a été possible que par l’intermédiaire d’un sponsor haut placé qui a été convaincu par le projet. De fait, plutôt qu’opposer top-down et bottom-up autant trouver comment ces initiatives vont se compléter afin de donner de meilleurs résultats et produire des « guidelines » concrètes.
l faut un accompagnement et ce ne sont pas les outils qui sont déterminants, mais les modes de management qui y sont liés. Il faut laisser le temps aux collaborateurs de comprendre ce qu’on attend d’eux et qu’ils identifient les gains potentiels pour eux. Le deuxième point est la frilosité et le refus de prendre un petit risque pour introduire ces nouveaux modes de fonctionnement.
Des exemples comme ceux de Lockheed Martin, une société mondiale dans le secteur de l’aérospatiale et de la défense, montrent que malgré tout on peut basculer vers l’entreprise 2.0 (pourtant la question de la sécurité et du secret est au coeur de son business model). Ils ont eu la garantie qu’en cas de problème il pourrait identifier d’où cela proviendrait (pour le moment cela n’a jamais été le cas).
Il conclue enfin sur la question récurrente du ROI. Il ne s’agit pas de mesurer de nouveaux process avec d’anciennes recettes. Il s’agit plutôt d’identifier ses besoins et enjeux et voir si ces technologies peuvent y répondre.
In addition to Web 2.0 itself however, we have two more important enterprise software trends: Office 2.0 and Enterprise 2.0, coined by Ismael Ghalimi and Andrew McAfee respectively. Office 2.0 represents the increasing use of browser-based software in the office, while Enterprise 2.0 is more Web 2.0-ish in that it specifically describes the use of freeform, emergent, social software to conduct collaboration and share knowledge.
Specifically this means the fact that corporate information tends to be non-shared by default, that the easiest productivity tools to use are the ones that have very little collaboration built-in, and that the information that does exist is often impossible to find and is often structured in some formal, centrally controlled way.
Certainly, increased transparency, some loss of control over information flow, and outright abuse of low-barrier Intranet publishing tools gives enterprise IT and business leaders pause for thought.
And while some of it must remain under strict control, particularly in public companies, much of it is unnessarily — and usually to a fault — hidden, unreused, and unexploited.
Unexploited sources. Action: Implement a Wiki so as to share and keep up to date this wealth of information e.g. manuals, meeting agenda, minutes of meeting. This would act as the memory of the enterprise
Explain the reasoning behind retaining more knowledge, in making it public, searchable, and organizing it via tagging. Describe the benefits of being able to access much fresher and more up-to-date information elsewhere in the organization because their colleagues are managing more of their projects, tasks, and other work via social tools.
Provide useful templates for common activities and reference material such as projects, tasks, resource management, policies, procedures, standards, and so on. You still have to keep template layouts and template usage simple; excessive structure tends to kill the golden goose of contributions quickly. But a little basic structure goes a long way and prevents contributors from having to figure out how to structure all the white space and provide a simple layer of consistency.
The enterprise has not caught up, largely because most enterprise information doesn't allow a hyperlink structure, and links aren't encouraged very much when it does
setting up blog and wiki directories as well as good enterprise search based on link ranking (which is what Google does to make the right information come up in the first few pages of search results.)
Provide your own search engine in the tools only if you must.
, the real issue, day in and day out, with getting Enterprise 2.0 to take off is to educate, evangelize, demonstrate, and most importantly, evolve the interface and structure of your tools until you pick the right formula that resonates with your audience.
This boils down to having some form of moderation, either human or automated, to ensure that the level of discourse remains at some bare minimimum acceptable standard.
A high-profile executive sponsor that obviously uses the tools can also help in a big way.
Triggering an Enterprise 2.0 ecosystem quickly is likely an early activity driver. This can mean a lot of things but the link structure of Web tools allows information to quickly flow, circulate, and mesh together. You can leverage this in a almost infinite number of ways to drive user activity, interesting content, create awareness of what the company is "thinking", and more.
For example, create a blog for every employee in the company and mail the link to them with instructions on how to use it.
>
Create a social bookmarking site for the enterprise where everyone can see what is being bookmarked by everyone else that day.
>
Create an internal Wikipedia that contains a seperate copy of all Intranet content and let users edit away.
> The possibilities are endless and provide a much greater number of "entry points" where people can get started with these tools.
The problems will be with the business culture, not the technology.
For example, create a blog for every employee in the company and mail the link to them with instructions on how to use it.
Create a social bookmarking site for the enterprise where everyone can see what is being bookmarked by everyone else that day.
Create an internal Wikipedia that contains a seperate copy of all Intranet content and let users edit away.
Allowing the output of SQL queries to be inserted into wikis when they load, calling Web services or using Flash badges that access data resources can turn Enterprise 2.0 tools from pure knowledge management into actual hybrids of software and data
And the reverse should be true as well, getting data back out into traditional tools including Office documents, PDFs, and XML must be easy to inspire trust and lower barriers to use.