Processpatching

4.2.1. Problem solving, reductive method

In problem solving, the expectations, which are projected to the ‘other’ discipline(s), represent an instrumental view. The situation outlined shows that one discipline looks for assistance from the other(s) to solve problems, which are hard to tackle with the expertise or methods available in their own discipline. This instrumental attitude matches a multidisciplinary approach, where collaborators are called in for their expertise without the intention of disciplinary blurring or merging of disciplines. This model for multidisciplinary collaboration has proven itself worth; however, it should not be confused with interdisciplinary or transdisciplinary collaboration, where the disciplinary borders may blur or (temporarily) disappear. As was shown in 2.1.3., the call for problem solvers is always formulated from a particular perspective and reflects a certain set of background concerns and need(s).

From the literature studies analysed in this thesis research, observable and reasonably distinct forms of research problems can be identified:

  • Most significant are the pleas for artists to solve the scientific communication problem. Here the scientific community searches for expert knowledge in communication from the arts (2.1.1.1.).
  • Urban designers, historians of science and policymakers suggested making up for the shortcomings of technology driven innovation, and to restore social cohesion (2.1.1.2.).
  • Solving technical problems is rooted in technical engineering and design practice. Here the electronic artist seeks expert assistance. Technological innovation by artists is among the outcomes of the technical problem solving approach. Here the electronic artist often works in multiple roles, as artist and engineer (2.1.1.3.).

The three distinct types of problems demonstrate that there is always a commissioning party and a party who carries out the task, and that the commissioning party approaches the other’s work in an instrumental way. The knowledge gleaned about the respective domains or disciplines does not always match reality, but this is partly compensated by the widely known and simple format of the method. The most common way to manage problem solving is to apply a reductive approach while formulating the scale of the problem and its domain of application. Here all noise around a problem is eliminated and the complicating factors are wiped out. This approach of problem solving shows a direct parallel with design and engineering practice (2.1.1.2., Gropius, 2.2.3.1.). A reductive method is also used in computer or technical science, which builds on existing knowledge (Kuhn, Popper 2.2.3.3, Smeulders 3.2.1., Schouten 3.2.1.). The case studies show that the art projects that were developed by a small team with little diversity in their disciplinary backgrounds, (3.1.1., 3.2.2.) and the scientific projects developed by people from limited scientific disciplines (3.2.1., 3.2.2.) worked according to a problem solving or reductive approach. The case studies also reveal that the artists, with mixed backgrounds in traditional art and science, feel most at ease as autonomous scientific researchers with a reductive or problem solving approach (Carpendale, Schouten 3.2.2.).

Creative Commons License