top of page
Operational Systems
The logic behind systems that started in spreadsheets and ended up as products used company-wide.
More Info
The Problem
When you're running 40+ publications across multiple markets, you can't manage production by instinct and institutional knowledge. Work was distributed unevenly, managers had no visibility into capacity, and the systems that existed were held together by whoever happened to know how things worked.
What I Built
I designed the logic behind a workload distribution system and a duration-based productivity tracker — both built initially in spreadsheets and Trello, then translated by the development team into actual products used company-wide. I also built the infrastructure behind the Pages Queue, which automated how design work was routed across markets when capacity was needed.
What Changed
Sales proof production time dropped by 50%. Design department costs reduced by 25%. Managers gained real visibility into capacity for the first time, which freed them to focus on the work that actually required their judgment.

01
Operational Systems

01
Production Date Schedule Changes
Summary for key stakeholders

02
Development Requirements
For a dummy automation project
.png)
03
Mockups for Design Traffic Reports (1/3)
.png)
04
Mockups for Design Traffic Reports (2/3)
.png)
05
Mockups for Design Traffic Reports (3/3)

06
Holiday Time Off
For all staff to be aware of who is and who is not working in key roles and departments

07
Development Notes
For which roles can view and edit a project
bottom of page