Generating the Program
In the reading, it stressed the importance of differentiating between "must haves" and "would like to haves" and knowing how to interpret what they are even if the client states that something is a "must have" when you know it is more of a "would like to have". It stated that the best way to go about creating a programming document is to first look at the bog picture, and then to design down to every detail. In a program, you need to program all the spaces that are needed in order for the site to function, and usually circulation accounts for 22-44% of the space. The reading said that "a low circulation number is often associated with good, efficient, space planning." A great way to get a good idea of the square footage needed for spaces, is to look at precedents and historical studies. The reading also including the definitions of floor useable space and gross measured area, which I found very helpful. I learned that flexibility is key because things may change in a few years and its good to show options for how the space can change in later years based on their needs. I found all of the examples and diagraph also very useful, and especially the idea about studying the users to find out their daily routines within the space to see what works and what doesn't work.
Botti-Salitsky, R. (2009). . New York: Fairchild Books.