What does a process owner do?

A short story

At a wholesaler, late deliveries came up in every management meeting. Sales blamed the warehouse, the warehouse blamed planning, and planning blamed the late order changes from sales. Each department owned its own piece. Nobody owned the flow.

The company named its logistics lead owner of order to delivery, with the authority to change hand-over rules across departments. The first decision took one meeting: order changes after a set moment go through planning, not straight to the warehouse. The same problem had been discussed for a year. (An illustrative example, not a client case.)

What does a process owner do, day to day?

• keeps one current picture of the process: the map, the task cards and the rules;
• decides on exceptions and rule changes, or names who does;
• watches two or three measures the team trusts;
• runs the reviews, and acts on review triggers such as a new system or an incident;
• resolves hand-over problems between departments;
• makes sure someone can take over each critical step.

What goes wrong without an owner?

• First: every department optimises its own piece of the process
• Then: the documentation drifts, because updating it is nobody's job
• Next: problems at hand-overs become standing agenda items that are discussed and never decided
• Eventually: the process runs on the few people who know how to work around it — and stops when they are away

Who should own a process in an SME?

Someone senior enough to change how the process runs across departments, close enough to the work to understand it, and with time for a short review every month. Often that is the manager whose team does most of the steps. It does not have to be the most senior person in the company.

The owner is not the same as the expert. The expert holds the knowledge; the owner makes sure it is captured, kept current and used. When owner and expert are the same person, you have found a key-person dependency worth solving first.

Is a process owner the same as a department head?

Not necessarily. A department head is responsible for people and a budget; a process owner is responsible for a flow of work that usually crosses departments. In a small company one person can be both — as long as the process duties are explicit and not lost in the rest of the job.

How much time does owning a process take?

Less than most managers fear, once the basics are in place. The heavy part is the start: agreeing the map, the rules and the measures. After that it is a short monthly review, decisions on the exceptions that come up, and a check whenever something changes.

How MentX helps

MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.

Every process we map gets a named owner from the first workshop. When we capture your operations, the owner, the decision rules, the exceptions and the review triggers are recorded together with the process, so ownership is visible instead of assumed.

What to do this quarter

1. List your core processes and write one name next to each.
2. Where you cannot, or where you wrote two names, you have found the first gap.
3. Agree three duties with each owner: the current picture, decisions on exceptions, and the review.
4. Choose two or three measures per process that the owner already trusts.
5. Put a short monthly review in the calendar.