Kevin asks, "How can a marketing team with zero AI / predictive resources get started, today? Where should they begin?"
We follow the STEM business lifecycle: strategy, tactics, execution, measurement.
Can't see anything? Watch it on YouTube here.
Listen to the audio here:
Strategy: what problem are we trying to solve? Is AI and predictive modeling the right solution to solve that problem? (AAR)
Tactics: what choices will we make? This is based on budget and resources.
- Budget but no time? Hire either an agency or FTEs.
- Time but no budget? Train yourselves.
- Neither budget nor time? Pass on it for now and focus on generating revenue so that you have budget and time later.
Execution: based on build or buy, do the thing.
Measure: did you solve your problem?
Links to courses:
- Got a question for You Ask, I'll Answer? Submit it here!
- Subscribe to my weekly newsletter for more useful marketing tips.
- Find older episodes of You Ask, I Answer on my YouTube channel.
- Need help with your company's data and analytics? Let me know!
What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for watching the video.
In today's you ask I answer. Kevin asks, How can a marketing team with zero AI machine learning predictive resources Get started today? Where should they begin? Well, we begin by following the stem business lifecycle strategy. Stem stands for strategy, tactics, execution measurement strategy, what problem are we trying to solve? There are a lot of business problems where AI and predictive modeling and machine learning, probably not the right solution.
A problem is ripe for solving with AI, and predictive and machine learning. And all these advanced technologies. If it follows the AAR format? Do you need more acceleration mean you need to go faster? Do you need more accuracy? When your existing processes? are not generating accurate enough results? Or is the problem highly repetitious? If it's one of those three, it's a great candidate for AI and machine learning. If it's two of those three, it's a really great candidate. If it's all three, you probably should have done some automation of it already. So
that's the first part of the strategy is that is that a problem for which this is the the correct solution? Second, on tactics, what choices are we going to make? Now, this is not necessarily choices about specific technologies. So this is choices about from a business perspective, could you do you have the ability to solve the problem with AI and machine learning? And that comes down to two fundamental factors? Well, really three, but budget and time are the two fundamental factors. If you have budget and you have no time
or you have more budget than time, I should say,
hire, hire an agency, hire full time employees, hire consultants, hire whatever you need to do to build in that capability quickly, and, and start the execution of the problem solving. If you have time, but no budget, Train yourself, right, spend some time training, there is a great crash course in machine learning from Google requires knowledge of Python. So if you have not learned how to code in Python, I strongly recommend the book learn Python the hard way, it's hilarious, it's a really good read. And then
you go on to the machine learning Crash Course,
that combined will take you somewhere between six and 12 months. But if you have time and no money,
use that time wisely, build that capability in figure you're going to spend an hour a day for the next 12 months building up that capability. But once you do you that capability can't be taken away. It's not once you have the knowledge and the skills even if your your, you know, your development budget gets taken away, your knowledge doesn't go away. So my personal preference is even when there is budget to acquire knowledge. Because, again, knowledge is something that only decays from lack of use. But it's not like someone can just slash a budget and suddenly your capability goes away. If you have neither budget nor time
pass on AI and machine learning. For now, just give it a miss.
And the reason you should do that is that you need to focus on generating revenue so that you have budget and time later, right. Rip revenue fixes many walls. So that's sort of the tactical choice you have to make, what do you have more of and what are you willing to commit. And the other thing I would add is that if you if you don't have
if you don't have the right people in place, again, you're going to need to get time or money to fix that.
Then the third stage is, of course execution based on your choice of build or buy, do one of the above and then you measure did we solve the problem do we build a capability that solves the business problem at hand,
one of the greatest dangerous is that people will
jump into action technology and just start using it without that strategy. Without that clear business problem to solve. Now,
if you are an individual practitioner, and you are learning
AI, and machine learning, and you are tinkering around, that's a totally fine strategy, tinkering, experimenting, playing with stuff, breaking things completely appropriate for an individual practitioner for a business
not as good
it is contained within the r&d function within your business. Again, r&d is professional tinkering,
you don't want to do that production once you have something ready to go you roll it out and and it is a proven
repeatable scalable process
you know throwing out AI solutions just for the sake of using AI and not because it it's the best choice to solve a business problem is not the way to go at a business level
production again rd separate story so
that's how you get started
today. That's where you begin, either build or buy and there's always I in my opinion, and this is just one practitioners opinion, you should always have a component of build, even when you buy if you work with a vendor who is completely unwilling to share any knowledge or experience or source code or anything, then you've got a lousy vendor bears, every vendor is going to have their own secret sauce, but at the very least, they should be able to tell you what they're doing.
Maybe like, you don't need the exact recipe and down to the individual measurements. But someone's You better tell you whether you're getting a pizza or a souffle or a cupcake, right? Very different.
They're very different outcomes, and they're not even willing to tell you he adds a pizza
Ben, then they're not a great mentor.
So good question. Kevin.
Like I said, those two courses, learn Python, the hard way is a great one that will give you the knowledge of Python itself. And then
the machine learning Crash Course from Google. I'll put a link to both courses
in in the notes here.
Bear in mind that
is a great choice as a general purpose language. If you've never coded before, if you have coding experience in the past, particularly in monolithic languages like c++ and Java, you may be more comfortable with the statistical programming language are I personally am much more comfortable with our than I am with Python because I have a lot more gray hair and I've done a lot more that older style of coding Python is much more suited for people who have never voted before and
I don't want to get to speak quickly are is
not as friendly. So thanks for watching. As always, please subscribe to the YouTube channel and to the newsletter and we'll talk to you soon. Take care
if you want help with your company's data and analytics. Visit Trust Insights calm today and let us know how we can help you
You might also enjoy:
- You Ask, I Answer: Microsoft Clarity vs. Google Analytics?
- How To Start Your Public Speaking Career
- You Ask, I Answer: Quantifying Hallway Conversations?
- How to Set Your Public Speaking Fee
- How to Set Your Public Speaking Fee
Want to read more like this from Christopher Penn? Get updates here:
Get your copy of AI For Marketers