Organizational Design

Organizational Structure and Process Organization: How Both Work Together So an Organization Delivers

Marin Niehues30 July 202611 min read

Two colleagues structuring sticky notes on a glass wall

Organizational structure defines who is responsible, process organization defines how work flows to a result, and an organization delivers only when the two are aligned. In practice, companies tend to design the structure and leave the flow of work to chance. This article clarifies the terms, sets out the right design sequence and provides a maturity model and the metrics for measuring how well both fit.

What is the difference between organizational structure and process organization?

Organizational structure describes how a company is divided into positions and units with their reporting lines, while process organization describes the sequence in which tasks are completed across those units. The first answers who is responsible. The second answers how an order travels from receipt to result.

The distinction has shaped German-speaking management science for decades, where the two are known as Aufbauorganisation and Ablauforganisation. Fritz Nordsieck argued early on that organization should follow the flow of work. Erich Kosiol set out both perspectives systematically in 1962 in his book “Organization der Unternehmung”. His analysis-synthesis approach first breaks the overall task into sub-tasks and then groups them into positions. For the flow of work, he breaks tasks into work steps and arranges them in time and space. The separation was meant as an analytical tool. In everyday business it has often become an organizational divide: HR or management owns the structure, while processes are owned by nobody or by a process team without authority.

Classic forms of structure include the line organization with a single superior per position, the multiple-line system with separate functional reporting lines, the line-and-staff organization and the matrix with two equally ranked axes. Which basic form suits which situation is covered in Functional, divisional or process organization compared.

Why structure and process drift apart

Structure and process drift apart because they change at different speeds. Structures are rebuilt in large steps, usually when leadership changes or a strategy program starts. Processes change continuously, with every new product and every new system. After a few years, the organization chart describes a division of labor that no longer exists in daily work.

The consequences are measurable, even if they are rarely measured. A customer order passes through many departments, and every boundary creates a handover with waiting time. Approvals travel up and down the line because the decision sits where the structure places it, far from where the information is available. Coordination meetings replace clear responsibilities. The processing time of a case is often short, the lead time long, and the difference consists of waiting.

Research describes a well-known pattern here. Melvin Conway observed in 1968 that organizations design systems whose structure mirrors their own communication structure. An empirical study of software products tested this mirroring hypothesis and confirmed it: loosely coupled organizations produce more modular products than tightly coupled ones. For organization design the consequence is clear. Whoever draws the structure also decides where processes flow smoothly and where they hit boundaries.

Which comes first, structure or process?

Design the flow of the core value-creating processes first, and then draw the structure along those processes. Structure is the tool, while the process produces the result for the customer. This sequence reflects the idea behind process organization and became internationally known through the business process reengineering approach that Michael Hammer and James Champy published in 1993.

The sequence applies with clear criteria. Where core processes take a customer order across three or more unit boundaries, the process takes priority and cross-functional process ownership is mandatory. Where value comes mainly from deep specialization, for example in legal or research, functional grouping remains sensible and the flow is secured through clear handover rules. In fast-growing companies whose processes change every quarter, keep the structure deliberately lean and review it at shorter intervals.

How do you align structure and process?

You align them by counting the interfaces of the core processes and drawing the structure so that most handovers take place within a single unit. A five-step approach has proven effective.

  1. Identify core processes: determine which three to seven processes account for most of the value creation, for example from quote to invoice or from incident to resolution.
  2. Map the process: capture each core process with its steps, the units involved and the waiting time between steps. Where system data exists, process mining provides a precise picture.
  3. Assess interfaces: count the handovers per process and flag those with the longest waiting time or the highest rework rate.
  4. Draw the structure: group positions so that connected work sits in one unit. Where a boundary remains, give it a handover rule with a quality criterion.
  5. Set decision rights and metrics: assign an accountable role to every recurring decision in the process and a target metric to every core process.

Step 5 is the one most often skipped and the one that most determines success. A new structure without clear decision rights produces the same approval loops as the old one. How to clarify decision rights with RACI or RAPID is shown in Clarifying decision rights. How process management and organization design work together permanently is described in Thinking process management and organization design together.

A maturity model for alignment

The following model shows how far structure and process are aligned in your company. It serves management as an assessment tool and as the starting point for a diagnosis.

Before assigning a level, check whether your process descriptions show the process as it is actually lived, because level 2 often looks like level 4 on paper. The step to level 3 matters most economically, because only measurement shows which interface slows delivery. Plan the reorganisation after the measurement.

Which metrics show whether structure and process fit?

The lead time of a core process relative to its pure processing time shows most clearly whether structure and process fit. If processing time is far below lead time, work is waiting at boundaries, in queues or for approvals. This metric is called flow efficiency and can be captured with simple timestamps.

  • lead time per core process from trigger to result
  • flow efficiency as the share of processing time in lead time
  • number of handovers between units per case
  • rework rate at the critical interfaces
  • on-time delivery to the customer
  • number of escalations that force a decision above the accountable role

Measure these values before the restructuring as a baseline and again after 90 days. Only the comparison shows whether the new structure speeds up the process or merely relabels it. The metrics that capture an organization's overall delivery capability are described in Measuring delivery capability.

AI changes the process first

AI applications intervene in process organization first. An assistant that classifies incoming documents, or an agent that handles standard cases independently, changes the sequence and duration of work steps before anything changes in the organization chart. Those who know their processes recognize early which handovers disappear and where new checks become necessary.

This leads to a recommendation on sequence. Introduce AI into the process, measure the effect and adjust the structure afterwards. Creating new AI units in the organization chart first builds responsibilities for processes that do not yet exist. The article characteristics and metrics of a high-performing organization places this topic in the wider context.

How Niehues Consulting brings structure and process together

Niehues Consulting designs organizations from the delivery perspective and therefore starts with the process. The basis is the Niehues Delivery Model with its phases Understand, Build and Embed. Three of its questions matter most for aligning structure and process. Who decides, who delivers, who uses? The answer sets decision rights along the process before the structure is drawn. Which roles, decision paths and interfaces does operations need? The answer translates the measured process into positions and handover rules. Which metric shows after 90 days that the solution is landing? The answer makes the reorganisation verifiable.

Marin Niehues leads such programs as delivery manager, project manager or product owner, in projects from VC-backed scale-ups to DAX 40 groups and across 20+ countries on six continents. The starting point is a free 30-minute initial consultation to establish your organization's maturity level and which core process offers the greatest leverage.

Frequently asked questions

What are the elements of an organizational structure?

An organizational structure consists of positions, management positions, staff positions and departments, along with the reporting lines between them. It is made visible in the organization chart and complemented by job descriptions that record the tasks and authority of each position.

What does process organization include?

Process organization covers the sequence of work steps with their arrangement in time and space, as well as the handovers between units. It is documented in process maps and flowcharts and measured through lead time and on-time delivery.

Is process organization the same as a process-based structure?

Process organization is the umbrella term for designing workflows, while a process-based structure is a form of organizational structure that builds units around core processes. Every company has a process organization, but only some draw their structure deliberately along it.

What is an example of structure and process organization?

In the order fulfillment of a machinery manufacturer, the structure defines that sales, engineering and production are separate departments with their own heads. The process organization defines the sequence in which an order passes through them and which documents must be ready at each handover. If approval of technical changes sits in a fourth department, every query extends the lead time.

Who is responsible for process organization?

Each core process should have a named process owner accountable for its performance and improvement across unit boundaries. This role needs a mandate towards line managers and a metric by which it is measured. Overall accountability for aligning structure and process sits with management.

How often should structure and processes be reviewed?

Review the core process metrics continuously within the steering rhythm, and the structure once a year against those metrics. An unscheduled review is due when a new product, a new core system or an AI application changes a core process. In fast-growing companies, shorten the interval.

Which type of organizational structure is best?

The best structure is the one in which most handovers of the core processes take place within a single unit. For companies with one product and one market this is often the functional organization, for companies with several distinct businesses the divisional one. A matrix pays off only when two steering axes are of equal weight and decision rights between them are clearly settled.

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