Case Study: Improving an Asset-Naming Workflow Through Automation

Context

In digital product creation, asset naming needed to follow a defined naming convention. The existing manual workflow was time-consuming and created repeated effort during production. I identified this as an opportunity to improve the workflow through automation.

Script Demo

My role

My role was to connect production needs with a technical solution. I defined which data could be extracted from CLO to create names that followed the required naming convention. I collaborated with a software engineer to support the script development, requested API expansion from the CLO team, tested the expanded API, collected user feedback, and confirmed that the improvement worked in the workflow.

Approach

I started by reviewing the naming convention and identifying which parts of the name could be generated from available CLO data. I then helped clarify the data requirements for the automation script and supported testing during development. When limitations appeared, I communicated the need for API expansion and later validated whether the updated API supported the workflow.

After the script was available, I tested it in a production-like scenario and collected feedback from other users to understand whether the improvement was practical and useful.

Outcome

The work helped reduce manual effort in the naming workflow and created a more consistent way to generate asset names based on available product data. It also improved the connection between user needs, tool capability, software development, and implementation testing.