That’s a pretty brief review of Outlook 2003 when connected to an Exchange Server.
When my IMAP server isn’t responding, I still have my local data. And it works. And when things change, they sync up nicely. Yesterday I spent the morning restarting Outlook as it kept crashing every time the network connection went down. Today I have this:
The little exclamation mark shows that I can’t get access to my Exchange Server. This means that at intervals the application freezes up. Considering that my calendar is part of this application as is my mail and most of my to-do list, I find myself pretty much unable to be 100% effective.
On the other hand, using a more decoupled service like IMAP with subscribed ICS feeds (a la Google Calendar) I’d still be able to work. At the moment I can just sit and look at the wait cursor and the little exclamation mark. Most of my work is, to be honest, in message passing and making sure people are doing things. As such, my reminders lists, calendars, follow-ups and email are crucial. When I can’t access the server I can’t even search my email. (and yes, I know I could change some of this, if I had access in my profile/policy to change things).
This is why I’m keen on decentralised outsourced services. If you’re not an IT company then why have a server on site. Why tie yourself down like that. Use decentralised services so if your broadband goes down you can pop down to any WiFi hotspot and use theirs. If your hosted email service goes down, you’ve still got access to other services and plenty of opportunity to change to a provider that won’t go down. This is why I use Pair Networks – pretty unrivalled in terms of reliability.
I loathe Windows and Outlook.