Tuesday, June 12, 2007

Differences in 2.0's Continued

Wow, we received fantastic feedback on our the last post, Differences in 2.0's. In particular, we received emails asking for more clarification about the difference of Enterprise Web 2.0 and Enterprise 2.0. I created a pic (see below) that I hope will help.

First, let me attempt to relate Enterprise 2.0 to Ford, the car company. We could draw parallels to Enterprise 2.0 and what Henry Ford did with manufacturing. In this case we could say Ford created an 'assembly plant 2.0' which changed the core of the whole organization; organizational processes & relationships with said processes, the workforce, their roles, relationships with partners and customers, and how all of these parts interact with each other. This is a stretch but what I am trying to convey is that the core of the enterprise, down to how its business & peoples operate, changes and doesn’t resemble that of the organization before. This change resembles more of a social diagram tied together by Web 2.0 social tools and loosely coupled web apps capable of being composed or customized by each node at a moments notice to respond to whatever need arises using inputs(data & information) from around and out of the network.

[...pause after that mouthful...and we're back...]

In this stretch example, the change creates a Ford company that looks and operates much differently (better) than other enterprises around it still assembling cars the pre-Ford way. This is due to the relationships between the people, data, and the collaborative nature of the new organization.

I expanded a portion of this new picture to incorporate the two facets of Web 2.0 (The social collaborative paradigm shift & the Web 2.0 technology enablers that make this possible), how these once implemented correctly make up the Enterprise Web 2.0 infrastructure, and lastly how with the addition of a Enterprise collaborative paradigm shift, all make up Enterprise 2.0.

You’ll notice that the nodes here state ‘The User’ but this user could be one person, a team, or even a business unit. The connecting lines can be thought of as the social construct or Web 2.0 paradigm that I talked about in the last post, and the Web 2.0 bubbles as Web 2.0 technology enablers connecting Users with systems and other Users.

So, simply stated (I hope) Enterprise Web 2.0 is a technology solution made up of Web 2.0 and Enterprise 2.0 is the organizational paradigm shift that leverages these solutions which, by EW2.0's very nature, must be deeply embedded in the organization to work, creating a much different 2.0 organization as a result. This transition takes time as the whole organization re-roots strategically around the embedded Enterprise Web 2.0 infrastructure. Now one could raise the point of why go through all of this -- benefits of Enterprise Web 2.0 adoption? But this is an entirely new post all of its own. Here are a couple of posts that might help if interested.

I hope this helps. Although I am not a graphic artist, I think it pretty much summarizes the connection and relationships of all four 2.0’s we touched on in the last post sums up how I put all these pieces together. As always I am open and would like to hear your thoughts. mike@jackbe.com

6 comments:

RTodd said...

This is an absolute wonderful vision of the future and one that is grounded in reality. We have already seen the first facet of this in our own organization where the dynamic replacement of the knowledge management components of applications are being pulled and replaced with collaborative / social applications.

Let me give more specific insight. The traditional internal ordering system as a very large set of business processes like ordering, product catalog, order approvals, status, etc. These core business processes are built with high end development tools and programming languages. However, much of the surrounding informational content is perfect for replacement with Web 2.0 technologies.

Take supporting product documentation where the product owner had to obtain the documentation, package it up and send to the application developer. Who then had to upload and connect all the right pieces. Why not replace this with a collaborative application like a document library where the product owner simply uploads the information and tags it appropriately. Instant updates with no delays. Need more 2.0 maturity? Replace the static documentation with a Wiki page with the same information and allow the consumers to update it as well. How about the FAQ, Contact Information, product Descriptions, Product Feedback, etc? All of these are prime candidates for Web 2.0 replacement.

Mike is spot on with his observation.

Mike Wagner said...

Thanks for your comments rtodd, and great examples of how web 2.0 tools can and are virally making their way into organizations. Now these tools are catching the eyes of management who are beginning to envision how web 2.0 is more than the hype of Myspace and YouTube, but rather an opportunity to achieve real productivity and efficiency gains in the enterprise. Thanks again.

Tushar said...

So this really means the enabler (web 2.0 technologies) as adopted into the organization as technology solutions (Enterprise Web 2.0) is really changing the way the business processes now run and creating the new way of how the Enterprise functions (Enterprise 2.0).

One example that I clearly see this influencing is the Web Content Management story. This will soon be replaced by wikis (with a little more sophistication). Gone are the days of a 7-step approval process hierarchy. This in turn will also influence the governance of the the portals to which this content gets deployed.

Helge V. Keitel said...

Let me comment about the social media and enterprise 2.0 applications in Finland. We’re a group of 20 people, academics, consultants, knowledge workers, writing a book about the evolution and use of Web 2.0 and social media in SME’s and large companies.

I’m writing about “Virtual Organizations 1970 – 2010”. The idea is to span pre-web 2.0 social media and networking tools and applications and compare them to the easy to use and cost-effective tools of the present Web 2.0.

There is a big change in the making. Large companies like Nokia are opening up, changing from command – control towards co-creation and collaboration, even beyond. Working together on a global scale is key to success.

The borders of the company are becoming more fluent. The Prosumer idea is invading business processes. Prosumers are more and more participating in the making of the whole supply chain. We see much more self-servicing and do-it-yourself.

The SME Enterprises can be big beneficiaries while they can multiple their size through global open innovation and co-operation with partners and clients.

The future Virtual Organizations will be much different in their working styles. Strangers from all over the world can embrace a common goal and start to work out new solutions. People who hasn’t met before, face to face, write the book. Our meeting place is a working platform with wikies and blogs. The work process and collaboration is very fluent.

The planning process, financing, marketing and writing is proceeding as parallel processes. The participants are taking part in the making of the whole. There are no different departments, the structure moves according to who knows best about a specific task.

There’s a coordinator of the project who supplies and maintain the working platform, but no traditional top down management. The evolution of the end product is taken care of a dispersed organization (geographical distribution), independent knowledge workers who set their own goals.

We didn’t need a long planning process. The agreements and decisions are made on the web. Work load is distributed. The whole machinery operates very differently from a traditional company. There is no need for assistants or secretaries. All participants are core value creators who add something to the end-product.

The book is written in Finnish language and covers the Finnish business and enterprise landscape. I will cover my own writing process in my blogs.

http://digitalvillages.blogspot.com/

Best regards / Helge Keitel

laurencooney said...

I think you approach this in a really interesting way. It's the first time I've read your blog and it looks like it includes more stuff like this - I'll have to dig in.

If we're talking 2.0's here, you should definitely check out Info 2.0. Info 2.0 is the fabric in which data (structured and unstructured) is organized in order to form mashups in ways that can be used within enterprise apps. You can read more about it at my blog at www.jroller.com/page/cooney. It's pretty interesting stuff, and I think the way of looking at Info 2.0 is unique in that it actually separates the information itself being used within Web 2.0.

I'd be interested in hearing what you think about this.

Thanks
Lauren

Mike Wagner said...

Thanks Lauren. I'll definitely check it out. I think you are leading a direction I talked about not to long ago about data(unstructured and structured. You can find it here: http://blogs.jackbe.com/2007/04/today-salesforce.html