inicio mail me! sindicaci;ón

John Hagel: The Web 2.0 vs SOA Chasm

by Paula Thornton

With John Hagel on the speakers list for FASTforward ‘08, it seemed reasonable come up to speed on some of his more recent thoughts (if nothing else, to prepare ‘zinger’ questions for him). Somehow I stumbled first on comments about Web 2.0 and SOA, where I was struck by the dimensions of time and space in conversations: the reference to the date of his post had to be uncovered in small print at the bottom of several page views (I’ll let you discover what I mean), and more recent voices have offered perspectives I consider more reasonable, but these aren’t connected to his post (not a criticism, just an observation).

The fact that in his piece he calls out another FASTforward ‘08 speaker is even better. I found Hagel’s insistence that Andy McAfee overfocused on knowledge capture and not enough on knowledge creation interesting, because from the quotes Hagel included, McAfee was talking about access. He also suggested that McAfee and Nick Carr saw things from different perspectives, when, they appear to totally agree with one another. Indeed the Carr reference Hagel offers includes the following quote: “McAfee first explains why past knowledge management ’solutions’ rarely solved anything. He then explains what makes Web 2.0 technologies different. ‘The good news,’ he writes, is that the new technologies “focus not on capturing knowledge itself, but rather on the practices and output of knowledge workers.’” And McAfee responds to Carr in another reference offered by Hagel, “Hear, hear.  The spread of Enterprise 2.0 technologies is definitely not a sure bet, and one of my deepest professional nightmares is being a hype merchant for each new IT gizmo that comes along.”

I did find Hagel’s specific advice about bridging the chasm between SOA and Web 2.0 interesting (but admittedly a bit one-sided):

“What is required to break this SOA logjam?  Two things.  First, Web 2.0 technologists need to work on connecting directly with line executives of large enterprises without trying to go through the IT departments. Second, they should avoid the temptation to present grand visions of new architectures and concentrate instead on starting points where these technologies can deliver near-term business impact. (This should not be too hard since by nature Web 2.0 technologists are bootstrappers and hackers.)”

Certainly there is a lot of this going on, but it doesn’t do anything to bring the two camps to a deeper understanding of perspectives (is there a theme here with Hagel?) and will miss opportunities to truly leverage the strengths of both.

But since Hagel has neither tags or search on his site, I can’t readily determine if he’s updated his position over the past year (but that would be an access issue :)  .

[Hmmm, did you also notice that not once does Hagel reference the term "Enterprise 2.0" except when quoting McAfee? Perhaps there are subtile perspective issues at play?] 

I hope Mr. Hagel isn’t feeling too abashed. Somehow, McAfee is always my champion in differences of opinion, particularly when jousting with Tom Davenport (I’m disappointed that these two won’t be on the same stage with one another at the ‘08 conference, but maybe we can stir up an exchange or two here on the blog).

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 »

David GoldsteinDecember 19th, 2007 at 9:43 pm

Everyone would like to have the information they need/want at their fingertips when they need/want it. The fact is that different types of information are best mined with different tools/approaches. The structured-unstructured type dimension is commonly referenced when dialoguing about web 2.0 vs. enterprise 2.0 vs. SOA vs. traditional enterprise integration approaches. However, there are other dimensions that need to be considered, including global-specific, fluid-static, complex-simple, and idea-solution. Uncovering structured, specific, static, simple, solution type data for results-driven (specific, measurable, actionable, realistic, time-bound, etc.) needs has been what CIO’s have been concerned with. This is a legacy of the industrial-revolution era linear mentality that continues to drive corporate thinking. We are moving (evolving?) to a non-linear, idea-driven, matrix-based value creation society that needs information storage, access/retrieval, processing strategies optimized for it. The corporate world is the nexus within which this evolution is taking place. And this is a place where experimentation is taking place. There is an incredibly complex interplay among the dimensions referenced above for which different approaches are suitable. My guess is that we are developing new tools for new ways of doing business that will be added to the toolbox; it’s not eiher or, it’s what works for the problem at hand.

Jon HusbandDecember 29th, 2007 at 11:52 pm

My guess is that we are developing new tools for new ways of doing business that will be added to the toolbox; it’s not eiher or, it’s what works for the problem at hand.

I’d call it redefining knowledge work along the lines of more natural human cognitive processes (they of course existed, but were constrained and handicapped by structure, protocol, policies, reporting lones, exclusion from basic decision-making, and so on). These processes occur in the hands and with the heads of knowledge workers, and find more effectiveness in interaction and collaboration … constructing purposeful knowledge out of relevant information. The heavy-duty databases have by and large been built, the social computing tools, services and platforms can be layered over those databases, and information and expertise are now beginning to find ways to find each other and get to work.

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>