The group runs a batch-processing system that evaluates deals. The application for monitoring batch results suffered from extremely poor usability, performance and stability: I was required to improve all three. I produced an interaction design for a new monitoring tool and, derived from this, an architectural design for implementing the tool.

The implementation of the design above: this consisted of an ASP.NET back-end communicating with an Ajax/DHTML front-end (technologies previously unused within the group). The product was very well received and is currently being evaluated for expansion to different groups within the bank.

The tool for creating batches suffered from problems similar to the monitoring tool. However, the interaction and architectural design in this instance was complicated by concurrent use of the tool in London, New York and Tokyo; with occasionally conflicting requirements.

A complex web-based project: an extensive feature set and competition with existing desktop tools meant ease of use and performance were essential and required extremely efficient client and server-side techniques.

This involved encapsulating a complicated research technology in an easy to use interface. I did all the interaction and graphic design and the majority of the programming on the project. Some design notes for the project can be found at www.jaimz.org/design/xensource.pdf

Introduced a design phase into the development cycle at XenSource. Encouraged the use of design tools such as personas and context scenarios to engender a more disciplined approach to designing the management software.

Produced a prototype of a web interface for the XenEnterprise product. The project uses RIA technologies such as Ajax and the OpenLaszlo framework.

When I joined the company, the existing interface was receiving a very bad response from beta-testers. I redesigned the interface and guided the developers who were implementing it. The redesign received a nine-out-of-ten average score in our beta program.

How do we make applications for collaborative groups characterized by rapid changes in connectivity, group membership, and synchrony? I created several prototype applications that explored questions of mobility, communication, consistency, and user-interface.

The framework promotes P2P collaboration and selective undo/redo as first class concepts. Applications made with the framework can run seamlessly across changing combinations of devices, users and synchrony. (.NET/C# - see publications - www.jaimz.org/joyce.html)

The service tracks multi-application tasks using a persistent graph structure that reflects application commands and their invariant semantics. The record is used to provide automatic persistence and snapshots, and system-wide selective undo/redo (.NET/C# - Microsoft patent - see publications)

Enables unconstrained, multi-synchronous concurrent editing. See design notes at www.jaimz.org/design/babble.pdf (.NET/C#, GDI+ - www.jaimz.org/babble.html)

RUFiS supports reconciliation within and between files. (.NET/Java - Microsoft patent - see publications).

Ported existing research prototype from Java to .NET. Advised MS product groups using the new code-base. (.NET/Java/C#)

Produced external academic papers, internal white-papers, and made presentations to lab staff and senior MS executives