Compare the two operating modes
At five people, a question can be answered aloud. Everyone may know which client is unusual, who is overloaded, and what “done” means. The owner can repair ambiguity by noticing it.
At ten people, there are more possible handoffs, more simultaneous work, and more distance between the person who made a promise and the person expected to deliver it. The same helpful behavior—asking the owner—turns the owner into a queue.
Map the transition across five fields:
| Field | Informal mode | Strained mode |
|---|---|---|
| Ownership | Remembered by the group | Assumed by several people or nobody |
| Status | Learned in conversation | Scattered across messages and meetings |
| Questions | Answered by the nearest expert | Routed repeatedly to the owner |
| Exceptions | Remembered as stories | Rediscovered after a mistake |
| Recovery | Owner notices and intervenes | Delay remains invisible |
Start with recurring questions
Do not document the entire company. For one week, capture every question that interrupts an owner or experienced employee:
- What happens next?
- Who is waiting on this?
- Where is the current file?
- Has the client approved it?
- Is this client an exception?
- Who can decide?
Group the questions by one recurring workflow. They reveal where the current process depends on unavailable context.
Map work and decision rights separately
A task owner can perform work without having authority to waive a requirement, change a deadline, approve a refund, or promise a client outcome.
For each handoff, write:
- person doing the work;
- person accountable for completion;
- person allowed to decide an exception;
- evidence that changes the status; and
- time after which silence becomes an escalation.
This prevents a common failed fix: assigning every task while leaving every decision with the owner.
Preserve exceptions without freezing the process
Document only exceptions that change routing, evidence, timing, or authority. Record why the exception exists, who approved it, when it should be reviewed, and how a new employee can recognize it.
Do not turn every past preference into a permanent rule. Some exceptions are workarounds for a condition that no longer exists.
Choose the smallest improvement
For the first failing workflow:
- create one visible queue;
- assign one current owner per item;
- define four or five meaningful states;
- attach the authoritative artifact;
- name decision rights and escalation time; and
- hold a short weekly exception review.
Software may later support this map. The immediate outcome is that work can move without the owner serving as memory, router, and recovery system.