|||
To automate a process is to codify it.
You’re not writing it in stone stone, but you are writing it.
A little elbow grease in the beginning is great to figure out what works: you’re experimenting, iterating, trial-and-erroring. And that’s part of the process of figuring out your process.
Then, when you’re already doing things repeatedly — and if it’s repeatable, it’s automatable — it’s a good time to introduce automations so that things can continue to happen consistently, even if you’re not there. You can get sick, take a day off, or be forgetful, and know that things are still taken care of.
True, it takes time and effort to set up and un-set-up automations. But how much effort? Well: effort (and therefore ease) is relative. So if setting up automations (and taking them down and changing them in case you need to iterate) is easier than doing the task, then… why not?
Or as a friend put it: when you’d rather drink tea than copy-paste.
