The standards nobody wrote down: professionalism and work ethic as a shared agreement
Ganesh HS ·
In brief
'Everyone knows' is not a standard; it is a set of expectations that punishes newcomers for not being mind-readers.
Professionalism is a short list of observable behaviours the team has agreed, not a lecture on attitude.
The list is built by the team, from real incidents, or it is not owned.
Managers enforce it by example first and by conversation second; a policy alone does nothing.
A capable new joiner, three months in, was on the edge of being let go for a series of small things: replying to a client at eleven at night from a personal number, joining a call late without saying so, forwarding an internal email chain outside, wearing something on a client visit that raised eyebrows. Each was, in the words of the manager, 'obviously not how we do things'. Asked where that was written, the manager conceded it was not, anywhere. The joiner had come from a business where two of the four were normal, and had been guessing.
The business did not have a professionalism problem in the joiner. It had a set of expectations that lived in the heads of people who had been there long enough to absorb them, and no way of transmitting them except by disapproval after the fact. Professionalism training is bought to fix the joiner and is worth having to fix that.
Why the lecture version fails
Most professionalism training is delivered as a session on attitude: integrity, ownership, respect, accountability. Everyone nods. Nobody's behaviour changes, because the words describe values people already believe they hold, and the actual friction is about specifics — what time is late, which channels are for clients, what is confidential, what to wear where — that the values session never reaches. A joiner who forwarded an internal chain did not lack integrity. They lacked the specific knowledge that this business treated that chain as confidential, and no amount of talking about integrity would have supplied it.
Turning 'everyone knows' into a standard
1 COLLECT the last twenty 'obviously not done' incidents,
from managers, without names
2 SORT into five or six areas: client contact, time,
confidentiality, appearance, internal conduct,
representing the business
3 WRITE one observable line per area, in the team's
own words. 'Client replies come from a work
address, between eight and seven, unless the
client has asked otherwise.'
4 AGREE the team reads it, argues with it, and owns it
5 INDUCT every joiner gets it in week one, from a
person, not a PDF
A page. Built from real incidents. Owned by the
people it applies to.
Step three is where the work is. 'Be professional with clients' is a value; 'client replies come from a work address, between eight and seven' is a standard someone can meet or miss. Writing each area as one observable line forces the business to decide what it actually expects, which it has often never done — and the arguments in step four, about whether eleven at night is ever acceptable, are the business finding out what it believes.
The list is built by the team
1
Managers supply incidents, not rules
The twenty incidents are the raw material. A manager who writes the rules alone produces a policy; a team that sorts the incidents produces an agreement.
2
Argue in the room
Where the team disagrees — on hours, on dress, on what is confidential — that disagreement is the finding. It has been operating silently as inconsistent enforcement for years.
3
Keep it to a page
A professionalism standard that runs to ten pages is a handbook and will not be read. Five or six areas, one line each, and a sentence on why.
4
Say what it does not cover
Judgement still applies. The page handles the twenty things that keep going wrong; it is not a substitute for asking when unsure, and it should say so.
The agreement step is what distinguishes this from a code of conduct. A code is issued and acknowledged; a standard is argued over and owned. The second is what a team will actually hold each other to, and the difference shows in whether a colleague will say 'that is not how we do it here' to a peer, or leave it to the manager.
Work ethic, and what it is not
The 'work ethic' half of the title is the more dangerous one, because it is where a standard can quietly become a demand for unpaid hours. Honest content distinguishes between reliability — doing what you said, when you said, and saying early when you cannot — and availability, which is a workload question the business has to answer for itself and should not disguise as a personal virtue. A team that agrees 'we say by Wednesday if Friday is at risk' has set a work-ethic standard. A team told 'we go the extra mile' has been given a slogan, and the joiner who takes it literally will burn out being professional.
The client-facing lines deserve the most care
Of the five or six areas, client contact is where an unwritten standard costs most and where the team's own disagreements run deepest. The eleven-at-night reply in the opening was, to the joiner, a demonstration of commitment; to the business, a signal to the client that its people had no boundaries and could be reached at any hour, which sets an expectation the whole team then has to live with. Neither reading is wrong. Which one the business wants is a decision, and until it is written down as a line — hours, channels, who may commit the business to what — every new person will make their own call and be judged against a standard they could not see. The client-contact line is also the one to induct first, because it is the one a joiner can breach in their first week without ever meeting a colleague who could have told them.
How managers enforce it
By example, first. A standard about client hours enforced by a manager who emails clients at midnight is a standard nobody believes.
By the same-day conversation. 'That chain was internal — here is how we handle those' on the day, privately, is the entire enforcement mechanism for most items. It takes two minutes and it is what the joiner in the opening never got.
Consistently across people. A standard applied to juniors and waived for seniors teaches the actual standard, which is that seniority exempts you. This is the same consistency question that runs through HR policies and governance.
Through the formal route only when it is conduct. Most professionalism lapses are ignorance and are fixed by the conversation. The few that are conduct belong in the grievance and disciplinary process, and the standard makes clear which is which.
What changes
A business with a written, owned standard onboards differently: the joiner gets the page in week one from a person who explains the why behind each line, and the guessing stops. It also manages differently, because 'that is not how we do it here' now has a reference point instead of a raised eyebrow, and the same-day conversation becomes ordinary rather than confrontational. That is what professionalism and work ethics work should produce — not a session on attitude, but a page the team built and a habit of pointing to it kindly.
The joiner in the opening, given that page in week one, would have made none of the four mistakes, because none of them was a character flaw. They were four things nobody had said. Where a business finds itself repeatedly disappointed by newcomers' judgement, the honest first question is whether the judgement was ever transmittable, and professionalism and work ethics training done properly starts there.
Questions we are asked
It is the common sense of the people who have been there longest. Newcomers arrive with a different business's common sense, and nothing written down to correct it. The gap is transmission, not attitude.
A code is issued and acknowledged. A standard built from the team's own incidents is argued over and owned, and that is the version colleagues will hold each other to without waiting for a manager.
Reliability: doing what you said, when you said, and saying early when you cannot. Not availability, which is a workload question the business must answer honestly rather than disguise as a virtue.
A page. Five or six areas, one observable line each, with a sentence on why. Anything longer is a handbook and is not read.
By managers' example and by the same-day private conversation — 'here is how we do that'. The formal route is for the small number of lapses that are conduct rather than ignorance, and the standard makes the distinction clear.
A proposal, a confident voice, a nod around the table, and a wrong decision nobody examined. What critical thinking and problem-solving training gives a team that has no time, and the four questions that would have caught it.
He had the facts, made his case, and the team stopped listening halfway through. What emotional intelligence training covers when it is stripped of jargon, why it is mostly noticing, and the three moments in a working week where it decides outcomes.
Eight capable people, forty minutes, and the one problem everyone knew about left unsaid. What communication skills training covers for experienced staff, why it is rarely about speaking clearly, and the three habits that change what gets said in a room.
Read the article
Let’s find your next step
Is your HR process ready to scale?
Identify critical compliance gaps, payroll leaks, and hiring bottlenecks with a free 360-degree HR audit. Get a clear roadmap for your business.