The employee ethics questions that keep coming back

These are the questions people actually ask, usually of a friend in another team, the evening after something happened at work. Each comes with a hypothetical to make it concrete and an answer that is honest about what it costs. None of the situations describes a real person or company.

The pattern across all of them: the question is rarely "is this wrong?" The person already knows. The question is what to do about it at a price they can pay.

What to take away

"Is this actually my problem?"

Example: you are a project coordinator. You notice that a status report going to a client marks a milestone as complete when the team has told you it is not. You did not write the report and you are not the account lead.

The test is whether your name would appear in an accurate account of what happened. You saw it; you understood it; you sent it on or let it go. That puts you in the account. It does not make you responsible for the report, but it does make you responsible for what you did after you read it.

What that requires is small. A message to the person who wrote it: "I read milestone three as complete; the team told me yesterday it is not. Have I got that wrong?" That is a question, it is on the record, and it is the whole of your obligation at this stage. What happens next is theirs.

"I already went along with it. Is it too late?"

Example: three months ago you approved an expense you suspected was not legitimate, because it was small and your manager had already signed it. Now you are being asked to approve a larger one from the same person.

It is not too late, and the earlier you stop the cheaper it is. The first approval does not commit you to the second. What it does is make the conversation slightly harder, because you will need to say that you should have asked last time.

Say exactly that: "I should have asked about the last one and did not. I am asking about this one."

People who are doing something they should not are rarely surprised to be asked, and people who are not will be glad you did. The mistake is approving the second because you approved the first, which converts a lapse into a pattern.

"My manager is the problem. Who do I go to?"

Example: your manager has told you to record customer calls under a category that triggers a bonus for the team, regardless of what the call was about.

The route is whatever the code names for when the manager is the problem. If the code names none, that is a finding about your organization.

In most places, the route is the manager's manager, HR, or a reporting channel. Which one you use depends on how serious the conduct is and how safe each route feels. Only you can judge the safety.

Before going anywhere, write down what you were told, when, and in what words, then ask your manager the question once, in writing: "Can you confirm you want calls about X recorded as Y? I want to make sure I have understood."

A manager who replies in writing has given you the record; one who refuses has told you the route you need.

Copy-ready wording for the written question:

Subject: Written question about the [X] instruction

Hi [name], I want to be sure I have this right. On [date] you asked me to [specific action]. My understanding is that this means [consequence]. Can you confirm that is what you want, and whether it applies to [scope]? I am asking before I act.

Thanks, [your name]

Keep your own note separate from the email: date, time, who said what, in their words, and who else heard it.

The pillar on employee ethics covers what this kind of request usually costs and how to weigh it; the reporting route your organization should have provided is set out under codes of conduct.

"Is it my job to fix it, or just to report it?"

Example: you have found that a data export the company sends to a partner includes fields the partner should not receive. You could stop the export yourself, or you could report it and wait.

Your obligation is to make the right person know, clearly, in a way they cannot later claim not to have understood. It is not to run the investigation, design the fix or take unilateral action, unless the harm is immediate and nobody else can act.

Where the harm is ongoing, say so in the report and say what you think the immediate step is. "This export runs nightly; I believe it should be paused until someone has reviewed the fields." Then, if nothing happens by the next run, ask again, and note that you asked.

When harm from acting competes with harm from waiting, a short introduction to the standard ethical lenses offers four ways to examine it in about ten minutes.

Whether you may stop it yourself depends on your authority. If personal data is involved, jurisdiction rules apply. Ask the person you reported to, or counsel. Do not decide alone at midnight.

"Can I talk to a colleague first?"

Example: you are not sure whether what you saw is a problem. There is one person on the team whose judgment you trust.

Yes, and it is often the right first step. One trusted person, asked "am I reading this right?", improves your judgment and costs nothing.

The line is between checking your reading and building a case. Talking to one person is the first, but talking to four, comparing notes, and arriving as a group is the second, which changes how what you raise is received, whatever its merits.

If more than one person has seen the same thing, each should raise it separately. Two independent reports carry more weight than one joint report and cannot be dismissed as a faction.

"They said it has always been done this way."

Example: you query a practice of backdating delivery confirmations so that invoices fall in the right month, and you are told that is how it has always been done and finance knows.

"It has always been done this way" is an answer to a question about history. You asked a question about whether it is right. Say so, politely. "I understand it is long-standing. I am asking whether it is something we should be doing, and whether finance has confirmed that in writing."

The second half of that sentence matters. Practices that "everyone knows about" frequently turn out to be known to nobody who would have to defend them. Asking for the confirmation is not an accusation; it is what a careful person does, and if it exists it will be produced.

Where a practice affects financial records, whether it is permitted is for the finance function and possibly counsel, not a team's custom.

"What if I am wrong?"

Example: the numbers in a report look impossible to you, but you are new, and the person who produced them has been here ten years.

You may be wrong, which is why you raise it as a question. "I am probably missing something, but I cannot reconcile this figure with that one. Can you show me where it comes from?"

The only way to be wrong expensively is to raise it as a conclusion. Do not.

"Should I resign first?"

Example: you have decided you cannot carry on with something and you are considering leaving so that you can speak freely.

Usually no, and for a reason that surprises people: leaving first often reduces the protection you have and the weight your account carries. Someone raising a concern while employed is a person using the organization's own channels. Someone raising it after leaving is, to some audiences, a former employee with a grievance, however unfair that reading is.

The sequence that protects you is generally to raise it inside, through the route that exists, keep your own contemporaneous note, and decide about leaving afterwards with the record made.

What protections apply to you in either case differ by jurisdiction and by what the concern is about. Ask counsel of your own before you resign, not after. The UK's whistleblowing framework is one worked example of how such a regime is built.

In the United States, the channel depends on what the concern is about. OSHA enforces the federal whistleblower protection statutes. A retaliation complaint usually has to be filed within 30 days of the adverse action, though some statutes allow longer.

The SEC and the DOJ run tip routes for securities and fraud matters. A state attorney general handles consumer, charity and public-funds fraud. The EEOC takes discrimination and retaliation charges, with a filing deadline of 180 days in most states and 300 where a state or local fair employment agency exists.

Most US private-sector jobs are at will. An employer can end the job for many reasons, but not for illegal retaliation, and a retaliation claim does not depend on having a contract.

The NLRB covers concerted activity about working conditions for most employees. Supervisors and managers generally fall outside that protection.

The personal document that makes this decision easier to face is described in the site's article on an employee ethics framework. The underlying conflict between what you owe the organization and what you owe yourself is in ethical dilemmas.

The question underneath all of these

Every question above asks the same thing: how do I do the right thing without it costing more than I can bear? It will cost something. The cost is lowest at the earliest moment and rises from there, and the routes open to you are only as good as your organization made them.

What it costs, concretely. Retaliation is not always dismissal. A stalled promotion, a thinner assignment or a sudden performance improvement plan is harder to prove and easier to impose, and a PIP can end a job within 30 to 60 days.

Legal fees for a retaliation or wrongful termination claim usually begin with a paid consultation, commonly in the low hundreds of dollars, and reach five figures if the case is litigated. Employment lawyers in US metro areas typically charge a few hundred dollars an hour; a typical range is 250 to 500 dollars.

Severance is not required by law in most US at-will jobs. It is usually offered in exchange for a release of claims. Back pay and reinstatement are remedies an OSHA or EEOC finding can produce, and the process usually takes months, not weeks.

A leader can lower that price for the people below; see leadership ethics, read it from the other side.

Common questions

What if there is no code and no channel at all?

Then your manager's manager and HR are the routes, and your own note is your protection. Write down that no channel existed; that fact will matter later.

Should I copy anyone on the written question?

Not on the first one. A question to one person is a question. A question copied to three is an escalation, and you have not yet earned the need for one.

How long do I wait for an answer?

Long enough for the person to have read it and acted, which is usually days, not weeks. Then ask once more, noting the date of the first. Silence after two asks is an answer.