The WCM vendor landscape has shifted again, as global information management solution vendor SDL has announced that it will acquire Tridion. SDL and Tridion are touting the complementary functionality of SDL’s translation management capabilities and Tridion’s WCM product, and the inevitable tighter integration between the two. The acquision certainly provides Tridion more stability, and gives the soon-to-be-christened SDL Tridion a strong Web content globalization story. This should also give Tridion leg up in the US; Tridion has opened two US offices over the past year or so in an effort to target the North American market, but SDL already has a bigger field organization there.
My take: this isn't an earthshaking announcement, but Tridion and SDL are stronger together than they are apart. For Tridion customers, the good news is that Tridion and SDL don’t have overlapping technologies, so this acquisition shouldn’t lead to any forseeable pain for future upgrades. And the Tridion management team will be in place for the next two years, lending some stability to the acquisition.
SDL and Tridion will be announcing a technology roadmap and integration timeline sometime in the next six weeks. Stay tuned.
Connie, Erica and I attended Adobe's analyst days this week in New York, and Connie and I had a chance to sit down with Bruce Chizen, Adobe's CEO, over lunch yesterday. Adobe is a major player in the Web 2.0 universe, with Flash (and the new Apollo technology) competing with Ajax-based technologies for creating rich internet apps (RIAs).
While Ajax is more open, Flash nonetheless can boast better cross-browser and cross-platform support, especially when moving into the realm of mobile devices. Ajax can run into problems just between Internet Explorer and Firefox, but the Flash player works in both browsers as well as in Safari — and on Linux too. In the mobile, world, Adobe showcased a first-of-its-kind tool for testing how a Flash movie looks on a variety of different cell phone models, with extremely rich metadata about each device. It was able to simulate things like the appearance of the screen outdoors vs. indoors, and the performance of a movie on different phones. We also saw a Sony PlayStation 3 running on Flash content.
One interesting question was about whether PDF was threatened by Microsoft's recent moves to create a replacement standard in its XML Paper Specification (XPS). Bruce's answer was, to paraphrase, "No." He believes — and I agree — that it's too late to displace PDF with any format, and especially not with one whose promoter has the goal of selling Windows and Office in mind. Adobe's recent submittal of PDF to the ISO will really help its adoption in government, too.
I recently spoke with an IT manager who came up with a great analogy for a problem I continue to see in the WCM space. He was telling me about how much customization his team has needed to do while implementing a WCM solution, and how he expected some features to be more out-of-the box, like advanced content authoring tools. He commented, “At Christmas time, the vendor sent us one of those gift baskets that vendors sometimes send. You know what those baskets are usually like - wine, cheese, candy. But you know what they sent us in this year’s basket? Brownie mix. We had to bake our own holiday gift. I wanted to call them up and tell them, ‘This is exactly what is wrong with your product!’"
Today, IBM announced that it will bring Google's consumer-style Web utilities, called Google Gadgets, into WebSphere Portal 6.0 and WebSphere Portal Express. Nearly 4,000 Google Gadgets will be available to WebSphere Portal 6.0 customers at no additional cost. Google Gadgets include things like package tracking, Wikipedia searches, language translators, weather, and--my personal favorite--the Virtual Flower Pot. (Just today I realized that the reason my red tulips weren't growing is because I wasn't watering them by mousing over them frequently enough.) What this all means:
Last spring, Forrester introduced the concept of retention management, which extends records management to all content from creation through long-term retention and destruction (check out the Retention Management document).Seems simple enough, but with so many repositories of information (hard drives, network file shares, SharePoint sites, email servers and archives, and any number of managed repositories) extending retention policies to all of it is all but impossible.
To get a sense of how organizations address retention management, I reached out to approximately 300 companies for a research interview, figuring maybe 10 would be willing to speak about what they are doing.In an indication of how hot the topic is, over 30 companies wanted to speak further.Having conducted about half the interviews so far, it’s clear we are at the very beginning of the learning curve for retention management.
I just got off the phone with a small software startup called Get Back Software. For $3/team member/month, a department head can use Get Back’s product, called Postware, to put a cap on the number of emails that people in their group can send. The thinking behind this new software as a service is that email has turned from a productivity-enhancing tool into a productivity sinkhole, and that by giving workers a limited “email allowance” you can change their behavior—you can get them to think twice before cc:ing their boss or replying to all, or inviting a colleague to lunch via email rather than by walking down the hall or picking up the phone. I agree with the core premise here—that the productivity benefits of tools like email (and instant messaging and mobile devices) go down when the volume of communications hits a critical mass and when workers have no control over the volume and frequency of interruptions to their work.
My mind is a sieve. It can take a few requests before I remember to do something. And even with a few prods, it takes a while for me to get moving. But I've gotten so many requests along the lines of "What does a collaboration strategy document look like? What should it include?" that it's all I'm thinking about these days.
I will be publishing a sample collaboration strategy document in Q2. If you have developed and documented an enterprise collaboration strategy and would be willing to share it with Forrester for the greater good of industry research--with our promise to guard it and not share it with anyone outside the company--we would love to include you in our research. You can find me at firstname.lastname@example.org.
On Friday morning I ventured out in the newly-fallen snow for my morning latte. The tree branches were heavy with wet snow. It was gorgeous. But promptly after settling in at my desk I miscalculated the length of my arm and spilled about 12 oz. of coffee and milk all over my laptop. Little red lights blinked a few times and my screen went dark. That was it. Done. Gone. Dead.
I got on the horn with Forrester's top-notch IT group and I had a new laptop at my doorstep in about 24 hours. Forrester IT rocks. But I'm not here to bemoan my clumsiness or sing kudos to our help desk. I'm here to tell you what happened when I took over my husband's laptop for the remainder of the day. He doesn't have Microsoft Office installed on his machine; he uses OpenOffice.org 2.1.
I had no choice -- I gave it a shot. I was able to get some of my tasks done, but not all. And the learning curve was not insignificant. For example:
Something really big is happening. Many companies and even software vendors aren’t aware of it because they’re so busy trying to get their arms around content—put it in repositories, integrate the repositories, manage corporate records, get people to stop emailing documents around—that they’re way too busy to see the ground shifting underneath their feet. This groundswell is about putting content to work—and that means, quite simply, doing something with the content that’s being managed so it creates business advantage.
For years, enterprises, vendors, integrators, consultants and others (including me) have strived mightily to get content under control. It’s still a massive problem: there’s so much content — written documents, presentations, email, web pages, spreadsheets, graphics, videos, podcasts . . . the list goes on — and it’s in every filing cabinet, drawer, hard disk and memory stick. Even today, after years of investing in document imaging, document management, collaboration, and web content management systems, most content is not locked down, versioned and searchable using metadata or tags. But it’s time to move on — “simply” (that’s a laugh) managing content isn’t enough.
This week, the mainstream press reported that Microsoft made a Wikipedia “no-no”: Microsoft offered to pay an independent contributor — Rick Jelliffe — standards expert and the CTO at an Australian tech company — to investigate the accuracy of, and change, if necessary, technical articles about Open XML and Open Document Format (ODF) on Wikipedia. ODF is an OASIS and ISO standard and Open XML is Microsoft’s alternative, currently an ECMA standard and potential ISO standard. Kyle McNabb and I were talking about this incident. Here are our thoughts: