some custom functionality if the requirements call for it, and in some cases automating the request and provisioning process, so that end-users can either create new collaboration sites on their own, or can fill out a form and route the request through a standard process.  Increasingly, the company will have some flavor of enterprise social computing, where the end users can vote and comment on content, subscribe to topics, post updates, and see activity streams.  We test the solution, incorporate feedback, receive some form of signoff, move all the new collaborative functionality into Production, train the end-users (who, of course, have received communication about the coming change along the way), and that's a wrap for that scope of work.  The IT department can tell their executives, "The deployment was a success, we now have collaboration."  There is a mental checking of the box. Take a look at the following team site.  It has many of the components of the ones I work on every day - a task list, a calendar, document storage, contact information, announcements, and even a picture of the day to keep things dynamic and engaging.  The entire team can contribute or remove anything at any time with no restrictions.  The site is an important hub of frequently-changing information, accessed multiple times a day. Is it the most mature team site in the world?  Admittedly not - there's no remote access, no automated notifications on new content, no integration with other systems, and no ability to share