Is the work clear?
Can the people involved explain what starts it, who owns the next move, what information is required, which decisions they can make, when an exception needs escalation, and what finished means? If not, clarify the process first.
A decision framework from Seth Woodall
Process, person, or technology?
Owners should use automation to carry clear, repeatable work—not to automate confusion.
Start with a visible recurring task, define its trigger, inputs, decision rules, exception path, accountable person, and proof of completion, then choose the simplest useful technology.
By Seth Woodall · Updated
The decision order
Start with the work.
Is responsible capacity sufficient?
If the work is clear but demand consistently exceeds responsible capacity, the answer may involve a person, training, role design, or a better allocation of the people already there.
Is the repetitive part stable enough for technology?
Technology earns a place when the task happens often, follows a clear pattern, has known inputs and outputs, removes meaningful avoidable work, and still has a person accountable for the result.
Clarify the work.
Make the trigger, responsibility, information, decisions, exceptions, and definition of done visible.
Test the real capacity gap.
Use persistent measured demand—not one busy week—to decide whether capacity, capability, or role design must change.
Carry stable repetition.
Use technology where the pattern is frequent and clear and a capable person remains accountable.
Use more than one when the work calls for it.
A sensible improvement may combine clearer work, capable people, and useful technology.
A fictional scheduling example
Why the order matters.
Imagine a field-service company deciding whether it needs scheduling software or another coordinator. The team cannot agree on what moves an accepted estimate into scheduling, which job details are required, or which exceptions require the owner.
The first need is process clarity: define the acceptance trigger, assign the responsible coordinator, identify the required information, and set the escalation boundary. Once that flow works, measure whether responsible capacity is still insufficient. Then automate stable repetitive steps—such as copying approved fields, sending the standard confirmation, or alerting the coordinator when information is missing—while keeping scope, safety, and capacity exceptions with people.
The point is not to force every problem into one category. It is to make the work clear enough to choose a sensible next step.
Choose the next move
What ambiguous operating problem are you trying to solve?
Bring one recurring example to a focused conversation with Seth Woodall.
Request an Owner Bottleneck Review with Seth