Best “Cycle” for developing new products?

Question

Given that everyone has their own "nitch" or style for developing new products/applications,

I was wondering if there is an ideal cycle that most ux professionals like to follow?

This could be controversial in given exactly what product is being developed, but there are so many tools and powerful resources for designers to use, I sometimes feel "lost" in which is the most ideal way.

For example:

User stories > Flow Charts > Site Map (IA) > Wire Frames > Prototype > test > Reiterate

Answer 1

I think that's a pretty standard way to do it, but don't serve the process if the process gets in the way of progress. I will never commit to a final deliverable (e.g., site map) before everything is done; IMHO, efficient UX work is never as neat as a waterfall-type project plan would indicate.

My own process is more like the curly line on a Hostess Cupcake (R.I.P.) than a straight line:

• I can rarely complete a helpful flow chart without designing an IA
• Since my IA might depend on the content that lives on a given page template, I should probably start blocking out my wires
• How will this IA and the labels I apply to it sit with users? I should probably test it.

I would also add that a critical part of my process is going back and forth between production fidelity levels: sketches to pixels and back.