Two people offer the same useful idea. One sounds familiar, dresses as expected, and knows the room’s unspoken rhythm. The other pauses to find a word and uses a different conversational style.

Who is more likely to be described as professional?

The answer should concern the work: competence, preparation, ethical conduct, and the standards the role requires. When familiarity becomes the hidden measure, an organization can overlook the very qualities it claims to value.

Ask what the standard is actually for

Some workplace expectations serve clear purposes. Protective clothing can serve safety. Accurate records support accountability. Reliable communication helps people coordinate work. Required credentials may protect the people a profession serves.

Other expectations may be conventions whose purpose has never been examined: a preferred accent, a narrow range of hairstyles, a particular style of eye contact, or ease with a social ritual outside the job itself.

Do not assume every convention is harmful or every requirement is arbitrary. Ask a more precise question: “What does this expectation enable, and is it necessary to do the work responsibly?”

If clear communication is required, assess whether the person can make relevant information understood. Do not substitute “sounds like us” for an examination of that ability.

Make evaluation concrete

Before evaluating someone, describe the behaviour or outcome you need. “Handles customer concerns professionally” is open to interpretation. “Listens to the concern, explains the available options accurately, records the agreed action, and follows through” gives people something observable.

In an illustrative recruitment process, a candidate with an unfamiliar conversational style can demonstrate how they would respond to a realistic customer problem. The evaluation can then focus on accuracy, judgment, clarity, and respect rather than an assessor’s sense of social comfort.

Use assessments appropriate to the role, accessible to candidates, and consistent with applicable law and organizational policy. This is an editorial framework for examining assumptions, not a legal hiring procedure.

Concrete standards also help existing staff. A person can improve a specific action. “Be more polished” may leave them guessing which part of their identity someone wants changed.

Examine whose effort is being treated as invisible

Someone working in a second language may prepare carefully to make a contribution. Someone unfamiliar with a workplace’s unwritten rules may be learning the task and the social code simultaneously.

That effort does not automatically make their work excellent. It does mean hesitation should not be interpreted carelessly. Ask what the contribution demonstrates and what support would allow the relevant ability to be seen.

The same care applies to the person who speaks smoothly. Confidence can accompany competence, but it does not verify it. Check the substance of a proposal, the quality of a decision, and the reliability of follow-through.

Keep respect connected to accountability

Inclusive standards do not require ignoring poor performance. They require explaining the expectation fairly and assessing the work against it.

If an error occurs, name the error. If communication fails, identify what was unclear. If conduct causes harm, address that conduct. Avoid turning a correctable problem into a judgment about a whole culture, background, or identity.

Leaders can begin with one small audit of their own language. When you describe someone as professional, impressive, difficult, or not a good fit, ask what observable evidence supports the description. If you cannot explain it, the label may be carrying an assumption you have not tested.

Professionalism should make work more trustworthy and people’s responsibilities clearer. It should be possible to explain what it means without pointing to the person who most resembles the people already in the room.

Keep one idea

Replace one vague judgment about professionalism with an observable requirement of the work.

Explore all Insights Follow this reading path