Skip to content
NEW: Martech, explained →

Martech, explained · Working in martech · 1:41

Martech skills: what AI won't fix

AI takes over the clicking. Three skills stay with people: saying what you want, judging what comes back, getting people to agree

The short answer

AI is taking over the clicking: building the segment, the journey, the report. It does not take over the work around the clicking, which comes down to three skills: saying what you want, judging what comes back, and getting people to agree. Buying another tool to cover a missing skill is working around the problem, not solving it.

Questions this answers

What does AI take over in martech?

The clicking: building the segment, the journey, the report. What it does not take over is the work around the clicking, which comes down to three skills most teams have had little reason to practice.

What is the first skill, saying what you want?

Writing a goal the software can act on, with limits, clear enough that someone else could check it. Most teams have had little reason to practice that: the tool used to walk them through it, step by step.

Why is judging what comes back a skill?

Because software sounds just as sure when it is wrong. What comes back can be good, off-brand, or wrong in a way that is easy to miss, and every one arrives looking ready. Telling the two apart is a skill, not a setting.

Why does getting people to agree matter?

The data you need often sits with another team. Reaching it takes trust and a shared goal, and no connector buys you those.

Why doesn't buying another tool fix a missing skill?

It feels like progress, but it is working around the problem instead of solving it. The tool in the meeting did what it was told; nobody had agreed on what to tell it, and the next tool will be told the same thing.

Embed this film

Paste this where the film should play. It links back here.

Transcript

Every chapter as text. Click a time to play the film from there.

0:00 The segment was wrong

The new AI tool will fix that.

Someone says it in the meeting about a campaign that went to the wrong segment.

The segment was built exactly as asked. Nobody had agreed on what was asked.

AI is taking over the clicking: building the segment, the journey, the report.

What it doesn't take over is the work around the clicking. That comes down to three skills.

0:28 Saying what you want

First, saying what you want. A goal the software can act on, with limits, clear enough that someone else could check it.

Most teams have had little reason to practice that. The tool used to walk them through it.

0:43 Judging what comes back

Second, judging what comes back. Is it good, off-brand, or wrong in a way that's easy to miss?

Software sounds just as sure when it's wrong. Telling the two apart is a skill, not a setting.

0:58 Getting people to agree

Third, getting people to agree. The data you need often sits with another team.

Reaching it takes trust and a shared goal. No connector buys you those.

When those skills are missing, the usual move is to buy another tool to bridge the gap.

It feels like progress. It's working around the problem instead of solving it.

1:22 The problem wasn't the tool

Back to that meeting, where everyone is waiting for a better tool.

The problem wasn't the tool. It did what it was told, and nobody had agreed on what to tell it.

Learn more at Martech Stack Builder, or build your own.