Websites. Design. Marketing. Automation.

All articles

Automation3 min read

Start with the task you keep copying.

Watch one piece of work travel through the business. The copying, chasing and checking will give you a useful place to start.

A request arrives by email. Someone copies the details into a spreadsheet, creates a task, assigns a colleague and writes back to say it has arrived.

Tomorrow, another request. Same tabs. Same copying. Probably the same sentence in the reply.

That is a useful place to start looking at automation. You can see the work, describe the steps and ask the person doing it where the time goes.

Watch a real request go through

Ask them to show you the last one they handled. Follow it from arrival to completion, including the parts they do from memory.

Which details did they copy? How did they choose the colleague? What did they have to check before replying? Where would they notice if something went missing?

Then look at a request that went differently. The ordinary one shows you the routine. The awkward one shows you where a person has to make a decision.

Keep both in the plan.

Give every step a reason to exist

Perhaps the spreadsheet and the task board hold the same information because two people once needed separate views. Perhaps the extra approval belongs to someone who left. Find out before you connect everything.

A step with no current purpose is a good candidate for removal. A step that still matters needs a clear rule, an owner and somewhere for its result to live.

For the request above, the first useful version could create a record, assign it using an agreed rule and prepare an acknowledgement. A person can review anything that needs judgement, including an unusual request or a commitment to a delivery date.

If reading free text is part of the problem, an AI tool may help suggest a category or draft a reply. Decide how uncertain suggestions reach a person before giving those suggestions consequences.

Make failure easy to find

Test an incomplete request. Send the same request twice. Make one destination unavailable and check what the person responsible can see.

Agree where failed work waits, who is told about it and how they can continue it. A visible queue gives someone a chance to act. A quiet failure gives them a surprise later.

The handover should name the owner, the connected accounts and the person who can change a rule. Someone will eventually need to change a rule.

Check the work you actually removed

Record the time spent on the task before the change. After it is running, include the time spent checking, correcting and maintaining it too.

That gives you something useful to judge. If the team has simply acquired another thing to supervise, revisit the flow.

Show us the task you keep putting off. We can work through what it would take to remove the repetition.

Back to all articles

Something to build.
Something to fix.

Tell us what you have in mind. We'll discuss the scope, timing and whether we're the right fit.

Start a conversation

Tell us about the project

A few details help us come back with something useful. We read every message and reply by email.

What do you need? pick any
Budget

We use these details only to reply to you. Privacy policy