Creative Systems
AMAZON ESSENTIALS
Case Study 01
Amazon Essentials Label System
There were 233 different garment-label variations floating around the business. I redesigned the system & brought them down to 45 standardized codes.
Case Study 02
Artwork Reporting System
I built a reporting system that connects artwork
requests, artwork usage, seasons & categories so we
could finally see what was being made & how often we
were reusing what we already had.
THE PROBLEM
Artwork was being created across multiple sources & workflows, making it difficult to consistently answer:
Where did artwork come from?
How much was purchased vs. created?
How much was reused?
How much was AI-generated?
How many versions were created?
Where was creative effort being spent?
What happened to the artwork after handoff?
THE SYSTEM
Created a naming convention that embeds artwork attributes directly into the workflow.
ARTWORK NAME
•SOURCE (LIBRARY, AI, IN-HOUSE)
• FAMILY
• VERSION
• SPIN / VARIATION
Case Study 03
Artwork Reuse Library
Our artwork library had hundreds of existing designs, but finding something useful often meant knowing where to look — sometimes in a category folder from a season that had already come & gone.
So I built an agent that goes looking.
844 designs
1,342 colorways
11 categories
11 seasons
Our artwork library had hundreds of existing designs, but finding something useful meant knowing where to look (often in a folder from a past season).
So I built an agent that goes looking. Using Kiro, an Amazon agentic engineering tool, I created a system that scans our artwork files, organizes them by category, season, subject, & other attributes, & brings them into a searchable archive.
Now a designer can search the collection, filter it, see available colorways, & actually find the stuff we've already made.