A full day of work can leave surprisingly little to show for it.
You answered emails, updated a spreadsheet, chased a missing document and moved the same information between three places. By the afternoon, you were too busy maintaining the work to get much of it finished.
That is worth looking at before adding another tool or deciding you need to become more disciplined.
Sometimes the business has simply outgrown the way the work moves through it.
What is the activity meant to achieve?
Recurring tasks have a habit of becoming permanent.
A report gets updated every Friday. A client receives two separate check-in emails. The same project details live in a spreadsheet, a workspace and someone's inbox.
There may have been a good reason for each step originally. That does not mean the reason still holds.
Choose one recurring activity and ask:
- What result should this produce?
- Who uses the information or receives the output?
- What decision or next action does it support?
- What would happen if we stopped doing it?
If nobody reads the report, a more attractive dashboard is unlikely to solve the problem.
If the information is useful but arrives too late, the timing needs attention.
If two people are updating the same details, the process may need one clear source of truth.
Those are different problems. They need different fixes.
Follow one piece of work
Imagine a consultant receives a new enquiry.
The message arrives by email. The consultant copies it into a spreadsheet, adds a reminder to their calendar and makes a note in their project workspace.
The enquiry is now recorded in several places. But the next action is still unclear.
Has anyone replied? Is the person waiting for a proposal? When should someone follow up?
More recording has created more places to check.
A simpler process might keep the enquiry in one reliable record, with a clear stage, an owner and a dated next action. The original email can remain linked rather than copied everywhere.
The useful improvement is that someone can see what needs to happen without reconstructing the story.
Look at the process, platform and pathway
I find it useful to look at work through three connected lenses.
Process: how does the work happen?
Write down the actual steps, including the chasing, copying and checking that rarely makes it into the official version.
Look for unclear ownership, repeated work and steps that depend on someone remembering.
Platform: where does the information live?
Check which tool holds the reliable record, what gets duplicated and whether people can find what they need.
You may already have the right tools. They may need clearer roles or a better connection.
Pathway: what does someone experience?
Follow the work from the customer's or team member's point of view.
Can they see what happens next? Are they asked for information they have already supplied? Does progress disappear between one stage and another?
A process can look tidy internally while being quite confusing to use.
Choose a useful measure
Once the intended result is clear, decide how you will know whether the process is helping.
For an enquiry workflow, that could mean checking for overdue follow-ups and whether every open enquiry has a next action.
For client onboarding, it could mean tracking how often someone has to ask for access or clarification.
For recurring admin, it could mean recording the time spent copying information and correcting inconsistencies.
Keep the measure close to the problem. Counting completed tasks tells you about activity, but may leave unanswered whether the work became easier to manage.
Marketing can be one example of this. Publishing regularly is useful only in the context of what the content is meant to achieve and what happens when someone responds. The same principle applies to delivery, finance and everyday admin.
Improve one part first
You do not need to rebuild the whole business.
Start with one recurring task that creates disproportionate effort. Trace the steps, find the friction and make the smallest useful change.
That might mean removing a duplicate record, clarifying who follows up, or giving a customer a clearer next step.
Run the revised process a few times before automating it. You will learn more from the exceptions than from a perfectly behaved demonstration.
Your action
Choose one recurring activity and finish this sentence:
“The result this activity needs to produce is…”
Then follow it from start to finish. Identify one step you can remove, simplify or make clearer.
If several processes feel tangled together, a Clarity Session provides space to understand the systems, processes and customer journeys behind them. Your tailored Clarity Blueprint sets out practical priorities, so you can build independently or choose the implementation blocks you want help with.