Recently in Portals Category

Last week I was pleased to have my second paper published here at Gilbane "Content and the Next-Generation PortalExperience" that you can now register for and download (for free) from the Beacon area of our website.

For many organizations, access to back office services is becoming an essential part of the experience they need to provide their website visitors.Their external websites form the front line of customer service and their Intranets play a vital role in employee engagement as the expectations rise for both audiences on what they can do over the web. In the paper I discuss how a portal infrastructure can be a natural fit for providing this blend of relevant services and content and there is an opportunity for organizations to shift their portal infrastructure from internal workhorse to a contemporary services interface.

The downside, as many organizations have discovered is that a portal implementation can come at the cost of the primary fuel of web engagement - good quality, fresh, relevant content. In the paper I look at the reasons for behind that and suggest a possible solution of adding a contemporary web content management system.

Like any enterprise integration, the fusing together of a portal platform and a WCM has it's own risks, principally that the resulting solution does nothing to improve the lot of the content author as it has the potential to expose these business users to multiple interfaces and complex processes. In the paper I go on to take a look at how to avoid and mitigate these risks, with the advice on some key attributes organizations need to look for when selecting the WCM system.

I hope you enjoy the paper and I'd very much like to hear your feedback - either here or you can find me on Twitter (@iantruscott)

 

The paper is now available from the Beacon area of our website and from e-Spirit, who sponsored the paper. You can also register for a webinar that e-Spirit will be hosting on 10th February 2011 during which I will be talking through the main points of the paper.  

 

Or collaboration, enterprise social software, search, analytics, market trends, customer engagement strategies, intranet architectures, multi-channel publishing ..., or a prediction one of us has previously made that was prescient or presumptuous.

To learn more about the analysts on the panel including links to their blogs and Twitter accounts click on their name below. 

K2. Industry Analyst Keynote Debate: Industry Analyst Debate - What's Real, What's Hype, and What's Coming - May 19th 4:00pm - 5pm, Westin Market St, San Francisco

We invite industry analysts from different firms to speak at all our events to make sure our conference attendees hear differing opinions from a wide variety of expert sources. A second, third, or fourth opinion will ensure you don't make ill-informed decisions about critical content and information technologies or strategies. This session will be a lively, interactive debate guaranteed to be both informative and fun.

Panelists:
Rob Koplowitz, Principal Analyst, Forrester
Hadley Reynolds, Research Director, Search & Digital Marketplace Technologies, IDC
Tony Byrne, Founder, The Real Story Group & CMS Watch 
Scott Liewehr, Senior Consultant, Web Content Management, Gilbane Group 

How to submit questions:

http://gilbanesf.com

Talk about a trip down memory lane...  Another excellent blog post yesterday by my friend and fellow Babson College alum, Sameer Patel, snapped me back a few years and gave me that spine tingling sense of deja vu.

Sameer wrote about how the market for Enterprise 2.0 software may evolve much the same way the enterprise portal software market did nearly a decade ago. I remember the consolidation of the portal market very well, having actively shaped and tracked it daily as an analyst and consultant. I would be thrilled if the E2.0 software market followed a similar, but somewhat different direction that the portal market took. Allow me to explain.

When the portal market consolidated in 2002-2003, some cash-starved vendors simply went out of business. However, many others were acquired for their technology, which was then integrated into other enterprise software offerings. Portal code became the UI layer of many enterprise software applications and was also used as a data and information aggregation and personalization method in those applications.

I believe that much of the functionality we see in Enterprise 2.0 software today will eventually be integrated into other enterprise applications. In fact, I would not be surprised to see that beginning to happen in 2010, as the effects of the recession continue to gnaw at the business climate, making it more difficult for many vendors of stand-alone E2.0 software tools and applications to survive, much less grow.

I hope that the difference between the historical integration of portal technology and the coming integration of E2.0 functionality is one of method. Portal functionality was embedded directly into the code of existing enterprise applications. Enterprise 2.0 functionality should be integrated into other applications as services. Service-based functionality offers the advantage of writing once and using many times.  For example, creating service-based enterprise micro-messaging functionality (e.g. Yammer, Socialcast, Socialtext Signals, etc.) would allow it to be integrated into multiple, existing enterprise applications, rather than being confined to an Enterprise 2.0 software application or suite.

The primary goals of writing and deploying social software functionality as services are: 1) to allow enterprise software users to interact with one another without leaving the context in which they are already working, and 2) to preserve the organization's investment in existing enterprise applications. The first is important from a user productivity and satisfaction standpoint, the second because of its financial benefit.

When the Enterprise 2.0 software market does consolidate, the remaining vendors will be there because they were able to create and sell:

  • a platform that could be extended by developers creating custom solutions for large organizations,
  • a suite that provided a robust, fixed set of functionality that met the common needs of many customers, or
  • a single piece or multiple types of service-based functionality that could be integrated into either other enterprise application vendors' offerings or deploying organizations' existing applications and new mashups

What do you think? Will history repeat itself or will the list of Enterprise 2.0 software vendors that survived the impending, inevitable market consolidation consist primarily of those that embraced the service-based functionality model?

box_logo.gifBox.net announced today that it has integrated its cloud-based document storage and sharing solution with Salesforce.com. Current Box.net customers that want to integrate with Salesforce CRM can contact Box.net directly to activate the service. Salesforce.com customers may now download Box.net from the Salesforce.com AppExchange.

Box.net services will now be available in the Lead, Account, Contact, and Opportunity tabs of Salesforce CRM. In addition, the Box.net native interface and full range of services will be accessible via a dedicted tab on the Salesforce CRM interface. Users can upload new files to Box.net, edit existing files, digitally sign electronic documents, and e-mail or e-fax files. Large enterprise users will be given unlimited Box.net storage. The Box.net video embedded below briefly demonstrates the new Salesforce CRM integration.

 

 

While Box.net started as a consumer focused business, today's announcement marks the first tangible manifestation of its emerging enterprise strategy. Box.net intends to be a cloud-based  document repository that can be accessed through a broad range of enterprise applications.

The content-as-a-service model envisioned by Box.net will gain traction in the coming months. I believe that a centralized content repository, located on-premise or in the cloud, is a key piece of any enterprise's infrastructure. Moreover, content services -- functionality that enables users to create, store, edit, and share content -- should be accessible from any enterprise application, including composite applications such as portals or mashups created for specific roles (e.g. sales and/or marketing employees, channel partners, customers). Users should not be required to interact with content only through dedicated tools such as office productivity suites and Content Management Systems (CMS).

Other content authoring and CMS software vendors are beginning to consider, understand, and (in some cases) embrace this deployment model. Box.net is one of the first proprietary software vendors to instantiate it. Adoption statistics of their new Salesforce CRM integration should eventually provide a good reading as to whether or not enterprise customers are also ready to embrace the content-as-a-service model.

Our colleagues over at CMS Watch have published a new report on enterprise portals. As our earlier reports here and here on the portal market suggested, the list of vendors covered in the report shows the market is now dominated by infrastructure players. Janus Boye, the author of the report is giving a tutorial on Enterprise Portal Software: Architecture and Products - Intensive Review & Roadmap for Product Selection at our upcoming conference in San Francisco, and also speaking on Challenges in Integrating Portals & Content Management Systems. The report, tutorial, and conference session would be a great way to get fully up-to-speed on corporate portals and content management.

Gilbane Boston 2011

Portals: Monthly Archives

Categories