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.

• The Age of Customization: Enterprise Web 2.0 is the perfect pair of pants!
  
• Enterprise Mashups and Total Cost of Ownership
• Enterprise 2.0 meme map

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

Read More...

Summary only...

Differences of 2.0's

A lot of people ask us here at JackBe about the definitions and or differences between Web 2.0, Enterprise Web 2.0 and Enterprise 2.0. So here are some of my thoughts simplified for a blog post.

Web 2.0 – There are two parts to this one which will make sense when I get into the difference between Enterprise Web 2.0 and Enterprise 2.0.

1. Web 2.0 – the user-driven paradigm shift. Youtube, blogs, wikis, RIAs with greater self-service capabilities… all of these are examples of a paradigm shift from older HTML static, mostly one way communication of ideas and information to a new User-Driven web model which enables you and me to more easily contribute content, share information and collaborate with each other through the web.

2. Web 2.0 - technology enablers. This user-driven shift has been made possible in part by new or now accepted technologies and techniques which have gained greater penetration as web application tools. Such include: Ajax, proprietary RIA tools like Flex and Lazlo and now Silverlight, Service Orientated Architecture (SOA), Ruby on Rail and other lightweight dev models, Web Services like REST and RSS, Mashups (data and visual) and Tagging. Of course this is not an exclusive list but I think you get my point.

Enterprise Web 2.0 – the Web 2.0 technologies mentioned above put into practice in the enterprise. For example: richer, more productive customer self-service apps, inter-department collaboration through bogs, and wikis. But simply ‘slapping’ these technologies into a rooted organization will not bring about the same successes and value that Web 2.0 apps have enjoyed in the public domain. Enterprises have too many constraints and need a mind and culture shift along with deep embedment of these 2.0 tools into its processes to have any kind of a definable impact.

Enterprise 2.0 – The Enterprise 2.0 is analogous to #1 above in that it represents a user orientated paradigm shift of the enterprise makeup itself. It embraces the decentralized organization built around disparate data and information with users empowered to create new information built around and on top of others ideas through sharing, and collaboration. An organic organization loosely designed and constructed to empower knowledge workers to do what they do best by giving them what they need, when the need it and how they need it by enabling them with 2.0 technologies and nurturing this new paradigm mind set internally. Here enterprises reap the benefits of 2.0 through network effects from its user’s contributions and collaboration and realize success that increases proportionally as more users contribute to the organism creating a potentially indefinable value proposition to stakeholders.

Each of these could be expanded in much more detail but why make it more complicated as this? If you have any thoughts please feel free to share or contact me. That is after all the point.

Read More...

Summary only...

New SalesForce.com Service is Yet Another Web 2.0 Proof Point

Read/Write Web reported yesterday that 'Salesforce.com Brings Web 2.0 To The Enterprise With ContentExchange': Today Salesforce.com announced a new product called Salesforce ContentExchange, a content management product for unstructured data such as email and html. They also publicly announced the acquisition of Koral, a web 2.0 content collaboration platform that was at DEMO07 earlier this year... Koral is a key enabling technology for Salesforce ContentExchange. The new product means that Salesforce.com now manages all types of content in a company - both structured information (e.g. CRM data like contacts and sales information) and unstructured information (office documents, HTML, video/audio files and email, etc). Marc Benioff, chairman and CEO of salesforce.com, calls this “another step towards our vision of managing all information on demand”.

So far, Web 2.0 migration into the enterprise world has seemed largely limited to the notion of enhanced content creation and sharing – for example, using a blog to add a human touch to a vendor/customer or management/employee relationship. Another example is using a wiki to create central repositories of information to which any employee can contribute, thereby exposing previously hidden but useful information. Both blogs and wikis are certainly '2.0' types of tools, and as such they are useful for sharing unstructured information associated with projects and processes. But they do nothing for structured information retrieval.

I think the SalesForce.com ContentExchange nicely reinforces what we at JackBe have been talking about for many months: a new level of ‘2.0 collaboration’ that empowers employees to share, access and interact with disparate information and data, both structured and unstructured. Check out the graph, stolen from one of our sales pitches, for an example. I think it's about delivering on the original promises of what Portals were aimed to do (but largely didn't do), and all in a 100% user-driven way.

Most business and knowledge worker tasks rely on access to the appropriate structured data in real, or near-real time. These information pieces are spread out across many enterprise applications, and databases. We as information workers are trapped in a world of monolithic siloed applications, each with its own login and password, access control policies, and confusing and user interfaces. Furthermore, because information is stored in different locations, the relation between the data is not obvious, and is usually only well understood by the information worker himself. It appears that SalesForce.com aims to change all that.

And, of course, JackBe's own Presto offers considerable efficiency potentials to the enterprise by presenting a user-driven consolidated view to both this disparate unstructured and structured information so to better respond to tacit activities. We think Presto will essentially redefine how information is located, consumed, and remixed as seen fit in the enterprise. Presto provides user insight and control of all accessible/governed information the knowledge worker needs to better respond to events. But enuf about my stuff for now.

Kudos to SalesForce.com.

Read More...

Summary only...