Microsoft recently published some new guidelines on whether companies should be implementing Exchange Public folders or adopting SharePoint instead. (http://blogs.msdn.com/sharepoint/archive/2008/04/01/updated-exchange-public-folder-vs-sharepoint-guidance.aspx) What interests me most about this is the idea that certain overlaps between products could be removed in this way and give Microsoft a more coherent software platform. For the idea of software as a service, the the functionality in different applications should compliment each other not clash or overlap, and be available via one interface. I see that as being SharePoint. So, if we way goodbye to public folders, which overlap with SharePoint Document Libraries and Calendars, what's next?
I'd like to see the overlaps with project server removed. MS Project is good for managers leading a process, assigning resources, tracking progress. SharePoint is a tool for the people they track mainly. There is some syncing between the two, but I think there should be only one source and interface for the information, no more need for syncing.
My least favourite Office app is Outlook, it's slow, has a horrible warren of tabs and menus if you are trying to change something, and it should seamlessly work with SharePoint. If I had my way I would scrap Outlook and users would simply pick up their email via a SharePoint list that others can share, workflow on etc.
SharePoint is the Office platform, or should be in time.
posted by Stephen Cummins |



