Going back a few years, I used this chart from Geoffrey Moore from Dealing With Darwin – internally, we call it the two-humped camel jpeg -- to talk about some of the changes occurring in the enterprise IT space, and more specifically, in the content management space.
The way to interpret this diagram is like this…(Per Harvard Business Review)
In the Content Management space, we clearly have lots of left-hump, right-hump confusion at the moment.
When we say the phrase “ECM,” we immediately create left-hump images – images of complex, expensive, mission-critical applications driving high volume transactional processes. Or images of case management systems that operate at scale, linking together disparate content and data repositories to create a consistent and rationalized view of the customer in context.
SharePoint originally entered the market as a project-team-focused collaborative solution dealt out by IT staffs to business people to handle very basic file share replacement functionality. Clearly, a right hump solution. However, as time has gone on, and the scale and complexity of SharePoint have grown – and as SharePoint began to be viewed as a business platform rather than a document-sharing application -- it migrated into Complex Systems Land. This confusion is clearly reflected in AIIM’s just released SharePoint Industry Watch, Connecting and Optimizing SharePoint – important strategy choices.
But since SharePoint came along, the market flipped again, and there’s another set of solutions like (just for example, NOT intended as an exhaustive list) Evernote, Box, DropBox, Google at Work, Office365, and M-Files clearly focused on right-hump land. And truly opening up the market to thousands of companies and organizations who previously and justifiably viewed document management (or heaven help us, ECM) as something way beyond their means.
Of course, there is nothing wrong with EITHER the left hump or the right hump. They are just different. I like to think there are two questions we should ask about a technology solution – 1) is it good technology?; and 2) is it appropriate technology?
I was reminded of this Complex Systems/Volume Operations dichotomy last week by an article in Forbes, The One Thing That Can Transform An Idea Into A Phenomenon.
Think for a moment about small businesses with between 10 and 100 employees. Just as a data point, there are 1,074,459 of these firms just in the United States.
How many of these 1,074,459 companies would be interested in a left hump “ECM” solution? Probably less than 1%.
How many could benefit from a right-hump “good enough” document management and workflow solution? I would bet almost all of the remaining 99%. How many of these have even rudimentary document management capability and how many are just utilizing a mess of unmanaged file shares and local hard drives? I’ll bet the ratio is 5%/95%.
I was talking to some colleagues about this "keep it simple" challenge today, and they came up with a good personal analogy that is extendable to organizations. How many people use all -- or even a majority -- of the functionality built into Excel? Answer -- probably just a very few finance types. How many just want to do some pretty simple things with spreadsheets, things that are terrifically useful but not very complicated? Almost everyone else.
I recently spoke with a legal clinic that had these fairly typically information chaos challenges:
Clearly, this legal clinic needs mid-range right hump functionality. Complex Systems Land is not even on the radar screen.
Which brings me to my point, and the points upon which I would like your help. What does a company with 10-100 employees need to know to simply manage documents effectively and responsibly? How can they do this for less than $25,000? (Can they?)
Post a comment and let’s get the “Document Management on a Shoestring” conversation started.