'Soft skills' is the term most people reach for when they want to describe communication, collaboration, problem-solving, adaptability, and the rest of the non-technical capabilities that work depends on. It's been the default for decades, sitting comfortably in textbooks, job ads, training programs, and government strategy documents.
If you've used the term, you're in good company. We're not suggesting anyone has been getting it wrong, just that there are richer, more deliberate, more useful words available, and that swapping them in costs very little and tends to help a lot.
What 'soft' quietly implies
The trouble with 'soft' isn't that it's offensive, it's that it carries a quiet implication every time it's used. Soft sits opposite hard, so if technical skills are hard skills then by definition the others are soft, which lands somewhere between 'easier', 'less essential', and 'less measurable'. Most of those associations don't actually fit the skills they're being applied to, but the word does the work anyway, whether we mean it to or not.
The term probably stuck because most of these capabilities happen inside someone's head. You can see a weld and you can audit a spreadsheet, but you can't see analysis or judgement or empathy in the same way. Things that aren't visible tend to feel less concrete, less concrete drifts toward 'soft', and from there 'soft' tends to drift toward 'less serious', leaving workforce strategies treating the skills that actually carry every interaction at work as a kind of optional add-on.
The good news is the word isn't load-bearing. We can drop it and still talk about exactly the same capabilities, usually more clearly.
Better options
Here's what we use instead, and roughly when each one fits.
Human skills
This is our umbrella term. It covers everything a person uses to do work, the technical parts and the transferable parts together, since every job uses a mix of both. Communication is a human skill, but so is operating a CNC machine, welding, or reading a room.
'Human skills' is the right word when you want to talk about the whole picture, or when you specifically want to push back against the technical-versus-soft framing. It's also useful with mixed audiences (students, parents, employers, educators), since it doesn't assume anyone has already absorbed an existing framework.
Transferable skills
This is the right term when you want to highlight that a skill applies across contexts. The work a chef does to coordinate a kitchen during service is the same kind of coordination a project manager does on a build site, different domain but the same underlying capability, and 'transferable' names that abstraction.
It's particularly useful for career changers, students looking at multiple pathways, and anyone trying to articulate what they'd carry from one role into another.
Cognitive skills
This is the right term when you want to be specific about the kind of skill that happens inside someone's head, like analysing, synthesising, deciding, or planning. 'Cognitive' is honest about where the work is occurring without implying it's lesser, and it tends to be more precise than 'soft' because not everything that gets grouped under 'soft' is actually cognitive (relating to other people, for instance, is something quite different).
It's useful in education, training design, and anywhere someone is trying to be specific about what kind of mental work a task involves.
Core skills
This is the right term when you want to talk about capabilities that show up across nearly every job, the ones that aren't role-specific but are still pulling weight everywhere. It's a useful framing in workforce planning, where the question is often 'what do we need across the whole workforce, not just this one role?'
Two ways to use them
You can pick whichever option fits the moment. The first approach is to be specific: if you're talking about analysis, call it a cognitive skill; if you're talking about something that travels with the person across roles, call it transferable; if you're talking about something everyone needs, call it core. Each term is doing a particular job, and using them precisely tends to make the conversation clearer.
The second approach is to use 'human skills' as the umbrella and qualify when you need more detail. Phrases like 'human skills, particularly the cognitive ones' or 'human skills that are highly transferable' work well when you're explaining things to someone new and don't want to fragment the conversation into multiple categories before you've established what you're actually talking about.
Why we bother
Words shape how people treat the things underneath them. If we call a capability soft, that tends to be how it gets treated. If we call it human, it tends to get treated as human. If we call it cognitive, it tends to get treated as something a person actually does with their mind.
None of this is about scolding anyone. The term is everywhere because it's been the default for a long time, and we're suggesting better ones because they describe the work more accurately, and because the people doing the work, every one of us in nearly every job, deserve language that takes their skills seriously.