Thomas’ point here about micro-silos is the achilles heal in most E2.0 solutions as compared to W2.0.

The primary challenge when you step into the enterprise is that people need to work across teams while also respecting the permission issues which are not present in the Web 2.0 model where everything is open.

So, when each workspace in an “E2.0” model carries its own Read permissions, it becomes a silo and prevents the benefits of open bookmarking, tagging and search.

I talk about how to solve this problem, and go into detail about the two types of Silos (Content Type and Workspace Boundaries) in Enterprise 2.0 and the importance of SILO SMASHING: http://traction.tractionsoftware.com/traction/permalink/Blog1049