ROLE
TEAM
TIMELINE
SCOPE

THE PROBLEM
SYSTEM IMPACT
branch locations across the city
people served in the Philadelphia area
800+
Employees relying on one shared system
WHERE WE STARTED · THE MAP AND ITS UNOFFICIAL DESCENDANTS

CONSTRAINTS
01
02
03
DECISIONS & TRADEOFFS
DECISION 01
Hand-drawn, not cartographic
CHOSE
A hand-drawn style paired with the library's brand fonts, so the map reads as approachable rather than technical.
COST
Strict geographic accuracy. A hand-drawn city can't be measured against — it can only be recognized.
DECISION 02
Keep the highways
CHOSE
Major streets and highways stayed on the map so locals could judge how close they actually live to a branch.
COST
Visual quiet. Every road added is a line competing with 54 branch labels for the same space.
DECISION 03
One system map, nine cluster slips
CHOSE
A two-tier system — the full city map for orientation, plus a buck slip per cluster for the branch a patron actually uses.
COST
Ten artefacts to maintain instead of one, and ten chances for a branch to hand out a stale version.
FINAL PRODUCT · ONE SYSTEM, THREE FORMATS

Nine colour-coded clusters, brand typography and enough street context for a patron to place themselves — without turning the map into a technical diagram.

Each cluster received a portable local guide built from the same system map, with branch-specific information staff could keep current.

The map travelled beyond wayfinding into a citywide announcement campaign, helping audiences understand where and when new Saturday service was available.

HOW THE MAP EVOLVED

Each cluster received a portable local guide built from the same system map, with branch-specific information staff could keep current.
NEXT PROJECT