Showing posts with label web 2.0. Show all posts
Showing posts with label web 2.0. Show all posts

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

Read More...

Sunday, June 3, 2007

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...

Tuesday, April 10, 2007

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...

Monday, March 12, 2007

Business Value Continued….Enterprise Mashups and Total Cost of Ownership Part 2

Well I’m back with some more ideas and thoughts about Web 2.0, the enabling technologies driving it, and the potential benefits for enterprises. I tend to focus on the technologies and the enterprise aspect of Web 2.0 simply because I get tired (am tired) of people defining it as simply a “social collaborative” movement. Although this is true, and great for my girlfriend who can blog and share her photos, this says little to the strategic impact that the underlying technologies, that make capable the social aspects, can have on the enterprise. Here are a few real universal business situations or rather timeless barriers to a better bottom line that technologies such as Ajax, Mashups, and a SOA can positively affect.

Quickly adapt to Changing Business Needs.

When organizations mandate a business process rule, such as a limit on the size of a particular type of business transaction, it is typically embedded deep within the application code. Finding, adjusting, and maintaining consistency with other systems can be error-prone and extremely time consuming and error-prone processes. By deploying such rules in a separate but integrated environment, organizations can empower business executives via a user interface to achieve extreme agility and oversight.

Effectively Monitor and Continuously Improve the Business

Systems information and transactional flows capture critical interactions that may be required for financial, contractual, regulatory, and business governance. Tracing and reporting audit data are tedious tasks and tenuously contingent on predefined conditions, including monitoring servers and client devices, coding predetermined subroutines to capture processing metrics, running batch routines for replication and reporting, and so forth. Due to the complexity of pulling this information together across a whole business process, the effort is often only made when critical issues arise. To avoid business risk, ongoing monitoring can be automatically captured by the abstracted process layer, which can trigger alerts, alternate process flows, provide automated reporting, and expose many other intelligence metrics. By reacting to early warnings a business can preempt situations that may cause undue and costly mistakes. Organizations may also seek to implement Six Sigma or regulatory initiatives via this type on mechanism.

Simplify Business Integration Efforts

Integration points that are incorporated and managed in close context to specific business processes will provide significantly more value. In the example, enterprise procurement activities are often scattered across multiple systems, where the collating, parsing, and regrouping of items to be sourced are typically very manual and labor-intensive processes. However, these processes can be centralized and automated into a composite application or mashup that avoids these inefficiencies.

Reduce Costs and Risks of Manual Processing

Many organizations still struggle trying to automate manual or paper-based transactions. Highly document-intensive composite application processes are very common targets for Web services. In the procurement example, a user may intervene in multiple places, introducing the potential to corrupt the process flow. With an orchestrated composite application, automated triggers engage users where and when necessary, removing the need for each individual to know every activity in the process required to continue the flow of a specific transaction.

Leverage Existing Systems and Resources

Reusability of code not only saver resource efforts in development and maintenance, it also impacts application quality and security. By utilizing a standardized framework, companies can focus skills development across a variety of systems and solutions to prevent these effects.

Again, these are just a few examples but I and JackBe believe it is these types of scenarios that are not as highly publicized at the moment (overshadowed by the Youttube/myspace buzz) but will at the end of the day drive real business value to the mass.

Read More...

Tuesday, March 6, 2007

Enterprise Mashups and Total Cost of Ownership

What is all the Web 2.0, Ajax, Enterprise 2.0, SOA buzz in the driving towards? What does it mean for the line-of-business manager or the enterprise itself? I thought I’d take a moment at breaking down how the approaches/ideas and supporting technologies could positively impact the underlying business books. As to not make this to vague, I’ll take the latest hallmark of Enterprise 2.0, Enterprise Mashups, and a classic financial benchmark Total Cost of Ownership (TCO), and we’ll deconstruct how this latest set of technologies and techniques stands up against an old benchmark.

The TCO of a solution must take into account the initial and ongoing costs of the solution, relative to the solution it replaces. Enterprise Mashups (which are closely related to composite applications if not the same depending on one’s definition) are based upon a SOA and have the potential to lower TCO in several ways, including:

  • Managing the Services in an SOA is less expensive and complex than managing the interfaces in a traditional integration solution.
  • By leveraging the Web Services standards, mashups can lower the cost of proprietary technologies. Standards level the competitive playing field for vendors by lowering prices generally, and also simplify the task of integration, lowering costs directly.
  • Business analysts and technical business users are able to compose applications without the involvement of more expensive IT personnel.
  • The more complex a business change is, the more effective SOA-based mashups can be at reducing the TCO of the solution because of their inherently flexible nature.

Fundamentally, a SOA provides business an “agility quotient” – the more complex the underlying infrastructure and the more dynamic the business environment, the greater the benefit of an agile architecture to the business. SOAs provide the ability for business users to create enterprise mashups, thus creating and managing business processes.

Where am I going with all of this and how does it fit into the world of Ajax, RIA, or JackBe for that matter? There is one important piece yet missing – the user interface itself. If the tools that users interact with aren’t agile themselves, the benefits of these enterprise mashups to the organization risk being lost. The services that contribute to a mashup can now be consumed by light-weight client models thanks to Ajax. This is why the integration layer will be driven by those who are experienced with client side models. The back-end can do their part, expose the services, which they have or are doing so, but they aren’t going to be able to create what is truly needed for the consumption because this is not there expertise. The services are moving out farther-the power of the apps as well-to the client so it only makes sense that the driver of this integration will be through the client tier experts and more specifically, those skilled in Ajax.

Later, I’ll attempt to address the benefits of incorporating SOA, Ajax, and Mashups into the enterprise to more strategic business benefits. Please feel free to leave your comments and opinions.

Read More...

Thursday, February 22, 2007

The Age of Customization: Enterprise Web 2.0 is the perfect pair of pants!

I spent last weekend searching for pants. I had a need. I looked for pants that were comfortable in the winter and summer but would always ‘breath’, the right material so they would last, and also pants that would be acceptable for multiple occasions. The problem is I couldn’t find a pair that met all these needs. I had to buy multiple pairs. I settled on the only solution that was available at that time. I will have to adapt the right solution (many pants) instead of having one solution (one pair of pants) that adjusts to my needs, when I need something different as situations arise.

I want a pair of pants that could change on-the-fly (no pun intended) easily; adapting to the environment and occasion as I see fit.

Well, we might not be able to do this with pants but now we can with Enterprise Applications. In fact, this type of flexibility, customization and efficiency of a solution that adapts to multiple needs will be the standard in five years time. Three forces are aligning to make this happen.

  • Web 2.0 – user empowerment and customization
  • Ajax – technology techniques to bring richness and back-end interactions to the user
  • Services – Exposed through SOA or other, services are the enterprise applications building block of tomorrow.

These forces are aligned to support the next generation of Enterprise Applications that will be common place in 5 years. These applications will be browser-based. They will unlock the value of information previously contained in separate silos through granular services. With AJAX client side technology, they will consume these assets and allow users to interact in a rich and dynamic fashion. And with the 2.0 social networking and collaboration aspect, the tilting of the IT pendulum back towards the client side leads to more empowered end users capable of generating content and even their own ad-hoc, mashup applications.

Now you can customize your organizations applications to your needs instead of forcing your employees to adjust to a heavyweight, monolithic solution that might not be a right fit for their need. Even further, you can empower your employees to further tailor the solution to meet a particular situational need when they need to.

Why will these applications be the standard?

This new paradigm is difficult for some to grasp. We have been offered large solutions that we had to make fit into our organization and make work for what we had to get done in our jobs. But the productivity that these applications brought to transactional activities is drying up. The future is focused on the knowledge worker who has tacit activities to accomplish and where no solution has arguably truly demonstrated much benefit with regards to optimizing these people’s situational activities.

This is where organizations can increase productivity. The problem is that because of economy of scale past applications couldn’t be developed to meet these situational, micro activities needs. The technologies weren’t all there, understood enough, or further, understood in the context of their synergistic relationships which yield the capabilities to meet these knowledge workers activities needs.

The Enterprise Web 2.0 Application can. It can because the forces listed above are now converging. Enterprise Web 2.0 is a natural evolution of consumer facing Web 2.0 Applications. Web 2.0 has introduced public consumer users to its benefits and now enterprises have begun to catch on to the technologies and techniques to further their web-based applications; to leverage existing assets, whether it be data locked behind a firewall or intellectual knowledge locked in your employees heads.

I can’t wait to see what unfolds this year! (pun intended)

Read More...

Saturday, February 3, 2007

The Age of Good Participation for Jim Gray

If you really want to see the Web 2.0 potential and do something good at the same time, help find Jim Gray from Microsoft. The renowned Microsoft computer scientist was reported missing at sea this week. Amazon’s Mechanical Turk (www.mturk.com) is being used to facilitate satellite imagery examination. Who is doing this? Everyone and everyone. Go to the following link to help:

http://www.mturk.com/mturk/preview?groupId=J0XZ58STDWJZ5QY4F9M0

Amazon’s Mechanical Turk commoditizes user activity tasking. When a company or person needs a human to complete a discrete task, whether complete or part of a larger set of tasks, it offers the tasks to anyone (and sometimes for pay) who is capable of completing. Think of the possibilities here. You have a task and don’t care who does it. Why don’t you care? Because, you have commoditized the task to the point where you trust the worker enough to let them do the work. In the case of Jim Gray, Amazon, the sponsor, trusts any user who is interested in helping.We’ve seen the the monetary potential of Web 2.0 and universal participation with YouTube, MySpace, etc. But, in this case, we are all participating for the good of finding Jim Gray.

Read More...