Skip to main content

Bertrand Duperrin's Library tagged implementation   View Popular, Search in Google

Sep
30
2011

"A growing number of companies talk about the benefits of adopting web 2.0 tools inside the organization, but the list is short for companies that are using them for increased business results.

Unisys, the 138-year old tech firm, has quickly made "going social" part of its culture. Here's how they did it, and how they're using social media tools to become more agile, to share knowledge, and to increase the speed of innovation."

socialbusiness enteprise2.0 productivity casestudies unisys strategy alignment technology pilot governance metrics implementation collaboration expertslocation

  •   

    One of the biggest barriers to social collaboration is a disconnect between aspirations to become collaborative and the reality of being a closed organization. Unisys CEO Ed Coleman addressed this through leading by example

  • Gloria Burke, Director of Knowledge Strategy & Governance, along with co-directors John Knab and Rajiv Prasad, launched Inside Unisys, a social network internal to the firm. Coleman began blogging and soon his senior executives encouraged their teams to do so as well. Employees are automatically alerted to blog postings and microblog postings on the newsfeeds on Inside Unisys. Over time, Unisys sales people began using Inside Unisys to share information about recent wins as well as share lessons in losses.
  • 5 more annotation(s)...
Aug
10
2011

"Sometimes there are postings on intranet discussion forums where people say “I’ve been asked to write an intranet strategy and was hoping I could have a look at somebody else’s”.

To me that’s a little like saying “I’m planning to have a really enjoyable holiday and was hoping I could come on yours”. Although seeing what somebody else does can be useful to get ideas, it is unlikely to be a good fit to your particular requirements. "

intranet strategy vision foals measurement implementation

  • 1. Vision or Purpose: What is the intranet for? 

     

    This innocuous-looking question can be hard to answer, but if you can get all your stakeholders to agree on this, then it stops an intranet programme being pulled in multiple directions. 

     

    Many strategies seem to state the blandly obvious, such as “To help Grotco communicate, collaborate and work more effectively”. The acid test is: given two otherwise equal options, does the vision guide you on which route to take?

  • 2. Goals : What are the 4-5 main things that the intranet will do in the future?

     

    This is where the intranet strategy should take a lead from an organisations’ strategy. So if your organisation aims to improve customer satisfaction, then a strong goal would show how the intranet could play a part in that: finding experts to solve problems, better tracking of issues to resolution or providing more accurate information to sales teams, for example.

     

    Some goals may be more inward-looking, such as ensuring 99% of employees can access the intranet. These are worth tracking, but won’t excite anyone, and may be better under “Implementation” (see below)

  • 2 more annotation(s)...
Nov
2
2010

"Luis Suarez (IBM) has been working in the areas of Knowledge Management, Collaboration, Online Communities and Social Computing for over a decade now. Here are some of his thoughts on that topic and his appearance at the Enterprise 2. SUMMIT."

enterprise2.0 luissuarez culture knowledgework knowledgeworkers implementation adoption sharing

  • Inside IBM we have put together, and shared across openly, such methodology from our internal social software adoption program called BlueIQ and folks can download a free copy of it by going into this URL to find out plenty more about the program I have been part of for the last three years.
  • you would need to have the best of both worlds combined as well; first, a commitment from top executives to support and lead rather actively your Enterprise 2.0 deployment efforts and, secondly, an online community, an army, of social software ambassadors and enthusiasts who will use plenty of grassroot efforts to help execute the various different activities that the internal adoption program may have set up itself to over time.
  • 2 more annotation(s)...
Aug
18
2010

"According to many, "resistance to change" is the biggest factor inhibiting the adoption of E2.0. This is not the case. The biggest inhibitor to the adoption of E2.0 technologies is when organizations attempt to make people use E2.0 tools - "make" being the operative word. This may seem subtle, but is an extremely critical distinction that separates tremendous success from puzzling failure with these technologies."

enterprise2.0 adoption implementation wording

  • In order to connect with the people who will ultimately touch some form of E2.0 technology, we need to rid our vocabulary of the words Wiki, Blog, Tag, RSS, Mashup, Microblogging and others that make sense to use, but mean nothing to end users.  In email example above, we do not talk about SMTP servers or TCP IP, but the about the value that an email brings to communication
Jan
8
2010

"About 19 months ago, I worked with the founder of BinaryPlex and creator of HiveMind, Tim Bull, to put together the 10 architectural principles for an Enterprise 2.0 implementation. Based on our experience since then, we have updated these principles. You'll notice that now we've removed 'architectural' from the title and now formally using the Enterprise 2.0 keyword. "

enterprise2.0 implementation

  • User controlled privacy, common security
  • Identity reuse
  • 8 more annotation(s)...
Nov
17
2009

"On a cru au départ au grand paradigme de la transformation globale et uniforme de l’entreprise traditionnelle en entreprise 2.0. La pratique est en train de prouver le contraire… En effet, plus je travaille avec mes clients au déploiement de stratégies Web 2.0 et de certains de ses outils à l’intérieur de leurs entreprises, plus je m’aperçois que ce déploiement doit se faire de façon graduelle, par projets pilotes."

enterprise2.0 pilots implementation communities communitiesofinterest communitiesofpractices projectcommunities

  • Premier niveau

     

    Comme nous venons de le voir, le premier niveau de communauté touche l’entreprise dans son ensemble. Des communautés que je nomme d’intérêt et qui sont ouvertes à tous les employés: profil personnel et professionnel à partager avec tous afin de faciliter la communication et la conversation, faciliter aussi l’identification des expertises et faciliter l’innovation participative.

  • Deuxième niveau

     

    À ce niveau, les communautés se spécialisent et deviennent des communautés de pratique, si chères aux spécialistes des ressources humaines qui ne jurent que par la gestion du savoir. En effet, c’est à ce niveau que les communautés génèrent des contenus d’expertise ou de mémoire d’entreprise™ à partager entre employés d’une même spécialité en vue d’un transfert générationnel.

  • 1 more annotation(s)...
Sep
16
2009

During our Insight Event last week, Sam Dimond (Director of Knowledge Systems) outlined his thoughts on how to get started with social tools, drawing from his experience of the adoption of blogs and wikis in Clifford Chance.

enterprise2.0 cliffordchance adoption implementation email collaboration wiki

This is the third in a series of interviews with Samuel Driessen, Information Architect at Océ, about their Enterprise 2.0 implementation and adoption experiences.

océ implementation informationarchitecture information informationmanagement structuredinformation unstructuredinformation integration

  • The information architecture is the glue that bonds business and IT components and it looks at both structured and unstructured information. The unstructured information can give context to the structured information.
  • In the past Océ could clearly distinguish the tools R&D and Manufacturing & Logistics (M&L) use. Only when data was transferred from R&D tools to M&L tools a joint responsibility existed. However, this led to silos and inefficiency. Now M&L needs more access, commitment and collaboration from R&D to be able to organize M&L in such a way to reduce such factors as lead time. There is a common product cycle management tool to help with this.
Aug
30
2009

There's an orthodoxy in Enterprise 2.0 circles about how you're supposed to run an implementation. The orthodoxy goes something like this: Start with small-scale pilots, define your business objectives, watch the pilots closely, evaluate their success, make a go/no-go decision. (A good recent articulation of this view is in Chris McGrath's recent post on 8 Tips for a Successful Social Intranet Pilot.)

As far as I can tell it's what everyone thinks. In fact, it's what I used to think. Unfortunately, it's dead wrong. The orthodoxy is wrong for a very simple reason: Size matters. By constraining the size of your pilot, you significantly alter the way your company can and will use the tools.

enterprise2.0 pilot implementation interactions metcalfslaw

  • There's an orthodoxy in Enterprise 2.0 circles about how you're supposed to run an implementation. The orthodoxy goes something like this: Start with small-scale pilots, define your business objectives, watch the pilots closely, evaluate their success, make a go/no-go decision. (A good recent articulation of this view is in Chris McGrath's recent post on 8 Tips for a Successful Social Intranet Pilot.)

    As far as I can tell it's what everyone thinks. In fact, it's what I used to think. Unfortunately, it's dead wrong. The orthodoxy is wrong for a very simple reason: Size matters. By constraining the size of your pilot, you significantly alter the way your company can and will use the tools.

  • An artificially constrained pilot is always a poor representation of post-pilot collaboration, because the range of potential interactions is so limited. The value delivered to each individual participant is exponentially smaller than it would be at full scale, and the ways that people will use the tool are different.
  • 1 more annotation(s)...
Aug
14
2009

The topic of corporate culture and social computing has been done to death but still seems to rumble on as an undercurrent for many blog posts. Views range from the suggestion that corporate culture needs to be right for social computing to succeed all the way through to suggestions that social computing can act as a catalyst for cultural change. Of course its never as clear as either of those academic stances and when you listen to people in workshops saying, "it's not about the technology, it's about the people," in the same breath as, "the platform has to be perfect," it becomes very apparent very quickly that there is confusion over where the optimum balance lies.

culture corporateculture technology adoption socialnetworks implementation

  • Let me start by saying the final aim of any social business program shouldn't be to find balance between technology and culture.
  • In a company with a good culture they'd see the benefit of sharing and make the best of the tools they have.  In a poor culture, one where there is fear or dislike of sharing, it's easy for people to use the drawbacks of the technology or process as an excuse not to share.  "It's too cumbersome to upload a document," "It's too difficult to find a time when everyone is available for a meeting." In this case an answer would be to set-up a blog platform.  Make the blog platform easy to use.  Make the process of posting to the blog wonderfully simple.  Those people who didn't share simple because the ways of sharing in the past weren't good enough will now be able to share.  Those who used technology as an excuse will still not share. 

I recently spoke with Samuel Driessen, Information Architect at Océ, about their enterprise micro-messaging experiences. Océ is a leading international provider of digital document management technology and services. Samuel is located in the Netherlands and his responsibilities include both the information architecture for structured data in applications such as PLMS and SAP and the unstructured content in places such as email and knowledge management programs.

océ microblogging yammer implementation adoption

  • The low barrier to entry helped expand the number of users. The intuitive and attractive interface also helped. Samuel said that there were only about 15 to 20 people using Twitter in the company when he introduced Yammer. Now there are over 250 Yammer users
  • about what they are doing and ask questions about their work while they work. Samuel has found that everyone who participates is very helpful and polite. There has been no bashing. He is collecting examples of where micro-messaging helped the organization.
  • 2 more annotation(s)...
Jul
29
2009

For the last 18 months, Intel has invested a significant effort to develop a full strategy & implementation roadmap for social computing within the enterprise. I am pleased to announce the release of a white paper Developing an Enterprise Social Computing Strategy that I did jointly with Malcolm Harkins, Chief of Information Security. The paper details our approach towards embracing the use of collaborative technologies while addressing the mitigation of legal, HR and governance issues. Here are some key areas you will find detailed in the paper

socialcomputing enterprise2.0 Intel businessvalue vendors security risk implementation

Jul
10
2009

Here are six conversations that I recommend occur in your organization that will help your organization bridge the cultural gap between the status quo and the organization as an effective user of Enterprise 2.0 tools. This builds on a previous post where I stated that "to optimize the technology and achieve improvements in organizational effectiveness...a focus on the overall organization is important."

enterprise2.0 culture implementation change changemanagement

  • A preliminary step prior to these six conversations is to educate members of the organization about these new Enterprise 2.0 tools. The matters to be shared include: the nature of the Enterprise 2.0 tools being deployed; how the tools compare with the popular Web 2.0 tools with which people may be familiar (Facebook, Twitter, blogs, bookmarking, wikis, search); how the new tools fit with existing tools being used
  • We can compare these behaviors, attitudes, norms and values to what exists in the current organization. We can ask, in what ways will we have to behave differently or need to develop different attitudes and values.
  • 4 more annotation(s)...
Jun
21
2009

Why are Enterprise 2.0 implementations of blogs, wikis, or forums not living up to the expectations of the technology?

The primary reason is because social media tools reflect the culture of the organization – they can’t change the culture of the organization by themselves. If the “social” part of social media doesn’t exist within your organization or is corrupted, all you’re going to end up with is “media” – a blog with no readers or a wiki with no edits.

enterprise2.0 implementation adoption culture

Jun
7
2009

Anyway, Social Software Tools: A Critical Evaluation offered useful insight into the choices SMBs need to make when moving into social networking. Tony Byrne, founder of CMS Watch, started with a useful breakdown of the complex world of social networking, beginning with separating external and internal applications, depending on whether the connections occur inside or outside your company:

socialnetworking smb usages adoption implementation

Jun
2
2009

A lot of organizations are struggling with what to do with a host of costly, high-maintenance technologies that they have introduced in the last decade, hoping these technologies would produce (a) improved internal productivity, and (b) better relationships with customers. They have achieved neither objective. So they're stuck with some very large and expensive lemons, three in particular:

implementation intranet organization socialnetworks adoption methodology enterprise2.0 problemsolving generationy

  • Real-Time Conversation: IM + Google Wave
  • Virtual Presence: Screensharing + Document Sharing:
  • 6 more annotation(s)...
May
23
2009

sks and benefits that must be considered in the governance process.

The Governance chapter contains:
* Definition of governance
* The importance of the governance
* Six steps in a typical governance process
* Worksheet on stakeholder interests
* Professional service firm case study

enterprise2.0 governance adoption implementation

Apr
24
2009

You seem to have nailed the technical aspects down but you’re missing or ignoring the most important aspects of this change. My business imperatives are simple: globalization, information management, innovation, speed, ROI, cost transformation, and survival. So when you come to my leader’s office, please be prepared to answer a few questions:

* How can I integrate these tools within my environment and address my imperatives?
* What do I need to do for my people? Training? Education? Transformation?
* What services can be added to the tools to serve my business needs?
* What solutions can you bring to table to have an immediate impact to my productivity?
* How do I convince my business managers to replace their current processes with you?
* How can I measure success and how will I know that I am heading down the right path?
* What patterns, templates, and success stories do you have to show me?

I have an enterprise full of people that claim to understand Web 2.0. What I need from you is the implication of 2.0 to my business model. My door is wide open and I am waiting for you,

enterprise2.0 implementation management information ROI innovation web2.0

I drew on the core ideas in our Implementing Enterprise 2.0 report and framework (as above). Enterprise 2.0 is ultimately far more about organizational change than technology, though it happens to be driven by web technologies. As such much of my focus today is on how to change organizations, to literally create the next version of the enterprise. Far more details on how to put the ideas below into practice are in the Implementing Enterprise 2.0 report.

My list got an extremely positive response from the audience, so I thought I’d share it here.

enterprise2.0 implementation vision bestpractices change changemanagement organizationalchange pilot

1 - 20 of 28 Next ›
Showing 20 items per page

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo
Move to top