Competent is not the same as certified

What a skills card tells you, and what it does not

By The Human Union team · 27 Oct 2026 · 5 min read

A certificate says that on one day, in one room, a person answered enough questions. It does not say what they do at four o'clock on a Friday with a customer at the door and the next job already late. Both matter. Only one of them is competence.

Every manager who has worked on the tools knows this. The engineer with the longest list of cards is not always the one you send to the awkward job. The one you send is the one whose work holds. You know that from years of watching, and you would struggle to write it down.

What competence actually looks like

It is not knowledge, though it needs knowledge. It is judgement under the conditions of the real job: short on time, short on parts, with half the information. Three things show it:

  • The work holds. The fix does not come back. The install passes first time. The line runs after the changeover without someone standing next to it.
  • They know what they do not know. The competent person stops and checks, rings someone, or says "not sure, let me look" instead of guessing. The confident novice guesses.
  • They can explain the why. Not the procedure, the reason behind each step. That is what lets them handle the case the procedure did not cover.

None of those appear on a card.

What the card is good for

Cards are a floor, not a ceiling. They keep people safe and keep you legal, and a trade without them would be worse. The mistake is treating the floor as the measure. When a firm's only picture of its people is the certification matrix, it promotes, pays and allocates work on the thing that is easiest to count rather than the thing that matters.

How to see the rest

You cannot inspect your way to it. You see competence in the record of the work: callbacks by person, first-time pass rates, how often someone is called by colleagues for advice, what they say when asked to walk through a job they are proud of. The last one is the richest and the least used. Ask a good engineer how a job really went and you learn in ten minutes what a year of cards will not tell you.

Build that picture for your whole team and you have something no certificate gives you: who can actually do what, and who is ready for more.


If this is on your mind, we would like to hear how your team learns. Thirty minutes with our team, no slides.

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo