>>36663122>pipeline is a metaphorical word that is supposed to illustrate the business process as a series of pipes that deliver content
Pipeline is actually a word that refers to a process that continuously produces some output without waiting for previous output to have been received.
For example, to execute an instruction in a program, a CPU needs to fetch the instruction, decode it, fetch any data required for it, perform the actual calculation/whatever, then store the result. Early CPUs did that sequentially all for one instruction, then moved on to the next one, etc. More modern CPUs have pipelining, which means that while one instruction is being processed, the next one can already be fetched and decoded. (Today, there are often dozens or hundreds of instructions in flow at any given time on a busy CPU.)
Similarly, in a business process, a pipeline is where you continuously move forward work without waiting for every single project to be completed. For instance, without pipelining, you could design one cartoon, approve it, write out a season, animate it, wait for it to air on TV, and then go back to deciding what you do next. Pipelining means that instead you get several things, and once one has been approved you start designing and approving the next, once one has been animated the writers should already have the next animation tasks ready, etc.
This makes sure resources are as efficiently utilised as possible without any idle downtime (whether the resources are CPU components, or production teams). The analogy is with a water pipeline where the water plant is constantly pumping water that people later use - as opposed to sending some batch of water through the pipe, then waiting for that water to get used before sending the next batch.