Tips for a successful Web proposal1. The strategic brief needs to be written in clear, concise, business terms. This part of the proposal requires writing skills which may be a challenge for some Project Managers. If you are uncertain about the writing for the strategic brief, feel free to email your rough draft to me one week before the proposal is due and I will critique the writing. You may also want to survey your team and ask if they would like to review the content of the strategic brief.
2. The Workflow Chart need to cover the entire semester. This documents what has been done, and what will be done. Resources at the Web site which can help you with these documents include: Meeting schedule which discusses what we will cover each week. If the testing of your site must begin by November 18th, then you would set a deadline for all pages to be done by that date, or a few days before (depending on your work style). If the testing report is due Dec 2nd you need to decide how much time you need to prepare the report. In the case of the client report, that may only take one day so a Dec. 1st deadline is reasonable. In the case of classmate testing you may have to process 15 critiques and so the deadline may be set so that you have 5 days to compile the report.
Other resources you can use include the roles lesson which has responsibilities pages for Project Managers, Designers, Programmers and Content Developers, as well as examples of proposals submitted by former students.
When preparing the workflow chart - please specify who will be doing what task. If you have more than one Content Developer I need to see each person's name. Stating that Gary and Linda will make the pages in incorrect. Stating that Gary will make the about, mission, calendar, and signup pages and that Linda will make the board members, volunteer, photo gallery, and newsletter pages is correct.
3. The deliverables need to be extremely specific
Listing navigational buttons is not enough. Instead - on the home page graphics for 8 navigation buttons will be created. The navigational buttons will have rollover images and in 3 sections remote rollovers will display third level navigation. This level of specificity also needs to be applied when describing the navigation for the second and if applicable 3rd and 4th level pages.
When producing a logo, describe how many versions will be created (for example: a large logo for the home page, a smaller one for the second level, no logo on 3rd and 4th levels)
Describe the header graphics which will be produced. For example the same header will be used on all second level pages (then describe what is in the header graphic), or a unique header will be used for each second level page and describe what will be unique about each header (ie the photo will change, the color will change, the text describing the section will change)
Describe the header graphic for 3rd and 4th level pages if needed.
How many photos are you willing to put into the body of the site? If a photo gallery or slide show is planned put a maximum on the number of images you are willing to process. I recommend between 20-40. It is OK to do a portion of the photo gallery, provide the client with a template and then let them do the rest.
Describe how many Web pages will be produced, and include a summary of the content which os part of these pags.
Describe what text navigation will be created. For example at the bottom of each page text navigation to the second level will be included along with client contact info. Another option is - at the bottom of each page text navigation to the second level and third level pages specific to this section will be included along with client contact info.
Describe any training you intend to provide, list the approximate dates of the training and the hours of training provided.
Include the client CD which will contain the web site, the original PSD files, the client manual and the Project Web site.
Describe in detail any programs or scripts which will be produced.
4. Present the proposal in a folder or plastic report holder so the pages don't get lost.
5. Make sure all pieces of the proposal are consistent. I have had proposals come in where the pages listed on the deliverables do not match those displayed on the storyboard.
6. Make sure you check over the proposal for last minute changes. I had a group who originally planned to create an online ordering catalog for their client. About 6 weeks into the project the idea was abandoned. The strategic brief had already been written and the online ordering was contained in the document. The PM would need to rewrite the strategic brief and remove all references to online ordering.
7. Feel free to place the proposal on the Web and ask for my input before the proposal meeting. I will need 3-5 days to review the content.