Attitude Isn't the Opposite of Skills. It's Part of Them.

"You don't hire for skills, you hire for attitude".

Simon Sinek wrote that in Start with Why, and it gets quoted in every second hiring discussion.

I ran into it again in a USG Professionals white paper on skills-based recruitment. The paper argues that companies should hire for capability rather than for the job as written. I agree, and it is well worth the read. But Sinek's line does something different, and it deserves a closer look.

Half of it is right: some things are hard to teach, so hire for those and build the rest. The problem is what the line becomes once it is quoted. It turns into permission to point at "attitude" and skip the harder question. The harder question is the only one that matters:

Which skills does this job require? At what level? What skills are needed now, and as AI reshapes the work? And can you realistically get this person to the new skill requirements?

Attitude and skills are not opposites.

Attitude, drive, and how someone handles pressure are traits.
And traits are one of the building blocks of a skill profile, alongside tasks, tools, knowledge, and languages.

So the decision was never to either “hire for attitude” OR “hire for skills”, because attitude IS part of a skill. It resides in it.

And if attitude resides in a skill profile, then the skill profile is what employers and hiring managers need to get right.

Build a Skills Framework

Skills are the building blocks of an employment relationship. Therefore, it’s important to invest in a skills framework and the taxonomies behind it. Here’s why:

1. A skills framework and taxonomy create a shared vocabulary between employer and employee for what they consider as valuable work.
2. Every hiring and career progression decision involves judgement. A skills framework makes judgement calls explicit, visible and transparent. Even though a framework will never be completely unbiased, a skills framework reduces bias and makes choices defensible. Additionally, because of the transparency other people can challenge it.
3. A skills framework is a great basis for skill-based job profiles. Roles and responsibilities can still be described with free text, but they should align with the skills profile, not the other way around.

At the end of the day, employers do not reward hours. They reward skills that deliver results. An employee that cannot do the work, and shows no sign of progress is a costly investment to make.

People deserve an honest mirror

A skill-based framework and job profiles are not only a tool helpful for employers, but are also beneficial to employees. Employees deserve a view on their own personal skills profile: what they can do, and at what level. But they also deserve to know how they fit their current job, how they map to future ones, and where new technologies will strengthen their skills and might make other skills redundant.

To have such a conversation around future skills with an employee is beneficial for both parties and is far more valuable than "You have a great attitude. We'll figure out the rest."

What we believe in at talentguide

We put skills-based recruitment, development, workforce planning, and internal mobility at the centre of how work gets organised and planned. Skills are made visible, assessed openly, and developed deliberately, with attitude treated as part of the picture rather than as a reason to skip the rest.

If you are working out how to define and validate skills rather than just talk about them, I'd be glad to talk it through