

Workflow is a generic term for orchestrated and repeatable patterns of activity, enabled by the systematic organization of resources into processes that transform materials, provide services, or process information. It can be depicted as a sequence of operations, the work of a person or group, the work of an organization of staff, or one or more simple or complex mechanisms.
From a more abstract perspective, workflow may be considered a view or representation of real work. The flow being described may refer to a document, service, or product that is being transferred from one step to another.
Workflows may be viewed as fundamental building blocks to be combined with other parts of an organization's structure, such as information technology, teams, projects, and hierarchies.
The development of the workflow concept occurred across several loosely defined, overlapping eras.
The modern history of workflows can be traced to Frederick Taylor and Henry Gantt, although the term "workflow" was not used in this context during their lifetimes. One of the earliest instances of the term "work flow" was in a railway engineering journal from 1921.
Taylor and Gantt launched the study of the deliberate, rational organization of work, primarily in the context of manufacturing. This gave rise to time and motion studies. Related concepts include job shops and queuing systems (Markov chains).
The 1948 book Cheaper by the Dozen introduced the emerging workflow concept to the context of family life.
The invention of the typewriter and the copier helped spread the study of the rational organization of labor from the manufacturing shop floor to the office. Filing and other sophisticated systems for managing physical information flows evolved. Several events likely contributed to the development of formalized information workflows. First, the field of optimization theory matured and developed mathematical optimization techniques. For example, Soviet mathematician and economist Leonid Kantorovich developed the seeds of linear programming in 1939 through efforts to solve a plywood manufacturer's production optimization issues. Second, World War II and the Apollo program drove process improvement forward with their demands for the rational organization of work.
In the postwar era, the work of W. Edwards Deming and Joseph M. Juran led to a focus on quality, first in Japanese companies, and more globally from the 1980s. There were various movements ranging from total quality management to Six Sigma, and then more qualitative notions of business process re-engineering. This led to more efforts to improve workflows in both knowledge economy sectors and manufacturing. Thought leaders recognized variable demands on workflows when they considered the theory of critical paths and moving bottlenecks.
Basu and Kumar noted that the term "workflow management" referred to tasks associated with the flow of information through the value chain rather than the flow of material goods: they characterise the definition, analysis and management of information as "workflow management". They note that workflow can be managed within a single organisation, where distinct roles are allocated to individual resources, and also across multiple organisations or distributed locations, where attention needs to be paid to the interactions between activities which are located at the organizational or locational boundaries. The transmission of information from one organization to another is a critical issue in this inter-organizational context and raises the importance of tasks they describe as "validation", "verification" and "data usage analysis".
A workflow management system (WfMS) is a software system for creating, executing, and monitoring a defined sequence of processes and tasks, with the broad goals of increasing productivity, reducing costs, becoming more agile, and improving information exchange within an organization. These systems may be process-centric or data-centric, and they may also represent the workflow as graphical maps. A workflow management system may also include an extensible interface so that external software applications can be integrated, providing support for wide area workflows that provide both faster response times and improved productivity.
The workflow concept is closely related to several fields in operations research and other areas that study the nature of work either quantitatively or qualitatively, such as artificial intelligence (in particular, the sub-discipline of AI planning) and ethnography. The term "workflow" is more commonly used in particular industries like printing, as well as professional domains such as clinical laboratories. It may have particular specialized meanings in these areas.

The following examples illustrate the variety of workflows seen in various contexts:
Several workflow improvement theories have been proposed and implemented in the modern workplace. These include:
Resource evaluation (both physical and human) is essential to evaluating hand-off points and creating smoother transitions between tasks.
A workflow can usually be described using formal or informal flow diagramming techniques and displays directed flows between processing steps. Single processing steps or components of a workflow can basically be defined by three parameters:
Components can only be plugged together if the output of one previous (set of) component(s) is equal to the mandatory input requirements of the following component(s). Thus, the essential description of a component actually comprises only input and output that are described fully in terms of data types and their meaning (semantics). The algorithms' or rules' descriptions need only be included when there are several alternative ways to transform one type of input into one type of output – possibly with different accuracy, speed, etc.
When the components are non-local services that are invoked remotely via a computer network, such as Web services, developers must consider additional descriptors (such as QoS and availability).
A workflow application is a software application that automates a process or processes to some degree. These processes are usually business-related but can be any process that requires a series of steps to be automated via software. Some process steps may require human intervention, such as development and approval of custom text, but functions that can be automated should be handled by the application. Advanced applications allow users to introduce new components into the operation.