VS 
As Web 2.0 paradigms influence (invade) corporate ECM implementations the questions I have mostly revolve around this:
Do you
1) start with whats out of the box and customize/configure the user interface for a web 2.0 delivery experience?
or
2) build a new system leveraging the out of the box ECM services for an "invisible ECM" approach?
The question can be asked in another way (as Pie and others have already asked), is ECM a platform for solutions development or an application to be leveraged for a specific purpose? The question, though, takes on a new aspect when considering Web 2.0 ends in mind.
So what do you think? Leave a comment
Comments (4)
Option 2 in principle. However, in reality, customizing the UI is more feasible and realistic.
I think the key is that if the UI works with minor mods, it is okay to use it. If it doesn't, get another and plug those ECM Services into the back.
-Pie
Posted by Laurence Hart | March 19, 2008 12:52 PM
Posted on March 19, 2008 12:52
Yeah, my thoughts too. UI tweaks are ok for small peas or POC work. But these days ECM should be more under the covers and servicing lots of enterprise needs and apps.
Posted by billy cripe | March 19, 2008 1:04 PM
Posted on March 19, 2008 13:04
ECM should be invisible and is not the center of a universe. For it to meet this goal, better integration with BPM, ERP and CRM is required.
Would be great if your next blog entry defined how those products should integrate especially when they are from different vendors.
Posted by James | March 26, 2008 6:51 PM
Posted on March 26, 2008 18:51
Definately ECM as a 'platform' offering content management services (version control, audit trails, records management, check in/out, whatever.....) to whatever application or interface works best for the user in the context of their business processes
Posted by Jed Cawthorne | April 10, 2008 2:40 PM
Posted on April 10, 2008 14:40