I always start with 'best guess' maximum development of the site for say, five years - that is, the most complex foreseeable development of the website, and then outline a directory structure to that standard. I don't even think about coding a thing until establishing what the structure or skeleton will be. A flow-chart/outline is the only way for me.

"quite a lot of functionality" suggests quite a lot of complexity. If not all at once, then in the pipeline. All the more important to build the directory structure that will account for all of the immediate requirements plus building in expected growth needs on the initial design.

"presenting a decent website plan" suggests a proposal and not your own project. I would present 'big picture' and paint with a broad brush and not provide specific details unless working on consultant basis. (Presumably, your previous work establishes skills, so it isn't like you have anything to prove.)

Thanks for the reply D_Blackwell. I'm relatively new to project management, and although I managed to get a jobsite with a lot of complexity built from scratch, having oversight and keeping track of changes to the initial spec is something that I know I should be improving.

There seems to be quite a lot of software available for flowcharts, which is great, but ideally I'd like something that allows flowcharts, but also wireframing for an idea of what is going to be included on each page and rough look.. I know Visio is supposed to do this, but is there any better or easier software?

Thanks

I'm always a fan of HTML mockups. Gives the impression of how things will really look and feel.

Hi Maximillianos - HTML mockups seem to be the most work initially (in my limited experience) and although I agree they give the best impression, if you think that they're going to require some serious changes, then the work involved could get even larger..

Would you make a decision on HTML mockups or not based on how confident you are that the initial mockup is close to sign off?