Of course, everyone has their own preferred way of doing things and no two projects are ever alike, but here is my most typical approach: I start with initial stakeholders’ interviews to define the scope and depth of project, conduct competitive analysis and deep study of any available usability tests/data as well as web metrics (google analytics, chartbeat, woopra, kissmetrics, etc - anything and everything available).
Based on findings, creating or re-defining personas, clarifying feature set, providing recommendations and developing new as well as improving old scenarios and use cases, creating flow diagrams, schematics and wireframes for new features or screens that will need to be redesigned.
Sometimes I start with paper prototypes and other times move directly to interactive ones to be able to test a certain process/feature faster under closer to reality conditions. Then, testing them with users and evaluating the results.
Once we get the repeatable/predictable/desired outcomes on the prototypes, it’s time for hands-on Photoshop & HTML/CSS coding iterations, to be implemented on the testing server. Once all coding bugs have been ironed out, moving latest changes to staging server and inviting select users to test new features (while watching metrics for any bottlenecks) and asking for feedback.
After things have been smoothed out once more, it’s time for code sign-off to the live production server and - sometimes - to start the process over on the next feature set :)
Design by Simon Fletcher. Powered by Tumblr.
© Copyright 2010
