There are three core systems which define my workflow and collaboration process: (1)Discovery, (2)Validation and (3)Integration.

In the Discovery phase, my workflow consists of:

• interviews and surveys
• site requirement gathering
• site-map and/or affinity-map creation

The interviews during the first part of the discovery process tend to reveal what is most important to the teams, and then coupled with survey responses, I formulate a logistical snapshot of user and business needs as well as some marketing analysis.

Gathering site requirements helps identify the high level tasks and messaging of the proposed interaction. This is usually an Excel document which lists the global direction of all messaging, potential rich-media opportunities, functional constraints and other items which help define the intent of the proposed interaction.

Site-map or affinity-map creation is a graphical representation of the relationships between the disparate parts of the proposed interaction. This effort helps bridge the connections between the larger elements of the system prior to page level design and interaction design.

In the Validation phase, my workflow consists of:

• wireframe one (simple/static)
• interaction design and final design
• simulation and user testing

In wireframe one development; relationships, content strategy and navigation get introduced as very general page level elements. I start to introduce the page structure in very simple graphical treatments which become better defined through contextual descriptions at the page/object level. This process helps designers better understand the intent of the interaction. The design process can now be fully engaged since all required documentation is available to the design team to better understand the full intent of the system.

Design comps can now be fully developed based on accurate data. These comps allow the wireframe two development to begin. Wireframe twos are based on final design layout and the proposed interaction design for key system areas.

The simulation can become fully evolved interactive prototypes which enable system validation through user acceptance testing and other user centered approaches. This is accomplished by deploying fully interactive web based simulations to active participants.

The validation phase can take the most time to work through and completion of this phase is dependent on the user tests, brand integrity and general re-work iterations.

In the Integration phase, my workflow consists of:

• functional specification writing
• R&D coding
• quality assurance preperation

When drafting functional specifications I trace all specifications back to the original site requirements collected at the discovery phase. This helps retain the integrity of the system and is critical in QA testing.

To better define what is possible with certain interaction metaphors, it is best to rapidly prototype working interactive elements using code APIs like jQuery. Done correctly, this can help increase integration timeframes at the subsequent production phase.

Preparing a complete IA package for hand-off which has gone through the cycles illustrated above helps empower the system architects and production teams. If you would like to discuss this workflow, or any parts of it, I would be more than happy to talk with you.