Archive for April, 2010

Implementing Enterprise 2.0 at Océ Part Three: Change Management

April 30th, 2010

This is part three in a multi-part series on how Océ is implementing Enterprise 2.0 within their organization. Part one covered the business drivers of Enterprise 2.0, and part two covered making the push for Enterprise 2.0

Today I will cover how Océ dealt with change management issues.

Océ was faced with how to deal with the current company culture.  Traditionally, employees were not encouraged to ask questions or be open about personal doubts and ideas.  Employees were oftentimes perceived as being weak if they had doubts about something and as a result, they refrained from asking questions or challenging ideas.  This was a difficult challenge to overcome and I commend Samuel and Jan for being so open and honest about this.  They overcame this culture of closed communication by leading by example.  This meant a few things; the first is that Samuel and Jan had to show their peers that other organizations have successfully adopted an open culture of sharing ideas and expressing doubts and uncertainties.  The second is that Samuel and Jan had to “walk the talk” so to speak and lead by example.  They had to ask questions and openly express their doubts, uncertainties, and need for help.

At one point, a small department called “The New Media Lab” was formed to enable the use of social media while helping to implement new social media tools and ideas.  The “Lab” was comprised of a group of employees that were interested in new tools, technologies, and strategies.  They tested everything on themselves first before deciding to roll anything out.  Unfortunately, over time everyone dropped out of the Lab due to lack of interest, time, or understanding.  The only two people left to carry the Enterprise 2.0 torch were Samuel and Jan.  They were the two visionaries that continued to see the need for these new tools and strategies.

Organizational structure shifts and technology adoption

If  Océ really wanted to see success in Enterprise 2.0, then a silo-ed structure (what they currently have) would not be able to deal with these new tools and technologies.  Océ knew that some of the things they wanted to try with E2.0 were going to fail for various reasons such as lack of adoption, bad timing, or perhaps not meshing well with the existing culture.  Océ admits they are still making baby steps in making organizational structure shifts.  Currently they are trying to create a new department called the “Social Media Lab” that can deal with both internal and external collaboration efforts.  Océ was very candid and admitted that currently their organization structure has not changed much at all, which is making things a bit difficult.  This is becoming an issue not just with Enterprise 2.0 but with their external facing social media efforts as well.  There are different Twitter accounts, various blogs, many wikipedia entries, and bits and pieces of scattered information.  This is a problem because new things are happening but the organizational structure is not adapting.  There still needs to be alignment between new technology use and strategies and how the organization is structured to support these things.  I’m hoping that over time Océ will start to see these changes happen.

New technology adoption is never easy and in Océ’s case one of the challenges was not simply getting people to use the new tools but actually getting them to understand the concepts behind them such as trust and transparency.  The reality is that people are just fine with using email and don’t want to share their conversations or activity with the rest of the organization.  As with Vistaprint, Océ observed that it was challenging to get employees to use the wiki platform at first (they used Mediawiki, the same platform used by Vistaprint).  The issue was mainly platform specific as the interface is not that simple to use or intuitive.  Yammer, on the other hand was adopted much more easily and quickly.  Samuel and Jan pointed out that not everyone is an early adopter; it’s natural that some employees will lead the charge, while others will follow.  A normal adoption cycle exists and companies need to remember that.

Key takeaways
  • Océ had an interesting cultural issue to deal with: the perception of weakness and vulnerability.  They overcame this by leading by example.
  • New initiatives were first tested out on a small group of a employees (just a handful) to ensure that they were viable and possible.
  • Océ knew in advance that some things would fail and some would succeed.  It was a natural part of how things work.
  • No organizational shifts have happened up to this point, which is starting to make things difficult for the organization.  Eventually this will force change.
  • Companies must remember that adoption cycles for new tools and technologies do exist.  Some employees will always lead, others will always follow.
  • It’s not only important to get people to use the technologies but also to understand the concepts and ideas behind them, such as building trust and transparency

Implementing Enterprise 2.0 at Océ Part Two: Making the Push

April 29th, 2010

This is part two in a multi-part series on how Océ is implementing Enterprise 2.0 within their organization.  This post will cover how Océ made the push to implement Enterprise 2.0 within their organization.

If you missed it, part one covered the business drivers of Enterprise 2.0, which discussed why E2.0 was the solution to the challenges that Océ was faced with.  Today we are going to focus on change management.

In Part One of this series, I promised that we would talk about what tools and platforms Océ is using.  Here is the full list:

  • Wiki implemented in 2006
  • Internal blogs started in 2008
  • Océ TV launched in 2008
  • Microblogging (Yammer) began at end of 2008
  • Social bookmarking initiated in 2009

Clearly Océ has a lot going, but where did the push for all of this come from?

The push actually came from the bottom up; in fact there was hardly any push from the top down.  Océ as a company is a very bottom up organization.  The good news though is that Océ employees are allowed to try things and to experiment (starting in the R&D department).  Jan and Samuel started playing around with wikis to manage project information.  However, they found that the wiki platform was not really a good fit to manage project information.  It was much better at handling business process and methods and currently, that is exactly what the wiki does.  It’s also important to note that Océ doesn’t use the wiki much to manage any type of documents since it’s not good at it.  Again, this all started from their R&D department which is where people get to try new things.  The R&D department helped lead the push for many of the E2.0 initiatives and at the end of the day the wiki (media wiki) was also free, so that certainly helped eliminate any cost barriers.

Océ believes that it’s always important to justify the business case for everything that you do.  In the case of their wiki, Océ had a problem which was housing and organizing project information.  The wiki didn’t solved that problem, but it did solve another problem of managing process information which became the use case and that was the catalyst for getting the wiki created.

Despite all of this, there still needed to some sort of force of influence to really propel all of these efforts within Océ. Thankfully, Jan and Samuel had two key areas of influence and for lack of a better phrase, they “worked the system.”  It’s actually quite an interesting strategy that Jan and Samuel used (and should be commended for doing so).  Their two key areas of influence were:

1.  Steering committee for the intranet

  • Both Samuel and Jan are on the committee
  • They already had a vision and idea of where they wanted to go
  • Budget disappeared due to the recession so they went with free tools instead

2.  Jan works within the corporate communications department

  • He developed the communications plan
  • He selected the tools: “these are the tools corporate communications is going to use”
  • Department managers approved

Eventually the organization let Samuel and Jan take off with their ideas as they started to see things working.  It was very difficult to work between IT departments and business units but they were able to manage it.  With Samuel working in the IT department and Jan in corporate communications, they are able to work together to make it happen.  When Jan ran into IT issues, he brought in Samuel to support him and vice versa.  Security has also been an issue with IT and although there is a specific process to get IT projects done, it’s rarely followed in social media implementations (and I suspect this is true for many large companies).  Samuel and Jan oftentimes get grilled on their ideas but together they make a perfect team, bringing together both IT and corporate communications.

Key Takeaways
  • Océ’s efforts were a result of IT and a business unit (corporate communications) working together
  • The push came from the bottom up
  • Samuel and Jan had considerable influence in the right areas (IT and Communications)
  • Océ encourages employees to test and try things out (in the R&D department)
  • The business case had to be justified to get started
  • Although Samuel and Jan are in very different roles, they both support each other to really make things happen

Implementing Enterprise 2.0 at Océ, Part One: Business Drivers

April 28th, 2010

If you recall, I recently wrote an in-depth case study on how Vistaprint deployed Enterprise 2.0 initiatives within their organization.  Next up in the E2.0 case study series is Océ; a printing company with over 21,000 employees around the world.  I had the opportunity to speak with Samuel Driessen- Information Architect and Jan Van Veen- [...]

Presentation Slides On Social CRM from the New Communications Forum

April 27th, 2010

My site was recently hacked but I’m back!  Hope you guys had enough time to digest the social CRM evolution process that was stuck as my most recent post for the past week. I recently presented on Social CRM at the New Communications Forum in San Mateo and wanted to share my presentation with you.  [...]

Disaster with American Airlines

April 26th, 2010

My site was hacked so I was unable to post for the past few days.   I had one hell (literally) of an experience with American Airlines over the past two weeks that I wrote up on the business section of my site.  I wanted to share it with you here so when you get a [...]

The Evolution of the Social CRM Process

April 21st, 2010

A few weeks ago I wrote about the Social CRM Process (read this first before moving on) which received quite a lot of attention and feedback from the online community.  The process that I have created has since evolved to incorporate some additional ideas and elements which were originally missing.  I incorporated some feedback from [...]