"Architecture is too important to be left to architects"

The title of this entry comes directly from De Carlo's text, and it sums up the reasons why we should design with the user, not for them, and why we should pay more attention to the "why" of a project instead of just the "how." 

Every time we set out to start a project, we have a prompt: a user base, general program for the project, and a location. Each of these categories has a long list of subheadings that demand our attention. At first our efforts are divided in understanding who is using the space, what is the exact breakdown of the program and spaces, and how the context will influence our design. At this phase, I think it is easier to design with the user in mind, engage with people outside of architecture and gauge their perceptions, and keep the "why am I doing this project" at the forefront.

Moving down the line, that tends to get lost in construction documents, code, details, cost, etc ad nauseam. Our focus shifts to "how can I get it all to work" instead of "what are the effects". Ultimately, we still juggle both aspects, but I think today's architecture still focuses more on the hows of designing for people.

Transitions of a micro unit in Vancouver
'how to fit in more people'


Suburbia efficiency

Comments

  1. I agree with you that we should design with the user, not for them. Cause what we think or plan for the user doesn't represent what the users have in their mind. Some spaces that we designed for the user, we would imagine how they would use those spaces, but the users might not end up the way we want.

    ReplyDelete

Post a Comment

Popular Posts