I think it's worth posting some ongoing musings on the web app design process as compared to the print design process.

Designing for the web has quite a different set of requirements. I like that you have to constantly think about the structure - where the user goes, how they get there, what they find when they are there and how they get back.
i think that the style and presentation are an additional layer on that, but decisions made about styling can have a direct impact on the method of interaction . . .

There seem to be 4 main part of the process

• aim and concept
• structure (which will modifiy aim)
• styling (which must understand the limitations of the structure)
• construction (coding - html, css, javascript)

the most logical place for overall direction of the design process would seem to lie at the structure/architecture level - because the site would need to retain it's structural integrity.

All the other areas require leads who are experts, and can respond to the requirements of the other parts of the process.

It's interesting that it is a somewhat more concrete process (than print). It is possible to build a working dummy more easily, because the medium you work in is the medium it is likely to be delivered on - and you can emulate the interactions quite easily (even if you can't code them - - - Keynote is working out well for me!) and see the holes, hone the process.

I must hone these thoughts at some point, but for now - post and be damned!