From above of multiracial colleagues in formal outfit working with papers laptop and tablet at table. How to answer the customer ethics questions leadership actually asks
Photo by Sora Shimazaki on Pexels

Rules

Part of Customer ethics and the asymmetry most companies never name

How to answer the customer ethics questions leadership actually asks

Customer ethics questions for the product manager, the marketer, the support lead and the board, with the answer that should worry you in each case.

The questions below are not for a customer. They are for the people who decide what happens to customers, and they are grouped by whose job it is to answer.

Each has an answer that should reassure you and one that should not. The worrying answers are all versions of the same thing: a practice that works because somebody does not understand it.

What to take away

  • Ask the product manager what the flow would look like if the customer understood it perfectly. If the answer is "different", you have found the design that is doing the work.
  • Ask the marketer what a reasonable reader takes away, not whether the claim is true. Those are different questions and only the first one matters.
  • Ask the support lead what they are measured on. If retention is in the answer, the queue is a sales channel and the complaint data is not evidence.
  • The board question that produces the most information is what the company does when it is wrong, in cash, without being asked.

For the person who owns the product

If every customer understood this flow perfectly, what would change?

Product ethics answers: reassuring vs worrying

Reassuring

Perfect understanding
Nothing much
Default unticked
Tested, fine
Support queue
Specific step + plan
Most profitable
Heaviest users

Worrying

Perfect understanding
A list
Default unticked
Would hurt numbers
Support queue
That is a support metric
Most profitable
Non-users, late fees

Reassuring: nothing much, or a specific small thing. Worrying: a list. Every item on that list is revenue that depends on misunderstanding, and you now know its size.

Which default would not survive being unticked for a month?

Reassuring: none, we tested that. Worrying: "we could not do that, it would hurt the numbers". That is a prediction that the default, not the product, is producing the result. Run it for a month on a slice and find out.

What does the support queue tell us about this design?

Reassuring: a specific step where people get stuck, and a plan. Worrying: "that is a support metric". Repeated confusion at the same point is a design output, and treating it as a service problem is how it survives for years.

Who are our most profitable customers, and why?

Reassuring: the ones who use the product most. Worrying: the ones who do not use it at all, or who incur fees for being late or disorganized. That is not a pricing detail. It is a finding about the business model, and it belongs in front of whoever owns it.

For the person who owns the marketing

What does a reasonable reader take away from this?

Marketing ethics answers: reassuring vs worrying

Reassuring

Reader takeaway
Roughly true
Limitation placement
Next to claim
Publish reversed result
Yes, and did
Independent reader
A name

Worrying

Reader takeaway
Technically accurate
Limitation placement
In the terms
Publish reversed result
A pause
Independent reader
Nobody

Reassuring: roughly what is true. Worrying: an answer about whether the claim is technically accurate. A page made entirely of true statements can leave a false impression, and that version is the more dangerous one because it survives internal review.

Where does the limitation sit?

Reassuring: next to the claim. Worrying: in the terms, or "the sales team explains it". A qualification the buyer does not encounter at the point of decision is not doing any work. The same reasoning runs through guidance for advertisers on endorsements and testimonials, which treats the placement of a disclosure as part of whether it exists.

Would we publish this comparison if it had gone the other way?

Reassuring: yes, and here is one we did. Worrying: a pause. A benchmark chosen after the results are known is a marketing artifact, and everyone who reads it carefully can tell.

Who read this who does not benefit from the sale?

Reassuring: a name. Worrying: nobody. The only reliable reviewer of a claim is someone whose result does not move with it.

For the person who owns support

What are your agents measured on?

Support ethics answers: reassuring vs worrying

Reassuring

Agent measures
Resolution, return
Should not sell
Named route, no offer
Recurring complaint
Named immediately
Complaint travel
First person fixes

Worrying

Agent measures
Retention, saves
Should not sell
Escalate to manager
Recurring complaint
A category name
Complaint travel
Manager every time

Reassuring: resolution and whether the customer came back. Worrying: retention, saves, or offers accepted. If saving the customer is the measure, the queue is a sales channel, and every complaint figure that comes out of it is shaped by that.

What happens when an agent thinks a customer should not be sold to?

Reassuring: a named route that does not end in an offer, used recently, with no cost to the agent. Worrying: "they would escalate to a manager". That is the same path as everything else, which means it is not a route.

What is the complaint that keeps coming back?

Reassuring: they name it immediately. Worrying: a category name. Categories are chosen for reporting convenience and hide the cause; the text does not.

How far does a complaint travel before someone can fix it?

Reassuring: the first person can fix most things. Worrying: a manager every time. Responsibility without authority at the front line produces slow, expensive, and eventually hostile handling.

For a board or oversight body

What did we do the last time we were wrong?

Board ethics answers: reassuring vs worrying

Reassuring

Last time wrong
Refunded all affected
Least public practice
Named and fixing
Newest data use
Asked, or expected
Customers lost
Number and reason

Worrying

Last time wrong
Credits, complainers only
Least public practice
None
Newest data use
The terms permit it
Customers lost
A number

Reassuring: identified everyone affected, refunded in the form they paid, without waiting to be asked. Worrying: credits, or refunds only for those who complained. This one answer tells you more about a company's customer conduct than any dashboard.

Which of our practices would we least like to see described accurately in public?

Reassuring: they name one and it is being fixed. Worrying: "none". Every business has one, and a management team that cannot name it has not looked.

What is the newest use of customer data, and was anyone asked?

Reassuring: asked, or a use customers would plainly expect. Worrying: "the terms permit it". A permission obtained for one purpose does not automatically stretch to another, which is the question the regulator's code of practice on data sharing is built around. Where personal data moves between organizations, counsel decides what is permitted and you decide what is expected.

How many customers left last quarter, and do we know why?

Reassuring: a number and a reason drawn from what they said. Worrying: a number. Exit is the only moment a customer has nothing to gain from being polite.

What the worrying answers have in common

AnswerWhat it actually says
"It is technically accurate"A reasonable reader will be misled
"The terms permit it"Nobody asked the customer
"That would hurt the numbers"The design, not the product, produces the result
"That is a support metric"The cause is known and owned by nobody
"We treat everyone the same"Nobody has looked at the price ladder
"None, we have never had that problem"Nobody has looked at all

None of these is proof of bad conduct. Each is proof that a question has not been answered, and the correct response is to ask it again with a date attached.

What the worrying answers actually say

Answer

Technically accurate
Reader misled
Terms permit it
Nobody asked
Hurt the numbers
Design produces result
Support metric
Cause owned by nobody
Treat everyone same
Price ladder unexamined
Never had that problem
Nobody has looked

What it says

Technically accurate
Terms permit it
Hurt the numbers
Support metric
Treat everyone same
Never had that problem

Asking them without starting a fight

Ask them routinely and of everyone, in the same words, on a schedule. A question asked of one team in a bad quarter is an accusation. The same question asked of every team every quarter is a process, and it is the only version that keeps producing answers.

Asking without starting a fight

  • Ask routinely, of everyone
  • Use the same words
  • Put it on a schedule
  • Ask every team every quarter
  • Write the answers down
  • Compare on the second ask

Write the answers down. Most of the value arrives the second time you ask, when you can compare.

The structure for deciding what to do when the answers reveal a genuine conflict is in ethical frameworks. The asymmetry that makes these questions necessary is in customer ethics. The rule that should already require most of these answers is in codes of conduct.

Common questions

What if I get a reassuring answer that turns out to be wrong?

That is common and not usually dishonesty. People answer for the system as designed rather than as it runs. Follow one answer a quarter to the underlying record, chosen at random, and say in advance that you will.

Is there a single question if I only get one?

Ask what happened the last time the company was wrong in its own favor, and what the customer received. Everything else can be inferred from the answer.

Should customers ever be asked these directly?

Some of them, in different words, and the answers will be less comfortable than the internal ones. The people best placed to answer are those who have just left, and they are the group least often asked. What stops staff from relaying what they hear is set out in employee ethics.

More in Rules

Latest from Costs Desk