
Processes are a lot more interesting than you’d first think. That isn’t some kind of joke — they’re interesting, I swear. But what is a process?
Although they’re defined as “a collection of interrelated work tasks initiated in response to an event that achieves a specific result”, there’s a bit of a backstory that helps us cut through the corporate tranquilizers and understand what a process is, and why processes matter.
First, a few examples of processes:
- Cleaning the store
- Finding an email address
- Deploying software
- Customer profiling
- Onboarding a new employee
- Planning a wedding
But why are those processes? Why aren’t they just jobs to be done? The point is that when you formalize a process, you think about the workflow with productivity in mind and it makes it easier to execute and optimize.

Creating workflows with
No process is perfect; there’s always room to improve. Unfortunately, many teams have no way to identify, test, and deploy the changes they make, meaning each tweak is a roll of the dice.



A recent Deloitte study found a mere 