Abstract
In Part I of the book, we explored the two “archai” of organizations indicating that they are social systems conducting experiments. In the present part, we will give a systematic exposition of ways of organizing this experiment. Given the “logic” of the experiment, this means that we have to look for principles enabling the design of infrastructural conditions allowing organizations to experiment. These infrastructural conditions are so important because an organization’s potential to select and reselect goals, infrastructures, operational regulation, and transformation processes (and all other “objects” related to these “focal” objects), crucially depends on the design of its infrastructure.
Above, we distinguished two classes of design principles: functional design principles and specific design principles. Functional design principles specify what a system’s infrastructure must be able to do if the system is to survive. Specific design principles, specify rules and heuristics for the design of particular parts of the infrastructure (the division of work, human resources management, technology), given the set of functional design principles.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Recursion derives from “recurrere,” which means “to run, walk back” in Latin. In mathematics or computer science, recursion is used to indicate that some function or routine calls itself. For instance, we can define F(n) (on N) as (1) 1 if n = 0 and (2) 3*F(n−1)+3 if n > 0. This is a recursive definition. However, the general description given in text also applies to these functions: In the main function (the concrete system f(n)) we can find a subsystem (the recursive call f(n−1)) with the same characteristics (the defining aspects).
- 2.
Beer uses the word “System” instead of function. We have two reasons to depart from this usage. The first is that the Viable System Model is a functional model of viable systems, specifying functions required for viability. This terminology is consistent with other recent descriptions of the Viable System Model in literature (see for instance, Espejo, et al. 1996) The second reason is that we reserve the word system for the viable system as a whole.
References
Achterbergh, J., & Vriens, D. (2002). Managing viable knowledge. Systems Research and Behavioral Science, 19, 223–241.
Ashby, R. W. (1958). An introduction to cybernetics. London: Chapman and Hall.
Beer, S. (1972). Brain of the firm. London: Allen Lane the Penguin Press.
Beer, S. (1992). The viable system model: Its provenance, development, methodology and pathology. In R. Espejo & R. Harnden (Eds.), The viable system model: Interpretations and applications of Stafford Beer’s VSM (pp. 11–37). Chichester: Wiley.
Beer, S. (1995). The Heart of Enterprise. Chichester: Wiley.
Beer, S. (1996). Diagnosing the system for organizations. Chichester: Wiley.
Christis, J. (2002). Causal explanation and functional analysis in Luhmann’s sociology. Unpublished paper.
Espejo, R., Schumann, W., Schwaninger, M., & Bilello, U. (1996). Organizational transformation and learning: A cybernetic approach to management. Chichester: Wiley.
Luhmann, N. (1991). Soziologische Aufklärung 1. Opladen: Westdeutscher Verlag.
Luhmann, N. (1995). Social Systems. J. Bednarz, Jr. & D. Baecker (Trans.). Palo Alto, CA: Stanford University Press.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Achterbergh, J., Vriens, D. (2009). Beer: Functional Design Principles for Viable Infrastructures. In: Organizations. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-00110-9_6
Download citation
DOI: https://doi.org/10.1007/978-3-642-00110-9_6
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-00109-3
Online ISBN: 978-3-642-00110-9
eBook Packages: Business and EconomicsBusiness and Management (R0)