The Assembled Web for CIOs New approaches to increase business agility Customer online behavior is shifting significantly Your business partners are struggling to respond IT should take open, iterative approaches to become more agile

The Assembled Web Conceptual Framework 1. Individuals are now in control and assembling their own view of the web – companies must go to where they are 3. IT must find a way to enable business partners to create numerous compelling solutions for customers at a rapid clip while at the same time maintaining control, security and scalability of core corporate systems 2. When customers do come to your websites they expect to be able to learn (Content), engage (Community) and buy (Commerce) all on one integrated site.

Conceptual Framework

10 Principles You should always be thinking multi-site, multi-interface, multi-project. Success on the web is no longer . . . about driving traffic to your site, or keeping eyeballs there once they arrive. Your brand is not what you say it is, but what . . . the Internet says it is. Design is critical, and design is not about pretty shiny objects. The internet itself, like the *nix operating systems on which it (almost entirely) runs, is a set of small pieces loosely joined. The difference between “behind the firewall” and “out in the cloud” is trending toward zero. There is no defensible reason to invent a proprietary standard wherever an open standard exists. Working in isolation from the rest of the internet is inherently limiting and dangerous. Consumer Technology is beating Enterprise IT, and soundly. Small incremental releases are essential. The Assembled Web

You should always be thinking multi-site, multi-interface, multi-project.

Success on the web is no longer . . . about driving traffic to your site, or keeping eyeballs there once they arrive.

Your brand is not what you say it is, but what . . . the Internet says it is.

Design is critical, and design is not about pretty shiny objects.

The internet itself, like the *nix operating systems on which it (almost entirely) runs, is a set of small pieces loosely joined.

The difference between “behind the firewall” and “out in the cloud” is trending toward zero.

There is no defensible reason to invent a proprietary standard wherever an open standard exists.

Working in isolation from the rest of the internet is inherently limiting and dangerous.

Consumer Technology is beating Enterprise IT, and soundly.

Small incremental releases are essential.

The Assembled Web

How Did We Get Here? Assembled Web Overview Era Characteristics Limitations Web of Documents Content-centric Static HTML experiences / lightweight CMS Focus on eyeballs, stickiness “ The web is a giant universal library for information” Results in Brochure-ware Experiences are not engaging Not digitally native Not interactive / immersive Web of Transactions Commerce-centric Focus on conversion rates “ The web is a giant universal marketplace for buying and selling things” No loyalty to merchants No depth of experience No social interaction Transactional focus often resulted in weak content – don’t distract the buyer Web of Communities (aka “Web 2.0”) Community-centric Focus on “engagement” “ The web is a giant universal cocktail party / high school reunion / community” Struggle to find business models Community for community’s sake Herd mentality Cost of community management underestimated

Assembled Web Overview

What does this mean to the CIO? Increased Collaboration With business partners With external communities Demand for Agility Changing business environment Changing consumer expectations Balance Influence and Control Not “my way or the highway” Not “anything goes” Assembled Web

Increased Collaboration

With business partners

With external communities

Demand for Agility

Changing business environment

Changing consumer expectations

Balance Influence and Control

Not “my way or the highway”

Not “anything goes”

Assembled Web

Relevant Technologies, Approaches, and Standards The Cloud Software as a Service, Infrastructure as a Service, Platform as a Service Autoscaling, autoprovisioning, metered utility Services Oriented Architectures “ Lightweight” SOA RESTful services, simple coordination Application Programming Interfaces For internal consumption For leverage by external parties The Open Stack OpenID, OAuth, oEmbed, OpenSocial, ActivityStreams, Portable Contacts The Closed Stack: Facebook Connect Open Source Collaborative Engineering, Crowdsourcing, Open Innovation Cost of Maintenance, Regression Testing Opportunity to Experiment, Lower cost of Failure

The Cloud

Software as a Service, Infrastructure as a Service, Platform as a Service

Autoscaling, autoprovisioning, metered utility

Services Oriented Architectures

“ Lightweight” SOA

RESTful services, simple coordination

Application Programming Interfaces

For internal consumption

For leverage by external parties

The Open Stack

OpenID, OAuth, oEmbed, OpenSocial, ActivityStreams, Portable Contacts

The Closed Stack: Facebook Connect

Open Source

Collaborative Engineering, Crowdsourcing, Open Innovation

Cost of Maintenance, Regression Testing

Opportunity to Experiment, Lower cost of Failure

To Learn More Listen to a fellow CIO on his change in approach Read a few blogs Be Useful Open source social software Open source content management Contact John Eckman, our practice director

Listen to a fellow CIO on his change in approach

Read a few blogs

Be Useful

Open source social software

Open source content management

Contact John Eckman, our practice director