In this week’s In-Ear Insights, Katie and Chris walk through effective process development for marketing, especially marketing technology. Listen in as they work out the process for setting up a Twitter hashtag monitoring bot for Social Media Marketing World.

[podcastsponsor]

Watch the video here:

Can’t see anything? Watch it on YouTube here.

Listen to the audio here:

Download the MP3 audio here.

What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode.

In this week's In-Ear Insights, we are talking about process development, particularly when it comes to marketing, marketing automation and marketing technology.

So Katie, what is process development? It sounds just like I mean, the the, the adventurous coder and me sounds like it's overhead.

It's,

it isn't it isn't.

So process development is exactly what it sounds like it is the act of developing a process.

And so while you might think it's overhead, to me, it's repeatability and scalability.

And so, if you're not, and I'm looking at you specifically right now, Chris, if you're not documenting what you do, then you can never pass it off to someone else to do the way that you want it done.

So you will forever have to do the thing.

So that's not the only reason while you want to do process development.

But for you, specifically, I know that that hits home.

So that is the argument that I would give to you is you need to document the stuff that you don't want to do that so that somebody else can do it.

Okay.

What about things that I want to do that I don't trust other people to be able to do as well.

I think that still valid because I, you know, process development is if you break it down to its most basic idea, it's writing down the steps of how something gets done.

And so let's say you know, whether you want to do it yourself, or you want someone else to do it, is sort of irrelevant.

So you know, I brought that up, because I knew that that would be like, Oh, if I write it down, that I can pass off the stuff that I don't want to do.

But regardless of who's doing the thing.

The reason you want to write something down is so that you can find where things are broken, and efficiencies.

And so it's part of the QA process, it's part of requirements gathering.

But primarily, the function that it serves is so that somebody else can test it to validate the thing.

And so if you, Chris are not writing down how a set of code works, then someone who isn't you, who is likely me who doesn't fully understand code