Standardized
Type
Product Design (Concept Study)
Focus
Visual Systems & Product UI
Timeline
2022 (Refined 2026)
Overview
Standardized is a conference identity and companion mobile app for a two-day education conference, built to fix a specific problem: navigating sessions, schedules, and speakers on the go shouldn’t mean juggling a paper program and a badge that’s easy to lose. I built a strict visual system for print, then extended it into the app itself, letting attendees browse the schedule, save sessions, and hold their digital badge in one place.
Problem
This is built for an educator or education-sector professional attending a two-day, multi-track conference. Two things are broken here, not one. Visually, education conferences play it safe, corporate, clean, forgettable, which is ironic given they’re usually selling forward-thinking ideas. Functionally, the tools built for these events make it hard to navigate on the go: a paper program that’s hard to scan mid-hallway between sessions or use to quickly look up a speaker, and a badge that’s easy to lose, with a check-in line waiting on the other side. Missing a talk because you were flipping pages, or losing time at check-in because you left your badge at the hotel, isn’t a branding problem. It’s the kind of friction that decides whether someone has a good day at the event.
Research
I checked both problems against existing event research instead of assuming they held up. Both check out. Overlapping sessions are common enough that event researchers have a name for it, “conference FOMO,” studied directly by the International Association of Exhibitions and Events and the Professional Convention Management Association. Lost badges are common enough that reprinting one is a built-in feature on nearly every event check-in platform, with one industry source citing 5–15% of arrivals needing some kind of exception handling at the door.
Existing event apps aren’t short on features. Whova alone covers agenda, networking, and check-in for over 5,000 organizers, but real user reviews describe the tradeoff: excessive notifications without effective filtering, cluttered community feeds, and a steep learning curve for first-time attendees with no walkthrough. That’s the gap this system is built against: not adding more features, but making the ones that matter legible at a glance without needing onboarding.
Process
I kept the palette deliberately tight and pushed the surface dark: black backgrounds, white type, and red reserved for exactly one job: marking what’s active. High-contrast black reads faster under bad venue lighting and costs less battery than a bright screen held for two full conference days. Big Shoulders Display carries headlines and the wordmark; IBM Plex Sans handles session titles, times, and speaker names at the small sizes a phone screen needs. Working on the print identity first, I scattered altered shapes and missing corners for visual interest, but coming back to it with fresh eyes, it read as a mistake, not a message. I scrapped the decorative approach and set a strict functional rule instead. Shape state is reinforced by high-contrast color, never color alone. Someone who can’t distinguish red from black still sees exactly which sessions are saved, because the shape itself already tells them.
Outcomes
Four pieces came out of this: Schedule, My Agenda, Speaker Profiles, and Digital Badge. Schedule is where you plan your day without flipping through a paper program; My Agenda filters down to just what you saved; Speaker Profiles lets you look up who’s talking without losing your place; and Digital Badge replaces the physical lanyard with locally stored speaker, staff, and attendee distinctions that still work on overloaded convention-center Wi‑Fi.
The navigation stays flat on purpose: four tabs, Schedule, Agenda, Speakers, Badge, all one tap from anywhere. At an event where someone might check the app for two seconds while walking between rooms, a deeper hierarchy would be the wrong trade. Speed mattered more than scalability here.
Retrospective
Turning this from a static brand identity into a real UI system taught me that constraints aren’t limits; they’re what gives a design decision meaning instead of being noise. That’s the difference between styling an app to match a brand and actually building the brand’s logic into how it behaves. If I kept going, the next step is testing this under real event conditions, not just concept validation. I’d want to time how fast someone can actually save a session and glance at their agenda during a five-minute hallway rush between talks. A UI either holds up under pressure or it doesn’t. Maintaining a strict, modular system throughout, rather than loosening it once things got real, is what let every product decision scale without adding visual noise.
