[curiousgeorge]

>> Coding before design. Software tends to be much more usable if it >> is, at least roughly, designed before the code is written.

In my experience, software and web development tends to fail when early work is made with specific UI assumptions in mind. The successful projects I have been a part of have concentrated on putting basic functionality first, and then iterating around the usability design and other features.

[mixmax]

As an opposing datapoint my experience is the exact opposite.

[webwright]

I think it works both ways.

Putting basic functionality first doesn't mean eschewing UI assumptions-- it just means making LESS of them. You can't make anything without making assumptions.

Too often, devs assume that iterative development means that they build the simplest version however they feel like and THEN call in the designer to work with them to clean it up, improve it, add features, and make it pretty.

IMO, the best way to do iterative development is to work with the UI designer in the designers preferred medium for early prototyping (xhtml/css, photoshop, paper, whatever) on the "basic functionality" that you mention. THEN build it and have your target audience use it. Rinse, repeat with improvements and new features.