Web 2.0 in ECM: lots of little UI Tweaks or Whole-Hog Architecture Re-engineering?
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
