User experience
and interface design
in Chicago

Chicago's economy was built on things you can touch — freight, grain, steel, insurance policies written on paper — and a lot of the software now getting designed in the city exists to digitize exactly that. Allstate and CNA Financial run large insurance operations out of the metro; CME Group runs the world's largest derivatives exchange from the Loop; O'Hare anchors one of the busiest cargo and passenger airports on the planet. None of that is a consumer app category, and it shows up in the design work: fewer growth-hack onboarding flows, a lot more dense data tables, compliance-driven forms, and internal tools that have to be legible to a claims adjuster or a floor trader, not a Series A user-acquisition funnel. A city that trades on volume and precision rather than novelty tends to reward a design process that respects the same values.

Insurance and trading software in particular carry design constraints that a purely consumer-facing studio underestimates: regulatory disclosure text that can't be shortened for the sake of a cleaner layout, audit trails that have to be visible rather than hidden behind a settings menu, and users who've been doing their job on a green-screen terminal longer than most designers have been working. Redesigning that kind of interface is less about visual modernization and more about compressing decision time for someone who makes hundreds of judgment calls a shift. The manufacturing base that still runs through the metro and its suburbs adds a related but distinct category: ERP-adjacent internal tools and supply-chain dashboards, where the design problem is less about persuasion and more about making a very large, very dense dataset scannable at a glance.

Chicago's weather isn't a footnote for anything with a local-commerce or home-services component. Search and transaction volume for a huge swath of local business — landscaping, HVAC, contracting, even retail foot traffic downtown — swings hard between a short intense summer and a long winter, and a product roadmap that ignores that seasonality tends to ship the wrong feature at the wrong time of year. We build that cadence into the release calendar for clients with a seasonal demand curve instead of treating every quarter as equivalent. The same seasonal logic applies to internal capacity-planning tools for logistics and manufacturing operators, where a dashboard that isn't ready before the pre-holiday freight surge is a dashboard that missed its actual purpose.

Chicago has an advertising and design heritage that predates most of Silicon Valley — Leo Burnett founded his agency here in 1935, and the city still trains a disproportionate share of its design talent through the School of the Art Institute and Northwestern's design programs. That heritage produces designers who default to strong visual craft and brand discipline, which is an asset for consumer-facing product work and occasionally a mismatch for the density-first, craft-second demands of enterprise dashboard design. Knowing which mode a given engagement needs is part of the brief, not an afterthought. McCormick Place, the largest convention center in North America, also keeps a steady flow of B2B trade-show activity through the city, which means a meaningful share of Chicago product demos are still first shown on a trade-show floor rather than over a screen share — a context that has its own design implications for kiosk and tablet-based product tours.

Plenty of software is not used on a personal device. A tablet at a loading dock, a kiosk at a gate or a terminal on a plant floor passes through many hands in one shift. Designs made for a single owner break there.

Signing in is the first friction. Typing a password with a queue behind you gets skipped, so people share one account and the records stop meaning anything. A badge tap, a short personal code or a quick switch between recent users keeps identity honest without slowing the line.

Signing out matters just as much, because people walk away in the middle of a task. The screen should lock after a sensible pause and return to a neutral state, never to the half-finished work of the previous person.

Drafts need an owner. Work left open when someone was called away should wait for that person, visible to them on return, and invisible to the next user.

Personal settings rarely belong on the device. Language, text size and favourites should follow the person, loaded at sign in and cleared at sign out.

Finally, the whole cycle has to be fast, and we time it during testing with the people who will use it. Walk up, identify, act, leave. If that loop feels slow, people will find a way around it.

United Airlines runs its corporate headquarters out of Willis Tower in the Loop, and O'Hare's role as one of the busiest passenger and cargo airports in the world means travel, logistics, and airline-adjacent software is a distinct product category in Chicago that doesn't show up in most other Midwest markets. That category brings its own interface demands: real-time operational dashboards where a delayed status update has immediate downstream consequences, and customer-facing tools that have to perform under genuinely high-stress conditions — a cancelled connection, a missed bag — rather than the more forgiving context of a typical e-commerce checkout flow.