A skills-based organisation stops pretending titles explain how work gets done. They don’t. What matters is what people can actually do on a given day.
In practice, this means you stop staffing projects based on who sits in which box.
You look at the work first, break it into capabilities, and then pull in people who can execute. Titles still exist, mostly for payroll, hiring, and external clarity, but they’re not driving decisions anymore.
When this shift clicks, a few things happen fast. Silos weaken. People move more freely. And you start seeing skills that were always there but never used.
That’s when engagement starts to change. Not because of a programme. Because people finally get to do the work they’re actually good at.
The Current Landscape Of Job Titles
Most companies still run on titles because they make things easy to organise. They define pay, reporting lines, and hiring criteria.
They also limit how work evolves. That’s becoming more visible as work itself starts to shift, especially with AI changing how tasks are handled and shared.
You see it when priorities shift, but job descriptions don’t. Someone could solve a problem, but they don’t step in because it isn’t part of their role. Or worse, they’re not even asked.
Wade O’Shea, Founder of BusCharter.com.au, runs a business where coordination across operations, logistics, and customer service only works when people step outside rigid roles.
He says, “We used to rely heavily on defined roles, and it slowed things down more than we expected. The same issue would bounce between teams because no one owned it end to end.
Once we started focusing on who could actually solve the problem, not whose job it was, things moved faster. People stepped in where they were useful, not where they were assigned.”
When people are boxed into roles, engagement drops because they’re not using what they’re actually capable of. Only 23% of employees globally are engaged, according to Gallup.
Closer to the work itself, skills go underused. The CIPD’s Good Work Index keeps pointing to the same problem: people aren’t getting to apply or develop what they’re capable of.
Titles create clean org charts. They don’t create adaptable teams.
Why Skills Over Job Titles?
Work is moving faster than role definitions can keep up.
AI is speeding that up. Work that used to sit cleanly inside one role is now split across systems and people, making fixed role boundaries harder to maintain.
You don’t need a report to see it. Look at any team that’s scaling or dealing with new tools. The work changes every few months. The titles don’t.
That gap is where things break.
Bryan Henry, President of PeterMD, works in a model where patient experience depends on multiple capabilities coming together smoothly, not just defined roles.
He explains, “What we’ve seen is that patients don’t experience our org chart, they experience the outcome. If teams stay locked in their roles, that experience breaks down. When we started looking at workflows based on capabilities instead, medical, support, operations, everything became more connected. That’s when performance improved.”
There’s data behind it, too. Skill sets for jobs have already shifted by about 25% since 2015, and that number could hit 65% by 2030. At the same time, 44% of workers’ skills are expected to be disrupted within the next five years.
Static roles can’t keep pace with that.
As work becomes more distributed, what stands out is how people apply judgement and combine skills. That doesn’t map neatly to a title.
Eric Yohay, CEO and Founder of Outbound Consulting, spends most of his time fixing execution gaps where work gets delayed because ownership is unclear.
He says, “A lot of inefficiency comes from people waiting for the ‘right owner’ instead of solving the problem. In role-based setups, that’s normal. In skill-based setups, it disappears. The moment you define work by what needs to get done instead of who should do it, execution speeds up without adding more people.”
A skills-based setup closes the gap, enough to matter.
- Someone learns something new → they use it immediately.
- A project needs a mix of capabilities → the team forms around that, not departments.
Gavin Yi, CEO & Founder of Yijin Solution, works in manufacturing environments where execution depends on how quickly teams can adapt to changing requirements, not just follow predefined roles.
He says, “In manufacturing, the work rarely follows clean boundaries. One issue can involve design, production, and quality at the same time. If people stay within their roles, resolution slows down. When teams focus on what they can contribute instead of what they’re supposed to do, problems get solved faster, and coordination improves.”
Internal moves stop being “big decisions” and start being normal.
It also changes who gets opportunities. When you focus on skills, not pedigree or titles, you naturally widen the pool of people who can step in and contribute.
That part matters more than most companies admit.
How Does This Impact Employee Engagement?
Engagement improves when people feel useful. That usually comes down to three things:
- They’re using their strengths
- They can see progress
- They’re part of work that’s actually moving
Skills-based setups make all three easier.
That shift becomes clearer as work is distributed differently, especially as AI takes on parts of the workflow. When roles are less rigid, people step in based on what they can contribute, not where they sit.
You see it in how teams form. People volunteer for work outside their usual scope because they know they can contribute something specific. Not because they’re told to.
You see it most clearly in environments where work doesn’t follow clean boundaries.
Nick Wiese, Regional Vice President at Priority One Heating & Air Conditioning, works in a service business where real-world problems don’t follow org charts.
He says, “On paper, roles look clean. In reality, customer issues cut across everything—sales, service, and scheduling. If teams stick strictly to their roles, things fall through. The teams that perform best are the ones where people step in based on what they can handle, not what their title says.”
Instead of waiting to be assigned work, people start looking for where they can add value. Cross-functional work stops feeling forced. It becomes the default.
And for individuals, the change is even more direct.
Someone who’s been “just a developer” suddenly gets pulled into product decisions because they have UX instincts. Someone in ops starts shaping strategy because they understand the data better than anyone else.
Nothing about them changed. The system did, and that’s what unlocks engagement.
How Do You Implement Strategies For Skills-Based Structures?
This is where most companies overcomplicate things.
You don’t need a full transformation plan to start. You need something that works in one part of the business.
Start with visibility
Map what people can actually do, not just their technical skills, but how they work, how they lead, how they solve problems. The first pass will be messy. That’s fine. You refine it later.
Fix the language
If one team’s “data analysis” means dashboards and another means modelling, you’ll run into problems quickly. Align on what skills actually mean in your context. ESCO is a useful reference point if you need a starting structure.
Pick your starting point carefully
Don’t force this into rigid departments. Start where work is already fluid, projects, cross-functional initiatives, anything that doesn’t sit neatly in one team.
Learning needs to follow naturally from there. Because the work itself is shifting, skills only stick when they’re applied quickly in real situations.
Sixin Zhou, Marketing Manager at LDShop, manages teams where growth depends on how quickly people can apply new skills, not just learn them.
He explains, “We noticed that learning only mattered when it translated into actual work quickly. If someone picked up a new capability but had no way to use it, it faded. When we started aligning projects around skills, people could apply what they learned almost immediately. That changed how engaged they were with both learning and execution.”
If that loop isn’t tight, the model falls apart.
What Challenges Will You Run Into?
Some people are attached to titles. They signal progress, status, and identity. Remove that without replacing it properly, and you create uncertainty.
So you don’t remove structure, you change what drives it. Make progression visible through skills. Show how pay and growth still work.
Assessment gets tricky, too.
If you rely only on self-reported skills, the data will be unreliable. You need a mix: real work, peer input, and occasionally practical validation.
Managers need the biggest adjustment.
Most are used to thinking in roles and headcount. Now they have to define work in terms of outcomes and capabilities. That’s not a small shift.
Then there’s compliance and pay structures. Titles still matter externally. Keep them where needed. Just don’t let them dictate how work is assigned internally.
And don’t wait for perfect tooling.
A basic skills map and a simple way to match people to work is enough to start. Waiting for a full platform usually delays this by a year.
Looking Ahead
This is where things are already heading.
AI is making work less predictable at the edges. It doesn’t remove the need for roles, but it does make static role definitions harder to rely on. As tasks, tools, and expectations keep shifting, organisations need people who can apply skills in different contexts, not just stay inside a fixed remit.
That is part of why skills-based ways of working are gaining ground. They give organisations more flexibility, and they give people more room to use capabilities that might otherwise sit unused.
What matters is whether new skills get used straight away. In some teams, people learn something new, and it sits unused. In others, they apply it to the next project, and that’s where you see the difference.
At the same time, the pressure to reskill isn’t slowing down. Continuous learning isn’t optional anymore.
The companies that connect learning directly to real work will move faster. And their people will feel it.
Making The Shift
You have to match work with what people can actually do, and what they’re ready to learn next.
If you want to test it, don’t start with policy. Start with one project. Map the skills. Build the team around those. Let the results speak.
That’s usually enough to get the rest of the organisation’s attention.
If you’re trying to improve engagement and want practical, evidence-backed ways to do it, it’s worth exploring what Engage for Success is doing. We’ve built a large body of research, case studies, and real-world frameworks around what actually drives engagement beyond surface-level initiatives.
Author: David Abraham – Programme Manager, Human Rights and Criminal Justice, CELSIR
Photo credit: StockCake
