The work changed, but the job title didn’t.
In many organizations, AI has already merged two or three roles into one. The title has not caught up. Neither has the JD, the comp band, or the headcount plan.
In a lot of operations, the most senior person on a team is now doing the work of what used to be two or three people, because AI tooling absorbed the lower-leverage half of those roles. The work has merged. The title has not. The job description still describes the role as it was three years ago. The comp band has not moved.
This is role drift, and it is well underway. Most organizations have not measured it yet.
What role drift looks like on the ground
A coordinator who is now operating a small AI workflow that produces what an analyst used to produce. An analyst whose deliverables have shifted from research-heavy outputs to judgment-heavy ones, because the research half is now automated. A manager whose span of control widened quietly because the team can move more work per head than the plan assumed.
In each case the work changed shape. In each case the title, the JD, and usually the comp band did not. The person is doing different work for the same money under the wrong label.
Why this matters beyond fairness
Three downstream effects, in our experience. The first: planning gets harder because the org chart no longer describes the work. The second: retention risk rises, because the person doing the merged role can read the market and knows what their actual work is worth. The third: hiring breaks, because new headcount is requested against the old JD and arrives unprepared for the actual shape of the role.
All three are quiet leaks. Together they are loud.
“If your most capable person is doing two jobs under one title, you are not retaining them — you are renting their patience.”
— Field note, workforce sprint
Three signals to look for.
The merged role
Look for the person on the team whose actual day no longer matches the JD. They are usually senior, often quiet, and they are carrying the merger.
The widened span
Look for the manager whose team produces more than the headcount model predicts. The model is wrong, not the team.
The hiring miss
Look for the role you have hired into twice and watched both new hires struggle. The JD is describing a role that no longer exists.
What to do, before retention or comp surprises you
Map the work as it is now, role by role. Compare it to the JD. Where the work has merged, re-shape the role on paper before the market re-shapes it for you. Re-band where the comp no longer matches the actual scope. Re-write the hiring spec before you open another req.
This is unglamorous, tactical work. It is also the work that decides whether your AI adoption shows up as a planning advantage or as a quiet attrition story.
Keep reading.
Stop chasing credentials without a map.
Credentials are not a career. A map is. Without one, more certificates just produce more overqualified people in misaligned roles.
AI is the last decision, not the first one.
AI is the highest-leverage decision in the sequence — which is exactly why it cannot be the first one.
AI that matches how your business actually operates.
The engagement that audits current AI usage, builds a prompt architecture mapped to real workflows, and hands you a reusable library.
If the work in your operation has merged and the org chart has not, the conversation worth having is about role design, not headcount.
Thirty minutes with a Sustineri principal. You leave with the right starting point — whether or not you engage us.
