Sharepoint and Enterprise 2.0: The good, the bad, and the ugl...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 4 people (0 private), first by anonymouse user on 2009-03-23
- Grahamperrin on 2009-05-30 - Tags Microsoft , SharePoint , organization2.0 , software , intranet , 2009
- Emaillard on 2009-03-27 - Tags zdnet.com , Sharepoint
- Vahidm on 2009-03-24 - Tags microsoft , organization2.0 , software , intranet
- Yeidel on 2009-03-23 - Tags sharepoint , web2.0 , enterprise2.0
Public Sticky notes
the Enterprise 2.0 story is primarily aimed at knowledge workers engaged in complex, collaborative projects which have had few effective software tools until recently, in other words strategic business activities. Industries like finance, government, civil engineering, transportation, and many others are trend to be top heavy with this kind of worker and are likely the last major bastions of productivity gains in modern economies, if the right solutions can be brought to bear. In other words, Enterprise 2.0 can help some of our most important and most valuable workers do better work while providing more value to the organization as a whole.
Highlighted by vahidm
innovation in social and collaborative systems is almost exclusively coming from the consumer Web
Highlighted by grahamperrin
SharePoint was designed before we had learned many of the modern social computing lessons
Highlighted by grahamperrin
excessively complex
Highlighted by grahamperrin
weak support for the most common Enterprise 2.0 application types
Highlighted by grahamperrin
multi-level security, governance, and policy controls
Highlighted by grahamperrin
more difficult than with other platforms which were designed to function in highly diverse environments
Highlighted by grahamperrin
Users should be able to create sites
Highlighted by grahamperrin
customize them over time to meet the local requirements
Highlighted by grahamperrin
evolve and improve through shared contributions
Highlighted by grahamperrin
complexity and high cost
Highlighted by grahamperrin
Public Comment