Rules of thumb can be dangerous — because of the inherent broad generalizations. But they can also be quite useful, especially if they highlight something that may be unpleasant to hear, but shouldn’t be ignored. Continue reading “Your CMS will be 7 times as expensive as you think”
I’ve said this before, in various ways. But sometimes, the simple analogies seem to work the best: if you think of SharePoint, think of it as a Swiss Army Knife.
That sounds great, doesn’t it? It’s like the multi-tool of content technologies. Imagine a major vendor and integrators turning up at dinner to explain how great their Swiss Army Knife is for any purpose, and yes, it’s excellent to carve your food with, too. Why go with just a knife, if you can have a whole range of additional functionality in one system? Continue reading “SharePoint is a Swiss Army Knife”
I tend use cars as a metaphor to describe the differences among software products. Even in internal discussions among our team of analysts. Which is how this came up last week: I described a particular system as a Toyota compared to another vendor’s Ferrari, “never mind the fact that Ferraris are expensive and hard to keep running, they’re still in a different league.” To which one of my colleagues said, “Yes, but you’d still buy one.” Continue reading “Do you really want a Ferrari?”
I sometimes warn that a vendor’s content management system is well suited to “simple” scenarios, but not necessarily a good fit for “more complex” cases. That’s a bit problematic: “simple” and “complex” are very subjective. So let me elaborate. Continue reading “Do you need a simple or a complex CMS?”
Microblogging is the quintessential “keep it simple” service. So when a vendor adds a seemingly minor new feature, that’s relatively big news. (Remember when Twitter added “retweets” last year?) Naturally, when Yammer announced its “community” functionality last week, it was immediately followed by a few gushy reports on what a game-changer this was. Rather than go by the demos, I waited until the service actually became available yesterday to have a look. Continue reading “Yammer not ready for the enterprise”
Quick question. If a conference runs simultaneous tracks on “Enterprise Search,” “Document Management,” and “Company XYZ’s project to replace the intranet with microwikiblogging,” which will have the largest audience?
I’d venture a guess that most people are drawn to the the experimental and innovative, rather than to the mundane reality of complicated enterprise tools. That’s only natural, certainly at a conference. You go there to be inspired, not to be reminded of that system designed to do essential, but relatively boring stuff; a system which, on top of that, is still exhaustingly difficult to get right. Call it content technology escapism, if you will. Continue reading “The dangers of social software”
Over the years, I’ve seen a large number of web site functional designs, technical designs, requirements, wireframes and mock-ups. But usually, the one thing missing from the planning of a WCM-driven web site is what’s most likely to shoot the implementation in the foot: the functional design of the CMS back-end. The form & function of how the CMS will work, look and feel for the end-user of the system, not the visitor to the web site, is too often overlooked. Continue reading “Why you’ll throw away your CMS in 3 years”
A lot of my time is spent evaluating technology, and I have a confession to make: the licensing is one of the least spectacular bits to review. It’s certainly relevant, and always one of the things we discuss, but it rarely makes the top-10 issues in a review. Continue reading “Open source: it’s just a license”
Spring is here, and, as in Autumn, this means new products released and new version numbers. But how major or minor will the releases really be? Can you tell from the versioning alone? Continue reading “Software versions – how strange the change from major to minor”
Google has announced its new Search Appliance, version 5.2. As usual, this has been marked by a slew of presentations — and of course, a video on YouTube. Probably the main upgrade: a 10 million document limit on one server.
The box, dressed in imperial yellow — or somewhat more irreverently: the pizza quattro formaggi — of course goes with the times. Faster (probably multi-core) processors allow for the higher document count. That’s not so much Google’s achievement, though you shouldn’t forget that this is one enterprise search solution that actually comes with the hardware to run on, and the company makes sure it can handle its workload. But what else is new? Continue reading “Google Appliance: the Emperor’s new box”