Why Does Toyota’s Chief Engineer Have No Authority?

The Toyota chief engineer carries full responsibility for a vehicle and holds almost no command authority over the people who design it. The engineers report to their own functional departments, not to him. He cannot order them, hire them, or move them. Most accounts call this a paradox and stop there. The more useful question is why Toyota built the role that way on purpose. The withheld authority is not a flaw the chief engineer has to work around. It is a device for development of the chief engineer and the style of leadership Toyota intended for the role.

This article is a companion to the main guide, What Is the Toyota Chief Engineer (Shusa) System?.

Did Toyota withhold the chief engineer’s authority on purpose?

Yes. It was a deliberate design choice, and a former chief engineer explains the reasoning.

Eiji Adachi, who served as a chief engineer and later wrote a detailed account of the role in his book Toyota Product Development, is direct about it. Command authority was kept away from the chief engineer because Toyota believed a sound proposal should win on its own merits. If the chief engineer could not persuade the other party on technical merit, then the proposal was not yet good enough to win. The lack of authority forces the idea to stand on its quality, not on rank.

This inverts how many organizations think. A normal manager is sometimes given authority so that good ideas do not get blocked by politics. Toyota did the opposite. It withheld authority so that the idea has to earn its way past every objection. A proposal that cannot survive that test is treated as a proposal that is not ready.

How is missing authority a way to train a chief engineer?

This is the part the Western accounts leave out. The constraint is what develops the person and creates the type of system that Toyota intended for the role.

When a chief engineer cannot give orders, he has to understand the other side well enough to personally move them. He has to know the engineering deeply enough to argue it. He has to listen closely enough to find the version of his idea that the other department can accept. Adachi makes the point plainly. If the chief engineer persuaded sincerely, the other party’s heart should move. And that act of persuading, repeated across a whole career, is what trains the chief engineer.

A chief engineer who could simply command would never build any of that. He would not need to master the other functions. He would not need to listen. He would issue an instruction and move on. The capability that makes a real chief engineer, deep technical range and the ability to integrate people who do not work for him, only grows under the pressure of having no authority. Remove the constraint and you remove the training and development component of the role.

So the paradox resolves. Toyota does not tolerate the missing authority. It relies on it.

What does the chief engineer have instead of authority?

He has an unusually wide license to persuade. Adachi calls it the right to persuade, and he is precise about how far it reaches with several examples in his book.

The chief engineer could go and attempt to persuade anyone. He could go over his own boss to the president. He could go to a supplier Toyota had no standing relationship with. He needed no one’s permission first. He judged what the program required, and he went. A staff engineer with no line authority could walk into any office in the company, or outside it, and make his case, because the role carried that right.

That is the trade Toyota made. It took away command authority and gave back reach. The chief engineer cannot order the engine department to do anything. But he can stand in front of the engine director, or the director above him, or the president, and argue the whole car’s case without anyone clearing the meeting first. Adachi tells this story in his book. As a chief staff member (主担当員) entrusted by the chief engineer, he went to the engine department himself to make the case for a new inline-six it had no capacity to build. It is recounted in Eiji Adachi — Toyota Product Development.

How does persuasion actually work in practice?

Persuasion in this role is a craft with rules, not charm. The chief engineers who wrote about the job describe similar disciplines. I will summarize some of the key aspects below.

Win on merit, not on leverage. Hasegawa’s principles are blunt about the shortcuts. The chief engineer must not work the angles. Trading on your face, making backroom deals, or pulling rank do not last. The only thing that holds up over a career is being right and showing why.

Make the proposal pay the other side too. Adachi states the maxim directly. Persuasion does not succeed unless the proposal benefits the other party as well. The chief engineer’s job is to find the version of his plan that the engine group, or the body group, or the supplier, actually wants. A request framed only as good for the program will stall. The same request framed as a win for the other department moves.

Listen hard, then concede the close calls. Wada described his own method. While an engineer explained a proposal, Wada was already building his counterargument in his head, ready to give it the moment the engineer finished. But he also set a threshold. If his own preference was only slightly stronger than the engineer’s, on the order of a sixty-forty call, he said yes. The engineer’s motivation to do the work mattered more than the last sliver of Wada’s preference. A leader with no authority cannot afford to win every small argument.

Own your mistakes immediately. Wada was firm on one rule. If a subordinate did exactly what you told him, you may never turn around and deny you gave the instruction. When your judgment turns out wrong, you say so, apologize, and ask for the rework. A chief engineer leads on credibility alone. One denied instruction or one covered mistake spends credibility he cannot get back.

Go in person and stake yourself on it. Adachi’s standard for the decisions that make or break a program is that the chief engineer advances them in person and stakes his life on them. The reach to persuade anyone means nothing if the chief engineer sends a memo. He shows up, and he carries the risk himself.

These mechanics replace the authority the chief engineer does not have. They are also why the role takes decades to build. None of them can be granted on an org chart.

Why not just give the chief engineer line authority?

Because it would break the system that makes the role work. Line authority would let the chief engineer order compliance, and compliance is the wrong output. Engineers who are ordered stop contributing judgment. Engineers who are persuaded bring their own thinking to the problem. The constraint that forces persuasion is the same constraint that develops the chief engineer and keeps the specialists fully engaged. Toyota understood that giving the role more formal power would make the position and organization weaker in the end. The further misconceptions about copying the role by handing it authority are covered in the main guide, What Is the Toyota Chief Engineer (Shusa) System?.

This article draws on Eiji Adachi’s Toyota Product Development (2014) and the Akihiro Wada Oral History (2008), both Japanese-language primary sources by former Toyota chief engineers, together with firsthand knowledge of the Toyota chief engineer system. Quotations translated from the Japanese are the author’s renderings. AI was used in the editing of this article.

Art Smalley is president of Art of Lean, Inc.