Enterprise 2.0 Conference: A Drupal Perspective

This week we sponsored and attended the Enterprise 2.0 Conference here in Boston. It was a useful week that produced several interesting insights about how Web 2.0 patterns are being applied inside large organizations.
Apparently last year this show was relatively small and mostly filled with vendors selling stuff to too few interested customers. This year has balanced that out: there were a good number of corporate clients at the show, and they appeared to be quite engaged with the concept of Enterprise 2.0 and hungry to learn more.
We sponsored a small booth in the Demo pavilion to attract potential customers and prospective partners. We had solid traffic all week. Few people coming by our booth had heard of Drupal before, so we spent considerable time educating them about the history and functionality of Drupal. We need to continue to evolve our demos and diagrams to make this process easier and more differentiating. See more on that below.
In addition to staffing our own booth, I spent some time checking out the competition to benchmark our messaging and functionality. I was struck by how thoroughly undifferentiated the pitches were. Everyone was giving essentially the same demo, talking about the same functionality and use cases.
Some of the solutions are delivered through on-premise software. Many were offered as software-as-a-service. A few are available through both. A [very] few are open source, but most of these are corporate-led non-organic open source. Drupal+Acquia was the only fully organic open source project represented.
We need to do more to help Drupal stand out in this messaging monoculture. As I've reflected on this, I think we need to more effectively emphasize the flexibility, agility, and adaptability of Drupal. It is the breadth and depth of the module library and the community behind it that makes Drupal stand out. Drupal is nearly always up to date with the latest trends. It can be adapted to meet a multitude of special situations without lots of custom coding. Not so for most of the solutions I saw at this show. Many of these solutions fall apart when it comes to delivering on the specific requirements of individual teams and internal communities. Things like custom content types, feeds that span multiple content types, and custom views of content are problematic for many of the vendors I spoke with.
This morning I participated on a panel moderated by John Eckman of Optaros. John Newton of Alfresco and Bob Bickel of Ringside Networks and talked about open source as applied to Enterprise 2.0. The audience was very engaged, the energy level was high, and truth was spoken. We took plenty of jabs at proprietary software models and highlighted the ways that commercial backers like Acquia, Alfresco, and Ringside Networks can close the expectation gap between enterprise customers and open source software. Kathleen Reidy of The 451 Group has an insightful write-up about the panel.
- Login or register to post comments
- Original article








Drupal needs its Toyota!
Drupal needs its Toyota!
I recall a time when I didn't take Linux that seriously. Sure it was nice to have a few Linux boxes but could an open source operating system really replace our Unix servers in operations or our Windows PCs on the administrative side? Back then, I had doubts about Linux. Then the stories of how Toyota was utilizing Red Hat Linux started to become known. Suddenly, everyone started saying to themselves that if Toyota could use Linux to meet their business needs, why couldn't Linux work for me too?
In my opinion, the defining moment for Acquia/Drupal will be when we (the potential customers) understand not what Drupal can do for us, but more importantly when we come to understand what we can do with Drupal.
In one form or another, I've been involved on both sides of the firewall in my organization. Ten years ago it was a huge challenge for organizations and businesses to figure out how best to utilize the Internet to meet their business needs. As challenging as I saw it for my own organization, I'm convinced that meeting the challenges on the intranet side is much more difficult. For the most part, we all can see what others are doing with their Internet Web servers, but few of us get to see what other organizations do with Enterprise 2.0 behind their firewall. It's very easy to find examples of "success" on the Web, but it is rare to get a peek of what goes on behind the closed door.
I think in order for specific Enterprise 2.0 applications to succeed, organizations need to see a blueprint for how other enterprises have successfully implemented those applications. In other words, what I think customers need most is to see the blueprint for how Acquia/Drupal can be implemented within organizations similar to their own. I'm not talking about needing to see the feature list but more importantly the strategic "how-to" list. I know what Drupal does, but show me and my coworkers examples of what we can accomplish with Drupal on our Intranet! This in my opinion is the path that will determine whether Acquia succeed as an Enterprise 2.0 application.
Bryan Ruby
CMSReport.com
Good point about the need
Good point about the need for more documented Enterprise 2.0 case studies.
The reason why Enterprise
The reason why Enterprise 2.0 is great for Drupal is because it includes social and networked modifications to company intranets and other classic software platforms used by large companies to organize their communication. In contrast to traditional enterprise software, which imposes structure prior to use, this generation of software tends to encourage use prior to providing structure.
keyword elite | search engine optimization | run your car on water | weight loss | learn spanish