Digitise Repetitive Work First: Finding Your Team’s Hidden Hours
A one-week lightweight log to surface the repetitive actions that actually consume time, sorted by how standardisable they are, with a method for setting priority.
Key takeaway
A one-week lightweight log to surface the repetitive actions that actually consume time, sorted by how standardisable they are, with a method for setting priority.
Teams often say they are busy but struggle to say where the time goes. Digitisation built on impressions tends to optimise the visible steps while the hidden ones keep consuming hours. Here is a measurement approach that does not disrupt daily work.
The one-week lightweight log
No timesheet system needed — two minutes per person per day, recording three things:
- Which actions today were also done last week and will be done again next week.
- Roughly how long each took, rounded to fifteen minutes; precision is unnecessary.
- Who received the output and what it was used for.
Sort by how standardisable it is
After a week, consolidate the log and tag each action into one of three tiers:
- Fully standardisable: identical steps and criteria every time, such as compiling data into a fixed format. Address these first; the payoff is predictable.
- Partly standardisable: the main flow is fixed but some steps need judgment, such as classification requiring confirmation. Suited to "prepare automatically, confirm manually".
- Hard to standardise: fresh judgment every time, such as discussing a proposal with a client. Leave these alone; the return on changing them is lowest.
Setting priority
Within the fully standardisable tier, rank by two factors:
- Total time = duration per occurrence × weekly frequency. Address the highest total, not the most annoying single instance.
- Number of people involved. Fixing something several people share doubles the return and makes the habit change easier to sustain.
Common sources of hidden hours
The four most consistently underestimated: copying between systems, reformatting the same information for different audiences, repeatedly confirming whether a file is the latest version, and digging through chat history to find an old document. All four are fully standardisable.
Summary
The value of this log is not precision but converting "we feel busy" into a list you can rank. With a list, the order of work stops depending on who argues loudest.