Old Site

This site is archived. I now update and maintain my blog here.

A view on the Autonomy/Interwoven CMS Vendor meme response

In February Kas Thomas blogged A reality checklist for (CMS) vendors which was picked up by Michael Marth at day.com and turned into the CMS Vendor Meme - I guess most of my readers are familiar with the term meme. Over time various ECM vendors were 'tagged' and responded accordingly.

As a long term independent TeamSite consultant I waited for a response from Interwoven which came courtesy of Tom Wentworth's Blog.

All of the blog posts made for interesting reading and Tom's response was open and honest - however all of the viewpoints being blogged were from the vendors themselves and therefore had some obvious bias.

Yesterday I found a blog post from Adrian Mateljan which gave an alternative response to the meme. Adrian answered the meme drawing upon his experience as RedDot CMS developer. I'm unable to work out from Adrian's site whether he has any connections with RedDot or whether his point of view is an independent one but the post inspired me to give some feedback on the Autonomy/Interwoven response.

By way of disclosure I've been working with TeamSite for over 8 years and I have represented Interwoven on client sites in previous years but not for the last couple of years. All of my opinions relate to TeamSite version 6.5 and are not relevant to any of the other diverse range of software that that they vend.

Tom W didn't see fit to score himself on each point as the meme suggested so I'll suggest one where I feel qualified to do so.

1. Our software comes with an installer program.

Yep. GUI and command line versions. Simplicity itself.

My score: 5/5

2. Installing or uninstalling our software does not require a reboot of your machine.

Nope, but like Tom I question how useful this really is. In my experience if you are installing/uninstalling/servive packing and ECM system then you'd expect some downtime.

My score: N/A

3. You can choose your locale and language at install time, and never have to see English again after that.

I'd never tried that before. Simple, as Tom says. I've just learned that French for logout is "Se d├ęconnecter".

One point, if you customise the GUI and add custom menu Items you don't appear to be able to "localise" those. I'm also pretty sure that when you build a data capture template in TeamSite you'd need to create a copy for each locale in order that field names are displayed in the appropriate language. You could workaround this using TeamSite inline callouts in the data capture template but this would mean custom localisation code.

My Score: 3/5

4. Eval versions of the latest edition(s) of our software are always available for download from the company website.

No. This has long been a frustration of mine. Your customer support account allows you to download the products that you are licensed to use from the support website. As an independent consultant there is no way I can try out new products/upgrades and service packs myself in order to recommend them to a client.

My Score: 0/5

5. Our WCM software comes with a fully templated "sample web site" and sample workflows, which work out-of-the-box.

I agree with Tom about the example workflows. They cover some sample scenarios for content publishing/deployment and I have often used them with minimal modification.

I've never used the "Component Guide" that Tom refers to. I'm not sure if it ships with TeamSite or LiveSite there is an example Templating directory which contains a lot of files and documentation but I've never needed them.

My Score: Not qualified to comment!

6. We ship a tutorial.

Absolutely, see above.

7. You can raise a support issue via a button, link, or menu command in our administrative interface.

No, but I don't see the point of this. You go to support.interwoven.com, login and file your issue. As a developer you could customise the TeamSite GUI and add a link to the support site which would satisfy this requirement. From my perspective I wouldn't want end users raising support issues to the vendor as more often than not they won't be able to distinguish between a bug in the product and a bug in our customisation of the product. Normally issues are reported to an internal development team who escalate to the vendor as appropriate.

My Score: N/A

8. All help files and documentation for the product are laid down as part of the install.

As Tom says, "Help files, yes. Documentation, no". The docs are available to download as a single bundle from the support website or can be viewed online.

My Score: N/A

9. We run our entire company website using the latest version of our own WCM products.

Take Tom's word for it.

My Score: 5

10. Our salespeople understand how our products work.

My *very limited* experience of Interwoven sales suggests that they understand the company product suite very well and how each product integrates with the others. They also seem to be a tight-knit company and the communication between sales and engineering seems to work, when there is something they are unsure of they'll go to the right person and get you an answer pretty quickly.

My Score: Not qualified to comment!

11. Our software does what we say it does.

Very general question. I always find the marketing blurb very high level and fluffy, but then it isn't really targeted at me.

My Score: N/A

12. We don't charge extra for our SDK.


My Score: 5/5

13. Our licensing model is simple enough for a 5-year-old to understand.

Agree with Tom "Since when do 5 year olds buy enterprise software?". I don't really get involved pre-sales.

My Score: N/A

14. We have one price sheet for all customers.

Tom says Yes

My Score: 5/5

15. Our top executives are on Skype, Twitter, or some similar channel, and: Feel free to contact them directly at any time.

Not sure I need to get in touch with 'top executives'. I think a better point would be to question whether it is easy to get in touch with the right people easily, e.g. developers able to contact support. I do know that most Interwoven customers have a dedicated account manager who can put them in touch with whoever they need.

Maybe Kas needs to clarify why he is asking this question. It is good to See Tom Wentworth on twitter and blogging regularly. I just wish Interwoven would give a little love to their developer portal which is missing a few very basic features.

My Score: N/A

In conclusion

I hope this made an interesting read an offered an alternative viewpoint on Autonomy/Interwoven's meme response.

Having stated that CMS vendors should "Violate these rules at your own risk" I wish that Kas Thomas could possibly follow up on his original post and let some of us who have been following know why he thought that some of the points that he raised are so important.



Leave a comment