In the 1960s, the designer Robert Propst worked with the Herman Miller company to produce “The Action Office”, a stylish system of open-plan office furniture that allowed workers to sit, stand, move around and configure the space as they wished.
Propst then watched in horror as his ideas were corrupted into cheap modular dividers, and then to cubicle farms or, as Propst described them, “barren, rathole places”. Managers had squeezed the style and the space out of the action office, but above all they had squeezed the ability of workers to make choices about the place where they spent much of their waking lives.
...It should be easy for the office to provide a vastly superior working environment to the home, because it is designed and equipped with work in mind. Few people can afford the space for a well-designed, well-specified home office. Many are reduced to perching on a bed or coffee table. And yet at home, nobody will rearrange the posters on your wall, and nobody will sneer about your “dog pictures, or whatever”. That seems trivial, but it is not.
The brick is one of those old technologies, like the wheel or paper, that seem to be basically unimprovable. ‘The shapes and sizes of bricks do not differ greatly wherever they are made,’ writes Edward Dobson in the fourteenth edition of his Rudimentary Treatise on the Manufacture of Bricks and Tiles. There’s a simple reason for the size: it has to fit in a human hand. As for the shape, building is much more straightforward if the width is half the length.
While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes.
Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all.
I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions.