As senior director of IT business partnerships & planning for platforms for Marriott International, Meghan A. Walsh works a little here and there with Web Content Management Systems (CMS). Kidding. She works in them a lot.
"Content management is not a one-size-fits-all task and yet vendors, for the most part, treat it that way," Walsh told CMSWire. "Every vendor tells me he can deliver content to multi-channels from one CMS, but I've not yet seen it proved. However, I'm still learning and meeting with vendors so maybe I'll have a different answer for you in the next couple of months."
Walsh talked with CMSWire about the challenges of running a CMS for a large, multi-channel organization.
Marriott wants to move some of the presentation/digital experience responsibilities from the Web Content Management (WCM)/Web Experience Management (WEM) platform to apps or custom apps.
Stressing there is no "all or nothing" in the digital space, Walsh said that while Marriott wants to remove presentation configurations and controls from content, it doesn't mean they will all be moved to the application layers. Some, she said, may still be managed in a CMS, and separating presentation from the actual content elements is what is priority.
"A key driver here is that the more closely presentation controls and content elements are tied together, the fewer channels in which that content may be used," said Walsh, a keynote speaker at the Gilbane Conference earlier this month. "For some content in some channels, this tight relationship may make sense, but I believe there is a core set of content that is re-usable across channels (web, social, mobile, email, TV, kiosk, etc.)."
What does she want to avoid? Maintaining as many versions of the content as there are channels. "That is inefficient," Walsh said, "and brings unnecessary risk to our relationship with our guests."
Approach to Different Channels
Is Walsh taking the same view for different content delivery channels (e.g., mobile, car, kiosk, web)? She believes the content platform should be able to feed all of these channels.
"We'll see if my gut is right and that there is core across all plus channel specific content for some," Walsh said. "A great opportunity is if we have solved the common content challenge through accessible, presentation-agnostic content then we can better focus and deliver on channel specific needs when they do arise. Right now, every feature, every content conversation is channel-specific, which requires huge amounts of energy."
Content Management Challenges
Wherein does Marriott's challenges lie here? People, process and technology, Walsh told us.
While some desired features and capabilities are not supported by its current technology, Walsh said she focuses on how her organization uses its current technologies, and, she added, whether it uses them to deliver the right type of content and experience.
"So, yes, I believe some of the technologies we currently use may need to be replaced," she said. "But determining that is part of the process we are undertaking now."
Platforms in Walsh's world means a combination of technologies, not a single one or even a group provided by a single vendor.
"We have some work to do to in assessing the current software we use, what we use it for, how we use it, and whether it can help us meet digital goals," Walsh added.
State of the WCM/WEM Space
We asked Walsh about unmet challenges in the WCM/WEM space around multi-channel (device) support and if vendors want to close the gap.
Walsh hears and sees WCM feeding traditional web, mobile and occasionally email.
"It's as if," she said, "there is an artificial boundary because we've historically use the word 'web.'"
Vendors should acknowledge that content can and sometimes needs to be widely distributed and that creation of content abstract from presentation has value, she said.
"There has been a huge swing toward in-context editing, which has value, but in the right situations, not all situations," Walsh said.
What Will Change for Marriott?
As it removes presentation from the CMS, most of Walsh's functional requirements (workflow management, version management, support for translated copies, reporting, etc) do not change, she said.
According to Walsh, key areas that require more scrutiny include:
- Content author experience. How do we make it easier for non-technical and casual authors to create, edit and publish content? Walsh said the move to in-context editing has been a direct response to years of complaints about "how awful content entry experiences have been." However, she added, she needs to balance having an understandable, usable content author experience with managing structured, presentation agnostic content. "There is natural tension between in-context editing and an adaptive content approach," Walsh said. "Many vendors are now offering dual-entry opportunities (traditional console + in-context), but that also requires you use that vendor's presentation layer. Pros and cons of that are part of a whole other conversation.
- Extensibility of the CMS. Can the CMS easily interact with other technologies in our platform? Can we customize without risking our support contract or our site? How easy is the CMS to code against?
- Distribution of content. "If we cannot build an API to deliver content to multiple channels both inside and outside our organization, then that CMS is of no use to me," Walsh said.
"No one has convinced me he can be my everything," Walsh said. "In fact, I've been told what I really want doesn't yet exist. That's disappointing."
- 5 Tech Trends We'll See More of in 2014
- Is Collaboration Limited by Organizational Structure?
- Top 10 Things to Measure in Google Analytics
- Navigating the Microsoft Forms Roadmap #SPC14
- This Picture Tells the Big Data Story
- Does Dropbox for Business Have a Secret Weapon?
- Lessons Learned From Cargill's Yammer Enterprise Launch #SPC14