The business case for portable computers
Just recently I read a blog post (which I can no longer find) that cast doubt on the business case for portable computers. The basic argument went like this:
- Portable users worked for 14% more hours
- Portable users produced 13% more work
- Therefore portable users were 1% less efficient
Assuming I remember this correctly it seems a pretty strange analysis, so here is my counter analysis. First the case for portables and productivity:
- Portable users do more hours when they have a portable device because it allows them to work when they would otherwise be undertaking some leisure activity, depending on the portable device in questions, these times are most often, whilst waiting in airports, travelling by train, sitting in front of the TV etc.
- Portable users do more hours because its easier to “just spend an hour” working at the weekend, than it is to drive to work and do it there
- Portable users spend more time with access to time critical information sources, email, IM etc and so respond faster reducing lead-times, and improving decision making
- Portable users make better use of their time in the office, processing email, expenses and other low low importance high volume tasks tend to …

I have worked in this area for most of my working life and it continues to amaze me that it is still an area of IT that has the – untapped – potential to transform peoples lives. Most of the customers I work with are struggling to deal with all the information they have to cope with in their work and home life (which are becoming more integrated). They live high-bandwidth lifestyles! Its with great interest therefore that I read the following results from the
These two great video (
I just came across an
I am currently considering my career options. After a year working part time I believe I have a very sound understanding of the opportunities and constraints associated with Adult Onset Still Disease and its affect on work.
Not a particularly challenging book on this subject. It starts with the basics and never really gets to the guts of developing SOA applications. However it does a good job of explaining the basics of the standards and key concepts, although it does over use very simple diagrams. I know a picture tells a thousand words, but in this case some of the pictures could be explained in 10 words without too much difficulty. 

Bill has just given a very interesting