Branding & Identity
Marks, wordmarks, and identity systems built from a small grammar of squares, letterforms, and color rules. Designed to apply cleanly across print, signage, and screen.
- Marks
- Color
- Guidelines
I'm Bryce — a graphic designer working across branding, web design, typography, digital interfaces, and visual systems. I make things that feel structured first, decorated second, and built to outlive the season they were made in.
A studio of one. Working out of the Midwest on identity, editorial, and interface systems for independent clients, small institutions, and self-initiated work.
I started out wandering between print and code — designing posters in the morning and prototyping reading software at night — and eventually realized the two were the same craft on different surfaces. The work has been roughly that ever since: build a quiet system, set it in squares, and apply it across whatever medium the project needs.
When I'm not at the desk, I'm usually walking, reading editorial archives, or trying to set the same word in twelve different ways to see which one finally fits.
Marks, wordmarks, and identity systems built from a small grammar of squares, letterforms, and color rules. Designed to apply cleanly across print, signage, and screen.
Reading-first websites and product UI built on modular grids. Vanilla HTML/CSS/JS where I can; fewer dependencies, longer shelf life.
Specimen booklets, type pairings, and the occasional custom face. Most projects begin with a measure and a single working size.
Posters, publications, and small-run print work. Risograph, two-color offset, and saddle-stitched booklets I can finish over a weekend.
Pictograms, icon sets, and signage systems anchored to a consistent unit. Designed so non-designers can extend the system without breaking it.
Quiet motion studies, generative iconography, and small experiments that feed back into the studio's identity work. Vanilla canvas, no libraries.
Spend the first calls in audit mode. Read what already exists, watch the team use it, and find the constraints worth keeping.
Set the grid, the type system, and the smallest unit of decision-making. The rest of the project lives inside that frame.
Make the deliverables and a small library of components alongside. The system gets stress-tested by the work, not the doc.
Document only what's actually load-bearing. Pair with whoever will extend the system. Archive what stayed.
Currently booking projects for August — October 2026. Quick replies on email; even a one-paragraph brief is plenty to start.