Thoughts on Content Management and Open Source.

Wednesday, January 26, 2005

Big Man

Sun's announcement that they are opening up 1,600 patents, coupled with I.B.M. announcing that they are opening up 500, reminds me of an anthropology class in college where we learned about the "Big Man" social organization structure. In the Big Man system (practiced in some isolated islands in the SouthWestern Pacific), leaders vie for popularity and influence by outdoing each other throwing feasts and giving gifts.


The Big Man - almost always a male - is an elaborate version of a village leader, but unlike a village leader, he often has supporters in several villages and is a somewhat more effective regulator of regional political organization. Big Men combine a small amount of interest in their group's welfare with a great deal of self-interested entrepreneurialship for personal gain.

reference


Is this what Sun and IBM are doing?

Monday, January 17, 2005

Mid-Market CMS

EContent Magazine recently announced the 7th edition of CMS Watch's CMS Report. According to the article, one of the big trends identified by the latest CMS Report is that the mid market of CMS products has really taken off. I too have noticed an increase attention paid to mid-market CMS vendors and have attributed it largely to a rejection of the big vendor's push towards ECM. Clients that I have spoken to are starting to be suspicious of the ECM vision and monolithic architectures. They are turning to targeted, best of breed solutions. These systems can be deployed with smaller initiatives that are more closely aligned with the needs of the users and enjoy a shorter time to benefit. There is also considerable interest in ASP solutions offered by CrownPeak and Atomz. By the way, the same market forces that are helping out mid-market CMS products are also driving adoption of Open Source CMS products. Clients are recognizing the practicality and benefits of a heterogeneous CMS infrastructure and are thinking of content integration strategies rather than ECM.

In addition to being less complicated and easier to use, targeted content management solutions are considerably cheaper than ECM products. The evolution of mid-market ECM is going to be very interesting to watch. Some of these companies will be acquired by the major players. Others may turn into the next generation of ECM companies by filling out their functionality either through acquisition or organically.

If you are selecting a CMS, you should consider targeted solutions and actively manage the risk that is introduced by this market volatility. Plan an exit strategy as part of the selection. Look for open standards and interoperability that will make the solution substitutable, wholly or in part. Make sure that your content is does not get locked up in proprietary formats. Stick with technologies that you feel comfortable supporting. Spread your bets. Your content will outlive any technology choice you make today. Plan for it.

Tuesday, January 11, 2005

I.B.M. to Give Free Access to 500 Patents

I noticed this article in the New York Times today. I not sure what making "software patents freely available to anyone working on open-source projects" actually means but it sounds like a significant change in strategy. Such a nice reversal from the ridiculous patent squatting practices of the 90's.

Selecting a CMS with Narratives

I just ran across this article by James Robertson of StepTwo Designs. The general point is that the best way to convey the requirements for a product is to create a narrative that describes the business need for the system. I like this strategy. It is a refreshing departure from the typical "column fodder" technique where customers create feature matrices to compare products. In addition to keeping focus on the business need, which is always a good thing, I think this technique breaks what I think are dysfunctional buying and selling habits created by checklist based selection.

On the buying side, putting a feature on a checklist makes an assumption that the feature (and the way it has been implemented) will solve a particular business problem. This assumption can be incorrect because there may be better ways to solve the problem. For example, auditing may be a more effective way of keeping a history of changes than versioning. Or, the feature may be implemented in such a way that it is unusable to the users.

I think that matrix buying leads to bad products as well. To compete, product companies need to be able to "check-off" certain features. This can either lead to marketing overstating functionality of the product or, worse, products growing un-useful features for checklist coverage. Having the most features does not make a product the best. Not only is there a tendency toward diminishing returns, there comes a point where additional features actually reduce the utility of the product by making it overly complicated.

So what do you do with narratives? State what your users need to do, and challenge your vendor to show how that goal would be satisfied with their product. If there is a disconnect (and there will be most of the time) have a dialog about how the product can be modified. Better yet, talk about how other customers have used the product to meet a similar need.

The narrative technique seems less quantitative than the matrix method. However, I think that these matrices are always less scientific than they seem. Focusing on narratives (both of the problem and the solution) is more work for both the buyer and the seller because they have to communicate a lot more. More importantly, the business users are more involved. They can visualize using the solution in their context. Just remember to control the natural desire for bright shiny objects.

Friday, January 07, 2005

Microsoft may be regaining interest in MCMS

I just read on CMS Watch that Microsoft may be re-energizing their efforts behind MCMS. The news comes from a presentation made by Mark Harrison (see blog entry for slides) which indicates MCMS 2002 will coexist and integrate with SharePoint. The slides also reference the vibrant community of add-on providers including Artemis's Open Source MCMS.Rapid solution which creates a starter site that can be used to kickstart MCMS development. However, I would expect Microsoft to cannibalize any worthy innovation.

There is a mention of special solutions for industry verticals (a theme that I have been hearing a lot in the CMS space). Currently there are solutions being developed for municipalities and health care