🚀 go-pugleaf

Picking up on JonT's last line...If the site is entirely SWF based: 

1) Sketch out site elements, navigation concept, load sequences and player level usage primarily using PENCIL and PAPER...A much superior conceptual design environment, if you ask me :-) This leads to diagrams, notes, AS code segments and sketches, that can be pinned to the wall and continuosly notated/changed/referenced as the project develops. 

2) once the site concept for graphic and functionality is at a reasonable level, I start developing the individual components separately. This essentially extends the concept of object oriented programming to the site...component based site architecture is the hip term, if I'm not mistaken... 

3) put the whole thing together, test it and fix whatever bugs have sneaked in. 

4) review with client - change - review - change - review - change - ........ 

5) Once the site is done, document your work. Save your sketches and notes. Make a document illustrating the final site architecture with whatever notes you need. Fact is that when the client comes back (hopefully he/she will) a year later with a request for an update, you no longer remember the finer details of the project...You will save tremendous amounts of time by taking the time to archive your work well. 

Above is really a very general approach - each project will have its unique challenges requiring a slightly different approach - but I have found it to work pretty well for me... 

$0.02 

-Bo