inicio mail me! sindicaci;ón

Enterprise 2.0 Conference Notes: Reality Check with Andrew McAfee

by Bill Ives

Andrew McAfee led a panel of the Wednesday morning presenters, including the two I just posted on, Pete Fields and Simon Revell, as well as Sean Dennehy of the CIA (not the Culinary Institute of America but the other guys who did Intellipedia) and Ned Lerner from Sony. Here are some bits of wisdom from the panel in note format with some comments from me added in parens. First the panel itself thanks to Flickr.

World is changing – tools reflect this – but challenge is to get those who are still in old world to come over to new world and the new tools, especially middle management – people now feel they need “middle cover” not just top cover.

Now major changes happening within a life time – older people lived before computers and younger people who have never lived without computers – make for a very different mindset (I think us old guys are not given enough credit to adopt here. This is also not the first time such transformations have happen – think electricity, trains, planes, cars, telephones, etc. – My uncle’s father took his family on vacation to Colorado in a covered wagon and they followed the train tracks because there was not a good road. – I have told many of these types of stories on this blog and will not repeat them now. People are better at adopting to new technologies than adopting to new management styles.)

Act of leveraging tools is different as older people are more likely to use single tool for everything, younger use a variety tools. (more beating up on us old people. Tom Davenport has written and said that really productive knowledge workers tend to use one or two tools really well for multiple things. Shall we get another debate going here? It may be that younger people are using different tools rather than more tools.)

Many more people are readers than contributors at Sony in the game making area but that is okay as not everyone can be thought leaders – their employees were already using wikis when they introduced them inside in 04 – challenge was to get them to use their wiki.

Andrew said is it correct that senior management is not a block to enterprise 2.0 (by implication it is more middle management)? People in the panel implied that in their companies the answer seems to be yes. Transparency can be a good management tool if used correctly – enterprise 2.0 makes it easier to look directly at work. Getting middle management on board is more of the issue. Middle management’s task is to make things work now – change is disruptive to making trains run on time. (especially when planes are introduced)

Senior executives want truth so they pay millions to consultants to get it since they cannot get it from employees. (I remember being on a sales call as a consultant a number of years ago with a senior executive that was going south. We could not get his attention. As a last resort we said that “your people say you are the reason nothing gets done” – which was the truth - that got his attention, - he got up from his desk and came over to the table we were sitting at in the corner of his office and said that he never approves anything because he never sees anything worth approving – we actually won the work which was to develop a new plan and he did not throw us out of the office – we quickly spun the story with middle management as a way to get support for what they wanted – disclaimer - do not hold me responsible if you try this sales approach) – so perhaps a their is a desire from senior execs for the transparency that can come from these tools – (if used wisely). The question often heard from management – how to do enterprise 2.0 safely – not “do not do it” – they see value in transparency. (BTW - I also have heard senor executives say that they paid millions of dollars to consultants to do the work that they could not get their own employees to do. Perhaps enterprise 2.0 tools could help here also.)

Andrew asked for final recommendations from the panel –
1. One person said go for the big project with big impact – not safe small pilots (that is what he did)
2. Another person said start with a pilot to show value (I guess that is what he did)
3. Hardest thing to do is to give up control – if you do it employees will come through for you (and it is cheaper than hiring consultants to do what you want ☺). Andrew added advice from a mentor when first starting teaching – trust you students – he said when he did it always worked but it was hard to do– so this should translate to trusting employees

4. Fight lock down (from CIA guy) – other said yes - need scale to get network effects

5. Look at email in box and see where the clutter is and move this to a wiki or a blog

6. Need to show appreciation when people do get involved

Question from audience – enterprise 2.0 implies large scale - Are tools valuable for ten people companies – yes if energy – new people will be able to use the knowledge made accessible through these tools (I agree completely but for more reasons. I am now part of a four person start up and we have reached the point where we need a collaborative platform to get our planning and collaboration out of the dark hole of email. I went looking for one at the conference.)

I will have some more notes on Friday from another session.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • E-mail this story to a friend!
  • Print this article!
  • TwitThis
  • del.icio.us
  • Facebook
  • Reddit
  • bodytext
  • Google
  • StumbleUpon
  • SphereIt


2 Comments »

Jon HusbandJune 12th, 2008 at 12:07 am

Senior executives want truth so they pay millions to consultants to get it since they cannot get it from employees

how to do enterprise 2.0 safely – not “do not do it” – they see value in transparency. (BTW - I also have heard senor executives say that they paid millions of dollars to consultants to do the work that they could not get their own employees to do. Perhaps enterprise 2.0 tools could help here also

Like you, too many past posts to refer to with respect to these issues, but wanted to note that I have often suggested that opening up to blogs and wikis and not being overly concerned about controlling the activity that takes place on them could easily save lots of consulting fees paid re: attitude and climate surveys and culture change initiatives. Executives and middle managers could learn to LISTEN more, and take time to digest, reflect, etc. .. and if they say they don’t have the time to read, for example, aggregated comments, etc. they could be reminded of all the time they’ll save not being at meeting with communications and survey analysts and consultants.

It’s an attitude and culture thing, as has been mentioned ad infinitum over the past several years by people writing about E2.0 and related issues. It’s essentially the same points that OD consultants have been raising for the past 20 years or so .. why does it seem to take so much effort to understand ? Is it because everybody believes so deeply in “the hard stuff” .. measurement, six sigma, action at all costs, etc. ?

Bill IvesJune 12th, 2008 at 8:48 am

Jon - Agree completely. Last year at this same conference I was on a panel called 90% people and 10% technology - because many people says well it is actually “90% people and 10% technology” but the spend in the other portions or worse. I think part of it is the American focus on measurement on everything from wine to work. Here is a post I did in 2004 - Talking About Wine (& Complexity) – The New Yorker - http://billives.typepad.com/portals_and_km/2004/09/talking_about_w.html. In many things, including my local basketball team, it is not always what shows up on the stat sheets that matters. It is the intangibles but we do not tend to appreciate complexity - I think you guys north of the border are a bit better on this but we all could improve. Bill

» Subscribe to the RSS feed for these comments

Your comment

Want an image to appear near your comment? Go to gravatar.com

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>