A simpler perspective of the architect's role

Here are a couple of givens that I have come to realize, even more this semester, when pursuing a career in architecture:

1. We have to build a broad knowledge base as architects, not a deep one.
2. We will continue to define what we are about, and what makes us tick as designers, throughout our careers - our personal design premise.
3. We have to establish a moral code as professionals – what you will and won’t pursue based on your personal values.

What do all three of these items have in common? They define how we as architects participate in the creative process. Habraken views the built environment as a self-sufficient entity, one that has evolved over thousands of years on its own without the hand of the designer. Therefore, the designer’s role is not to figure out how the users participate in what they create, but to decide how their participation in the existing environment can be a positive influence to the users.

Whether we realize it or not, these “givens” we tend to forget about when immersed in a competitive school environment, as well as in a new job setting, eager to please our new team or client. The next project always has to be better than its predecessor, and we will go to great lengths, often at the expense of the project and its users, to make sure that happens.

Notice, nowhere above is our role to please. In contrast, we are to stand our ground on personal morality, while using our skills and personal beliefs to positively influence our environment. As long as we keep those few things in mind, the form, size, or systems can change fluidly as needed, and you will stay true to yourself, who you are working for, and have a better project in result.