Library of Things

Designing a Scalable Brand and Operations System for a Multi-Audience Lending Program

I designed a unified brand identity and operational template system for a public library lending program spanning 380+ items across two collections, adult and youth, supporting four distinct audiences: end users, program coordinators, operations staff, and fulfillment teams.

Challenge

The program needed more than a visual identity. It needed a system that non-designers could operate independently and consistently at scale, across a large and growing inventory, without ongoing design support. The parent organization had an established brand that needed to inform the new system without being duplicated by it.

Solution

A card-based system for the adult collection and packaging-based system for the youth collection, built on a shared color-coded category architecture. Both collections share the same production infrastructure and file system.

The color system needed to satisfy three requirements simultaneously: categorical differentiation, brand harmony, and accessibility. Rather than compromise on all three, one constraint was eliminated architecturally — restricting color to backgrounds and accents only, with all text in black or white, removed contrast ratio as a variable entirely.

Templates were built in Google Slides to facilitate seamless adoption. Every staff member already had access, IT already supported it, and Google Drive's native collaboration tools enabled real-time remote troubleshooting. Element locking restricted staff inputs, producing consistent output with no design decisions left to the operator.

Throughout the project, continuous working sessions with every department ensured the system was designed around how staff actually used each component.

Results

  • 30+ modular templates supporting 380+ items across youth and adult collections

  • Staff independently produce all materials for new inventory without designer involvement

  • Expansion capacity built into the palette before redesign is needed

  • Operational infrastructure — tooling, file architecture, troubleshooting process — designed for the organization's existing systems and skills