You probably need a Chief Automation Officer

You probably need a Chief Automation Officer

Insight from Steph Smith

There’s too much damn work to do, and most of it can be automated.

Unfortunately for us, automating work is also work.

As a COO with a thousand other responsibilities, you probably don’t want to spend another 10 hours/week messing around in Make or Zapier.

What’s the solution? Hire a CAO (Chief Automation Officer).

Imagine how much more efficiently your business would run if you had an experienced individual whose only job was taking the busy work off of everyone else’s plate.

That’s the role of the CAO:

• They interview (or shadow) your team to better understand their workflows

• They mercilessly root out the repetitive, busywork tasks that dominate so much of our teams’ days

• They build the automations, create documentation on how they’re set up (so others can diagnose any issues/breakage), rinse, and repeat

Now, this doesn’t have to be a C-level hire.

The CAO role can be an agency, a part-time contractor, or even an experienced VA.

The point is, if you want to actually implement some of the incredibly useful automations and practices that we’re going to be talking about in today’s edition, you should find someone to do it for you.

Delegation, remember?

Learn more: A conversation about why most companies needs a CAO