Partially Algorithmic Processes

In a prior blog post I explained what an algorithm is. In a different blog post I talked about the process, project, and workflow in a digital environment. In yet another blog  post I talked about work. Let me summarize a few definitions:

  • Algorithm: An algorithm is a finite sequence of well-defined instructions, typically to solve a class of problems or to perform a computation.  Algorithms are always unambiguous and are used as specifications for performing a task or process.
  • Process: A process is a set of steps or actions that when consistently followed leads from some starting point to the completion of some objective.  A process can involve multiple tasks or multiple workflows.  A process tends to repeat.  
  • Project: A project is a type of process that does not repeat.  All projects are processes; but not all processes are projects.  The difference between a project and a process is how often you perform some set of steps or actions.  The more often a set of steps or actions is performed; the more benefit there is to spending time to gain control over a process.
  • Workflow: A workflow is a sequenced set of processes; it describes the flow of inputs to outputs as a result of a process.
  • Computable: Not everything is computable. This article discusses computability and complexity.
  • Best practice: A best practice is a method or technique that has been generally accepted as superior to any other known alternatives because it produces results that are superior to those achieved by other means or because it has become a standard way of doing things.

In very simple terms, an algorithm is a formal, step-by-step procedure or specification or a plan for solving a problem or performing a task. A process is the instantiation or enactment of that algorithm.

For example, a recipe is an algorithm; cooking something using that recipe is a process.

Processes can be partially algorithmic, where specific "subroutines" or "tasks" are computable and therefore automatable; but the overall workflow resists computation because it involves human coordination, judgment, creativity, or emergent decision-making to complete the entire process.  Or saying this another way, workflows have some tasks that are computable and others that are not computable.

Excessive automation is a mistake.  Elon Musk learned this the hard way, admitting, "Yes, excessive automation at Tesla was a mistake. To be precise, my mistake. Humans are underrated.

Automating bad processes is also a mistake.  Before automation should be attempted, processes and workflows need to be dialed in.

Attempting to automate a process that you don't understand will not work. Important subtleties and nuances will bring you to your knees.

Misfit tools also cause problems.  Automation is not about technical tooling, it is about having the right skills and experience; it is about talent.

Additional Information:

Comments

Popular posts from this blog

Big Idea for 2025: Semantic Accounting and Audit Working Papers

Microsoft CEO: "AI Agents will Replace All Software"

Professional Study Group for Digital Financial Reporting