Grant Harvey

Or you can train a system to do that.

You've got to know what the hell Dave's team does.

That's right.

You've got to understand what your outputs are, what your inputs are.

You've got to understand your process.

That doesn't necessarily mean mathing out your current process, because another big problem is people are like, oh yeah, my process runs like this, AI-ify it.

Imagine if you'd said to someone in 1900, like, right, I want the best and fastest form of land transport we can get.

They'd be like, here's a really fast horse.

We'll make it faster.

Like the motor car is a different paradigm.

In a similar way, your process might be some Frankenstein's monster of bolt-ons and other things.

And actually you've got to break it down to what's the desired outcome?

What are the inputs I need?

Then you can actually reimagine it from the ground up and have it ready to be improved.

Like, so that's a couple of them.

Like, if the data's a mess, forget about going any further.

If you just don't understand your process, you may need to break it down to an outcomes basis.

And then lastly, like, if someone's like, oh, I want this task to be automated, like, okay, here's an example of the task.

Like, tell me why it was a good task.

If they're like, because I like it.