Workflow management

Why it matters

Hand-offs are where time and information disappear. Each one adds waiting, a chance of misunderstanding and a reason to chase. In a business of eight to thirty people, poorly designed workflows can quietly consume a day or two of each person’s week in checking, chasing and re-entering. Fixing them is often the difference between needing to hire and not.

Find the bottleneck before you redesign anything

Every workflow has one step that limits its throughput. In a design studio it might be the one senior reviewer every job must pass through. In a wholesaler it might be the person who approves credit. Work piles up in front of that step and the rest of the team either waits or starts new work that will also pile up. Speeding up anything other than the bottleneck changes nothing.

To find it, look for the queue. Where do tasks sit longest? Who has the most "waiting on me" items? Count work-in-progress at each stage over a week; the stage with the biggest pile is your constraint. Fix it first by removing work from that person, raising the limit of what others can approve, or splitting the step.

Design the hand-offs, not just the tasks

Most workflow pain lives between tasks rather than within them. A good hand-off answers four questions automatically: who gets this next, what do they need to do it, when is it due, and how will they know it has arrived? When those answers depend on someone remembering to send an email, the hand-off will eventually fail.

The practical fix is to carry the information with the work. If a job moves from sales to production, the production team should see the quote, the customer’s notes and the delivery date in the same record, not in three email threads. Decide one system where each type of work lives and make that the only place it is updated.

• Define the next owner for every hand-off; "the team" is not an owner.
• Attach what the next person needs to the work item itself.
• Set a due time or service level for each stage so delays are visible.
• Notify through a channel people actually watch, and only when action is needed.

Choose the right level of tooling

Workflows can run on a whiteboard, a shared spreadsheet, a task board, the workflow features inside the software you already own, or a dedicated automation platform. The right level depends on volume, how many people touch each item, and how much the steps vary. A five-person team handling ten jobs a week does fine with a board and clear rules. Thirty people and two hundred items a week need software that routes work and shows queues.

Start with the tools you have. Most accounting, job management, CRM and help desk products include assignment, status and reminder features that go unused. Only when the workflow is stable and the manual version is clearly working should you connect systems or automate the routing. Where several systems need to talk to each other, integration work is often the unlock; SMBH Consulting’s integration services exist for exactly this kind of hand-off problem.

Make the queue visible and review it weekly

A workflow you cannot see is a workflow you manage by complaint. Whatever tooling you use, make sure anyone can see how many items are at each stage, how old they are and who holds them. A short weekly review of the oldest items at each stage catches stuck work before customers do, and shows whether a change has actually helped.

Visibility also changes behaviour. When the whole team can see that eleven quotes are waiting on one person, the conversation about fixing it starts on its own.

How to redesign a workflow

1. Pick one workflow with visible pain Chasing, missed deadlines or repeated questions are the signals. Start with a single workflow.
2. Walk a real item through it Record every task, hand-off, decision and wait for one recent example from trigger to finish.
3. Find the bottleneck Count items waiting at each stage for a week. The biggest pile is your constraint.
4. Relieve the constraint first Remove work from that step, delegate approvals or split it. Ignore the rest for now.
5. Redesign the hand-offs Name the next owner, attach the information, set a due time, notify once.
6. Run it on the simplest tool that works A board or built-in features before integration or automation.
7. Make the queue visible and review weekly Oldest items at each stage, every week, with the team.
8. Automate once stable When the manual version has run cleanly for a couple of months, connect systems or add rules.

Real-world example

A Melbourne marketing agency unblocks client onboarding

Northbank Creative has fourteen staff and signs three or four new clients a month. Onboarding a client takes an average of nineteen working days from signed proposal to first campaign brief, and clients regularly ask the same questions twice. The operations lead walks one recent client through the workflow and finds eleven hand-offs across sales, accounts, the creative director and the account manager, with the creative director approving every brief personally.

Counting work-in-progress shows seven briefs waiting on the creative director at any time. The agency lets senior account managers approve briefs under a set budget, moves the kick-off questionnaire into the project management tool so answers travel with the job, and sets a three-day service level on each stage with a Monday review of anything older. Three months later, onboarding averages eight working days, the creative director reviews two briefs a week instead of twelve, and the team takes on two extra clients without hiring.

Common mistakes

• Speeding up the wrong step Making non-bottleneck steps faster just builds a bigger pile at the constraint. Find the queue and fix that step first.
• Hand-offs by email Email hides work, loses attachments and has no status. Move work items into a system where the next owner and due date are explicit.
• Automating a broken workflow Automation makes a bad workflow fail faster and more expensively. Run it manually and cleanly first.
• Everything needs the owner’s approval This caps the business at the owner’s hours. Define approval limits others can work within.
• No visible queue If nobody can see what is waiting where, problems surface as customer complaints rather than as early warnings.

KPIs to track

• End-to-end lead time Working days from trigger to completion for a given workflow. The headline measure of improvement.
• Work-in-progress per stage Items waiting at each step. A persistently large pile marks your bottleneck.
• Items past their stage due time How many hand-offs are breaching the agreed service level each week. Aim for near zero.
• Touches per item How many times a piece of work changes hands. Fewer hand-offs usually means faster, cleaner work.
• Chase rate How often someone has to ask "where is this up to?" A rough but honest signal of workflow health.

Frequently asked questions

What is the difference between a process and a workflow?

A process is the what: the repeatable sequence that turns an input into an output. A workflow is the how: the specific route a work item takes through people, systems and approvals. You improve processes by redesigning their workflows.

Do I need workflow software?

Not until the manual version is stable and volume justifies it. Most small businesses get a long way with a visual board and the assignment features already inside their existing software.

How do I stop being the bottleneck as the owner?

Write down which decisions and approvals others may make, with limits (for example, discounts up to a set percentage, refunds up to a set dollar amount), and check a sample afterwards rather than approving everything in advance.

How many workflows should I redesign at once?

One. Fix it, let it settle for a month or two, then move to the next. Changing several at once makes it impossible to tell what worked.

Key takeaways

• Work gets stuck at hand-offs and bottlenecks, not usually within tasks.
• Find the queue, relieve that constraint first, and ignore the rest until it is done.
• Every hand-off should name the next owner, carry the information and have a due time.
• Use the simplest tooling that works and automate only once the workflow is stable.
• Make the queue visible and review the oldest items every week.