The simple idea
Look at where work waits before deciding what the team needs next. Clear ownership and sensible approval boundaries can reveal whether the gap is capacity, coordination or both.
Follow one delayed job
A customer is waiting for an answer. A quote needs approval. Someone needs information buried in a message. Your team is working, but the next step still lands with you. Being busy and moving work forward are not always the same thing.
Start with one recent job that took longer than expected. Reconstruct what happened from the first request to the last update. Use the actual messages, notes and task history rather than asking everyone to remember a typical week.
Mark where work paused. Was someone doing the task, waiting for a decision, looking for information or unsure who should act? A fictional example: a quote sits untouched because the salesperson expects the owner to approve it, while the owner thinks the office has already sent it. The delay is an unclear handoff, not necessarily a lack of effort.
Separate capacity from coordination
Sometimes you really do need more people. If capable staff have clear instructions, the right information and authority to proceed, yet the workload consistently exceeds available time, capacity deserves attention. Skills, coverage and workload peaks matter too.
But another person may inherit the same waiting points if every exception still needs your answer. Look at both questions: how much work needs doing, and how much time is lost between steps? Avoid using a process problem to dismiss a genuine staffing need, or assuming hiring alone will solve unclear responsibilities.
Name the owner and the next action
For the delayed job, write down one person responsible for moving it forward. That does not mean they must do every task. It means they can see the status, arrange the next step and raise a blocker.
Replace vague instructions such as “follow up” with something observable: confirm the missing measurement, prepare the revised quote or ask the customer to choose an appointment. Agree when the team will review it and where the update belongs. Keep essential context with the work, rather than scattered across private messages.
- Who owns the next action?
- What information do they need?
- What signals that their step is complete?
- Who receives it next, and what should happen if it stalls?
Make approval boundaries clear
Some decisions should remain with the owner. The useful distinction is which ones, and why. Document the situations that require approval, the information needed for a decision and what staff may handle within agreed limits.
For example, a team might prepare a standard quote within approved scope but escalate an unusual request before making a commitment. That is an illustration, not a rule for every business. Agree boundaries that fit your responsibilities. Give urgent exceptions a clear route, so work is not left waiting in an inbox nobody is watching.
Automate a clear handoff, not an assumption
Once the steps are understood, a routine notification, task assignment or status update may be suitable for workflow automation. Start small. Confirm the tools can support the intended connection and test what happens when information is missing, a request is duplicated or a connection fails.
Keep a person responsible for reviewing exceptions. A reminder being sent does not prove that someone acted. Limit access to the information each role needs, and avoid copying sensitive details into unnecessary notifications. If existing tools cannot show ownership and status clearly, a scoped business software project may be worth exploring; a new system is not automatically the first answer.
Review whether work moves without chasing
Try the revised process on a manageable piece of work. Check whether the next person received enough information, whether approvals happened at the right point and whether someone noticed a stalled task without you prompting them.
Ask the team what still required guessing. Adjust the handoff before expanding it. The aim is not to remove the owner from every decision. It is to make necessary decisions visible and let agreed routine work continue without relying on your memory.
Where does work stop until you step in?
Bring one example to a discovery call. We can discuss the people, tools and handoffs involved, and where a clearer process may help. You do not need a complete systems plan to start the conversation.
Request a Discovery Call