Skip to main content

Rules, Plans and the Normativity of Technological Knowledge

  • Chapter
  • First Online:
Norms in Technology

Part of the book series: Philosophy of Engineering and Technology ((POET,volume 9))

Abstract

It is not uncommon to describe the efforts of engineers, the results of these efforts and the specific knowledge employed in normative terms. Take, for instance, ‘The engineer, and more generally the designer, is concerned with how things ought to be – how they ought to be in order to attain goals, and to function’ (Simon 1981: 7).

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 109.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    In this chapter, the efforts of engineers are labelled designing, the results of their efforts are technologies or artefacts, and the specific knowledge employed is technological knowledge. Occasionally, efforts, results and knowledge are indiscriminately referred to as ‘technology’, employing the ambiguity of this notion, which may refer to a system of knowledge, a system of objects (Mitcham 1978) and a set of (institutionalised) practices – as in usage of the term ‘information technology’.

  2. 2.

    Here and throughout this chapter, I take ‘prescriptive’ as a synonym of ‘normative’, that is, as ‘concerned with norms or directives’. Thus, prescriptive statements include (expressions of) rules, recommendations and requirements.

  3. 3.

    The aim must be phrased in terms of prescriptive content of knowledge to avoid triviality: on non-naturalist conceptions, all knowledge involves norms on beliefs and is therefore ‘prescriptive’. The guiding idea behind this chapter is that, in addition to the norms on knowledge, there are norms in some knowledge, that is, it is about prescriptions.

  4. 4.

    The aim is not even to capture the only or the only important prescriptive part of technological knowledge. Another part, not discussed in this chapter, consists of the category-specified value statements (e.g. ‘This is a good bridge’) identified by Hansson (2006).

  5. 5.

    Bunge’s later work differs marginally from Bunge (1966).

  6. 6.

    Interestingly, Bunge does not discuss the ‘rules of science’ in his paper.

  7. 7.

    Here, the analysis connects to the notion of ‘practical norm’ introduced by Von Wright (1963) and, indirectly, to the analysis of instrumental knowledge given by Niiniluoto (1993). Like Bunge, Niiniluoto aims at understanding applied research through focussing on relations between means (actions) and ends. His discussion and its relation to the present analysis are complicated, however, by Niiniluoto’s insistence on distinguishing between technology, which concerns actions and is evaluated in terms of its effectiveness, and instrumental knowledge, which concerns technical norms and is evaluated in terms of truth. This raises the question whether technical norms are indeed truth candidates (an issue Von Wright stays agnostic about) and the question how technology and instrumental knowledge are related, although they involve different core values. I submit that the plan analysis clarifies the relation while restoring Von Wright’s agnosticism but will not substantiate this here.

  8. 8.

    The plan analysis does not systematically distinguish between contributions to goal realisation by objects and by other people. Like plans may require artefacts to manifest dispositions (e.g. to conduct heat or electricity), they may require actions taken by people (e.g. drive your train).

  9. 9.

    The general merits and difficulties of a plan-centred approach are not considered here. Planning may or may not, for instance, be reducible to a series of intention formations; this is irrelevant for present purposes as long as the (possibly irreducible) concept of use plans can be used to analyse artefact design and use, and the prescriptive content of technological knowledge.

  10. 10.

    This characterisation of designing resembles Herbert Simon’s: ‘Everyone designs who devises courses of action aimed at changing existing situations into preferred ones’ (1981, p.129).

  11. 11.

    The effectiveness standard on plans may be so fundamental that the very notion of ‘plan’ incorporates a measure of effectiveness. If I would try to find extraterrestrial life by reading The Waste Land in my roof garden, I would not be executing an irrational plan, but no plan at all (e.g. because my house has no roof garden).

  12. 12.

    These standards are taken from Bratman (1987, §3.2), who uses ‘internal consistency’ for the first standard. We changed this label to indicate that the other standards also derive from the internal structure of plans. See also Audi (1989, Ch.7).

  13. 13.

    Calling knowledge of plans ‘procedural knowledge’ matches usage of the latter term in AI (Georgeff and Lansky 1987). The term is also used in cognitive psychology (e.g. Anderson 1981), where it indicates knowledge of how to realise a goal, that is, what we have called ‘instrumental knowledge’; cognitive psychologists contrast procedural knowledge with declarative knowledge, which we would call ‘descriptive’.

  14. 14.

    This touches upon a deeper worry regarding the status of procedural knowledge as knowledge, namely, whether knowledge of a plan is a candidate for being true. The standards of practical rationality may distinguish good and bad examples of this type, but this does not resolve whether it is a properly epistemic type.

  15. 15.

    See Hughes (2009) and Hughes’ contribution to this volume for a way to make the connection between plans and means-end reasoning more explicit.

  16. 16.

    Nelson and Winter and their successors model technological and organisational change as an evolutionary process, by looking at generations of populations of organisations and organisational routines, connected by the core Darwinian mechanisms of variation, selection and retention. Here, organisations may be allowed to change their routines over time, introducing the required divisions between generations on the level of temporal stages of organisations (say, fiscal years). Alternatively, organisations may not be allowed to change routines, dividing generations by moments at which new organisations may enter the market and/or unsuccessful ones disappear. The application of the plan analysis in this chapter is supposed to be neutral with respect to these two modelling approaches.

  17. 17.

    See Becker (2004), Dosi et al. (2000), Hodgson (2004), Vromen (2006) and the references in these papers.

  18. 18.

    Assuming, for the moment, that these taxonomies stand up to critical scrutiny.

  19. 19.

    Cf. the distinction between product and service characteristics of technologies made by Saviotti and Metcalfe (1984) and developed further in Saviotti (1996).

References

  • Anderson, J.R. 1981. Cognitive Skills and Their Acquisition. Hillsdale: Lawrence Erlbaum.

    Google Scholar 

  • Audi, R. 1989. Practical reasoning. London: Routledge.

    Google Scholar 

  • Becker, M. 2004. Organizational routines. Industrial and Corporate Change 13: 643–677.

    Article  Google Scholar 

  • Bratman, M. 1987. Intentions, plans and practical reason. Cambridge, MA: Harvard University Press).

    Google Scholar 

  • Bunge, M. 1966. Technology as applied science. Technology and Culture 7: 329–349.

    Article  Google Scholar 

  • Cohen, M.D., R. Burkhart, G. Dosi, M. Egidi, L. Marengo, M. Warglien, and S. Winter. 1996. Routines and other recurring action patterns of organizations. Industrial and Corporate Change 5: 653–699.

    Article  Google Scholar 

  • De Ridder, J. 2006. Mechanistic artefact explanation. Studies in History and Philosophy of Science 37: 81–96.

    Article  Google Scholar 

  • Dosi, G., R.R. Nelson, and S.G. Winter. 2000. The nature and dynamics of organizational capabilities. Oxford: Oxford University Press.

    Google Scholar 

  • Faulkner, W. 1994. Conceptualizing knowledge used in innovation. Science Technology and Human Values 19: 425–458.

    Article  Google Scholar 

  • Franssen, M. 2006. The normativity of artefacts. Studies in History and Philosophy of Science 37: 42–57.

    Article  Google Scholar 

  • Georgeff, M., and A.L. Lansky. 1987. Procedural knowledge. Proceedings of the IEEE 74(10): 1383–1398.

    Article  Google Scholar 

  • Groover, M.P. 2007. Fundamentals of modern manufacturing. New York: John Wiley.

    Google Scholar 

  • Hansson, S.O. 2006. Category-specified value statements. Synthese 148: 425–432.

    Article  Google Scholar 

  • Hendricks, V.F., A. Jakobsen, and S.A. Pedersen. 2000. Identification of matrices in science and engineering. Journal for General Philosophy of Science 31: 277–305.

    Article  Google Scholar 

  • Hodgson, G.M. 2004. The mystery of the routine. Revue Économique 54: 355–384.

    Google Scholar 

  • Houkes, W. 2006. Knowledge of artefact functions. Studies in History and Philosophy of Science 37: 102–113.

    Article  Google Scholar 

  • Houkes, W. 2009. The nature of technological knowledge. In Handbook of philosophy of technology and engineering sciences, ed. A.W.M. Meijers, 309–350. Amsterdam: Elsevier.

    Chapter  Google Scholar 

  • Houkes, W., and P.E. Vermaas. 2009. Contemporary engineering and the metaphysics of artifacts. The Monist 92: 403–419.

    Google Scholar 

  • Houkes, W., and P.E. Vermaas. 2010. Technical functions. Dordrecht: Springer.

    Book  Google Scholar 

  • Houkes, W., P.E. Vermaas, C.H. Dorst, and M.J. de Vries. 2002. Design and Use as plans. Design Studies 23: 303–320.

    Article  Google Scholar 

  • Hughes, J. 2009. An artifact is to use. Synthese 168: 179–199.

    Article  Google Scholar 

  • Jackson, J.D. 1975. Classical electrodynamics, 2nd ed. New York: Wiley.

    Google Scholar 

  • Kroes, P.A. 1992. On the role of design in engineering theories. In Technological development and science in the industrial age, ed. P.A. Kroes and M. Bakker, 69–98. Dordrecht: Kluwer.

    Google Scholar 

  • Mitcham, C. 1978. Types of technology. Research in Philosophy and Technology 1: 229–294.

    Google Scholar 

  • Moran, M.J., H.N. Shapiro, B.R. Munson, and D.P. DeWitt. 2003. Introduction to thermal systems engineering. New York: Wiley.

    Google Scholar 

  • Mokyr, J. 2002. The gifts of Athena. Princeton: Princeton University Press.

    Google Scholar 

  • Nelson, R.R., and S.G. Winter. 1982. An evolutionary theory of economic change. Cambridge, MA: Belknap Press.

    Google Scholar 

  • Nightingale, P. 2009. Tacit Knowledge and Engineering Design. In Handbook of philosophy of technology and engineering sciences, ed. A.W.M. Meijers, 351–374. Amsterdam: Elsevier.

    Chapter  Google Scholar 

  • Niiniluoto, I. 1993. The aim and structure of applied research. Erkenntnis 38: 1–21.

    Article  Google Scholar 

  • Pollock, J.L. 1995. Cognitive carpentry. Cambridge, MA: MIT Press.

    Google Scholar 

  • Saviotti, P.P. 1996. Technological evolution, variety and the economy. Cheltenham: Edward Elgar.

    Google Scholar 

  • Saviotti, P.P., and J.S. Metcalfe. 1984. A theoretical approach to the construction of technological output indicators. Research Policy 13: 141–151.

    Article  Google Scholar 

  • Simon, H.A. 1981. The sciences of the artificial, 2nd ed. Cambridge, MA: The MIT Press.

    Google Scholar 

  • Staudenmaier, J.M. 1985. Technology’s storytellers: Reweaving the human fabric. Cambridge, MA: The MIT Press.

    Google Scholar 

  • Van Aken, J.E. 2004. Management Research Based on the Paradigm of the Design Sciences. Journal of Management Studies 41: 219–246.

    Article  Google Scholar 

  • Van Aken, J.E. 2005. Management research as a design science. British Journal of Management 16: 19–36.

    Article  Google Scholar 

  • Vermaas, P.E., and W. Houkes. 2006. Use plans and artefact functions. In Doing things with things, ed. A. Costall and O. Dreier, 29–48. London: Ashgate.

    Google Scholar 

  • Vincenti, W.G. 1990. What engineers know and how they know it. Baltimore: Johns Hopkins.

    Google Scholar 

  • Von Wright, G.H. 1963. Norm and action. London: Routledge and Kegan Paul.

    Google Scholar 

  • Vromen, J.J. 2006. Routines, genes and program-based behavior. Journal of Evolutionary Economics 16: 543–560.

    Article  Google Scholar 

Download references

Acknowledgments

Research for this chapter was made possible by the Netherlands Organisation for Scientific Research. Helpful comments on an earlier version were given by Marieke van Holland, Auke Pols and Krist Vaesen.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Wybo N. Houkes .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer Science+Business Media Dordrecht

About this chapter

Cite this chapter

Houkes, W.N. (2013). Rules, Plans and the Normativity of Technological Knowledge. In: de Vries, M., Hansson, S., Meijers, A. (eds) Norms in Technology. Philosophy of Engineering and Technology, vol 9. Springer, Dordrecht. https://doi.org/10.1007/978-94-007-5243-6_3

Download citation

Publish with us

Policies and ethics