Why engineering needs responsibility

Engineering is often defined by competence. By technical knowledge. By methods. By experience. By the ability to analyse complex problems and develop solutions.

All of that is necessary. But it is not enough.

Because engineering does not end with a technically correct solution. Every technical decision has consequences – for a product, a project, a company, and sometimes for people who had no part in the decision at all.

Which is why something belongs to engineering that we talk about too little:

Responsibility.

As the willingness to make a decision and to carry its consequences.

Knowledge is not responsibility

I was trained as an engineer. Like many engineers I learned to break problems down, to look for causes, to weigh up variants and to derive a solution from information. That way of thinking shapes me to this day. But the longer I lead companies and people, the clearer one limit becomes:

A decision can be technically sound and still be wrong.

Because the assumptions were wrong.
Because important relationships were not taken into account.
Because nobody looked at the consequences outside their own remit.
Or because many people were involved in a decision, but in the end nobody was truly responsible for it.

Complexity can be distributed. Responsibility cannot.

Delegating responsibility is not the same as enabling it

I had to learn that myself. I have given people responsibility too early, and sometimes let go too late. I have known too much and asked too little. I have pushed projects through and sometimes missed what my decision set off elsewhere.

For a long time I thought good leadership meant above all handing people responsibility. Today I see it in a more differentiated way.

Delegating responsibility is not the same as enabling it.

Whoever is to take responsibility needs a clear space in which to decide. They need to know what they are responsible for – and what they are not. They need access to the relevant information. They must be allowed to make decisions, even when those are not exactly the decisions I would have made. And they must be able to make mistakes without responsibility being pulled back upwards at the first one.

That is harder than delegating tasks. Because real responsibility demands trust on both sides.

Leadership needs clarity

The more responsibility is distributed, the more clarity matters.

What are we trying to achieve?
Which principles apply?
Who decides?
Which consequences are we prepared to carry?
And when does a decision have to be escalated?

In complex engineering organisations the opposite arises quickly.

Many people are involved. Many functions have legitimate interests. Information is distributed. Decisions travel through committees, meetings and approval loops.

That can be necessary. But it can also dilute responsibility.
In the end a decision was formally carried by everyone – and actually by no one.

Good engineering therefore needs more than good processes. It needs clear responsibility.

Mistakes are part of it

Responsibility does not mean always deciding correctly. That would be a dangerous notion.
Anyone allowed to take responsibility only when the outcome is already certain takes no responsibility at all. They are merely executing a known solution.

Engineering, though, often happens precisely where the answer is not yet known. We work with assumptions.
We decide under uncertainty.
We develop something that did not exist before.
Mistakes therefore cannot be eliminated entirely.

The decisive question is a different one: How do we deal with them?

Do we look for someone to blame?

Or do we try to understand which assumption was wrong, which signal we missed, and what the system has to learn from it?

For me, responsibility therefore also means not pushing a mistake away from oneself.

Saying:

That was my decision. That was my assumption. That is what I missed. And this is what I am changing now. That is not weakness. It is a precondition for learning.

AI changes the engineer's role

Artificial intelligence makes this question more important still. AI will make knowledge available faster.
It will analyse documents, generate variants, recognise relationships, support calculations and prepare decisions. Many activities that today require technical experience and time will become faster and cheaper.

But AI does not thereby take on responsibility. A system can produce a recommendation. It can calculate probabilities. It can point out contradictions.

The question of which consequence we draw from it remains.

The more capable our technical systems become, the more it therefore matters that a human can bring judgement and responsibility together. The engineer of the future will not be valuable for holding more information than a machine. But for understanding what that information means – and being willing to decide on that basis.

Engineering is more than technical excellence

I believe we have to think engineering further. Technical excellence remains the foundation.
But it has to be joined by judgement, entrepreneurial thinking and responsibility.

A good engineer does not only ask:

Does it work?

But also:

What consequences does it have?
Which assumptions underlie our decision?
What are we overlooking?
And who takes responsibility for turning a technically good solution into a good decision?

Perhaps that is exactly where one of the most important tasks for the future of engineering lies. Not only developing better technologies. But developing people who are able to make better decisions with those technologies.

Because in the end it is not the method that carries the decision.
It is the person who makes it.