Designing for Two Very Different Audiences at Once

During a typical month in the studio, our desk holds two radically contrasting design briefs. On one screen sits an interactive creative showcase with custom 3D WebGL meshes and duotone hover shaders. On the other sits a municipal park permit portal requiring strict keyboard focus rings, high-contrast text ratios, and clean screen-reader announcements.

Different audiences demand different volumes. Good design is knowing when to crank the volume up and when to mute the theatrics completely.

At first glance, these two projects look like products of different studios. A commercial client often needs to build brand excitement within three seconds to turn an evening browser into a booked appointment. But when a grandmother in Stockton needs to reserve a picnic shelter or pay an irrigation assessment, any visual flourish that obscures the submit button is a failure.

The discipline that bridges both worlds is respect for user intent.

We use the exact same underlying design token architecture, semantic HTML tags, and accessible contrast ratios across both builds. For the commercial brand, we spend the performance budget on GPU-accelerated motion that communicates craft. For the public agency, we spend that budget on lightning-fast table lookups and crystal-clear form error messages. The underlying engine remains rock-solid; only the volume knob moves.