Most organizations were designed for a world that no longer exists.


I work with leadership teams to design the architecture that changes that.


Organizational Architect | CODP®

Icon Pfeil nach unten

It's a design problem. Structures that weren't designed for today's complexity block decisions, slow execution, and leave HR reactive instead of shaping.


I work with leadership teams willing to look at the system. Together, we design the organizational architecture and the HR function that translate strategy into impact.


When leadership drowns in operations, it's rarely a people problem.



Projects & mandates for clients such as...


Familiar symptoms. Underestimated causes.


Most leadership teams treat the symptoms, not the system. The following patterns are widely recognized - their structural causes rarely are.

Leadership trapped in operations.


When decisions that should be made locally get pulled to the center, leadership becomes the bottleneck - and the organization slows down with it. That points to structure, not people.

Strategy fails at the structure.



New directions are agreed upon - but the organization isn't built to carry them. The plan is sound. The system is not.


Internal complexity slows everything.



Unclear accountabilities, too many coordination loops, decisions that no one makes. The system works against itself.

HR reacts instead of shapes



When HR is driven by day-to-day demands, the connection between strategy, structure, and people breaks down. The organization plans - but not with the people it actually needs.

Growth without a foundation that holds


What worked at 50 people doesn't work at 200. Structures that don't grow with the organization become the brake on its growth.


Critical knowledge leaves with the people.


When key people leave, critical knowledge goes with them. Without systematic succession planning, every departure becomes an avoidable crisis.


Do you recognize patterns in your organization? That's the starting point.

Design shapes behavior.


When organizations don't work the way they should, the cause is rarely a lack of effort or competence. It lies in what the system asks of people - in structures, accountabilities, and decision pathways that produce certain behaviors - intended or not.


Culture isn't directly designable. It emerges as a consequence of design. Those who want to change behavior need to work on the architecture.

My approach


I don't start with analysis. I start with the question of where your organization needs to be. Only then do we look at what is keeping the system from getting there.

Clarity about the whole system


Before we intervene, we understand. Vector³ creates a shared picture of where the organization is headed, where it stands today, and where the critical gaps are.

Architecture that holds



Together, we design structures, accountabilities, and decision pathways so that your strategy becomes executable and leadership gains room to lead.

Change that lands



Puzzle Transformation ensures that change doesn't fail as a project - it becomes how the organization operates. Incremental, adaptive, self-correcting.


The difference: the work builds your capacity, not your dependency.

Every change begins with the right question.


In an initial conversation, we clarify where your organization stands and whether my approach fits your context. No commitment, no strings attached - just a direct conversation.