This article needs additional citations for verification. (May 2009) (Learn how and when to remove this template message)
A process theory is a system of ideas that explains how an entity changes and develops. Process theories are often contrasted with variance theories, that is, systems of ideas that explain the variance in a dependent variable based on one or more independent variables. While process theories focus on how something happens, variance theories focus on why something happens.
Process Theory Archetypes
Process theories come in four common archetypes. Evolutionary process theories explain change in a population through variation, selection and retention—much like biological evolution. In a dialectic process theory, “stability and change are explained by reference to the balance of power between opposing entities” (p. 517). In a teleological process theory, an agent “constructs an envisioned end state, takes action to reach it and monitors the progress” (p. 518). In a lifecycle process theory, “the trajectory to the final end state is prefigured and requires a particular historical sequence of events” (p. 515); that is, change always conforms to the same series of activities, stages, phases, like a caterpillar transforming into a butterfly.
Applications and Examples
Process theories are important in management and software engineering. Process theories are used to explain how decisions are made  how software is designed and how software processes are improved.
Motivation theories can be classified broadly into two different perspectives: Content and Process theories.
- Content theories deal with “what” motivates people and it is concerned with individual needs and goals. Maslow, Alderfer, Herzberg and McClelland studied motivation from a “content” perspective.
- Process theories deal with the “process” of motivation and are concerned with “how” motivation occurs. Vroom, Porter & Lawler, Adams and Locke studied motivation from a “process” perspective.
Process theories are also used in education, psychology, geology and many other fields; however, they are not always called "process theories".
- Van de Ven, Andrew (2007). Engaged scholarship: a guide for organizational and social research. Oxford University Press.
- Van De, A. H.; Poole, M. S. (1995). "Explaining development and change in organizations". Academy of Management Review. 20 (3): 510–540. doi:10.5465/AMR.1995.9508080329.
- Ralph, Paul (1 January 2015). "Developing and Evaluating Software Engineering Process Theories". Proceedings of the 37th International Conference on Software Engineering - Volume 1. IEEE Press. pp. 20–31.
- Poole, Marshall Scott; Roth, Jonelle (March 1989). "Decision Development in Small Groups IV A Typology of Group Decision Paths". Human Communication Research. pp. 323–356. doi:10.1111/j.1468-2958.1989.tb00188.x.
- Ralph, Paul (April 2015). "The Sensemaking-Coevolution-Implementation Theory of software design". Science of Computer Programming. 101: 21–41. arXiv: . doi:10.1016/j.scico.2014.11.007.
- Ralph, Paul (February 2016). "Software engineering process theory: A multi-method comparison of Sensemaking–Coevolution–Implementation Theory and Function–Behavior–Structure Theory". Information and Software Technology. 70: 232–250. arXiv: . doi:10.1016/j.infsof.2015.06.010.
- Allison, I.; Merali, Y. (1 June 2007). "Software process improvement as emergent change: A structurational analysis". Information and Software Technology. 49 (6): 668–681. doi:10.1016/j.infsof.2007.02.003.