Group items tagged

Workforce mobility and changing communication patterns are two more trends that are driving change at the infrastructure layer, and so unified communication and collaboration requirements form an important part of Enterprise 2.0 strategy.

Enterprise Web 2.0 might be about putting the user (i.e. employee, customer, or stakeholder) first, but in order to do so it also requires supporting technology. And so at the IT infrastructure level, Enterprise 2.0 means Internet Protocol (IP) everywhere -- voice, video, and data. Enterprise 2.0 also means, 'open' standards rather than proprietary or 'closed' systems. Furthermore, Enterprise 2.0 technology means user-driven technology and not IT-driven technology.

Having accepted the fact that 'processes' means 'people', then we have to look for ways in which these people (i.e. processes) can self-organise and reference one another. Then, where possible, we need to somehow incapsulate the processes into a set of business services. One day (we might call it Web 3.0), Artificial Intelligence (AI) will enable organisations to do with computers that which they do via human beings today, but until that day arrives, organisations must do more to aid interdepartment and inter-company collaboration. Workflow has not yet figured largely in the consumer-oriented world of Web 2.0, but Butler Group sees this as pivotal when considering Enterprise Web 2.0.

Today applications that embody processes are built by IT professionals, but tomorrow they will be built by a new breed of power user, using mashup builders, software agents, and other Web 2.0 technologies.

Business and IT managers must therefore prepare themselves for the new generation of power user who will be creating mashups and situational applications that have a far broader impact than the typical spreadsheet macro of yesteryear, and that if organisations are to avoid a proliferation of unmanageable, siloed, micro-applications, then they must blend the power of personal productivity with an appropriate management layer and a degree of central oversight.

Web 2.0 is no longer PC-centric.

It is clearly a mistake to think that Web 2.0 is all about technology, and likewise Enterprise Web 2.0, but it is also a mistake to dismiss the technology altogether. Therefore, selecting and implementing enterprise social software solutions, next-generation collaboration solutions, and Rich Internet Applications requires careful thought, consideration, and planning.

The driving force behind just about every aspect of Enterprise Web 2.0, is of course, the user -- something that has not always ranked highly on the list of priorities for corporate IT mangers -- and so the challenge for all forward-looking organisations is to refocus on this aspect of their IT strategies.

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.

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.

Create an internal Wikipedia that contains a seperate copy of all Intranet content and let users edit away.

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.

, 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.

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.

Peut on “upgrader” les seniors ? Oui, certains en tout cas. Mais pas en passant en force. Cette génération n’est pas foncièrement hermétique, mais l’expérience lui a également appris le recul et la circonspection. Et ils sont habitués à des cycles de changement beaucoup plus longs que ceux que nous connaissons et connaitrons à l’avenir. Le changement passera par l’exemple. Ils ne sont pas contre a priori, mais ils sont également les gardiens d’un système qui fonctionne (plus ou moins) tant que la preuve que quelque chose de plus efficace existe ne leur sera pas apportée de manière tangible. Bien sur qui ne tente rien n’a rien et, c’est peut être là le point d’achoppement principal, ils ont moins la culture de l’expérimentation que leurs successeurs.

Bref nous entrons dans une ère de transition où on devra s’appuyer sur des seniors moteurs, en convaincre quelque autres, faire en sorte que les digital natives ne s’acculturent pas et utiliser la génération intermédiaire comme véritable cheville ouvrière

construire des synergies entre ces deux tendances qui seront les piliers de l’entreprise dès demain.

A moins que la réalité économique ne nous impose une transition plus abrupte…

Les outils seraient donc, à ce moment, le support d’une politique d’entreprise et ils y trouveraient de suite leur place par le besoin même de l’organisation.

Stratégie 2.0 implique ==> Management 2.0, Outils 2.0, marketing 2.0, recrutement 2.0, Rh 2.0 afin de construire ==> Entreprise 2.0.

Le projet entreprise 2.0 doit donc être un projet d’entreprise.

Darwin cherche à faire émerger les thèmes corrélés entre eux issus d’un environnement chaotique en se basant sur la mesure de corrélation vue dans la théorie du chaos. Ainsi, Darwin s'éloigne clairement des systèmes de classification par vote ou popularité actuellement utilisés par nombreux moteurs de recherche et aggregateurs de contenu pour ordonner leur résultats.

Darwin n’est pas un engin de remplacement des technologies entreprise 2.0, tableaux de bord, et autre outils de management des documents. Il est conçu pour compléter et renforcer ces technologies en rendant plus visible le savoir tacite enfermé dans leurs systèmes.

C’est une application internet (Scan Cloud™) ou cela peut aussi devenir une solution customisée grâce à l'accès API offert. Cela fonctionne sur un serveur Web avec des services et base de données qui corrèlent les différentes sources Web 2.0.

La question n’est pas de mettre du “social” partout et n’importe où mais d’en mettre là où cela contribue à faire mieux.

La socialisation permet donc ici d’identifier, mobiliser et faire intéragir de manière plus ou moins provisoire des personnes extérieures à l’équipe “formelle”. Voire de favoriser les intéractions au sein de cette équipe et favoriser la formalisation des expériences “au fil de l’eau”.

L’objectif est clair : rendre possible l’exécution d’un process, d’une succession de tâches, en minimisant les retards liés aux circonstances imprévues et en l’améliorant au vu des “correctifs” effectués.

ci on crée des intéractions en fonction de besoins réels, de problèmes quotidiens sans essayer de donner corps à d’hypothétiques communautés qu’on aimerait voir échanger dans le vide.

un process de résolution de problème et d’amélioration permanent. Une logique qui s’outille avec des wikis, blogs, profils riches, outils de microblogging, réseaux sociaux… mais dont la logique est compréhensible de tous.

Bien sur tout ne se socialise pas, d’une part, et selon des périmètres restreints, d’autre part. Parfois ce sera au sein d’une équipe, parfois au niveau de l’entreprise, parfois avec des clients, et d’autres avec le grand public.