In this week’s In-Ear Insights, Katie and Chris walk through the software development life cycle – the SDLC – and how we can apply it to marketing operations. From Data Studio dashboards to Google Ads to SEO, the overall process behind the SDLC applies well to any kind of marketing operations that require planning. Tune in to learn more!

[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're talking about the software development lifecycle, the SDLC.

And when you hear that phrase, one of the things that may spring to mind immediately is, you know, coders hacking away at at 1000s of lines of code.

And, you know, drinking Red Bull.

And in marketing, were probably like, well, how is this relevant to me, because I'm not doing development of software.

And yet, I would argue every single time that you make a dashboard saying Google Data Studio, or you make a report in your the social media marketing software of your choice, you are, in essence, creating software for somebody else use you may not be writing code.

But every time you're assembling bits and bytes of of technology for somebody else to use.

You are doing software development.

So Katie, you manage teams of developers, you've managed software development life cycles, can you walk us through the general process, and then how we should be thinking about it in terms of marketing?

Well, and that's just that the SDLC, or the software development lifecycle is just a process.

And a process is something that you can adapt to any team, any industry.

And that's the way I've always looked at things like the project lifecycle, the product lifecycle, the software development lifecycle.

At the end of the day, they're all roughly the same idea, which is you start with the why, what are you doing? Why are you doing this? Your business requirements? What's your purpose? You know, depending on what you're doing, you might need a set of data requirements or technical requirements.

And that's generally one of the differences with the software development lifecycle.

So you do your business requirements, what is the business need, then you do your data and technical requirements, what does the development team need, then you have, you might have a design phase, depending on what the thing is meant to be.

And if not, then you might move on to your development phase, which is where you start doing, you know, your proof of concept, you do your information architecture, you build your databases, you're basically setting up the foundation based on the previous set