The problem addressed by the Process Owner role
To the point: Who is responsible for a process that runs across three departments and affects several systems? A critical gap in medium-sized companies.
We have observed a recurring pattern in the DACH midmarket for over 1,200 projects: processes are running, but no one is explicitly responsible for their performance. This typically costs 5-15% of process efficiency. The Process Owner role was invented to solve this problem: a clear assignment of end-to-end process responsibility without the need to hire a new manager.
The role at a glance
In a nutshell: A Process Owner combines three responsibilities: Design ownership, performance accountability and continuous optimization - often as an additional task to an existing position.
Tasks and powers
A process owner has five typical tasks: (1) process design and documentation, (2) KPI definition and monitoring, (3) identification of weaknesses and optimization initiative, (4) change communication and stakeholder management, (5) empowerment and knowledge transfer.
Practical example: Anonymized Dreher methodology project
To the point: A medium-sized manufacturing company with 6 variants of the same order-to-cash process - and no clear owner. We defined the role, appointed a person and measured three results.
An international kitchen manufacturer operated six process variants for contract orders. We appointed a process owner, consolidated the variants, and configured ERP automation.
Results after 4 months: Data quality: 75% reduction in incorrect rework; turnaround time: 36% faster (median 14 days); staff burden: 0.5 FTE saved.
Frequent errors during implementation
To the point: The three mistakes: too broad a role, too little time, wrong person.
1. assigning too broad a role. Define 3-5 specific process stages, not "everything from A to Z".
2. no protected time. Recommendation: 20% protected time for a "dual role" PO.
3. wrong person. Choose someone with assertiveness, data affinity and patience - not tech expertise.
Application in 2-3 industry verticals
To the point: The Process Owner role has different weights depending on the industry.
Manufacturing: 30-40% capacity protected; strong data affinity and store floor collaboration required.
Services: 20% capacity; closer to the administrative/ERP core; more intensive IT collaboration.
Hybrid/variant production: Very strategic; process owner as governance layer for standardization vs. flexibility.
Frequently Asked Questions
A Process Owner has no direct authority over staff. Power comes from three sources: a management mandate, data (KPIs), and the right to escalate. It only works when senior leadership actively backs the role.
Yes, with limits. One owner running two sub-processes is realistic (20% + 20% = 40% of capacity). Shared ownership requires explicit boundary-setting.
Ideally three to five years. Enough time for two or three optimisation cycles. After five-plus years there's a risk of insularity.
Three reasons: the role is unclear, no protected time, the wrong person in seat. In SMEs there's often a fourth: no active governance support from the management board.
Next steps
The introduction or redesign of a Process Owner role is a strategic project. A common start is a workshop with management and the top 5 process owners to write clear owner profiles. This takes 2-3 days and saves 100+ hours of process chaos over the next year.
|
Matthias supports medium-sized companies through complex ERP implementations and specialises in the methodical integration of process design and system selection. |