Artificial intelligence can recommend. The signature cannot be delegated.

The last question of the panel was which decisions an organization should never fully delegate to an artificial intelligence system. It is the question that comes up most often at these tables, and it is almost always answered with a list: credit, hiring, firing, pricing, medical diagnosis. Everything that touches people's rights.

The list is not wrong. The problem is that you cannot work with it. A director who walks back to the office holding that list still does not know what to do on Monday, because most of the decisions the company is actually automating are not on it. Approving a discount. Prioritizing a service order. Deciding which customer gets called first. None of those touch fundamental rights, and together they govern the business.

There is a better test, and it is uncomfortable precisely because it is simple.

What the machine reveals

In thirty years of operating, few things have been as consistent as this: when an organization tries to automate a decision and gets stuck, it almost never gets stuck on the model. It gets stuck when someone asks who answers for the outcome.

The conversation stops, someone says a committee reviews that, someone else clarifies that the committee only validates, and within twenty minutes it is clear that the decision had been made for years without an owner. It worked because the cost of being wrong was diluted across several areas and nobody measured it.

Artificial intelligence does not create that problem. It makes it visible, and it makes it visible quickly, because a system demands that the rule be written down. As long as a person with judgment was making the call, the ambiguity could hold: judgment filled the gaps without anyone noticing them. The moment it has to be programmed, the gaps surface all at once.

That is why the hardest implementations I have worked on did not fail for lack of data or for picking the wrong tool. They failed because the project forced the organization to define a responsibility it had spent years avoiding, and that is a political conversation, not a technical one.

The signature test

Before automating any decision, you have to be able to answer three questions without hesitating:

1. Who signs. Not which department: which role. If the answer contains the word committee, there is no answer yet.
2. On what information. Which figures support the recommendation, where they come from, and whether that person can audit them without depending on whoever built the system.
3. What happens when it is wrong. Not in the abstract. What is the measurable consequence of having followed the wrong recommendation, and who absorbs it.

If all three have answers, the decision can be automated with confidence, even when it affects people, because someone answers for it. If any of them does not, the artificial intelligence project has just uncovered a governance problem, and that gets fixed first, and not with technology.

Recommending is not deciding

None of this argues against automation. Quite the opposite. A system that calculates well frees a person from the mechanical part of judgment and leaves them exactly the part that cannot be delegated: understanding the context, weighing what is not in the data, and owning the outcome.

The distinction that matters is not between important decisions and minor ones. It is between recommending and answering. A machine can recommend more consistently than any of us, and without getting tired. Answering is something else, and as far as I can tell, it remains a job with a first and last name.

This piece came out of the closing question of a panel on artificial intelligence implementation at EGADE Business School, on August 14, 2026. It contains no private conversation, no client company and no one else's figures.

Back to the start