Successfully reported this slideshow.

Communication / Collaboration / Content / Competition, Peter O'Kelly



1 of 51
1 of 51

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Communication / Collaboration / Content / Competition, Peter O'Kelly

  1. 1. <ul><li>Communication/Collaboration/Content Competition, &quot;Co-opetition,&quot; and Culture: </li></ul><ul><li>Opportunities for Traction Software and its Customer Community </li></ul><ul><li>TUG 2010 – 2010/10/13 </li></ul><ul><li>Peter O’Kelly </li></ul><ul><li>[email_address] </li></ul><ul><li> </li></ul>
  2. 2. 3C Competition, &quot;Co-opetition,&quot; and Culture <ul><li>Agenda </li></ul><ul><li>A brief history of and framework for communication, collaboration, and content </li></ul><ul><li>The battle of the titans </li></ul><ul><li>Where Traction fits in </li></ul><ul><li>Cultural considerations </li></ul><ul><li>Discussion </li></ul>
  3. 3. 3C History and Framework <ul><li>The big picture </li></ul><ul><li>Communication and collaboration are about </li></ul><ul><ul><li>Connecting people with information resources and other people </li></ul></ul><ul><ul><ul><li>In order to get things done </li></ul></ul></ul><ul><li>Content is basically anything not well suited to a traditional relational database management system </li></ul><ul><ul><li>Resources and relations… </li></ul></ul><ul><li>Communication, collaboration, and content are, collectively, fundamentally important for </li></ul><ul><ul><li>Productivity </li></ul></ul><ul><ul><li>Responsiveness and agility </li></ul></ul><ul><ul><ul><li>Including the ability to work in distributed teams, and across organizational boundaries </li></ul></ul></ul><ul><ul><li>Effective time and attention management </li></ul></ul><ul><ul><li>Information governance and regulatory compliance </li></ul></ul>
  4. 4. 3C History and Framework <ul><li>A couple historical snapshots </li></ul><ul><li>65 years since “ As We May Think ” </li></ul>Also see
  5. 5. 3C History and Framework <ul><li>A couple historical snapshots </li></ul><ul><li>50 years since PLATO </li></ul>
  6. 6. A 3C Framework Communication Collaboration Synchronous Asynchronous
  7. 7. Blurring Boundaries <ul><li>Optimization opportunities </li></ul><ul><li>Evolving from specialized and proprietary applications to simplified and integrated services on the Internet platform </li></ul>
  8. 8. Core 3C Concepts <ul><li>Key themes </li></ul><ul><li>Workspaces </li></ul><ul><li>Information items and models </li></ul><ul><li>Tools </li></ul><ul><li>Composite views </li></ul><ul><li>Activities and programming models </li></ul><ul><li>Templates </li></ul><ul><li>Integration </li></ul>
  9. 9. Market Dynamics Enabling 3C Optimization <ul><li>Some recent drivers </li></ul><ul><li>Contextual activities </li></ul><ul><li>Social content and social networking </li></ul><ul><li>XML information architecture </li></ul><ul><li>Integrated work and personal tools </li></ul><ul><li>The software + services shift </li></ul>
  10. 10. 3C Competition, &quot;Co-opetition,&quot; and Culture <ul><li>Agenda </li></ul><ul><li>A brief history of and framework for communication, collaboration, and content </li></ul><ul><li>The battle of the titans </li></ul><ul><li>Where Traction fits in </li></ul><ul><li>Cultural considerations </li></ul><ul><li>Discussion </li></ul>
  11. 11. IBM’s 3C Platforms <ul><li>Overview </li></ul><ul><li>IBM has three largely distinct communication/collaboration platforms, with </li></ul><ul><ul><li>Different underlying application and information models </li></ul></ul><ul><ul><li>A business model partially predicated on perpetuating protracted professional services engagements and legacy software licensing revenues </li></ul></ul><ul><ul><li>A sometimes politically-motivated standards policy </li></ul></ul><ul><li>This approach has resulted in an often confusing, cumbersome, and costly enterprise communication/collaboration value proposition </li></ul>
  12. 12. IBM Lotus 3C Platforms: Notes/Domino <ul><li>Notes 1.0 (1989) </li></ul>Source: Ray Ozzie
  13. 13. IBM Lotus 3C Platforms: Notes/Domino Communication Collaboration Synchronous Asynchronous *Note: IBM announced at Lotusphere 2009 that future releases of Sametime would be based on WAS and DB2
  14. 14. IBM Lotus 3C Platforms: WAS-based Communication Collaboration Synchronous Asynchronous
  15. 15. IBM Lotus 3C Platforms: SaaS Communication Collaboration Synchronous Asynchronous Note: the full LotusLive suite includes a mix of Notes/Domino and WAS/DB2, along with Outblaze- and WebDialogs-derived services
  16. 16. IBM’s 3C Migration Mandate <ul><li>IBM’s Enterprise Customer Dilemma </li></ul><ul><li>Two incomplete communication/collaboration platforms, with IBM pushing migrations to the WAS platform </li></ul><ul><ul><li>Despite the fact that the WAS suite does not include enterprise messaging </li></ul></ul>Notes Domino WebSphere DB2 Collaborative applications Enterprise messaging Web applications Information management
  17. 17. Microsoft’s 3C Platform <ul><li>Overview </li></ul><ul><li>Microsoft has a consistent and coherent communication/ collaboration architecture </li></ul><ul><ul><li>Addressing most facets of the communication/collaboration continuum, with </li></ul></ul><ul><ul><ul><li>A singular focus on unified information architecture and platform services </li></ul></ul></ul><ul><ul><ul><li>The same architecture, tools, and user experiences for both software and services </li></ul></ul></ul><ul><ul><ul><ul><li>On-premises, cloud-based, and hybrid </li></ul></ul></ul></ul><ul><ul><ul><li>The deepest integration with the tools most information workers use every day (Office applications) </li></ul></ul></ul><ul><ul><ul><li>Significant new innovation in Office 2010, SharePoint 2010, and Visual Studio 2010 </li></ul></ul></ul>
  18. 18. Microsoft’s 3C Platform Communication Collaboration Synchronous Asynchronous With the Microsoft Business Productivity Online Suite, the same solutions are used on-premises and on-line
  19. 19. Another View of Microsoft’s 3C Platform <ul><li>Reflecting a multi-year shift to a unified architecture </li></ul>
  20. 20. Google’s 3C Platforms <ul><li>Google is attempting to redefine the enterprise 3C landscape </li></ul>
  21. 21. Google’s 3C Vision Communication Collaboration Synchronous Asynchronous
  22. 22. Oracle’s 3C Platforms <ul><li>Taking another run at communication/collaboration </li></ul><ul><li>Oracle has failed with at least 3 major communication/ collaboration offerings since the early 1990s, most recently with Oracle Collaboration Suite </li></ul><ul><li>Oracle is also determined to become a more significant 3C player, however, in part because </li></ul><ul><ul><li>Collaboration and content decisions now drive DBMS deployments, directly impacting Oracle’s primary platform franchise </li></ul></ul><ul><ul><ul><li>Threat: being displaced, especially by SQL Server (via SharePoint) </li></ul></ul></ul><ul><ul><ul><li>Opportunity: expand Oracle Database role in content management via XML information management </li></ul></ul></ul><ul><ul><li>Oracle’s application businesses can be usefully extended with contextual communication/collaboration services </li></ul></ul><ul><ul><li>Oracle understands the IBM Lotus installed base is in transition, and seeks to capitalize </li></ul></ul>
  23. 23. Oracle’s Communication/Collaboration Vision Communication Collaboration Synchronous Asynchronous
  24. 24. Cisco’s 3C Vision Source: Cisco “Transforming Collaboration Through Strategy and Architecture” white paper
  25. 25. Cisco’s 3C Vision
  26. 26. Cisco’s 3C Platforms <ul><li>Scrambling to move beyond voice communications </li></ul><ul><li>Some related acquisitions </li></ul><ul><ul><li>WebEx (2007/03, Web conferencing) </li></ul></ul><ul><ul><li>PostPath (2008/08, open source Exchange Server clone) </li></ul></ul><ul><ul><li>Jabber (2008/09, IM/real-time communication) </li></ul></ul><ul><li>Cisco Quad </li></ul><ul><ul><li>“ This enterprise collaboration platform combines the power of social networking with communications, business information, and content management systems. At the same time, it meets IT's needs for policy management, scalability, security, and ease of management.” </li></ul></ul><ul><ul><ul><li>Source: http:// </li></ul></ul></ul><ul><li>Cisco’s likely success level in this 3C leapfrog attempt is still tbd </li></ul><ul><ul><li>Burton Group (2010/10/05): </li></ul></ul><ul><ul><ul><li>“ Cisco's WebEx gambit is in its opening moves and, therefore, enterprises should adopt a wait-and-see approach concerning Cisco's development of its SaaS 3C strategy and technologies. </li></ul></ul></ul><ul><ul><ul><li>Enterprises can safely add WebEx web conferencing to their short list but should evaluate the other WebEx offerings carefully because of their technology gaps. </li></ul></ul></ul><ul><ul><ul><li>In particular, WebEx Connect and WebEx Mail should only be implemented in limited circumstances where they fulfill needs for lightweight communications.” </li></ul></ul></ul>
  27. 27. 3C Competition, &quot;Co-opetition,&quot; and Culture <ul><li>Agenda </li></ul><ul><li>A brief history of and framework for communication, collaboration, and content </li></ul><ul><li>The battle of the titans </li></ul><ul><li>Where Traction fits in </li></ul><ul><li>Cultural considerations </li></ul><ul><li>Discussion </li></ul>
  28. 28. Traction Among the Titans <ul><li>A collaborative hypertext journaling pioneer </li></ul><ul><li>Traction considerations </li></ul><ul><ul><li>“ Best of breed” versus suites </li></ul></ul><ul><ul><ul><li>Focused and fast-moving </li></ul></ul></ul><ul><ul><ul><ul><li>E.g., not attempting to pull a Web app server platform or comprehensive programming framework </li></ul></ul></ul></ul><ul><ul><li>History and team expertise </li></ul></ul><ul><ul><ul><li>Including many of the most advanced customer deployments </li></ul></ul></ul><ul><ul><li>“ Co-opetition” </li></ul></ul><ul><ul><ul><li>Competitive for generic blogs, wikis, social networking, … </li></ul></ul></ul><ul><ul><ul><li>Complementary for </li></ul></ul></ul><ul><ul><ul><ul><li>Beyond-the-basics hypertext collaboration </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Synergy with multi-vendor enterprise deployments </li></ul></ul></ul></ul>
  29. 29. Traction Among the Titans <ul><li>Very well aligned with the Internet platform </li></ul><ul><li>TeamPage can serve in multiple roles, including </li></ul><ul><ul><li>Blogs and wikis for asynchronous communication/collaboration </li></ul></ul><ul><ul><li>Hypertext-based compound document management </li></ul></ul><ul><ul><li>Social software services </li></ul></ul><ul><ul><li>Taxonomy/other metadata-driven information item classification </li></ul></ul><ul><ul><li>Hypertext application platform </li></ul></ul><ul><ul><ul><li>Traction software developer kit and SDL (Skin Definition Language) “to extend or customize Traction TeamPage's appearance, behavior, and connections to other systems” </li></ul></ul></ul><ul><li>The underlying Traction meta-model – its collaborative hypertext journaling system – is a key enabler </li></ul>
  30. 30. 3C Competition, &quot;Co-opetition,&quot; and Culture <ul><li>Agenda </li></ul><ul><li>A brief history of and framework for communication, collaboration, and content </li></ul><ul><li>The battle of the titans </li></ul><ul><li>Where Traction fits in </li></ul><ul><li>Cultural considerations </li></ul><ul><li>Discussion </li></ul>
  31. 31. Cultural Considerations <ul><li>Some key themes </li></ul><ul><li>We’re in a “paradox of abundance” 3C product/service phase </li></ul><ul><ul><li>With an incredible selection of cost-effective alternatives </li></ul></ul><ul><li>Effective 3C-conducive culture is a perennial challenge, however </li></ul><ul><ul><li>Many of the same challenges faced with Lotus Notes 1.0 20+ years ago </li></ul></ul><ul><ul><li>Avoid “Field of Dreams” (if you build/deploy it, they will come) wishful thinking </li></ul></ul><ul><ul><ul><li>Organizations must provide clear guidance on what to use when </li></ul></ul></ul><ul><ul><li>Promote effective communication, collaboration, and content management </li></ul></ul><ul><ul><ul><li>Train people to communicate and collaborate via hypertext content </li></ul></ul></ul><ul><ul><ul><ul><li>But also to avoid over-sharing and other risks </li></ul></ul></ul></ul><ul><li>The explosive growth of social software is a mixed blessing </li></ul><ul><ul><li>Making 3C less of a hard sell </li></ul></ul><ul><ul><li>But also introducing new challenges, e.g., in terms of encouraging information workers to use the right form-follows-function-fit tools/services </li></ul></ul>
  32. 32. Cultural Considerations <ul><li>Example: tool guidance </li></ul>Document library Discussion forum Web content, including wikis Work product File collections Information item collections arranged by topic Web sites with hypertext pages Life cycle Process- or project-oriented; library for results Persistent discussion threads Purposefully organized Web pages User conceptual model Folders, files, and activities Topics and responses; channel-based updates Semi-structured Web pages
  33. 33. 3C Competition, &quot;Co-opetition,&quot; and Culture <ul><li>Agenda </li></ul><ul><li>A brief history of and framework for communication, collaboration, and content </li></ul><ul><li>The battle of the titans </li></ul><ul><li>Where Traction fits in </li></ul><ul><li>Cultural considerations </li></ul><ul><li>Discussion </li></ul>
  34. 34. Additional Content
  35. 35. Core Collaboration Concepts <ul><li>Key concepts </li></ul><ul><li>Workspaces </li></ul><ul><li>Information items and models </li></ul><ul><li>Tools </li></ul><ul><li>Composite views </li></ul><ul><li>Activities and programming models </li></ul><ul><li>Templates </li></ul><ul><li>Integration </li></ul>
  36. 36. Core Collaboration Concepts <ul><li>Workspaces </li></ul><ul><li>Workspaces are simply spaces (real or virtual places) wherein people collectively engage in activities </li></ul><ul><li>Workspaces are composed of </li></ul><ul><ul><li>Information items </li></ul></ul><ul><ul><li>Tools </li></ul></ul><ul><ul><li>Membership-related services such as the ability to identify workspace participants and their respective access control privileges </li></ul></ul><ul><li>Some workspaces are optimized for ad hoc projects, such as collaboratively composing a customer request-for-proposal (RFP) response </li></ul><ul><ul><li>These workspaces are, ideally, retired after the final work products are transferred to other systems of record </li></ul></ul><ul><li>Workspaces may also be general-purpose and/or otherwise ongoing, such as a wiki workspace for tracking and discussing best practices for a given business domain </li></ul>
  37. 37. Core Collaboration Concepts <ul><li>Information items and models </li></ul><ul><li>Information items are the artifacts used to facilitate collaboration in workspaces </li></ul><ul><li>In general, there are two primary types of information items </li></ul><ul><ul><li>Documents are typically used for narrative content that is optimized for human comprehension, and organized in terms of hierarchy (e.g., sections and subsections) and sequence </li></ul></ul><ul><ul><ul><li>Documents are not limited to print-oriented tools such as word processors; modern document-oriented information items also include wiki pages and other types of hypertext Web content </li></ul></ul></ul><ul><ul><li>Lists : list-based information items are generally data-centric, used to describe real-world things such as customers, project tasks, and calendar events </li></ul></ul><ul><ul><ul><li>Lists are ideally application context-independent, so that the list information may be shared by multiple applications (and also used with standards-based query and analysis tools) </li></ul></ul></ul>
  38. 38. Core Collaboration Concepts <ul><li>Information items and models (continued) </li></ul><ul><li>Information models are used to define how information items may be related </li></ul><ul><li>Document-oriented information models are typically based on hierarchies and links </li></ul><ul><ul><li>A discussion forum, for example, includes hierarchies of topic and response documents </li></ul></ul><ul><ul><li>Document directories, with folders and sub-folders, are also used to manage hierarchical relationships among collections of documents </li></ul></ul><ul><ul><li>Wiki pages, as a third example, are more likely to be related by hypertext links </li></ul></ul><ul><li>List-based collections of information items may also be related through links, but they are more generally related by shared data attributes (a.k.a. schemas, in the relational model) </li></ul>
  39. 39. Core Collaboration Concepts <ul><li>Tools </li></ul><ul><li>Information items are viewed and edited with a variety of tools for specific information item and model types </li></ul><ul><li>The tools range from relatively simple document viewer and editors to more elaborate tools for domains such as calendar and project management </li></ul><ul><li>In all cases, the tools are used to manipulate specific types of information items </li></ul><ul><ul><li>Or collections of similarly-structured information items </li></ul></ul>
  40. 40. Core Collaboration Concepts <ul><li>Composite views </li></ul><ul><li>Composite views are used to combine a variety of types of related information items into a shared view context, typically in the form of portal- or dashboard-centric pages </li></ul><ul><ul><li>A customer-focused composite view, for example, might centrally focus on a specific customer request and peripherally include lists of recent customer-related orders and meetings (likely with links to views with more detailed information) </li></ul></ul><ul><ul><li>Most wiki page tools are also composite views, composed of a page editor along with lists of related information (such as links to related pages, along with people who have recently edited the current page) </li></ul></ul><ul><li>Since Web-centric composite views are now mainstream, in both enterprise and consumer-oriented computing contexts, it’s increasingly redundant to refer to “portal-centric” pages </li></ul><ul><ul><li>Such pages are now the norm rather than the exception, and portal-related capabilities are pervasively included in modern collaborative application platforms </li></ul></ul>
  41. 41. Core Collaboration Concepts <ul><li>Activities and programming models </li></ul><ul><li>Activities and programming models are used to facilitate taking actions on information items or collections of information items </li></ul><ul><li>Activities can be </li></ul><ul><ul><li>Simple, e.g., checking out a document, creating a new document version, or submitting a document for team review and feedback </li></ul></ul><ul><ul><li>Not so simple, e.g., people collaborating to create a detailed customer RFP response </li></ul></ul><ul><ul><li>Complex, e.g., coordinating and managing a multi-month services engagement </li></ul></ul><ul><li>Information item collection-oriented activity examples include assigning a set of project tasks to a workspace participant, or escalating overdue project tasks to a supervisor </li></ul><ul><li>In all activity and programming model scenarios, related goals include </li></ul><ul><ul><li>Using declarative constructs whenever possible, in order to minimize low-level coding (that can be more complex and difficult to maintain) </li></ul></ul><ul><ul><li>Maintaining a clean separation of structure, presentation, and activity (also known as “behavior”) concerns </li></ul></ul>
  42. 42. Core Collaboration Concepts <ul><li>Templates </li></ul><ul><li>Templates are used to minimize rework and maximize consistency </li></ul><ul><li>Some examples: </li></ul><ul><ul><li>Information item templates are used to specify information item structure, presentation, and activity details </li></ul></ul><ul><ul><li>Document templates, often referred to as form definitions, are commonly used when creating new document instances </li></ul></ul><ul><li>Tool templates combine information item types and models along with activities and programming models appropriate for a given tool context (such as document libraries and discussion forums) </li></ul><ul><li>Workspace templates typically include multiple tools and information item templates </li></ul><ul><ul><li>A project team workspace template, for example, is likely to contain document library, discussion forum, and project calendar tools </li></ul></ul>
  43. 43. Core Collaboration Concepts <ul><li>Integration </li></ul><ul><li>There are two high-level categories of integration for collaborative applications and content </li></ul><ul><li>The first involves platform services, including </li></ul><ul><ul><li>Identity, authentication, and authorization </li></ul></ul><ul><ul><li>Encryption and information rights management </li></ul></ul><ul><ul><li>Indexing and search </li></ul></ul><ul><ul><li>Tagging and other means of categorizing information items </li></ul></ul><ul><ul><li>Subscription and notification (including XML syndication, e.g., via RSS) </li></ul></ul><ul><ul><li>Workflow services </li></ul></ul><ul><ul><li>Contextual presence awareness and real-time communication tool invocation </li></ul></ul><ul><ul><li>Storage, including caching and synchronization </li></ul></ul>
  44. 44. Core Collaboration Concepts <ul><li>Integration (continued) </li></ul><ul><li>The second category of integration involves other applications and information management solutions, such as external (to the workspace) databases </li></ul><ul><ul><li>For example, it’s useful be able to integrate workspaces with existing systems for human resources (such as organizational structure), product/service, and customer information, rather than maintaining duplicate copies of the information </li></ul></ul><ul><ul><li>With this approach, corporate systems of record maintain control over shared information resources, and synchronization challenges are minimized </li></ul></ul>
  45. 45. Market Dynamics Enabling Communication/Collaboration Optimization <ul><li>Some key drivers </li></ul><ul><li>Contextual activities </li></ul><ul><li>Social content and social networking </li></ul><ul><li>XML information architecture </li></ul><ul><li>Integrated work and personal tools </li></ul><ul><li>The software + services shift </li></ul>
  46. 46. Contextual Activities <ul><li>Taking actions in preferred, familiar tools </li></ul><ul><li>There is no one-size-fits-all solution </li></ul><ul><ul><li>People have different work styles and tool preferences </li></ul></ul><ul><li>To optimize information worker time, attention, and productivity, IT must be able to seamlessly integrate communication and collaboration tools into familiar work environments such as productivity applications and browser-based user experiences </li></ul><ul><ul><li>On PCs and other device types, including smartphones </li></ul></ul><ul><li>Information workers can then have a consistent user experience for activities ranging from business intelligence to ERP transaction entry </li></ul><ul><ul><li>Blurring the traditional boundaries among applications, documents, and Web-centric user experiences </li></ul></ul><ul><li>And IT can apply and capture data and metadata required for operations and record-keeping policies without placing additional burden on information workers </li></ul>
  47. 47. Social Content and Social Networking <ul><li>Connecting people with other people as well as content </li></ul><ul><li>Social software generally refers to a mix of </li></ul><ul><ul><li>Blogs </li></ul></ul><ul><ul><li>Wikis </li></ul></ul><ul><ul><li>Bookmarking </li></ul></ul><ul><ul><li>Tagging </li></ul></ul><ul><ul><li>Rating </li></ul></ul><ul><ul><li>Expertise and social search </li></ul></ul><ul><ul><li>Podcasts, videos, and other means of facilitating social collaboration </li></ul></ul><ul><ul><li>Domain-specific communities including some or all of the above </li></ul></ul><ul><li>Social software tools are increasingly familiar to information workers from services used outside of the workplace </li></ul><ul><ul><li>And non-trivial to robustly provide in a model that addresses all enterprises concerns and requirements </li></ul></ul>
  48. 48. XML Information Architecture <ul><li>A fundamental information management advance </li></ul><ul><li>Industry standards such as Open XML and OpenDocument Format (ODF) make it possible to seamlessly manage productivity application content using structured, schema-backed XML </li></ul><ul><li>Blogs, wikis, and other more social interaction models are also XML-based </li></ul><ul><ul><li>And have ushered in a shift to hypertext models – focused on collections of information items rather than traditional documents and files </li></ul></ul><ul><li>Modern database management systems (DBMSs) have no-compromise support for data and content (e.g., XML documents) </li></ul><ul><ul><li>With significant potential to consolidate around fewer moving parts, and to improve end-to-end information management </li></ul></ul>
  49. 49. XML Information Architecture <ul><li>A fundamental information management advance </li></ul><ul><li>The XML-based service orientation shift also makes it possible for modern information worker tools to seamlessly integrate with back-end systems and Web-based resources </li></ul><ul><li>This is a significant advance relative to earlier, proprietary, and binary content models </li></ul><ul><ul><li>Creating new options for application development and information management </li></ul></ul><ul><ul><li>Providing an opportunity to reduce dependencies on specialized tools and application-specific user experiences </li></ul></ul>
  50. 50. Integrated Work and Personal Tools <ul><li>Removing boundaries without sacrificing governance </li></ul><ul><li>Work and personal domains are both challenged with growing information and communication intensity </li></ul><ul><li>Mobile devices are now essentially small form-factor, Internet-connected personal computers </li></ul><ul><li>To optimize information worker time and attention, it’s critical to make communication and collaboration tools available in models that provide consistent and seamless user experiences </li></ul><ul><ul><li>Making it possible for information workers to maximize their focus on work activities while also staying on top of personal concerns </li></ul></ul><ul><ul><ul><li>Across all of their preferred tools and device types </li></ul></ul></ul><ul><ul><li>While simultaneously ensuring enterprise resources are protected and policies consistently enforced </li></ul></ul>
  51. 51. The Software + Services Shift <ul><li>Sustainable synergy </li></ul><ul><li>There can be considerable financial and administrative benefits from moving from on-premises to online solutions </li></ul><ul><li>It’s not an either-or equation, however </li></ul><ul><ul><li>Information workers can, ideally, continue working in familiar tools </li></ul></ul><ul><ul><li>Application developers shouldn’t need to learn new languages and frameworks </li></ul></ul><ul><ul><li>IT can benefit from a hybrid approach, e.g., using services for some employee roles and on-premises solutions for sensitive or regulated activities and information </li></ul></ul><ul><ul><li>Business management can optimize a mix of new opportunities and maximized return on existing investments </li></ul></ul>

Editor's Notes

  • Programmed Logic for Automated Teaching Operations See
  • Notes: This is a vendor-independent view – IBM, Microsoft, and others are competing to lead in the new generation enabled by the market dynamics that produced the framework The framework is also useful for highlighting market transitions, e.g., wiki going from product category to way of working Work flows among quadrants, e.g., Customer request appears as an email message or phone call (async or sync communication) Group gathers to discuss request and next steps (async or sync collaboration) Perhaps a workspace is created for the response/project When the group publishes its results, another communication/collaboration cycle begins
  • Notes This is another view of the communication/collaboration market, highlighting the fact that today’s increasingly integrated communication/collaboration platforms have evolved from previously more distinct product categories
  • Not an exhaustive list, but some of the primary drivers
  • From “ Release 1.0 offered the following functionality, much of it revolutionary in 1989: Encryption, signing, and authentication using the RSA public-key technology, which allows you to mark a document in such a way that the recipient of the document can decisively determine that the document was unmodified during transmission. Lotus Notes was the first important commercial product to use RSA cryptography, and from that point on, users considered security as a prime feature of Lotus Notes. Dial-up functionality, including the ability to use the dial-up driver for interactive server access, the ability to allow users to specify modem strings, support for operator-assisted calling, and automatic logging of phone call activity and statistics. Import/export capability, including Lotus Freelance Graphics metafile import, structured ASCII export, and Lotus 1-2-3/Symphony worksheet export. Ability to set up new users easily, including allowing system/server administrators to create a user mailbox, to create a user record in the Name and Address database, and to notarize the user&apos;s ID file through dialog boxes. You can also automatically create a user&apos;s private Name and Address database, in case that user wants to use private distribution lists. An electronic mail system that allows you to send mail without having to open your private mail file, to receive return receipts, to be notified when new mail arrives, and to automatically correct ambiguous or misspelled names when creating a mail message. On-line help, a feature not offered in many products at this time. Inclusion of the formula language, making the programming of Notes applications easier. DocLinks providing &amp;quot;hotlink&amp;quot; access between Notes documents. Keyword (checkbox and radio button) features. Access Control Lists (ACLs) determining who can access each database and to what extent. Ability to administer remote replicas of databases from a central place, if the database manager desired that behavior. You can replicate ACLs as an entire list, not just individual entries, to remote copies of the database.”
  • Quickr/D – Domino-based version of Quickr; essentially the latest release of QuickPlace
  • Quickr/J: Java/WebSphere-based version of Quickr; completely different product architecture, relative to Quickr/D
  • WebCenter: Oracle’s portal roll-up, with multiple entry points (e.g., Plumtree Portal, acquired by BEA before Oracle’s hostile acquisition of BEA) UCM: Oracle Universal Content Management, based on its Stellent acquisition Beehive: Oracle’s latest attempt to deliver a unified/full-scope communication/collaboration suite; rumored to already be effectively dead
  • SDL info:;title=Features&amp;sectionid=products&amp;type=single&amp;rec=44
  • Adapted from Burton Group’s 2007 “Asynchronous Collaboration Alternatives” technical position
  • Documents and lists are types of resources and relations
  • Not an exhaustive list, but some of the primary drivers
  • Wikis are more a way of working than a distinct software product category – wiki capabilities are increasingly pervasive
  • ×