← All field notes

If nobody can disagree with the AI, who is really in charge?

A person can approve an AI recommendation without having much control over the decision. In Zinc’s view, human oversight matters only when disagreement is a real option.

Abstract illustration of an ochre circle taking a separate path from parallel blue lines.

That makes the arrival of AI in Salesforce a management question as much as a technology question. What happens when the person reviewing an answer disagrees with it? What if they agree, but only because challenging it would take too long?

The approval button can conceal the argument

Imagine an account manager reviewing an AI-drafted renewal offer. The price follows policy. The account looks healthy in Salesforce. The manager also knows that the customer is frustrated about a problem that has not reached the record.

The draft may be reasonable given the information available. The manager’s hesitation may be reasonable too.

A required approval could help bring that missing context into the decision. It could also become a formality if the manager faces a queue of drafts and a response-time target.

That is the ambiguity in “a human will review it.” A person might examine the evidence, challenge the recommendation, and change the outcome. They might instead click a button because the process rewards moving the queue.

This is an imagined situation, not a claim about a particular company or Salesforce product. It is a question about the working conditions around review.

Human judgment deserves scrutiny too

It would be too easy to cast the employee as wise and the software as careless. People can overlook details, apply rules inconsistently, or defend familiar habits that no longer help customers.

AI assistance could make relevant information easier to compare. A consistent recommendation could expose differences that a team previously accepted without discussion. Some routine decisions may be better served by clear rules than by another manager’s approval.

There is a cost to preserving every human checkpoint. Customers may wait while employees repeat checks that rarely change anything.

But there is also a cost to treating every disagreement as resistance to change. An employee may notice a problem that the system cannot yet represent. Removing that person’s discretion could remove useful information from the decision.

The difficult question is which kind of disagreement you are seeing. A protective habit and a valuable objection can sound remarkably similar.

Who gets the benefit, and who carries the consequence?

Imagine a leader choosing an AI workflow because it could shorten response times. A frontline employee must approve its recommendations. When a response goes wrong, that employee has to explain it to the customer.

Is that employee exercising judgment, or absorbing responsibility for a system someone else chose?

There may be a fair arrangement. The employee could have enough context and authority, with leadership supporting reasonable overrides. The same arrangement becomes harder to defend if the employee cannot change the process but is blamed for its results.

NIST’s AI governance guidance calls for documented responsibilities. That is useful groundwork. Our concern goes further: a role on paper does not tell you whether someone feels able to challenge a recommendation.

This is a discussion of management responsibility, not a determination of legal liability.

What happens to judgment when people use it less?

Consider a newer employee who mostly reviews answers rather than building them. They might learn faster by seeing good examples. They might also struggle to recognize a weak answer if they rarely work through the problem themselves.

Both possibilities deserve attention. Neither is an inevitable result of using AI.

Experienced employees face another version of the question. If software handles the routine work, they could spend more time on difficult cases. Or they could inherit a day made almost entirely of exceptions, without the relief of simpler tasks.

That prospect complicates the promise of freeing people for higher-value work. More demanding work can be rewarding. It still needs time, support, and a realistic workload.

We believe a credible AI strategy leaves room for human judgment to develop and matter. That does not require approval for every action. It requires taking disagreement seriously when the consequences justify it.

If the only acceptable response to an AI recommendation is agreement, what exactly is the human there to do?

How Zinc can help

Zinc combines Change Management with Salesforce Consulting. We can help your team work through where automation belongs and where people need meaningful discretion.

That discussion can shape a defined workflow, including the responsibilities and support around it. A Slack Workflow Quickstart covers one workflow and an agreed connection when that is the right fit.

Bring Zinc the decision your team is not comfortable delegating yet. It may reveal more than a list of tasks you are ready to automate.

Continue reading

Another useful angle.

Manufacturing

Should AI give your customer an answer you would hesitate to give?

Read the field note
AI economics

What if AI saves time and your business changes nothing?

Read the field note