Spring 2003
Design Direction - Flanagan
Final Proposal
The Design Direction Project Proposal is a written, word processed document which describes a
proposed artistic or business project in depth. The Proposal is used to communicate the scope, scale, approach, and
content of your project. The project must showcase your understanding of
conceptual, aesthetic, and technical aspects of your area of study. It could be
a book proposal, an installation project, a web site, etc.
The proposal must be in the following format and should be appx 5 pages
in length.
Alternatively, you can choose a proposed funding source with similar
length and detail guidelines (such as the Oregon Arts Commission or the Daniel
Langlois Foundation) and follow their format. It’s up to you.
1. Abstract
The abstract is a 250 word mini-description of your
final project. It should be a short, few sentences of what the project is
in a nutshell. What you plan to do? Does it clearly identify your project for
the readers? Why is the project worth
doing? Importance?
2.
Artist Statement
The artist statement is a one page description of yourself and
what interests you about making art or doing design work. It should not be
about assignments, or about school, but about your personal approach to making
projects and work. What motivates you? What is your process?
See
various web sites for inspiration when writing an artist statement: http://www.nitaleland.com/articles/statement.htm,
http://www.artadvice.com/advice/article12.pdf, http://www.artistresource.org/forums/forum6/39_2.htm,
http://www.artists.ca/FCA-7c1.html, http:// www.artbusiness.com/statement.html
3.
Project Description
The project description is a 1-2 page complete description of the
project. It serves as a brief summary of the project's purpose, and
effects. The Project
Description is a written narrative which presents the content and format of
your project in some detail. Its purpose is to give your
readers a solid understanding of the project without excessive detail.
1.
It
describes the project you are proposing.
2.
It
explains how the project will solve a problem or explore a concept in a unique
way.
3.
It explains why your approach to project is the best approach and why it
is significant.
The
description section is your opportunity to describe how you will create your
piece, why it is a unique artwork, why web technology is the best way to
present your idea, and why viewers will find it interesting. It should also
address your conceptual concerns. Are you interested in …representation?
surveillance? language? history, memory, violence, popular culture, poetry….etc
etc…. Where is the project going to be shown? Is there a publisher? What are
the concepts behind your design idea? Who is the target audience, target
viewer, or interactor?
The
proposal needs to include a minimum of 3 rough sketches and at least 2
references to work (artwork and books/theorists) which are inspiring you.
4.
Exhibition Format/Dissemination
This section should be appx. ½ a page and should describe in detail
where you plan to enter the work into competitions,
publish/broadcast the work, publish it, or show in a gallery setting. Explain
how you will document the work. This material should occupy at least a
paragraph in the document. Be specific, and do research.
5.
Technical Approach
This section should be ½ a page and should outline the
technical approach including tools used and platforms the piece will run on.
For example, will the piece require the user to have a plug in? What is the
minimum configuration of the user's machine? What tape format will you master
on?
6. Budget
You might not think you have a
budget for your projects, but generally you do. Construction paper, video
tapes, zip discs, travel, etc? Document these items in a table format. The
budget should take up at least ½ a page.
Make sure to include any additional resources required (number of people
helping on project, if any; additional hardware, software, expenses, fees,
etc.)
7. Schedule
This section focuses on how you will
complete the tasks you have laid out for yourself. See example below. Yours
will be monthly (at least) in detail and should include actual dates for
finalizing "deliverables". Make sure you include time for user
testing the project, uploading to the server early, etc. The schedule should be
detailed to at least a page.
The
following is an example of an approximate overall project timetable for a
project
|
Time |
Development Phase |
Production Task |
Other Activities |
|
Weeks/ Months 1-3 |
Planning,
Design, and approval |
Meet
with client, write preliminary version of the proposal; project abstract and
slides/documentation; Proposal revision. Advisor must sign off on idea. |
Interest/design
testing; seeing other related artwork, attending visiting artists' lectures. |
|
weeks 4-7 |
Prototyping,
working out concept, sketching |
Research.
Finalize conceptual sketches |
Technical
tests (for example, learning updates to software, testing camera lenses with
your animation, etc). |
|
weeks 8-10 |
Finalizing
research |
Produce
work. (detail what) |
|
|
weeks 11-13 |
Acquire
materials, Begin production |
Produce
work. (detail what) |
Seeing
other related artwork, attending visiting artists' lectures. |
|
weeks 14-17 |
Production |
Produce
work (detail what) Alpha Stage. |
Seeing
other related artwork, attending visiting artists' lectures. |
|
weeks 18-21 |
Production |
Revise
work, produce work, Beta Testing. |
Seeing
other related artwork, attending visiting artists' lectures. |
|
weeks 22-25 |
Testing,
final feedback |
Document
test set up of the work. Enter work into outside competitions and gallery
shows. |
Seeing
other related artwork, attending visiting artists' lectures. |
|
weeks 26-29 |
Hanging,
testing, and in some cases, showing! |
Work is
hung or uploaded for testing. Enter work into outside competitions/gallery
shows. |
Document
work in a packet with artist's statement and supporting materials. Update
portfolio. |
|
weeks 30-31 |
Crits |
Work is
shown in competitions |
Post
Mortem. |
8.
An appendix of sketches and diagrams
An appendix of sketches and diagrams
must be included to illustrate the proposal. Include
sketches or storyboards, and proposed interface design if applicable.