Designing one automated process from several people's expertise

Yes, and it's the only way it works. The sales lead knows what good looks like, finance knows the rules, and the person who does the job knows the exceptions. Put them around one drawing, give one person the pen, and keep the builder in the room.

By Matthew Steele3 min read28 October 2026

Overhead view of a table covered in a long printed process map, four pairs of hands pointing at different steps
Illustrative scene, not a customer's premises.

Who needs to be in the room

There are five roles, and in a small company that might be three people:

  • The doer: whoever runs the process today. They know the exceptions, which is most of the design.
  • The approver: whoever signs it off at the end – the quote, the order, the credit limit. They know what they're actually checking for.
  • The rule-holder: finance, compliance, or the owner. They know what must never happen.
  • The customer of the output: the next team along, or the actual customer. They know what good looks like from the receiving end.
  • The builder: the person or firm who'll make it. Their job in the room is to listen and ask what happens when.

One person holds the pen. That's the "one head" in the question, and it's a real role – they decide what goes on the drawing when two experts disagree, and they decide when the design is finished. Usually it's the department head whose process it is. Not the builder, who'll design for what's easy to build.

How to run it

Five roles around one drawingA process line of six steps runs across the middle. Above it sit the approver and the rule-holder; below it the doer, the customer of the output and the builder, who listens. One person holds the pen. To the right, the exceptions list, where most of the design lives.One drawing, one penStep 1Step 2Step 3Step 4Step 5Step 6The approverknows what they actually check forThe rule-holderknows what must never happenThe doerknows the exceptionsThe customer of the outputknows what good looks likeThe builderlistens, asks "what happens when"ExceptionsThe customer who wantsit emailed.The supplier whoseinvoices never match.The quote that needsthe owner's eye.Most of the design is here.One person holds the pen and decides when the drawing is finished. Usually the department head. Never the builder.
Three sessions, one drawing. Most of the design ends up in the exceptions list.

Session one is drawing today. The process as it actually runs, not the version in the procedure manual. Every step, who does it, what system it lives in, and a growing list down the side of the exceptions – the customer who always wants it emailed, the supplier whose invoices never match, the quote that needs the owner's eye. The doer talks, everyone else asks.

Session two is drawing tomorrow. The same process with the steps a tool could take marked, the steps that stay with a person marked, and every exception assigned to one or the other. This is where the rule-holder earns their seat. Anything that touches money, a customer promise or someone's job gets a human step until proven otherwise.

Session three is running 5 real cases. Take 5 actual cases from last month, including two awkward ones, and walk them through the new drawing step by step. The design changes more in this session than in the other two. Only once it's survived 5 real cases does the builder start.

Most of the design is in the exceptions

The happy path is easy, and everyone agrees on it in 20 minutes. The exceptions list is the real specification. In our experience a process that looks like 8 steps in the manual is 40 steps once the exceptions are written down, and the tool that works is the one built for the 40 – with a clear rule for what happens when it meets a forty-first: it stops and asks a person.

The things nobody can put into words

Some of what you need isn't in anyone's head as a rule. It's in how the doer reacts to a particular email. The way to get it out is to watch them do the job for an hour, with the builder taking notes, and ask "why did you do that?" at every pause. Getting knowledge out of people's heads goes into this properly.