Repeated follow-ups
Teams had to be reminded to submit their monthly data, creating recurring coordination work.
Designing an automated monthly workflow to collect, process and identify relevant operational data across multiple teams.
Multiple teams were involved in a recurring monthly process that required data collection, consolidation, processing and identification of relevant users and tickets.
The process depended on repeated follow-ups and manual handling of information. It could take individual team members two to three days to complete their part of the exercise.
I worked on coordinating an automated workflow that connected data collection, shared-folder hand-offs, processing and ServiceNow to produce a consolidated working list.
Teams had to be reminded to submit their monthly data, creating recurring coordination work.
Received files needed to be collected, transferred and processed through separate hand-offs.
Relevant tickets and associated users had to be identified before teams could take the next action.
The workflow runs on a monthly cycle, connecting reminders, file-based hand-offs, data processing and ServiceNow ticket identification.
An automated workflow triggers on the first day of each month and sends reminders to the relevant teams to share their data.
A designated person places the received data into a shared folder, creating a common hand-off point for the next stage.
The shared-folder workflow passes the data to the DSAG team for processing. The processed output is returned to the same folder.
The processed data feeds into a ServiceNow workflow, which identifies the relevant tickets and associated users.
The workflow produces the final list of relevant users and tickets, ready for review and follow-up.
The concerned person reviews the final list and connects with the relevant users. This communication remains a manual activity.
Analyst hours saved every month across the participating teams.
Manual effort per person for the process
Time saved is an aggregate estimate across participating team members, based on the effort removed through the automated workflow.
Understood the recurring activities, team dependencies and hand-offs involved in the monthly exercise.
Helped coordinate the automated journey across reminders, shared folders, DSAG processing and ServiceNow.
Worked across participating teams to establish the required inputs, ownership and process hand-offs.
Helped move team effort away from repetitive data handling towards reviewing the final output and taking action.
01Automation works best when the complete process is understood before individual steps are automated.
02The value of automation is not only fewer manual actions, but also clearer ownership and more predictable hand-offs.
03Good process design keeps human intervention where judgement and communication are still needed.