Problem Seeking: An Architectural Programming Primer

by William M. Peña, Kevin Kelly

The classic programming guide for architects and clients-fully updated and revised

Architectural programming is a team effort that requires close cooperation between architects and their clients. Problem Seeking, Fourth Edition lays out a five-step procedure that teams can follow when programming any building or series of buildings, from a small house to a hospital complex. This simple yet comprehensive process encompasses the entire range of factors that influence the design of buildings.

This new edition of the only programming guide appropriate for both architect and client features new ways of thinking about programming, new strategies for effective group action, and new settings in which to explore programming concepts. Supplemented with more than 120 helpful illustrations and diagrams, this indispensable resource provides updated technical information and faster, easier access to explanations, examples, and tools, including:

Updated building costs and their relationship to interior fit-up costs A primer on discounted cash flow analysis and net present value analysis Project statement examples organized by project phase and building type Useful techniques for data management, functional relationship analysis, and more

Genres: Architecture, Design, Interior Design, Nonfiction, Reference

202 pages, Paperback

First published January 1, 1977

Reviews

[rqoeyzcf rqwezcv · Rating 2 out of 5]

Overview
I forgot why did I borrow this book from NYPL. Maybe because when I study the PA, there is this book in reference?
I like the clear five steps of programming: establish goals, collect and analyze facts, uncover and test concepts, determine needs, and state the problem.
Architectural problem to be determined are: function, form, economy and time.
Previously I can consider most of the nine steps, except time. Building speed and time consumption is really important these days and in order to save time, some new building technology like light wood prefab structure and movable house are invented.
Programers and Designers
seperate wants from needs
programmers must be objective and analytical.
// Do I want to read this book because I need to pass the ARE? or do I read this book because I want to be good at programming? Both
analysis and sysnthesis
the total design process includes two stages: analysis and synthesis. in analysis, the parts of a design problem are separated and identified. in sysnthesis, the parts are put together to form a coherent design solution. the difference bwteeen programming and design is the difference between analysis and synthesis
Programming is analysis. design is synthesis
// This is such a good book. The author have great logic and explained the design process so clear.
Programming does not need creativity. Programming establishes the considerations, the limits, and the possibilities of the design problem. Creativity thrives when the limits of a problem are know.
Sometimes I think we arrive at a solutioni before we know what the problem is. We say:” my next design will be round!” without logic or analysis
requires a distinct separation of programming and design
a designer who can not wait for a complete, carefully prepared program is like the tailor who doesn’t bother to measure a customer before starting to cut the cloth
Uncover and test concepts
the difference between programmatic concepts and design concepts
programmatic concepts refer to abstract ideas intended mainly as functional solutions to clients’ performance problems without regard to the physical response
design concept refer to physical response to clients’ architectural problems
there are 24 programmatic concepts
Priority: accomplish a goal based on a ranking of values
Hierarchy: exercise of authority
Cahracter: goal concerning the image the client wants to project in terms of values and the generic nature of the project
Density: efficient land or space use, a goal for high degrees of interaction, or a goal to harsh climate conditions

[Camy Do · Rating 4 out of 5]

Good Book on Arch. Programming with illustrated graphic and step by step analysis.

[Don Valdez · Rating 5 out of 5]

I read this as a resource for teaching.

[David (F3 Fountainhead) · Rating 1 out of 5]

This book does an excellent job of making simple concepts seem complex—exactly the opposite of what I look for in a technical book. I appreciate that the graphics are excellent and clear, but since the concepts behind them are also simple, I’d prefer to devote my energy to more challenging subjects.

That said, it’s good, I suppose, for beginners and students. But for professionals who already know basic concepts of programming and space planning, a quick summary from Ballast, or the first chapter of this book, is all you need for the ARE.

[Jun Guo]

I read it for preparing my ARE exams. It is my second time to read it. I love those diagrams illustrating the strategics used for the programming process in this book.

Secondly, it is useful to understand what is programming, how we do during programming process, and most importantly, what is the difference between programming and design.

[John · Rating 4 out of 5]

William Pena does a great job of describing the programming phase of design. Very simple and easy to read. Some great tips for beginners.

[Susie · Rating 4 out of 5]

This is a great book to help guide an architect through the programming process. It's easy to follow and provides a great template and is universal to project type and client base.

[Melina · Rating 2 out of 5]

Basic book on programming. Short on examples and brief. A few sections are useful and should be kept handy for occasional reference.