Recently I had to switch to using Firefox (you know, the browser that is tied up in an anti-Gay Marriage scandal and is now trying to look like Chrome as part of its witness protection program) and/or Chrome (you know, the company that created Glassholes…) to manage my Office 365 components (login.microsoftonline.com and/or portal.microsoftonline.com). This was driving me crazy and I had to get to the bottom of it.
The following post has been updated to reflect SharePoint 2013.
Internally, we are using SharePoint blogs very effectively, to replace common sharing of information (in our case, typically about technology like ‘how I fixed this or that’. Using Microsoft Word as our blogging tool (and if you don’t have Microsoft Word (2007 through 2013), you could use Windows Live Writer, which is free), and SharePoint as our blogging engine, we have all that we need to create a rich, blogging experience with the following benefits:
We create/share information using a rich tool, just like composing an email to the team (A subject, some paragraph/body text and maybe some clipart, screenshots, etc.). However, this information is retained within SharePoint, meaning it is not lost in someone’s Sent Items – it is searchable and discoverable within SharePoint (by search or category lookup). As well, as you’ll soon see, as we have subscribed all staff to Alerts, regarding new content, we also receive the latest blog information, real time. By storing the information in SharePoint, we also get the added benefit of this information being available to NEW employees as they come on board (again, not lost in someone’s thoughts, memos or Sent Items bin). Knowledge is then:
- Retrievable chronologically
- Available to new staff when they arrive on the scene