Organizational Design
How does the desired image become a coherent interplay?
How should collaboration function in the future? Where should responsibilities lie, and how should decisions be made? Organizational design translates this ideal into a suitable structure, clear roles, effective interfaces, and transparent decision-making processes.
Crucially, it examines how strategy, tasks, and collaboration interact and whether the chosen organizational model is viable in daily work.
We develop potential designs together with relevant stakeholders, examine their implications, and refine them where ambiguities or inconsistencies remain.
Discover which design areas are particularly relevant.
What design question would you like to clarify?
In a no-obligation consultation, we will work with you to identify the organizational design question behind your current situation and where it is worth taking a closer look.
: Where organizational design specifically begins
Organizational design becomes relevant when tasks, responsibilities, and collaboration no longer align well, or when new requirements necessitate a different organizational model.
Aligning the organization with new goals
A new strategic direction can change which tasks, skills, and responsibilities are needed. We will work with you to examine the consequences for organizational design and how the organization can support the desired development.
Reorganize areas and tasks
Growth, new business areas, or changes in the value chain can challenge existing organizational structures. We clarify which tasks logically belong together, where responsibilities should lie, and how units can be linked.
Clarify roles and interfaces
When responsibilities overlap, gaps arise, or handovers require extensive coordination, we jointly examine roles and interfaces. The goal is to clearly assign responsibilities and simplify cross-departmental collaboration.
Design decision-making processes appropriately
When decisions regularly escalate, take a long time, or are made in places where relevant knowledge is lacking, it’s worth taking a look at decision-making rights. We clarify who should decide, who needs to be involved, and what powers are necessary.
This makes responsibility clearer in everyday organizational life.
Good organizational design doesn’t simply create more rules. It ensures that tasks, responsibilities, coordination, and decisions work together in a transparent and comprehensible way.
Clearly define responsibility
Those who are to assume responsibility need clarity regarding tasks and authorities. A suitable organizational design makes it clear who is responsible for what and what scope of action is associated with that responsibility.
Organize voting where it is needed.
Not every interface can be avoided. What matters is which handoffs are necessary and how they function. Clear areas of responsibility and coordinated interfaces reduce unnecessary loops and make collaboration more reliable.
Making decisions closer to relevant knowledge
Decision-making authority should be appropriate to the specific task. Organizational design clarifies which decisions must be made centrally and where responsibility can be reasonably decentralized.
Can accommodate new requirements
An organizational design should not only fit the current situation. Roles, responsibilities, and forms of collaboration must also be adaptable to changing tasks or framework conditions.
Organizational design requires diagnosis before redesign.
Before we design solutions, we examine where the current organization no longer fits well with its tasks and goals.
DEFINING REQUIREMENTS
We clarify what the organization should achieve in the future and which principles are important for the desired organizational design.
Identifying Misfits:
We examine where strategy, structure, processes, systems, and collaboration don’t mesh well. Our Spotting Misfits approach (link to the paper) can support a structured diagnosis in this regard.
DEVELOPING DESIGN OPTIONS
We develop alternatives and examine what consequences they would have for responsibility, cooperation and control.
FIT TESTED
Not every detail needs to be decided on the drawing board. Where it makes sense, elements of the new design are tested, checked, and further refined.
An organizational chart shows only a part of the organization.
Organizational design doesn’t just answer the question of where each area is placed. It also shapes how responsibility is distributed, how people collaborate, and how decisions are made. The existing cid website accordingly distinguishes between structural organization and a collaborative model or process organization .
Structure and collaboration must be aligned.
The organizational structure describes which units exist and how they are formally linked. However, this does not automatically imply how collaborative work across departmental boundaries functions.
Therefore, the collaboration model is also part of the organizational design. It clarifies roles, responsibilities, interfaces, decision-making processes, and relevant forms of coordination. Only when the formal structure and actual collaboration are aligned does a coherent overall picture emerge.
Design principles provide guidance for individual decisions.
Before defining areas, roles, or processes in detail, it’s worthwhile to agree on the principles the future organization should follow.
For example, should responsibility be closer to the customer? Should specialist expertise be more centralized? What balance of autonomy and shared standards is needed?
Such design principles help align individual design decisions with a shared vision, instead of developing many isolated solutions in parallel. cid explicitly distinguishes in its specialist content between design principles that shape processes, roles, and tools.
Roles need purpose, responsibility, and authority.
A role title alone doesn’t provide clarity. What’s important is the contribution a role makes, the tasks it undertakes, and the decisions it’s authorized to make.
Especially when responsibilities are distributed more flexibly, this distinction helps to clearly define expectations. The cid Role Canvas therefore uses purpose, responsibilities, and authority as the central elements of a role.
Interfaces are a design consideration.
When multiple departments collaborate to produce a result, handoffs and dependencies arise. Problems at these interfaces are therefore not automatically a communication problem.
Sometimes clear agreements are lacking. Sometimes responsibilities are ambiguous. And sometimes the very definition of tasks creates an unnecessarily high number of handoffs.
Organizational design, therefore, considers not only individual departments but also the work that must take place between them.
Decision-making rights shape the ability to act.
Unclear decision-making processes lead to decisions being voted on multiple times, delegated upwards, or not made at all.
Good organizational design makes it clear who is authorized to make which decisions, who contributes relevant information, and who is responsible for the consequences . Not every decision needs to be made using the same procedure. The decision-making process should be tailored to the specific task.
A new organizational design also changes leadership.
When responsibilities are redistributed and decision-making authority shifts, the leadership role often changes as well.
Leadership is less about making every operational decision personally. Rather, it’s about…
To provide guidance, clarify priorities, and establish a framework for responsible action
to create these consequences.
These consequences should be considered in organizational design. The targeted development of leadership roles and leadership skills then falls under the umbrella of leadership and leadership development .
Organizational design can be further developed.
Even a carefully developed organizational design is based on assumptions about how tasks and collaboration will function in the future.
Therefore, not every question needs to be definitively resolved before a new model is launched. Individual roles, interfaces, or decision-making processes can be tested in daily practice and adapted based on experience.
The old cid website already explicitly describes organizational design as an iterative process and points out that it’s not always necessary to redesign the entire organization.
Change-Themen auf einen Blick
Frequently Asked Questions
What is organizational design?
Organizational design is the conscious shaping of how an organization is structured and how its members collaborate. This includes, for example, departments and units, roles, responsibilities, interfaces, and decision-making processes.
The goal is an organizational model in which these elements are optimally aligned with the organization’s strategy, tasks, and framework.
When is organizational design useful?
Organizational design can be beneficial when responsibilities become unclear, interfaces require extensive coordination, decisions are frequently stalled, or new strategic requirements are difficult to implement with the existing organization.
Growth, new business areas, or changing forms of value creation can also be reasons to review the existing organizational design.
What constitutes organizational design?
Depending on the specific issue, organizational design includes aspects such as the structure of departments and units, roles, responsibilities, interfaces, decision-making authority, and forms of collaboration.
Not every project requires changes to all elements. The crucial factor is identifying where relevant mismatches exist.
What are misfits in organizational design?
Misfits can be described as a lack of alignment between key elements of an organization. For example, a new strategy might require different processes or responsibilities, while the existing organizational model remains unchanged.
The cid approach , Spotting Misfits, therefore examines the relationships between strategy, structure, processes, systems, and cultural prerequisites in order to identify relevant areas for organizational design.
How do you develop an organizational design?
The starting point is a clear vision of what the organization should achieve in the future. This is followed by an analysis of how the current organization functions and where relevant misfits exist.
Based on this analysis, various design options can be developed, their consequences compared, and then gradually refined or tested.
Does organizational design always have to change the entire organization?
No. An organizational design can affect the entire company, but it can also focus on a business unit, a function, or individual cross-functional units.
The existing cid page explicitly points out that not every organizational design issue requires a complete reorganization.
What is the difference between organizational design and organizational development?
Organizational design focuses on the conscious shaping of structure, roles, responsibilities, interfaces, and decision-making processes.
Organizational development is broader in scope. It deals with how collaboration and the overall development capacity of an organization can be further developed. Organizational design can be one of several areas of development within this framework.
What is the difference between organizational design and change architecture?
Organizational design answers the question of how the organization itself should be structured and how it should collaborate.
Change architecture, on the other hand, answers how the change process leading to a new state is designed. It connects, for example, governance, participation, communication, and change management measures.
What role does culture play in organizational design?
A new organizational design can change expectations regarding responsibility, collaboration, and leadership. Therefore, it’s important to consider whether existing cultural patterns support the desired organizational model.
If the goal is to further develop values, norms, and behavioral patterns themselves, cultural development is the appropriate area of focus.
Are agile organizational forms part of organizational design?
Agile or dynamic organizational forms can be a possible answer to certain requirements, but they are not an end in themselves and not a standard solution.
What matters is which organizational design fits the tasks, strategy, and context. This page also follows your established semantic distinction: Agile organization belongs in the context of organizational design when discussing change , while agile leadership and agile collaboration address separate issues at the leadership and team levels, respectively.