Setting the
Foundations.

A civic housing data tool rebuilt on a design system, launched to its first users, and now scaling.

  • SYSTEMS
  • UX
  • PRODUCT
Challenge
A civic housing data tool had strong underlying data but no design system, no validated understanding of its users, and no visual language consistent enough to build on.
My Role
Lead product designer from discovery through execution. I owned user research, information architecture, the full design system, the Figma component library, and the built product.
Team Structure
Lead Product Designer (me), Engineer, Product Manager
Impact
A complete design system and a fully built product, launched and onboarded to its first users. A year later, that foundation is supporting the next phase and scaling to more users.

Overview

OpenRent had strong data and a clear mission, but its interface wasn't meeting users where they were. I started with research to understand who was actually using the product and what they needed, then rebuilt the UI from the ground up, designing a component library, improving search and filter interactions, and introducing new features like map breadcrumbs, scannable hover cards, a detailed information panel, and a comparison panel as a future-facing primitive. The result was a fully built product, in use by its first researchers and advocates, on a foundation designed to grow.

BeforeAfter

The problem

The product had been built screen by screen. Nothing was reused, so nothing was consistent: three shades of grey for the same label, four spacing values inside one panel, a coral that meant “our brand” on the header and “rent is rising” on the map.

The system was trying to serve researchers and advocates at once, but was not fully serving either. It needed to flex for both without becoming muddled or losing clarity.

HMW make spatial data legible to non-technical advocates while preserving what researchers need to trust it?

The reconciliation card: one data model, two reading modes, with the Building / Zipcode toggleWhat researchers and advocates each read for: position on a spectrum, or which category a building is

User exploration

The first assumption I tested was whether researchers and advocates needed different products. They actually needed the same data but framed two different ways.

I conducted user interviews to surface what each group actually needed in practice. Researchers and advocates didn't disagree about the data, they disagreed about the framing and context. Researchers wanted comparable data - where does this neighborhood sit on the full spectrum and how does this building compare to the neighborhood? Advocates wanted categorical clarity - is this affordable, mixed-income, or market rate? They wanted to be able to drill down into the details of each property. I was able to meet both needs through information hierarchy across unit hover cards, detail panels, and a comparison panel being intentional about the product real-estate in a way to future proof the design.

Tokens and styles

The token board: Brand, Signal and Choropleth color tracks plus Junicode, Work Sans and mono data values

Primitives

Creating a shared language across user groups gave the product a unified look and feel, while allowing it to meet different needs without becoming muddled.

Components

The interactive components below addressed global needs across users and bespoke needs for each user, taking primitives and scaling them to unique functions that established the product value.

The final design

Hover cards surface the most scannable facts about a property or neighborhood - name, rent figure, burden signal, and affordability category - on hover. Researchers scanning twelve buildings across a neighborhood don't have to open a panel to triage; they can read the relevant data inline and move on. The filter panel controls the map without leaving it. It was one of the decisions that looked small but set the tone for the whole experience.

Filters narrow the map to the right data, hover lets you move through the map quickly, and the right panel acts as a source of validation, gathering the right data at the right zoom. Comparing in the bottom view supports thorough, shareable conclusions.

Hover cards, the detail panel, and filters launched first; the comparison view was a nice-to-have, so it was scheduled for a later release. The order was important to be able to first clearly navigate the data, then validate the information, and finally alleviate cognitive load through visual analysis.

Outcomes

Launched

Built, launched, and onboarded our first users

1

Design system with type and color styles

8 + 12

Primitives and components in one library

What's next: designing for scale. A year in, OpenRent is expanding to more users. Every element was built from a shared primitive, so it can easily scale and flex, but my next goal is to design how the full experience scales with it.