Content management - how smaller companies can learn from larger Enterprises


how smaller companies can learn from larger

Recently, I got around to reading the AIIM "State of the ECM Industry 2009" report published at the end of March. It's based on a survey of 568 respondents, with a majority (52%) from large organizations (1000+ employees). There was a high percentage (21%) of people from the local and national Government sector, and there was a distinct US & Canada (61%) skew.

What struck me about the report was that it could be seen as a prescription for smaller companies and startups, along the lines "This is what big companies don't like about themselves, you have an opportunity to do it differently". After all, one of the good things about a new startup is that you don't have to make the same mistakes.

It's easy to say, harder to do, but in my experience the degree of "start as you mean to go on" that smaller companies can muster is a good way to keep the growth curve as accelerated and smooth as possible. When you have to switch-in a new process or workflow, it can be a massively disruptive force at a time when you can least afford disruption. Of course, cost is a factor - many a person has left behind an expensive ERP system at their former company, unable to replace it in their new startup. But with the growing availability of Free and Open Source software packages, that isn't the only factor any more.

So what ails the larger Enterprise in their Content Management, and how can SMEs adapt this as guidelines for a better strategy?

By inverting the AIIM ECM findings, I'd say they are:

(1) Start with a low-cost strategy and keep to it - never think that you will switch to an expensive solution at some point in the future. Make other requirements such as compliance and legal discovery a sub-set of the cost saving requirement.

(2) Treat e-mail usage as a dangerous drug - if you become over-dependent you will find it impossible and/or expensive to quit. If e-mail attachments become the main method for communication, it will get out of control more quickly than you'd prefer.

(3) Don't allow documents to be buried. It isn't enough that it was ready by the deadline and reviewed at the meeting. It also has to be just as easy to find in 6 months time.

(4) Beware multiple solutions. It's easier to let two teams 'go their own way', but then very hard to re-integrate them. Keep asking why does it need to be different and whether anything can be done to integrate them across the top.

(5) Don't abdicate business solution decisions to IT only (even when it is a part time role done by one of the engineers or founders). This is as important as all your other strategic decisions, and it will have a very significant impact on your company culture.

(6) Get support directly from vendors rather than consultants. They have up-to-date knowledge and it is in keeping with low-cost guideline #1.

(7) Enterprise content will become a large repository quicker than you think, so the earlier you start to think about Enterprise search, the better.

(8) Blogs and wikis are useful but remember they are content too and will need to be included in your records management.

I'm hardly neutral on this topic, but I don't see or accept why any startup or small company cannot develop a short strategy paper that sets out their business solutions needs and priorities. If they can't afford Oracle or SAP using third party implementers at this stage, it is totally not a problem. In fact, guideline #1 says it would be better to find an open-source alternative.

Tags: Document management and control, New Product Development

Paul Walsh

Written by Paul Walsh

Paul Walsh was one of the founders of Cognidox. After a period as an academic working in user experience (UX) research, Paul started a 25-year career in software development. He's worked for multinational telecom companies (Nortel), two $1B Cambridge companies (Ionica, Virata), and co-founded a couple of startup companies. His experience includes network management software, embedded software on silicon, enterprise software, and cloud computing.