Interaction Design

Our Interaction Design services use the Naviscent Customer-Centered Design Process. Our process is based on the Iterative Design Process. In iterative design, a new or existing design is reworked until it fits the needs of customers. This process is widely considered to be a valuable technique for designing interfaces, but at a more fundamental level iterative design acknowledges that no design team is perfect. Designs are perfected as part of the process and only with customer feedback.

Complete Iterative Design CycleTeams are made of people, and people do not always know the right answers. It is difficult to have complete information about the needs of customers and clients. Iterative design compensates for these shortcomings, letting us continually improve a design. The key to iterative design is to quickly create design prototypes that are good enough to provide feedback but flexible enough for significant changes to be made down the line. The goal is to conduct as much iteration as possible to solve as many problems as possible early, when they are inexpensive to fix.

The iterative design process has three steps (see figure):

  1. Design. In this step, teams consider business goals and customer needs, setting measurable goals and developing design concepts.
  2. Prototype. In this step, teams develop artifacts as basic as scenarios and storyboards, and as complex as running Web sites, that illustrate how the site will accomplish the goals outlined in step 1.
  3. Evaluate. In this step, teams assess the prototypes developed in step 2 to see if they meet the desired goals.

The results of this process are used to inform design in the next iteration, and the entire process repeats until the goals have been met. Scheduling and budgeting constraints sometimes force work to begin on the final production site before all the goals have been met.

For More Information

Fill in the following. A consulting services representative will contact you and answer any additional questions you might have.

Fields marked with an asterisk (*) are required.