We'll finalize an agenda by midweek; this thread is open for a discussion of that upcoming agenda. Below, I've copied in some of Seth Meranda's Jan. 31 post to the 'Jan. 27 Meeting Discussion' thread. Seth has sketched out a pretty good outline of an agenda:
1. Where do we start?
Let's decide the color of red/scarlet we will use.
Then, let's decide what fonts will be used.
Finally, let's decide what aspects are required and where they should be positioned.
Splash page, or no splash page?
Drop-down navigation, or static navigation?
Home page design first, or secondary page design first?
2. Flush out the above requirements
Explain where, when, why and how the required aspects are to be used.
3. Examine the submitted prototypes and determine which parts resemble the required aspects.
Remember, not all required aspects will come from the same design. Finalized designs will represent parts of many designs.
4. Put together a team of top designers to develop the final design submissions.
Let's not have too many cooks in the kitchen
5. Use future web dev group time to discuss bells and whistles (i.e. drop down forms, sliding navigation, sIFR, etc...)
This could be done at any time after requirements are established
I think Seth's done a great job here of prioritizing the work ahead. The only thing I might suggest changing is to put several teams of designers together. We need at least three designs to go to focus group testing; it might make sense to have three groups of designers. That way, each group of designers could be highly-focused.
After Feb. 10, let's plan on making this a weekly meeting until we substantially finish this phase of work.
