inicio mail me! sindicaci;ón

What Will Drive Enterprise 2.0 Adoption?

by George Dearing

I created this widget using the FeedBurner / SpringWidgets solution and (as usual) it got me thinking about the enterprise ramifications. Are widgets the new composite applications?

Once widget building (app dev 2.0 ) moves into the enterprise (Coghead,Teqlo), things start to get real interesting. Giving business users the ability create mashups, integrations, and all sorts of other apps will finally help us break the cycle of proprietary, closed-loop systems with terrible interfaces and poor connectivity.

What I’m wondering is what things (like Widgets) will drive the bottom-up adoption needed for enterprise 2.0 (e2.0) to materialize? Once the notion of “hey, we have the ability to configure and compose this stuff ourselves!” is pervasive, the barriers begin to break down. Couple that user epiphany with the upswing of SaaS and open source and you’ve got some real enterprise 2.0 meat on that bone.

But we know it’s more than just the widgets themselves (technology), it’s about changing the mindset of enterprises, changing their perception. And the enterprise mindset is driven by ROI. Prove it to me we say! But the crux of the challenge these days is referenceable data, things like good ‘ol fashioned case studies. So are we doomed to crash and burn next time we’re pitching the benefits of e2.0 in the boardroom?

When’s the tipping point?

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google


2 Comments »

  Jim wrote @ January 9th, 2007 at 11:41 am

Huh, widgets are going to be the savior of it all. User epiphany? Not even close. Typical Web 2.0 hype. Flickr, youtube, maps, big whoop.

  George Dearing wrote @ January 9th, 2007 at 12:03 pm

Hi Jim -
Just clarifying, I wasn’t imnplying widgets were going to be a savior. I do however think widgets represent newer approaches to application development with the main characteristics being service-orientation, flexible configuration, and self-publishing.If those things save me (or anyone else) the hassle of going through IT to get content published or growing old waiting for traditioonal application development cycles then, on second thought, maybe widgets are the savior.

Thanks for the input.

Your comment

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