Organizational Design

Process Management and Organization Design: Why They Belong Together

Marin Niehues6 November 202511 min read

A workshop wall with sticky notes on problems and solutions

Process management and organization design must be planned together, because a process runs reliably only when roles and decision paths fit it. German business administration calls this pair process organization and structural organization. Redrawing workflows without reassigning accountability yields a clean diagram and the same operation. Changing structures without knowing the workflows moves the friction into other units. This article shows where the two disciplines connect, the sequence in which the approach proves itself and how the executive team recognizes success.

What is the difference between organizational structure and process organization?

Organizational structure defines who in the company holds which tasks and decision rights, while process organization defines the sequence and handovers through which work gets done. The distinction goes back to classical German organization theory, shaped above all by Erich Kosiol. It is an analytical tool: both sides describe the same company, once as structure and once as flow.

Structure shows up in the organization chart and in the allocation of decision rights. Process organization shows up in process maps and approval chains. Organization design mainly shapes the first side, process management the second. Problems arise where the two do not fit: a workflow that runs across three functions without anyone owning the whole, or a position that decides according to the chart but is never consulted in the workflow.

The cut of the functions can itself follow the workflow. When a process-oriented organization outperforms a functional or divisional structure is compared in Funktionale, divisionale oder Prozessorganisation im Vergleich.

Why do process management and organization design often work separately?

The two disciplines often work separately because they come from different traditions and in many companies answer to different sponsors. Process management grew out of quality programs and business process reengineering, which Michael Hammer and James Champy popularised in 1993. Organization design grew out of strategy and HR work. Models such as Jay Galbraith's Star Model have connected the two for decades, yet in practice they still often work apart.

Both disciplines have their own methods and their own committees, often their own sponsors on the executive team as well. A process project is set up in the line, a reorganisation comes from the executive team, and the two meet only when the result is to be rolled out. It then turns out that the new process requires a decision that is assigned to nobody in the structure. Or the new structure cuts through a workflow precisely where most handovers take place.

The Star Model describes an organization through five design areas, namely strategy, structure, processes as well as rewards and people. Its central claim is that the five areas must fit one another. If a company changes only its structure while processes and rewards stay the same, the organization works against the new structure. For decision-makers the model is a checklist: every change in one area raises the question of what it means for the other four.

From a delivery perspective, the damage occurs at these seams. Customers notice lead time and the reliability with which a promise is kept. Both depend on process and organization at the same time. The interplay is captured in the Operating Model: it describes how a company delivers its output and defines workflows and roles together for that purpose, along with steering.

Four seams where process and organization meet

Collaboration between the two disciplines can be tested at four seams. Each can be assessed in a workshop with the function heads within a few hours.

  • Accountability: every process needs an owner with a mandate over the entire workflow. Without a mandate, accountability ends at the functional boundary.
  • Decision: at every step with an approval, it must be clear who decides. This includes a fixed deadline. The procedure is described in Entscheidungsrechte klären.
  • Interface: every handover between functions needs a defined output and an acceptance criterion as well as a contact person.
  • Steering: metrics must be captured along the entire process, otherwise each function optimizes its own segment and worsens the whole.

The four seams also form an order of urgency. Without accountability, the other three help little, because nobody drives improvements. Without steering, every improvement remains a claim, because nobody can measure it.

Which methods are used in process management?

The most important methods in process management are modeling with BPMN and value stream mapping. They are complemented by SIPOC as an overview, process mining as data analysis and DMAIC from Six Sigma as an improvement procedure.

  • BPMN (Business Process Model and Notation): the international standard for graphical process modeling, maintained by the Object Management Group and standardized as ISO/IEC 19510. BPMN suits the unambiguous description of workflows with branches and roles in swimlanes, including as a template for later automation.
  • Value stream mapping: originates in lean management, described by Mike Rother and John Shook, and maps a workflow from customer order to delivery, with processing and waiting times for each step. It reveals how much of the lead time is actual work.
  • SIPOC: a one-page overview of suppliers, inputs, process steps, outputs and customers. It suits the start, before a workflow is modeled in detail.
  • Process mining: analyses event logs from ERP and workflow systems and reconstructs the actual workflow with all its variants. It reveals workarounds that no workshop mentions.
  • DMAIC: the improvement cycle from Six Sigma with the steps define, measure, analyze, improve and control, suited to workflows with measurable quality problems.

The choice follows the question to be answered. If waiting times and lead time are the issue, start with value stream mapping. If clear responsibilities in a workflow with many variants are the issue, BPMN is the right tool. If the data sits in systems and the lived workflow presumably deviates from the documented one, process mining delivers the fastest diagnosis. For the link to the organization, the same applies to every method: every swimlane and every process step gets a role, and every role appears in the organization chart.

A four-step approach

The approach follows the logic Understand, Build, Introduce. A fourth step secures the effect.

In the first step (Understand), process and organization are surveyed together. For the most important workflows, the actual course is mapped, including the workarounds that have become entrenched in daily practice. In parallel, a picture of responsibilities emerges: who actually decides today, and where does this deviate from the organization chart? How such an assessment works is described in Organisationsdiagnose: Wie eine Bestandsaufnahme abläuft.

In the second step, Build, the target picture emerges. Workflows are designed from the customer's perspective, then roles and decision paths are tailored so that every workflow has an owner and every approval a decision-maker. Structure and process are worked on in the same workshops, so that trade-offs become visible while they can still be resolved cheaply.

In the third step, Introduce, the target picture is transferred into operation. This includes adapting job profiles and target systems as well as enabling the managers who apply the new workflow daily. A gradual roll-out in a pilot area provides experience before the model is transferred to further functions.

In the fourth step, the effect is secured. A fixed steering rhythm, for example a monthly meeting of the process owners with the executive team, reviews the metrics. Obstacles are also cleared there. Without this rhythm, there is no one who notices deviations, and entrenched workarounds return within a few months.

How can you tell whether process and organization fit together?

Process and organization fit together when lead time and on-time delivery, along with the rework rate, sit stably at target level across the entire workflow. Lead time measures a workflow from trigger to result. On-time delivery shows the match with the customer promise, the rework rate the quality of handovers. All three are process metrics, and all three respond to organizational decisions. A long lead time with short processing time indicates waiting at handovers. A high rework rate points to unclear acceptance criteria between functions.

Comparing the approaches makes the difference visible.

How structure and workflows fit together as a whole is set out in the article characteristics and metrics of a high-performing organization.

Niehues Consulting as a partner for process and organization

Niehues Consulting connects both disciplines from a delivery perspective. Founder Marin Niehues builds organizations that deliver and brings AI into operations. His projects range from VC-funded scale-ups to DAX 40 corporations, with assignments in 20+ countries on six continents.

Delivery management and organization design belong together here. As delivery manager, project manager or product owner, Marin Niehues steers initiatives in live operation and therefore knows the points where workflows break in practice. The approach follows the Niehues Delivery Model with its phases Understand, Build and Introduce. For process and organization, three of its review questions matter most: who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? And which metric shows after 90 days that the solution is landing? From this emerge structures and roles that fit the workflows and hold in daily business as well as in transformation.

The free 30-minute initial consultation clarifies at which seam your company has the greatest leverage: book an initial consultation.

Frequently asked questions

What is the difference between process management and organization design?

Process management describes and improves workflows, that is the sequence of steps that produces a result for the customer. Organization design shapes structures and roles as well as the decision paths that own these workflows. Both disciplines describe the same company from different angles and only together deliver a complete operating model.

What does a process owner do?

A process owner is accountable for the result and lead time of a workflow across all functions involved. The owner determines how the workflow is designed and clears obstacles at the handovers. People and budget remain with the line, which is why both mandates are delineated in writing.

Who should be responsible for processes in a company?

Every core workflow needs a process owner with a mandate over the entire course, including across functional boundaries. The owner decides on the design of the workflow and reports to the executive team. Line management remains responsible for people and professional quality.

What is Galbraith's Star Model?

Jay Galbraith's Star Model describes an organization through five design areas: strategy, structure, processes, rewards and people. It requires all five areas to fit one another. Changing only one creates friction in the other four.

What is a process-oriented organization?

A process-oriented organization cuts its units along the core workflows from customer order to delivery. Process owners hold a strong mandate, while functions contribute expertise. It pays off when a few core workflows drive the business and handovers between functions drive lead time.

Where do you start when processes and structure do not fit?

The starting point is a joint assessment of the most important workflows and the actual decision paths. It shows at which handovers time is lost and which approvals are assigned to no accountable person. On this basis a target picture emerges that describes workflows and roles together.

Which metrics show that process and organization fit together?

Lead time and on-time delivery provide the answer, complemented by the rework rate at handovers. If lead time falls while processing time stays the same, waiting at handovers has been reduced. A falling rework rate shows that acceptance criteria and responsibilities have become clearer.

Let’s talk about your initiative.

In 30 minutes we clarify where your organization stands and which step will pay off most now.

Request a consultation

30 minutes · free · no obligation