Abstract

Talking about architecture means talking not only about buildings but also about processes or systems. In the latter context, architecture is a way of thinking and looking at people, spaces, interrelations and interactions. Proclaimed by IDEO’s Tim Brown as one of the best system design forms of education available, architecture has potential in fields beyond the physical. In keeping with the views of renowned systems thinker Russell Ackoff, who graduated in architecture before focusing on operations research, the question arises whether the skills of architects can be applied more broadly in system and innovation design. This paper describes how architects deal with context and complexity from the perspective of the practice-oriented architectural programming method. From its early days in the 1960s, it offered architects a viable basis for an applied architectural design thinking method, but did not receive widespread attention from practitioners and academics. The method is critically assessed and compared to the known forms of design thinking from the viewpoint of industrial design. By describing a real-life project and students’ work from a newly created seminar in a department of architecture, the paper investigates the current and future relevance of an advanced version of architectural programming for architectural practice and education. It stresses the desirability of reinforcing the core skills of architects by developing a design thinking method rooted in architecture, which needs to be taught, developed and disseminated. In the long term, it is argued, architecture should be considered and integrated as a ‘systems and innovation design discipline’ in the fields of systems thinking and innovation research.

Highlights

  • Talking about architecture means talking about buildings and about processes or systems

  • Christos Chantzaras Architecture as a system and innovation design discipline immerse themselves in a long-term perspective for their clients, while considering the changing usage of space over time (Nelson & Stolterman 2012; Pallasmaa 2016; Samuel 2018)

  • They are constantly moving between problem and solution while analysing, synthesising and evaluating their approach, in order to create a state that “ought to be” (Lawson 2005, p. 49; Nelson & Stolterman 2012)

Read more

Summary

Systems Design

Development of architectural programming The term programming, i.e. setting up the project programme and brief, is familiar to architects to a greater or lesser extent. In the decades since CRS (later CRSS) was established, the method was developed further in varying forms by HOK and other architectural practices It became listed as an additional service by the American Institute for Architects (AIA), and was synonymously known as pre-design, brief design or facility programming (Duerck 1993; Kumlin 1995; Cherry 1999; Faatz 2009; Hodulak & Schramm 2011). The programmers apply an abstract, holistic form of systems thinking, conceptualise processes and the arrangement of functions and operate efficiently with iteration and loops to confirm the results and agreements of each step of the process They focus on quantitative as well as qualitative information and precisely record, calculate and forecast demands in terms of square metres and areas, as well as collecting and listing the kind of technical equipment needed for the project and the mechanical, electrical and climate requirements (Peña & Parshall 2012; Cherry 1999). Comparing architectural programming with the design thinking method rooted in industrial design by its applied version for management and innovation processes reveals the existing knowledge (see Table 2)

Programming Principles
Level of Detail Abstract
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call