Why Your Marketing Automation Isn't Working (And What’s Getting in the Way)

Last week looked like a fairly standard mix of marketing work. I was setting up some marketing automation through automated workflows, running a CRM walkthrough, and working through a campaign that needed to be adjusted because the enquiries coming in were not turning into anything meaningful. On the surface, all of that sits under execution, and it is the kind of work most people expect to move quickly once the tools are in place.

However, the work kept slowing down, and not for the reasons you might expect. Because as soon as we start talking about platforms, the platforms usually get the blame when things take too long. But this time around, it was because the tasks were unclear. More specifically, it was because, in each case, we had to stop and work out what should actually be happening from the customer’s point of view before we could continue. And once that started happening, it became clear to everyone involved that the real work didn’t lie with tinkering about on the platform; it was in understanding how the journey should function in the first place.

A Pattern I Noticed Throughout the Week

When I started building the workflows, the assumption was that the structure would come together fairly quickly. You define the steps, set up the emails, and connect everything so that it runs automatically. But that only works if you know exactly why someone is entering that workflow and what that action represents. Saying that someone signed up or downloaded something is not enough, because that does not tell you what they need next or how they should be treated in the system.

So we had to pause and work through what those actions actually meant, how they were recorded, and what they signalled about the person on the other side. That thinking shaped the workflow far more than the tool itself ever could.

The same thing happened in the CRM session. The original request was to walk through how to use the system, and that usually means showing where things sit and how to move between them. But the conversation moved very quickly into how their process actually worked, because the system can only reflect what is already happening in the business.

We had to look at where bookings were being handled, how contacts were updated after meetings, and what needed to happen for the next step to be triggered. At one point, we realised that a follow-up sequence depended on someone manually updating a contact record after a meeting, and if that did not happen, the rest of the process would not continue. And that is not something a system can fix on its own, because it comes down to how the process is designed and whether it is consistently followed.

The campaign work followed a similar pattern, although it showed up differently. Leads were coming through, and that would normally be taken as a sign that things were working. But when we looked at what was happening after that, it became clear that the path from enquiry to outcome was not holding together.

The message in the ads was bringing people in, but it did not fully reflect what they needed at that point, and the form they landed on did not guide them in a way that made the next step obvious. The follow-up also did not carry that forward in a way that helped them move closer to a decision, so each part was doing its job in isolation, but the experience across them did not feel connected.

Identifying the Problem in Marketing Automation

What stood out across all of this is that the issue did not sit within any single element. It sat in how those elements related to each other and in how clearly the overall journey had been thought through before anything was built. It is very easy to approach this kind of work by focusing on the visible parts, because those are the things you can change quickly.

You can adjust a campaign, rewrite an email, or add more steps to a workflow, and sometimes that does make a difference, but only within the structure that already exists. The assumption that often sits underneath this is that improving individual components will improve the overall outcome, and that is not always the case. If the journey itself is not clearly defined, then each adjustment is working within something that is already misaligned.

Why Adding More Doesn’t Fix It

There is also a tendency to respond to this by adding more complexity, because it feels like a more advanced setup should produce better results. More workflows, more conditions, more detailed segmentation. But that only makes sense if the basic journey is already clear, and in many cases, it’s not.

So, adding more layers on top of something that has not been fully thought through tends to make it harder to see where the breakdown is actually happening, and it creates more points where things can stop working without being noticed.

What Changes When the Journey Is Thought Through Properly

What last week made very obvious is that the starting point for building any workflow, campaign, or CRM setup is not the tool itself, but the moment someone enters that journey and what that moment actually represents.

Before opening any platform, it helps to take one specific entry point and write it out in plain language. Not all entry points at once, just one. For example, someone downloading a resource or submitting a form. Then describe what has just happened from their point of view and why they chose to do it, because that decision spells out their intent, and that intent should shape everything that follows.

Once you know that, the next step is to decide what they need immediately after that interaction, and this is where most journeys start to get a bit vague. It is so easy to default to sending a generic follow-up or a sequence that has been used before, but that often ignores what the person is actually trying to do in that moment. If someone has just downloaded something to solve a specific problem, then the next interaction should help them make use of it or take a small step forward, rather than introducing something new or unrelated.

From there, you need to decide what they should be able to do next, i.e., what you want them to do with the information you gave them. And it is so easy to introduce friction here if you don’t consider this in context with their reason for entering the workflow. The action then tends to be either too big for where they are, or it is not defined at all, and in both cases, the journey tends to stall. If someone has taken an early step, asking them to commit to something significant can feel premature, and if they have already shown intent, sending them back into general content can slow things down unnecessarily. The next step needs to match the stage they are in; otherwise, the system starts working against the outcome rather than supporting it.

Have You Covered All Bases?

Only once those pieces are thought through does it make sense to move into the system, because at that point, the questions become practical. You know what should trigger the workflow because you understand what action matters, and you know which CRM fields need to be updated because you know what needs to be tracked. You also know how the next step should be activated, because that step has already been decided rather than guessed inside the tool.

This is also where gaps tend to show up early, and that is where a lot of value sits because if a workflow depends on a manual update that may not happen or if a trigger relies on data that is not consistently captured, you will see that before anything is built… saving you a lot of time, effort, and frustration because it gives you the chance to adjust the process itself, rather than trying to fix the symptoms later inside the platform.

So, if you’re feeling unsure, before changing campaigns, rewriting emails, or adding more steps into a workflow, it is worth taking one entry point and working through it properly from start to finish in plain language. Ask yourself, where did this person come from, what did they expect to happen, what did they receive, and what were they able to do next?