The ESP initiative was created by the beach party and consists of four parts. Below is part one, or "Q1." Q1 is a qualifying document which will aid both the developer and client in determining what the client needs, their resources, familiarity with the Internet and the scope of the project. By using Q1, you will know whether the client is ready to undertake the building of a Website or first needs consultation.
This is an important initiative for the entire Internet and we encourage your involvement and support.
- What was your name?
- And your telephone number in case we get cut off?
I. How did you hear about us?
- What can we do for you?
- What is the nature of your business?
- Who are your customers/constituents? (Not always the same)
II. How familiar is your company with the Internet?
III. Have you defined the scope of the project?
- Do you have an internal network?
- __ LAN
- __ Intranet
- __ Email (email@example.com)
- __ Webmaster
- Do employees have access to the Internet?
- How many of them?
- Is there an existing website?
- If yes, will this project change it or create a new one?
- If the answer is yes, "it will change it", why do you want to change it?
- Have you or your company done a project like this before?
- Is there anything written that you could send us?
- __ Project Description
- __ Creative Brief
- __ Request for Proposals (RFP)
- If nothing is written, can you briefly describe what you're envisioning?
IV. Is there a budget for this project?
- If no, then you may need a consultation to help define one...
- If yes, is there a line item for development (i.e storyboards and proposals)?
- If not, can one be added?
V. Let's talk about the proposal process:
- On what date did the original proposal or project description go out?
- When is the response due?
- How many developers have you approached?
- Who are they? (The goal here is to define what kind of a peer group you are working in if possible, but if they don't want to answer, don't press it. For example: "It's important to know what kind of style you are looking for")
- How many proposals are under consideration at this time?
- Are there other contractors or in-house staff that are already attached to the project?
- If so,who are they--and when can we meet or talk with them?
VI. When is the final produced project due?
- Are there any events tied to the project launch (i.e. product release, tour, media event, etc.)?
VII. What goals do you have for this project?
- What do you specifically hope to accomplish? (i.e. how will you judge the success of this project?
- Who is your target audience/market?
- How do you envision the project supporting your organization missions and objectives?
- What are the three most pressing problems that your company is trying to solve right now? Who are your competitors?
- What are their competitive stategies?
- Do they have a Website? If yes, what are your comments about it?
VIII. How is your organization structured?
IX.What features or functions do you want on the site?
- Who is it who wants the project done?
- Who is/are the final decision maker(s)?
- What level of approvals are needed for the project?
- Does approval authority reside in your division or another?
- Who approves upgrades and changes to the site?
- Will anyone else have input or approval?
- What are their roles as you understand them?
- Who is responsible for design (look and feel of the project)?
- Who is responsible for deliverables?
- Who is responsible for signing off on the deliverables of this project?
- Who approves the payments?
(i.e. database, commerce, animation, build an email list, etc.)
X. Do you have existing content?
- What form is it in? digital art?
- digital documents?
- printed photos?
- rendered art?
- printed documents?
- Are the rights for all your content cleared?
- If not, is there a budget for clearance?
XI. Who is or will be the prime contractor?
- Who is the project manager?
- How are the contractors and subcontractors on this project organized?
XII. If there is a budget, have you included line items for:
- Storyboards and Proposals Design and formal specifications (i.e. creation of a document that describes the business context, technical architecture, functionality, roles and responsibilities, etc for the entire project.
- Creative (written and graphical content) Custom programming (cgi, database, Java, etc.) Software Hardware Revisions Training (your in-house staff) Testing and QA (quality assurance) Hosting (i.e. ISP, In-house) Maintanence
FINAL NOTE: if a budget is not well defined or funded, you may wish to suggest a consultation at this point if you haven't already. If the budget is in order to your satisfaction, then continue to Q2...