Simplicity

Simplicity drives our Interface Design.

The right interface will enable affordances for each interaction in the requirements. No more and no less.

A smaller feature set means less policy and less structure. Less policy lets you maximize the subtlety and polish of details. Less structure increases performance and maximizes the impact of each interaction. A smaller set of possible interactions enables the system to leverage Context to provide higher quality feedback. The dialog between the user and the interface is focused and direct. There is less noise because there are fewer signals to process.

Computing power and network connectivity are largely commodity costs in software deployment. Successful engineering solutions are driven by a careful examination of constraints rather than an exhaustive exposition of features. It is easy to recognize the benefits of "just one more" feature--they are focused and immediate. The costs tend to be diffuse and long-term.

Each thing you choose not to do is a thing you don't have to design, build, test, deploy, and maintain. With lower costs, more time can be spent honing the essential features. Maintaining a discipline and focus on Simplicity minimizes the impact of these parasitic effects. Simplicity promotes innovation. Developing software is an iterative process. More refinement can be undertaken with each feature since the cost of experimentation is reduced.

Simplicity drives our Project Management.

Simplicity means smaller teams with less overhead. Less manpower increases the discipline at which a team must operate to be productive. Every pair of hands is essential. Everyone must row at the same pace. It becomes obvious when someone is out of sync and corrections can be made swiftly. Management and communications remain very direct and immediate.