State the Problem

 Programming is a process leading to an explicit

statement of an architectural problem. It’s the handoff
package— from programmer to designer.
 After pondering information derived from previous steps,
designer and programmer must write down the most
salient statements regarding the problem, the kind of
statements that will shape the building. These, if skillfully
composed, can serve as premises for design, and later
as design criteria to evaluate the design solution.
 There should be a minimum of four statements
concerning the four major considerations, components
of the whole problem: Function, Form, Economy, and
Time. Typically, they cover the functional program, the
site, the budget, and the implications of time. Rarely
should there be more than ten statements. More than
this would indicate that the problem is still too complex
or that minor details are being used as premises for
design. Statements must represent the essence of the
problem.
 The problem statements must be clear and concise— in the
designer’s own words so there is no doubt that he or she
understands. The problem statements should focus on the obvious—
which is often overlooked. Stress the uniqueness of the project.
 The format for a problem statement can vary with individual
designers, but it is good practice to acknowledge a significant and
specific condition and establish a general direction for design.
While each condition must be precisely stated, the direction (what
should be done) should be ambiguous enough to prevent the
feeling of being locked into one solution. This direction should be
made in terms of performance, so as not to close the door to
alternative solutions nor to different expressions in architectural form.
 These qualitative statements relate to the whole problem by
including all the complicating factors, yet they must represent the
essence of the previous steps. They anticipate a comprehensive
solution to the whole problem — not by discarding the information
in the previous steps (which is kept on display), but by resolving the
initial complexity of the design problem into simple and clear
statements. The act of resolution pervades the programming
process, but it is most vividly expressed in this fifth step. Resolution
requires an intensity of intellectual effort. It is hard work to simplify
and clarify the statement of the problem, yet this is necessary so
that everyone on the project team can cooperate toward the
same end.