Having a single monolithic system to manage all the content in the enterprise has always sounded like a great idea, but it's simply too complex to implement consistently and projects fail more often than not. It's time to face facts that enterprise content management is not the answer.
File sync and share has been all the rage in content management in the last couple of years, but as we learned with search and enterprise social, you need to be more than a one trick pony to survive in this business.
When I learned Netflix has a Chief Content Officer, that alone caught my attention, but when the number of new subscribers driven by House of Cards came out this week, it really drove home the importance of content in driving business. Maybe your company should have a CCO too.
There's a notion that in order to collaborate effectively, you need to be in the same room with a whiteboard to do it. I categorically reject that notion and I don't even think it's realistic to expect people to be able to be in the same building anymore.
Do you still believe your users are sitting at their desks using beige box PCs? If so, you could be living a content security illusion and you really need to wake up because your users can find their way around every stop sign you put up using their mobile devices and simple cloud apps.
While it's clear the content management industry is evolving as content goes in motion and moves to the cloud, vendors and customers are having a tough time balancing that transition (and that could be true for just about any enterprise software).
Marissa Mayer caused quite a ruckus last week when she announced a ban on telework. In this week's Editor's Corner, I write an open letter to her and suggest she get together with Andrew McAfee, the MIT professor who coined the term "Enterprise 2.0." He could teach her a few things about how enterprise social software could encourage the very type of innovation she is hoping to foster without banning telework.
With all the choices out there, including open source platforms that provide a framework for greatly customizing a content management system, I'm wondering why anyone today would go the trouble of creating on on their own from scratch. It seems it would put you behind from the get-go. You would think we learned that in the 90s.