The Death of Roles (And Why We Hold On to Them Anyway)
In most organisations, one question defines everything:
“What is your role?”
It determines:
- what you work on
- what you’re responsible for
- how you’re evaluated
- how others interact with you
Roles create structure.
They make organisations understandable.
They give people a place.
Why Roles Ever Made Sense
Roles were never arbitrary.
They emerged because work needed to be:
- divided
- assigned
- coordinated
If work is complex and slow, you need:
- specialists
- clear ownership
- defined responsibilities
That’s how we got:
- developers
- testers
- product owners
- project managers
- consultants
Each role bundles a set of tasks.
And for a long time, that worked.
AI Starts to Unbundle the Role
In the previous post, we looked at how work is decomposing.
This has a direct consequence:
If tasks disappear or become trivial, the role that bundles them starts to dissolve.
Take a typical role.
A Product Owner, for example:
- writes user stories
- prioritises backlog
- aligns stakeholders
- defines requirements
AI can already:
- generate structured user stories
- summarise stakeholder input
- suggest priorities based on data
- draft requirement documents
Not perfectly. But increasingly well.
Now the uncomfortable question:
If most tasks of a role can be supported—or executed—by AI… what remains of the role?
From Roles to Capabilities
This is the shift:
Roles are bundles of tasks.
AI breaks those bundles apart.
What remains are capabilities.
Instead of:
- “I am a Product Owner”
It becomes:
- “I can frame problems”
- “I can make trade-offs”
- “I can align people”
These are not roles.
They are human strengths or skills.
Why We Resist Letting Go
If this were purely rational, roles would already be fading.
They’re not.
Because roles are not just operational constructs.
They are psychological anchors.
Roles provide:
- identity (“this is who I am”)
- security (“this is my place”)
- recognition (“this is my value”)
Removing roles doesn’t just change work.
It challenges how people define themselves.
The Hidden Fear
When roles start to blur, a deeper question appears:
“If I’m not my role… what am I?”
That’s not a process question.
That’s an identity question.
And organisations are not designed to handle that.
So instead, they:
- defend roles
- refine role descriptions
- create new titles
Not because it’s effective.
But because it feels safer.
The Organisational Reaction
You can already see this happening.
Instead of removing roles, organisations:
- add prefixes (“AI-enabled Product Owner”)
- create hybrid roles (“Tech Product Manager”)
- redefine responsibilities
All attempts to preserve structure.
But underneath:
The boundaries are already breaking.
Because capabilities don’t follow org charts.
They move. They combine. They appear where needed.
The Real Shift
This is not about eliminating roles overnight.
It’s about a gradual shift from:
- role-based thinking → “What is my job?”
to - capability-based thinking → “What value can I create here?”
That shift is subtle.
But it changes everything.
Because it:
- increases flexibility
- reduces dependency on structure
- exposes gaps in real capability
What This Means for You
If roles become less stable, then your leverage changes.
Not your title.
Not your position.
But your capabilities.
- Can you think clearly?
- Can you frame problems?
- Can you connect people?
- Can you make decisions under uncertainty?
These don’t disappear. They become more important.
What Organisations Will Struggle With
Most systems are still built around roles:
- hiring
- performance management
- career paths
- compensation
If roles weaken, all of these become unstable.
And that creates friction.
Because while reality shifts toward capabilities,
systems still reward roles.
Closing Thought
Roles made work manageable.
But they also made people predictable.
AI challenges both.
Not by removing people.
But by removing the need for rigid role boundaries.
The question is no longer “What is your role?”
It’s “What can you actually contribute?”