The person may need replacing. Their old job description probably doesn’t.
When someone leaves, reopening their old brief feels like the fastest route back to full capacity. But automation, changing client expectations, regional team structures and commercial priorities may have changed the job underneath it. Before you hire like-for-like, use the vacancy to work out what the role should actually own in 2027.
Someone resigns.
The team is stretched.
Clients still need servicing.
Work needs redistributing.
So somebody finds the last job description, changes the date and sends it to recruitment.
It feels efficient.
It can also be one of the easiest ways to hire for a version of the business that no longer exists.
Because the person may have been hired two, three or five years ago.
Since then, reporting may have become automated.
Platforms may be doing more optimisation.
Client expectations may have moved.
Another regional team may have taken on part of the workload.
The role may have quietly accumulated responsibilities nobody ever formally added.
And some of the work that once justified the position may no longer need a person doing it at all.
That doesn't necessarily mean removing the role.
It means the vacancy is a useful moment to redesign it.
Job descriptions are struggling to keep up with the work
This isn't unique to AdTech.
HRCI's November 2026 research argues that AI is changing work primarily by reshaping tasks inside jobs rather than simply eliminating whole occupations. Its recommendation is straightforward: define the purpose and outcomes of the role first, break the work into tasks, decide what technology should support or automate, then update the job description accordingly.
PwC makes a related point: job architecture has traditionally been built around inputs — tools, skills and years of experience — when businesses increasingly need roles built around outcomes and accountability.
That matters enormously in AdTech and performance marketing.
Because a title can stay exactly the same while the job underneath it changes completely.
Take a programmatic role
The old brief might include:
Campaign setup.
Pacing.
Optimisation.
Reporting.
Troubleshooting.
Client updates.
All perfectly reasonable.
But what does the team actually need now?
Perhaps setup is increasingly automated.
Reporting is generated faster.
Another team handles routine trafficking.
The client now expects much stronger strategic advice.
The business needs somebody who can identify revenue risk.
And the trader is increasingly expected to judge automated recommendations rather than manually make every adjustment.
If you simply reopen the old brief, you'll hire someone to do yesterday's workload.
Then six months later, wonder why the role doesn't quite fit.
Start with the work, not the title
Before asking:
“Who should replace them?”
Ask:
“What actually needs replacing?”
There are five useful questions.
1. What still requires human judgement?
Start with the responsibilities where the value is not simply completing the task.
What needs somebody to:
interpret;
challenge;
prioritise;
negotiate;
recommend;
make a trade-off;
understand the client;
or take accountability for a decision?
For a trader, that might be deciding whether an automated optimisation genuinely supports the campaign objective.
For an Account Manager, it might be interpreting performance and deciding what the client needs to hear.
For a performance marketer, it could be determining whether stronger headline ROAS is actually producing better commercial outcomes.
Those are the responsibilities worth protecting — and possibly expanding.
Don't ask only:
“What does this person do?”
Ask:
“Where does this person make the work better because they are thinking?”
2. What can now be automated?
Then be ruthless about the repetitive work.
Not because automation is automatically better.
Because there is little value in hiring someone specifically to spend hours on a process the business already knows how to reduce.
Look at:
routine reporting;
first-draft analysis;
basic campaign setup;
standard summaries;
data aggregation;
repetitive QA;
administrative coordination;
or parts of optimisation.
Then ask two things:
Can technology reliably do this?
And:
Does a person still need to check, interpret or approve the result?
That distinction matters.
Automating the first draft does not necessarily remove the responsibility.
It may simply move the human contribution later in the workflow.
HRCI's recent role-redesign guidance recommends exactly this task-level analysis: work out what technology can support, what it can automate and what should remain with people.
3. What belongs somewhere else?
Not every responsibility needs to disappear.
Some may simply belong with another team.
Perhaps a regional trading hub now owns campaign execution.
Maybe reporting has been centralised.
Technical implementation sits with specialists.
Creative adaptation has moved into a regional capability centre.
Or a shared operations team can handle administrative work that currently sits inside an expensive client-facing role.
This is especially relevant as Southeast Asian teams become more distributed.
The question is not:
“What can we offshore?”
It's:
“Where can this work be done best, with clear ownership?”
If a Singapore Account Director spends a meaningful part of the week preparing reports that a regional team could produce just as well, don't automatically replace the same workload.
Redesign the workload.
4. What has become more commercially important?
Roles rarely lose responsibilities without gaining others.
This is where many replacement briefs go wrong.
Businesses automate or redistribute part of the old workload — but never formally decide what the freed capacity should be used for.
Look at what has become more valuable since the previous person joined.
Client advice?
Account growth?
Strategic planning?
Cross-market coordination?
Commercial ownership?
Measurement?
AI-assisted workflow management?
Partner relationships?
Team leadership?
Perhaps the new hire should spend less time producing information and more time deciding what the business should do with it.
That is a materially different role, even if the title stays the same.
5. What outcome should the new hire own?
This is the question that forces everything else into focus.
Instead of beginning with a list of tasks, complete this sentence:
Six months after this person joins, we should be able to say that…
Perhaps:
client retention has strengthened;
campaign quality is more consistent;
the trading team needs fewer escalations;
the regional hub owns more work independently;
the account portfolio is growing;
senior people spend less time on execution;
reporting produces clearer decisions;
or campaign issues are caught earlier.
Now you have something to hire against.
Because an outcome tells you what success looks like.
A task only tells you what somebody will be busy doing.
Don't confuse inherited work with essential work
When someone has been in a role for several years, their workload often becomes a collection of history.
They picked up reporting because somebody left.
They became the owner of a spreadsheet because they happened to know how it worked.
They started joining a meeting that no longer really needs them.
They became the escalation point for something that should sit elsewhere.
Then they leave.
And every one of those responsibilities gets copied into the replacement brief as though it were essential.
It isn't always.
The exit gives you permission to ask:
Why does this person do this?
If the only answer is:
“Because the last person did,”
keep digging.
Build the replacement brief in three columns
A simple way to audit the role is to separate the work into:
Keep
Work that still matters and still belongs in the role.
Especially responsibilities involving judgement, ownership, client value or specialist expertise.
Change
Work that still needs doing, but should happen differently.
Maybe AI creates the first draft.
Maybe another team supports it.
Maybe the new hire approves rather than produces.
Maybe a junior person executes while this role owns the decision.
Remove
Work that no longer contributes enough value to justify keeping it.
Old reports nobody uses.
Duplicated processes.
Administrative work created by systems that no longer exist.
Tasks that have already effectively moved elsewhere.
You might discover the replacement role becomes smaller.
You may also discover it becomes more senior.
Both are useful outcomes.
Then check whether the title still fits
If you materially redesign the responsibilities, don't assume the old title remains correct.
Perhaps an execution-heavy role now carries substantial client ownership.
Perhaps an Account Manager has become closer to a commercial lead.
Perhaps a trader now spends more time on strategy, diagnosis and stakeholder advice.
Or perhaps what was previously one senior role can now be divided between specialist execution and regional ownership.
The title should help the right candidates recognise themselves.
If the work changes and the title doesn't, you can end up attracting the people suited to the old job.
Check the salary too
This is where redesign becomes commercially useful.
If you've removed large amounts of repetitive execution, that doesn't automatically mean the role should be cheaper.
Perhaps the responsibilities that remain require more judgement.
More commercial accountability.
More client confidence.
More leadership.
Equally, if much of the senior workload has moved elsewhere, you may no longer need to replace at the same level.
Don't benchmark the salary against the person who left.
Benchmark it against the job you have just redesigned.
Protect the progression path
There is one final question worth asking before publishing the new brief:
What does this role become next?
If you remove all the foundational work, are there still ways for someone to learn?
If you move all strategic responsibility into another market, can people in this team still progress?
If technology takes over routine execution, how will someone develop the judgement required for more senior work?
This is where role redesign connects to talent planning.
Gartner has warned that organisations automating early-career work without redesigning development pathways risk damaging their future talent pipeline.
So don't optimise the role so aggressively that you remove the route into the next one.
A 30-minute replacement audit
Before you reopen an old job description, get the hiring manager and recruiter together and answer:
What still requires human judgement?
Highlight it.
What can now be automated?
Remove the manual work where appropriate, but keep the necessary review and accountability.
What should move to another team or regional hub?
Don't pay someone to own work that now belongs somewhere else.
Which responsibilities have become more commercially important?
Make them visible.
What outcomes should the new hire own?
Build the brief around them.
Then — and only then — start writing the job description.
The vacancy is an opportunity
Replacing someone quickly can feel like the safest decision.
But a vacancy is one of the few moments when a business can rethink a role without disrupting the person already doing it.
Use it.
You don't need to reinvent every position every time somebody resigns.
But you should be able to explain why each major responsibility is still there.
The objective isn't to eliminate the job.
It's to make sure you're hiring somebody for the work your business needs next, rather than a collection of tasks left behind by the person before them.
Sources
HRCI, Redesigning Work: How AI Is Changing Jobs and How HR Can Lead, November 2026.
PwC, Role convergence and AI workforce redesign, 2026.
Gartner, AI Automation Is Reducing Some Entry-Level Hiring at Nearly One-Quarter of Organizations, July 2026.
Replacing someone in 2027?
Send ugp the existing brief before you put it back into the market.
We'll help you identify what should stay, what should change and what may no longer need to be there.


