Part of the Contextual Design process, this step generates a comprehensive set of functional requirements with the essential linkages between them.  The unique aspects of how functionality is clustered by this method gives teams a way to double-check their ideas before prototyping pages.

Method

The User Environment Design process is a collaborative way to define the purpose and functionality of each page in an application. This technique manages the complexity of what functionality and features to put "where" in a sequenced page environment.  Once the functionality is defined, paper prototypes can be built.

The team must have clarity about the user goals, functional needs and system requirements for the product prior to starting this technique. We recommend doing contextual interviews with users and then writing scenarios to explain their task processes.

Results

The outcome of this technique is to organize all functionality and taskflows that are needed to support user process. By managing the complexity at this higher level, figuring out what each aspect of the product's design looks like becomes straight-forward. Having the product architected on paper allows the team to grapple with the flow of its design.

Timeframe

Several hours for each major task set and distinct user group.

Additional Reading

A brief description of the User Environment Design process and outcome is found at the site of Contextual Design's developers: http://www.incent.com/cd/cdp.html#ued.   See also their book: Contextual Design: Defining Customer-Centered Systems by Hugh Beyer and Karen Holtzblatt (1998), Morgan Kaufmann Publishers, Inc. Amazon sells it.

An example of a UED is available here: http://www.isrc.umbc.edu/HCIHandbook/figures/49-10.html