Change is not development

In many companies, “transformation” is currently showing. A real blockbuster. New tools like people analytics, new processes like OKRs and agile frameworks, AI-supported processes.

At first it runs smoothly, with big pictures, strong dramaturgy, and lots of energy. And often a feeling remains: a lot is changing, but nothing is developing. The film is running, but the system stays the same. At some point, the strength for the next act is missing.

Change can come from outside: through technology, restructuring, targets. Development, however, arises from within.

A team with clear OKRs does not automatically become more effective.

A company with modern HR software does not automatically become stronger in leadership.

Process landscapes with AI-generated output do not necessarily bring “better” results (whatever that means).

If you want development, you have to turn your gaze from the screen to the projection system. It is not the picture that decides, but what makes it possible. That is what I then get to question:

Not simply introducing tools, but clarifying relationship patterns; in interaction or in delivering the work. It is about “relating”; between human and machine, too.

Not just speeding up workflows, but opening spaces for thinking, process, and decision-making.

Perhaps real development is so rare because it cannot be produced. It wants to be allowed. Like a good film—one that changes you because you allow yourself to have it.