Business Agility-CIO on Assembled Web


Published on

Business units are growing increasingly frustrated with IT's ability to support them - especially for customer-facing web applications. The rapidly changing customer behavior online is forcing a new approach in the era of the Assembled Web.

Published in: Business, Technology, Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Business Agility-CIO on Assembled Web

  1. 1. 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
  2. 2. The Assembled Web <ul><li>Conceptual Framework </li></ul>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.
  3. 3. 10 Principles <ul><li>You should always be thinking multi-site, multi-interface, multi-project. </li></ul><ul><li>Success on the web is no longer . . . about driving traffic to your site, or keeping eyeballs there once they arrive. </li></ul><ul><li>Your brand is not what you say it is, but what . . . the Internet says it is. </li></ul><ul><li>Design is critical, and design is not about pretty shiny objects. </li></ul><ul><li>The internet itself, like the *nix operating systems on which it (almost entirely) runs, is a set of small pieces loosely joined. </li></ul><ul><li>The difference between “behind the firewall” and “out in the cloud” is trending toward zero. </li></ul><ul><li>There is no defensible reason to invent a proprietary standard wherever an open standard exists. </li></ul><ul><li>Working in isolation from the rest of the internet is inherently limiting and dangerous. </li></ul><ul><li>Consumer Technology is beating Enterprise IT, and soundly. </li></ul><ul><li>Small incremental releases are essential. </li></ul><ul><li>The Assembled Web </li></ul>
  4. 4. How Did We Get Here? <ul><li>Assembled Web Overview </li></ul>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
  5. 5. What does this mean to the CIO? <ul><li>Increased Collaboration </li></ul><ul><ul><li>With business partners </li></ul></ul><ul><ul><li>With external communities </li></ul></ul><ul><li>Demand for Agility </li></ul><ul><ul><li>Changing business environment </li></ul></ul><ul><ul><li>Changing consumer expectations </li></ul></ul><ul><li>Balance Influence and Control </li></ul><ul><ul><li>Not “my way or the highway” </li></ul></ul><ul><ul><li>Not “anything goes” </li></ul></ul><ul><li>Assembled Web </li></ul>
  6. 6. Relevant Technologies, Approaches, and Standards <ul><li>The Cloud </li></ul><ul><ul><li>Software as a Service, Infrastructure as a Service, Platform as a Service </li></ul></ul><ul><ul><li>Autoscaling, autoprovisioning, metered utility </li></ul></ul><ul><li>Services Oriented Architectures </li></ul><ul><ul><li>“ Lightweight” SOA </li></ul></ul><ul><ul><li>RESTful services, simple coordination </li></ul></ul><ul><li>Application Programming Interfaces </li></ul><ul><ul><li>For internal consumption </li></ul></ul><ul><ul><li>For leverage by external parties </li></ul></ul><ul><li>The Open Stack </li></ul><ul><ul><li>OpenID, OAuth, oEmbed, OpenSocial, ActivityStreams, Portable Contacts </li></ul></ul><ul><ul><li>The Closed Stack: Facebook Connect </li></ul></ul><ul><li>Open Source </li></ul><ul><ul><li>Collaborative Engineering, Crowdsourcing, Open Innovation </li></ul></ul><ul><ul><li>Cost of Maintenance, Regression Testing </li></ul></ul><ul><ul><li>Opportunity to Experiment, Lower cost of Failure </li></ul></ul>
  7. 7. To Learn More <ul><li>Listen to a fellow CIO on his change in approach </li></ul><ul><li>Read a few blogs </li></ul><ul><ul><li>Be Useful </li></ul></ul><ul><ul><li>Open source social software </li></ul></ul><ul><ul><li>Open source content management </li></ul></ul><ul><li>Contact John Eckman, our practice director </li></ul>