Hogarth

​For six years at Hogarth Worldwide, I led iOS screen production for a confidential Cupertino client, building and maintaining the systems that made high-volume, high-consistency output possible across a large team. Due to the nature of the work, the final work is confidential, however I have highlighted some of the processes below. Thank you for your understanding!

The assets I oversaw production for were used downstream by five different teams: Print, Retail, Interactive, Keynote, and Video. Each team had different needs, but required visual uniformity between them for brand consistency. Keeping artists across the team informed of changes as they happened rather than after the fact since upstream creative directions were always moving, was one of the key things that kept quality consistent at scale.

I also owned the annual library refresh, auditing upcoming asks ahead of time based on past asks, building out principal assets with the states most likely to be needed, and archiving everything to our internal tool with metadata that made assets searchable and usable by others without needing to ask.

One of the more complex recurring challenges was managing component states. A single asset like a status bar could require combinations of hero times, connectivity indicators, privacy markers, light and dark options, and multiple device sizes. Early versions of our library included 50 variants per component to cover every possible variant. We later reduced that based on team feedback about which states were actually used in production, a good reminder that a library's job is to be useful, not exhaustive. Keyboards carried similar complexity: upper and lower case, predictive text bar states that varied by app context, light and dark, and multiple device sizes.

Onboarding new artists involved written documentation, recorded video training, live demos, and hands-on practice tickets to put the standards to work before touching live files.