Stop Calling It Soft: The Case for Talking About Judgement at Work

Open almost any UK job advert for a junior-to-mid role and you will find the same paragraph near the bottom. Excellent communication skills. Strong stakeholder management. A team player with a positive attitude. Then, further up, the things the salary is actually attached to: SQL, ACCA, React, whatever the technical currency happens to be.

The division is not accidental. It is baked into the language. We call one set technical and the other soft, and the word soft does a job on everyone who uses it. It suggests pliability, nice-to-have, sprinkles on the cake. It suggests that these things cannot really be assessed, so nobody seriously tries.

For younger professionals, that framing is expensive.

What the label does to the person wearing it

Say “I'm working on my soft skills” in an appraisal and watch what happens. The manager nods, writes something vague about visibility, and moves to the budget conversation. Say it in a job interview and the panel hears either “I am pleasant” or “I am a bit awkward but trying”. Neither of those is a reason to hire you over the other candidate with an identical CV.

Meanwhile the actual thing you have been doing — deciding when to escalate, choosing which of two imperfect options to back, spotting that a client's silence meant trouble rather than satisfaction — has no name in the conversation. Unnamed work is hard to reward.

The description is wrong anyway

Think about what you actually did last quarter when a project wobbled. You noticed a pattern in the numbers before it became a problem. You worked out which of three stakeholders would block the fix and spoke to them first. You decided not to raise it formally because the timing would have made it worse. You then wrote a two-paragraph update that kept everyone calm without pretending the issue did not exist.

Call that soft skills if you like. It is actually reasoning under uncertainty, sequencing, political awareness and written clarity. Every one of those is a judgement call, and judgement is about the least soft thing there is.

Three buckets worth using instead

Judgement. How you weigh incomplete evidence and pick a course of action. Show it by describing the information you had, what you decided without it, and why.

Decision quality. The process, not the outcome. A good decision can end badly; a lazy one can get lucky. Employers who understand this will ask about the process, and you should be ready to give it to them.

Risk awareness. What you spotted early, what you escalated, and — just as important — what you deliberately did not escalate. Knowing when not to raise something is a leadership skill, not a personality quirk.

Rewriting three lines off a junior CV

Before: Strong communication skills. After: Wrote the monthly trading summary for a £40m account and presented it to the client's finance lead; cut a nine-slide standing agenda to three after they told us the detail was not being read.

Before: Good team player. After: Coordinated operations, finance and design through a supplier switch; flagged two risks early enough to protect the launch date.

Before: Works well under pressure. After: Took over a delayed reconciliation three weeks before year-end, prioritised the four accounts that mattered to the audit, and left the rest documented for January.

Notice that none of the second versions contains an adjective about you as a person. They contain decisions. That is the whole trick.

In appraisals, argue from evidence

UK review cycles reward people who turn up with a narrative, not a list. Keep a running note through the year of judgement calls: what was unclear, what you chose, what happened, what you would do differently. Four lines each, written the same week. By the time the form lands in your inbox you have twelve examples and no need to invent any.

When you write them up, resist the urge to claim a trait. “I am resilient” invites disagreement. “When the supplier missed the second deadline I moved the plan to a later date rather than push for a patch job, and told the client before they asked” invites a conversation about how you think.

One more thing, especially relevant if you work somewhere with a formal behaviours framework — the Civil Service's Success Profiles, a bank's competency matrix, an NHS trust's values grid. These documents already describe judgement in all but name. Use their vocabulary, not the generic one, and your evidence will land where the panel is actually scoring.

In interviews, talk in trade-offs

Competency-based questions reward structure. A working shape:

The situation was ambiguous. Here were the two options I could see. Here is what I weighed and what I did not know. Here is what I chose and why. Here is what it cost. Here is what I would do differently.

That last part does more good than any amount of confident self-description. Knowing where your own judgement runs out is how a 26-year-old sounds like someone who could be trusted with a bigger decision next year.

Do not overclaim

There is a failure mode on the other side. Judgement claims need boundaries, or they sound like bluster. Say where you would stop and escalate. Say what you would not have decided alone. A young leader who is clear about the edges of their authority reads as more senior, not less.

The point of all this

Language is not decoration. The words a profession uses decide what gets counted, and what gets counted decides who gets promoted. If enough of us start describing our work in terms of judgement, decision quality and risk, then eventually the phrase soft skills will sound as dated as a fax number on a business card — and the people who were held back by it will have a better claim on the next rung.

Start with your next appraisal. Swap one adjective for one decision.