What was getting in the way
At one point, I was reviewing a pipeline of around 20 automation and reporting ideas. We had limited time to deliver them, so we needed to choose where to start.
What I contributed
I ran the discovery and request process, assessed feasibility and set priorities. For work we agreed to do, I wrote requirements, acceptance criteria and rollout plans. I also built prototypes and automations myself.
How I approached it
- Watch how the work is done before estimating the time saved.
- Count the manual review that will still be needed.
- Compare the benefit with the work and risk involved in building it.
- Talk through the choices with the people affected.
- Check the result after rollout and adjust the priorities.
What changed
My current estimate is 400–500 hours of manual work saved each week across recruitment, payroll, quality checks and allocation. This includes automations I built and the allocation improvements I helped design.
API and Python checks account for 100+ hours of that weekly total.
The prioritisation work gave us a way to compare requests and agree what to work on first.