How to analyze a handheld user interface - project management as an example

An earlier post described a terrific discussion at Edward Tufte's web site about building effective project management user interfaces. I have had recent experience with handheld interfaces to project management systems and want to add some thoughts about that.

The critical place to look is at who will be using the handheld interface to the project management system and why they are using it from the field. As soon as you ask these questions, the discussion is shifted. Desktop project management systems are used by project managers, trained in the complexities of gantt charts, resource leveling, float dates, critical path analysis, budget planning, etc. etc. These are experts looking for a powerful tool with lots of options and complex visual displays. They want to browse around among many interlinked projects and tasks, selecting the views and operations consistent with their job of managing all the many disparate pieces.

Why get field managers involved in project management at all? They have their daily "to-do" list and are not involved with big picture project management and resource planning. Instead, they are the critical link that provides data from the field to reconcile the plan with what actually happened. Project management tools can only deliver value when they are closely linked with real data about what is really happening.

We now have the focus we need to develop an effective handheld user interface. Present a "to-do" list with the current plan and easy ways to provide the "what really happened" information needed back at the office by the project manager. This is probably done with pop-up responses associated with each todo list task -- "completed", "requires 1 more day", "delayed due to weather". There is no need for gantt charts, resources leveling, visual displays, etc.

The lesson: handheld user interfaces should focus on the task at hand for the field staff member. The desktop user interface for the back end software to which the handheld application is tied typically tells you very little about what the handheld interface should look like. Instead, look at the tasks of the person who will be using the handheld.