We came across a study entitled "The 2008 Tribalization of Business" while preparing to publish a new Gilbane white paper on web experience management. The "Tribalization" research looks at communities and online marketing: how they deliver value, obstacles to making them work, what contributes to success, and how marketers measure effectiveness. Highlights of the research (co-sponsored by Beeline Labs, Deloitte, and the Society for New Communications Research) are reported on marketingcharts.com.
This datapoint caught our eye:
"The greatest obstacles to making a community work are not related to technology or funding, the study found; rather, getting people [to engage] in the community (51%)."
Community is one of four components of engagement strategy discussed in the new Gilbane white paper (the others are personalization, user-generated content, and collaboration). In the paper, we provide some guidance about making communities work not just at start-up but throughout their lifecycle.
Engage Me! Web Experience Management as the New Business Imperative is the companion white paper to a webinar in which we participated with Linksys and the Colorado Department of Transportion. The webinar and paper are sponsored by FatWire. An archive of the webinar is available for viewing, and the paper is now available for download on the FatWire site. It will be posted on the Gilbane site later this month.
Join the Gilbane Group and Vignette on July 30, 2008, at 2:00 p.m. (Eastern) for a webinar entitled “The Keys to a Targeted Online Experience.” The primary topic will be the synergies derived from the tight integration of Web Content Management-Portal-Collaboration suites versus stand-alone applications.
Click here to register.
An attendee at an industry conference recently asked me, “Who are Vignette’s products really best suited for?” While the full answer to this broad question would require a consulting engagement to deliver, the short version is “medium-sized and large enterprises that have needs for a unified WCM, collaboration, and portal solution.” While each of these Vignette applications is fully functional on its own, the real value proposition of Vignette’s products stems from the synergies of tightly integrating all three modules. In support of this statement, one client several months ago bluntly stated that for the kind of static Web publishing it had in mind, the Vignette Content Management product was “too complicated and too expensive.” I agreed. But for larger enterprises with collaborative intranets, extranets, or public-facing internet sites - especially those with demanding requirements for dynamic content and personalization - less sophisticated Web publishing solutions would certainly fail, regardless of price.
In a recent consulting project, the Gilbane Group had the opportunity to get a hands-on look at the current version of the Clickability Platform. Several marketing-oriented product enhancements over the past year will be of particular interest to our clients. While the product maintains its strengths in traditional online publishing (due in part to its origins in the publishing industry), there have been major improvements in areas such as analytics and reporting, social computing, and user interface design. In fact, Clickability has re-oriented its Platform to align specifically with the usage and campaign requirements of non-technical online marketing managers. Although product features such as in-context editing, workflow, library services, and user management, remain important and robust parts of the product, the new social computing functionality for online visitor collaboration have done much to bring Clickability to the forefront of Web 2.0-oriented content management offerings. This functionality includes out-of-the-box support for visitor loyalty profiles, discussion boards, visitor ratings, blogs, wikis, and podcasts.
Combining these new social computing components with improvements to Clickability’s analytics and reporting capabilities makes the product a natural fit for companies looking for a Web content platform to support online marketing initiatives. Areas of improvement within analytics and reporting include visitor analysis, profile targeting and reporting, campaign management, A/B split testing, reporting dashboards, ad weighting, and embedded in-context statistics. While organizations looking for a Web content management application to support traditional online publishing can still successfully use the product, they may find the marketing-orientation of the product unnecessary or awkward. And because good analytics and reporting in the service of online campaign management delivers high value for online retailers (in the form of higher average sales prices and better conversation rates among online shoppers), the product may demand a higher price than those publishing static HTML sites can justify. But for at least one of Clickability’s target audiences - online retail marketing managers - the new version of this platform warrants careful, hands-on consideration.
Several clients have recently asked about Day Software and whether its Communiqué is still being actively developed. The answer is a resounding “yes.” In fact, the product remains one of the most technically sophisticated and flexible content management applications on the market. Because Day continues to be highly involved in Java development communities, information technology departments are usually its strongest supporters. Communiqué’s technical flexibility affords IT rich integration and product-extension capabilities and an overall standards-based architecture that often aligns well with services-oriented design methodologies.
Unfortunately for Day, its focus on the technical side of the product has been at the expense of simplicity and elegance in the user interface, producing at times a product too complex for non-technical business managers. To its credit, the vendor has recent made improvements in user interface design. Its longstanding reputation for UI complexity, however, still sometimes causes enterprises to eliminate Day from serious consideration.
Given Day’s past marketing foibles in the U.S. (including a near withdrawal in 2002-2003), there still lingers in the minds of prospective customers some question about the vendor’s commitment to the U.S. market. We feel comfortable saying that Day has demonstrated a strong commitment to this market over the past three to four years; and we see this trend continuing with its recent UI improvements, ongoing leadership in Java development, and a nascent but well-deserved increase in interest from enterprises trying to combine integrated multi-module solutions (Web content management, digital asset management, document management, portal, and collaboration) with technically strategic services-oriented architectures.
While many of our clients use analytics applications to support their WCM projects and e-commerce initiatives, other clients not yet using analytics often ask what value can be derived from doing so. The answer depends on the purpose of the client’s website.
For online commerce sites, analytics functionality can be invaluable in that it allows companies to track user behavior on the site and to correlate user behavior with conversion rates, average sales prices, and other useful sales metrics. The bottom line is that analytics almost always increase online revenues. Analytics can also be of great value to non e-commerce clients by enabling them to monitor content consumption rates and to gauge the relevance and effectiveness of content through the analysis of consumption patterns. This naturally makes analytics (sometimes built into “campaign management” modules) indispensable to marketing professionals interested either in optimizing content dissemination on information-based sites (“content portals”) or in maximizing profitability on retail sites.
Please join us on May 8, 2008, at 1:00 p.m. (Eastern), for a webinar sponsored by Bridgeline Software entitled: “Marketing Trends: Enabling Intelligent, Analytics-Driven Content.”
On a recent phone call with a Gilbane Group client, we were asked about the defining differences between WCM applications and portal applications. This question has two answers – a theoretical one and a practical one. In theory, portals provide a doorway (portal < Latin porta, gate) that, when opened, allows content consumers to view a particular set of content. The exact set of content to which consumers are exposed is (a) dynamic, and (b) controllable either by the application administrator or by the consumers themselves. Because the function of the portal essentially rests in this “doorway” or “frame” function, some customers see portal software as an empty shell or framework, with a set of underlying services, to which content-connected portlets can be added. WCM applications, on the other hand, theoretically provide all of the features and functions required to create, manage, expire, and archive content. This feature set typically includes authoring and editing tools for multiple content types, automated workflow, versioning, audit control, channel management, metadata management, library services, templating, access controls, personalization etc.
In practice, however, the feature sets of WCM and portal applications often overlap. One vendor’s portal product might provide the same feature as another vendor’s WCM application. Because portals are composite applications that expose component applications, this phenomenon also extends to products or modules such as ERP, CRM, search, collaboration, campaign management, etc. For this reason, depending on how vendors group features and functions in their product offerings, any given set of WCM or portal requirements may be satisfied by a variety of product combinations. One vendor’s WCM application may suffice. Another vendor’s portal product may also be a good fit. And a third vendor’s solution may include WCM, portal, and collaboration modules.
Because of this variation in vendors’ grouping and naming conventions, Gilbane clients should, during the technology selection process, seek solutions to their set of content management problems without becoming distracted by the exact names or number of modules or products required to provide the solution. Let vendors include whatever products they wish in their RFP responses, but hold them responsible for (a) satisfying every requirement, (b) identifying the modules that satisfy each requirement, and (c) giving a total price for all of the modules included in the response. In the end, “WCM and portal” by any other name is still “WCM and portal.”
While WCM needs-analysis and generation of a master requirements document (MRD) usually prove to be quite in-depth undertakings for most clients, the RFP submitted to vendors should aim to be as simple and concise as possible. Here’s why.
When vendors receive a very long, nuanced description of a functional requirement, it becomes easier for them to craft a response that technically satisfies the requirement and simultaneously to withhold other relevant and more meaningful detail. On the other hand, when vendors receive a brief description of a functional requirement or category, along with specific instructions to provide as much detail as possible (at risk of not receiving credit if enough detail is not provided), they often feel compelled to write as much they can. The abundance of information found in such responses usually allows the customer to discern just how well a vendor’s products or solutions match line items in the MRD.
Recommendation to Gilbane clients: After detailed needs analysis and creation of an MRD, pare the language for each functional criterion in the RFP to a somewhat general level. For example, rather than inquiring specifically about content locking models (along with the other 20-30 minute components within library services) ask instead for a complete description of what the vendor’s solution provides in the library services category. It is essential to state that more detail in the response is better than less, and that if a vendor omits relevant information, they may not receive full marks for that category. Following this suggestion, you will be surprised at how much more insight you gain from vendors RFP responses.
Over the next few months, I will post a series of 6-8 best practices for ensuring a high degree of usability in WCM implementations. This first entry in the series focuses on the ability for users to author content in the context of actual web pages.
While many vendors claim to support in-context editing, there is a lot of variation in how this feature is presented to users. In some cases, content authors fill in HTML forms and then click a preview button, which renders a virtualized copy of the web page. In other cases, authors double click on a staged version of a web page, which launches a WYSIWYG editor. Upon saving content in this editor, the author refreshes the web page and sees the updates. In the best cases, authors can simply edit content directly on web pages without having to fill in separate web forms or to launch an external editor. Content on web pages can be edited just as though it were in MS Word.
These differences may at first seem trivial, but it quickly becomes apparent to those who spend much time authoring content or creating web pages that eliminating unnecessary steps and reducing the number of applications in these highly iterative processes produces dramatic time savings throughout the organization. For example, if an enterprise has 25 content authors who each maintain 10 web pages daily, and each page update takes just 10 extra minutes because of redundancies, the time wasted over one year totals more than 10,000 hours. This represents about $500,000 of unnecessary labor costs.
Recommendation to enterprises: Be sure to analyze carefully during vendor demonstrations exactly how content can be edited directly from a web page. The most highly usable WCM systems will allow you to treat the web page like word processor.
This is just a quick reminder to our Analyst on Demand subscribers that the results of our survey on the usability of commercially available content management solutions will be available in early September. The data will come directly from the feedback of the solution providers' customers. Vendors covered will include Interwoven, Tridion, Vignette, FatWire, Percussion, RedDot, EMC/Documentum, CrownPeak, Mediasurface, PaperThin, Oracle, Day, Hot Banana, Clickability, Acumium, and others.
