63
Essences of Interaction
this second instance implies perhaps a single product that (through services)
provides a similar functionality as with multiple products. So, by either
increasing the number or speeding up a service, scalability is achieved.
Products and services can be thought of as different in this regard. For example, project management and systems engineering can be thought of as two
distinct but related services, the end result of which is a product (or
service).
While products and services are different, both provide for functionalities
that can result in uses with various performances. The ability to perform or,
as Taguchi (1986) prefers to think of it, the variance in the performance can be
thought of as the quality of the product or service. In contrast to products that
are built and then subsequently delivered, services are built and used simultaneously (Kotler and Keller 2007). The differences between products and services include how products and services are used and thought of, how they
are delivered, how users behave once they have access or use, how users
behave because of the product or service, how the management processes are
planned and enacted, and how products and services are integrated into
operations. Indeed, it serves the producers of products well to think of the
services provided by their products with equal consideration to those
intended uses as a product. What decisions will the customer make because
they have purchased a piece of wood? The customer may be thinking about
using the wood as means to support a bookcase. The service provided by the
wood is to support a bookcase. The product function of ‘to support’ is not
designed into the wood product per se, only envisioned by the customer who
purchased and the user who used the wood to support a bookcase.
While our perception of integration may be skewed by the framing of a particularly vexing issue, the nature of integration does not change. The nature of
integration is to result in the exchange of energy, matter, information, and
capital wealth. The goal of integration should be to enable this exchange in an
energy-efficient manner, consistent with the limitations imposed on a lifecycle
basis and the constraints allocated in the architecture of the system.
Objects
We commonly think of an object as a fundamental element, entity, or representation. It may be atomic or an aggregation of entities. Objects can be physical or abstract. Objects may be conceptual, phenomenological, or ideological.
Some but not all objects are teleological. Animal objects can be said to be
exhibit processes that are purposeful (Bainswanger 1990). Teleological processes explain phenomena by the purpose(s) or their end(s) they serve rather
than by causes postulated to explain behaviors. Bainswanger (1990, p. 119)
describes three conditions for teleological action: self-generation, significant
Essences of Interaction
this second instance implies perhaps a single product that (through services)
provides a similar functionality as with multiple products. So, by either
increasing the number or speeding up a service, scalability is achieved.
Products and services can be thought of as different in this regard. For example, project management and systems engineering can be thought of as two
distinct but related services, the end result of which is a product (or
service).
While products and services are different, both provide for functionalities
that can result in uses with various performances. The ability to perform or,
as Taguchi (1986) prefers to think of it, the variance in the performance can be
thought of as the quality of the product or service. In contrast to products that
are built and then subsequently delivered, services are built and used simultaneously (Kotler and Keller 2007). The differences between products and services include how products and services are used and thought of, how they
are delivered, how users behave once they have access or use, how users
behave because of the product or service, how the management processes are
planned and enacted, and how products and services are integrated into
operations. Indeed, it serves the producers of products well to think of the
services provided by their products with equal consideration to those
intended uses as a product. What decisions will the customer make because
they have purchased a piece of wood? The customer may be thinking about
using the wood as means to support a bookcase. The service provided by the
wood is to support a bookcase. The product function of ‘to support’ is not
designed into the wood product per se, only envisioned by the customer who
purchased and the user who used the wood to support a bookcase.
While our perception of integration may be skewed by the framing of a particularly vexing issue, the nature of integration does not change. The nature of
integration is to result in the exchange of energy, matter, information, and
capital wealth. The goal of integration should be to enable this exchange in an
energy-efficient manner, consistent with the limitations imposed on a lifecycle
basis and the constraints allocated in the architecture of the system.
Objects
We commonly think of an object as a fundamental element, entity, or representation. It may be atomic or an aggregation of entities. Objects can be physical or abstract. Objects may be conceptual, phenomenological, or ideological.
Some but not all objects are teleological. Animal objects can be said to be
exhibit processes that are purposeful (Bainswanger 1990). Teleological processes explain phenomena by the purpose(s) or their end(s) they serve rather
than by causes postulated to explain behaviors. Bainswanger (1990, p. 119)
describes three conditions for teleological action: self-generation, significant