Adventures in home working

In my previous blogs, I talked about my concerns over the neglect of employees productivity and my personal productivity challenges.  In this blog I talk about some of the simple things I would like.  Its interesting that lots of them sound quite easy to achieve, and some of them work right now if only the systems were configured that way.

1. A single inbox, that works all of my email services and with the appropriate directories I need to access
2. A single calendar, that aggregates and synchronises calendar information from different sources and allows me to interact with different resource reservation and freebusy services
3. A single task list, that aggregates tasks from different sources and responds to the source with task progress and completion information
4. A single contact database, that synchronises with the server side record if there was one
5. A single presence/IM environment, that integrates with my contact database
6. A single way to get subscriptions, RSS seems the likely candidate, whether its subscriptions to company announcements, or WSS lists, or search results, or changed web sites
7. Then a place to make notes, link stuff together, annotate
8. a way to record everything I have touched in any way, has written by me, read by me, been pushed to me, subscribed to by me, and store it in a way that makes it easy to find again and easy to backup, perhaps peer to peer, ie to another machine in my home, rather than just to that expensive server infrastructure in my company.
9. an easy way to share subsets of the above with my peers
10. Then a UI for it all like the Avalon/WinFS stuff people are showing that allows me to search across all of this, group/visualise it in anyway I can imagine etc.

All of the above need to be integrated, so tasks can be converted to email, emails into tasks etc and other applications need to interact with them.  This sounds fairly easy.  Web Services standards for handling tasks, calendar items, emails etc.  A standard client side representation like that in WinFS, standard UI components that all spps can leverage client side.  Standard ways to deliver subscriptions, but more extensible than RSS, because I need more metadata associated with the items in the subscription.

Then I need something similar for files, probably a lot like WebDAV on the server side, but with support for pulling down all that rich meta data that’s on the server, remembering which server the files came from, understanding how to work offline/synchronise, version control etc.

Finally I want my devices to be in sync, without having to think about it, and if I get a new device I just want to be able to tell it who I am, and it rebuilds all of the above from some peer to peer replica.

This sounds a lot to me like Longhorn, but probably not explained as neatly and tidy.  However I don't see the Longhorn value proposition being communicated in these terms, they are still trying to sell to the corporate audience, not to the individual.  Maybe that comes later.

- Posted by Steve Richards - 2:23:49 PM - comment []

In my previous post In Pursuit of personal and team productivity I talked about general problems.  In this post I talk briefly about my problems.  My company:

1. Uses Notes for email and some applications
2. Has an extensive Intranet for functional web sites, news, standards etc
3. Uses Plumbtree as its portal and to host communities, some are still hosted on Notes
4. Some of the projects I am working on use MS Project Server
5. Others use just MS Project
6. My company uses Lotus Sametime for IM
7. One of my project teams uses Microsoft Exchange IM
8. External contacts use MSN IM
9. Some of the projects use a Windows file server for project files
10. My function uses a Notes Database as its repository for Work In progress and approval
11. Some of the projects use WSS, for documents, risks, issues and changes
12. Some use spreadsheets
13. Some of the projects use an in house developed collaboration server
14. My customers use even more systems, some MS Team Services, others use Documentum

What do I use, in addition to all of the above:

1. I use my local disk for all my work in progress, archive, to read, to review, to watch etc
2. The family email is accessed using Outlook express
3. My personal email is accessed using Outlook, because I use Newsgator for RSS
4. I use Onenote for note taking and for my daily log
5. I use Radio for my blog
6. I use Office 2003 Pro most of the day

I have a range of different devices, which I talked about here and here.

I think this mess is pretty typical, but one thing I know - it certainly is not productive!

- Posted by Steve Richards - 1:49:03 PM - comment []

There is a conflict between people and the companies they work for, (well probably lots, but I'm only going to talk about one of them).  The bigger the enterprise a person works for the more focussed that company is likely to be in central server centric computing, central support, consolidation, BPM, single sources of information etc.  All very important for sure, but these companies will probably not even consider team productivity and almost certainly personal productivity as worthy of investment.  These companies are on a crusade to save money, real money, i.e. savings off the bottom line.  1 hours labour saving per month for a big company project would be amazing. 

Individuals on the other hand, especially information/knowledge workers will happily spend hours a month honing their personal environments to suite their needs, aggregating, storing, and restructuring the data that they are researching, or creating.  They often invest their own money on Home PC's, PDA's, Task management Software, List Management Software, PC search software, Laptop to server file synchronisation tools etc.  In the pursuit of personal productivity they probably spend more than 1 hour per week.

So how come individuals spends perhaps 4 times longer trying to make themselves more effective, than big companies are trying to save through server side business process reengineering projects, or major application upgrades.

In my view it comes down to three things:

1. The tools available to information workers are so poor that people live in a state of perpetual frustration, trying to find an environment that lets them aggregate, integrate, process and create information more effectively.
2. The people working on server side improvement projects assume people only work on their project, process or team.  When often people are working with such a wide range of different web sites, document management systems, team sites, portals, networked file systems, personal file systems and trying to access them through a range of different devices.
3. The benefits that people perceive they will see if they could only get the two issues above resolved are so amazing,  not just in raw productivity terms, but especially in quality and team coordination, that they feel very motivated to continue to strive for them.

Lots of peopole have tried to solve this problem.

1. Server side guys have taken the portal approach, which at best integrates a few processes, or a few fragments of information
2. The client side guys have created ever richer PIM's, but made the mistake of assuming everyone will work only in their PIM
3. The device guys have given us an ever greater number of devices to fragment our information across

Some players have realised that the only way to solve this problem is at the platform and standards level, on both clients and servers:

1. You can see some evidence of this with groove which provides a rich set of platform services, and some real application functionality on top that addresses just this area.  But the platform is not popular enough to really transform the way people work outside a few enlightened environments, and of course the platform costs quite a bit of money, for bottom line centred enterprises to invest in it.
2. A slightly different approach is taken by the guys developing Chandler, which is an open source set of platform services, which will eventually be funded by layered application vendors building on top of the platform.  However its unlikely to become pervasive with such a small team behind it, although the vision looks great, if a bit limited in its scope, (given the size of the team though a small scope is essential if they are to ever deliver).
3. Everyone continues to invest in full text search and its longer term accuracy as more metadata becomes searchable as data migrates to XML format, but search is still such a blunt instrument.
4. Microsoft have a grand vision with Longhorn at the client end, with WinFS as the store utilising the Shell and Avalon presentation services.  Reaching out and integrating a vast array of server side environments exposed through Web Services, but its a long way off. Microsoft is certainly taking a platform centric approach, and of course will deliver a slew of compelling applications to exploit that platform.  They are also in a unique position with the release of Longhorn to invest in the marketing of a new way of working, and to present the commercial opportunity for thousands of ISVs to exploit that platform to tempt people to upgrade their applications.

So what’s my take on the future, cautiously optimistic:

1. I think Microsoft has learnt some lessons in the past and will do a great job of delivering the Longhorn platform and some great applications that leverage that platform
2. I think Microsoft is the only company who has a vision of the future that takes an integrated and balanced view of client side and server side computing
3. I think Microsoft is VERY strongly motivated to re-invent client side computing, which has hardly evolved for nearly a decade
4. I think the Linux community needs to seriously look at what Microsoft is doing to the platform, and build standard services of the type provided by WinFS especially if its not to get left behind still trying to complete with XP when Microsoft has completely moved the goal posts.
5. I think Longhorn lives or dies by how good it is at aggregating and integrating a mix of client and server side information.  Which means that it needs to be the premier client for aggregation using for example RSS as it evolves.  All Microsoft’s applications need to start exposing their capabilities in a standard way, again RSS and Windows Sharepoint Services comes to mind.  If WSS provided an RSS interface to subscriptions, lists, document libraries etc, and had come offline support it would be transformed.

Ray Ozzie, of Notes and Groove fame provides some good commentary in this area as well and Adam Bosworth's Weblog discusses some of the server to client interactions as well.

A releated area is support, almost everyone prefers to receive certain types of support from their friends and their peers, who they know to have particular expertise or who understand their needs and environment.  In a survey I did about 5 years ago over 90% of people preferred to receive support from their local "super user" rather than call the help desk.  However in the central/standards dominated corporate IT environment this support model is not encouraged, which means that it is not facilitated and made efficient.  It still happens of course, (a 90% preference is too strong), it is just not done very well.  This is a real shame because peer support tools like Microsoft's remote assistance, discussion groups, expert groups etc can be very effective.  Again a few years ago I setup a support forum for my corporate, that provided both peer support and support directly from the developers and architects responsible for the environment.  In many ways it was much like some internet forums today and like blogs, in that it put the developers and users in direct contact.  The affects were amazing in the goodwill generated within the user community and the improvement in quality that the developers were able to achieve with this direct linkage to their users.  I will blog more on this whole area soon.

Finally I would love some of these Longhorn Evangelists to start talking about the future for Knowledge workers, and not just about how Longhorn and Indigo will affect vertical business processes.  However maybe that would mean revealing some commercial in secret stuff about the next version of the Office System and Longhorn Server.

- Posted by Steve Richards - 1:26:54 PM - comment []