CHALLENGE

CoStar owns the data that real estate people need to make decisions. Property comps, market trends, neighborhood details, transaction history. The depth is what makes the platform valuable. The problem is what comes with depth: seventeen-column tables that force you to scroll horizontally, keep multiple numbers in your head, and remember what you saw two columns back while you're looking at what's in front of you now.

Dense information is fine for specialists. They expect it. What kills the experience is the layout. A table makes you work harder than the data actually requires. Your brain is focused on navigation instead of analysis. That's the gap between having good data and being able to use good data.

SOLUTION

I moved the information into cards. Not as a design trend. Because cards let you read top to bottom instead of left to right. Because related information sits together instead of scattered across a row. Because your eye stops hunting.

One hard constraint: keep all the information. You don't simplify data by removing it. You simplify by reorganizing it so the structure does the work instead of the user doing it mentally.

Three things had to happen:

Visual hierarchy that actually works. The number that matters most sits at the top. Context below it. White space that creates meaning. A user glances at a card and knows what's primary and what's supporting information before thinking about it.

Vertical movement instead of horizontal. Cards stack down a column. Comparing five properties becomes reading five cards top to bottom instead of flipping your head sideways five times across columns.

All the precision stays intact. I built small, composable pieces. A card for a single data point. A card for a ratio. A card for historical data. Same data, different shapes, different context. The system works because the building blocks stay consistent and snap together different ways depending on what question the user is trying to answer.

APPROACH

The architecture underneath changed to support this flexibility. A broker looking at one property needs something different than an analyst building a market report. Both of them access the same data. The system presents it differently based on what they're doing.

What that meant:

Breaking data into pieces that could snap together different ways. Tables are monolithic. Cards are composable. You build a component library and then combine those components depending on context.

Interaction patterns that don't change. A filter works the same way across every screen. A drill-down gesture works the same way. A user learns once and that learning applies everywhere they go in the platform.

Responsive layouts that stay coherent. Desktop and mobile shouldn't feel like different products. Cards reflow. The information hierarchy holds. The experience feels continuous.

Transitions that keep users oriented. When a user clicks into a detail view or switches between datasets, the layout shifts without breaking the sense of where they are. That continuity matters when someone's moving fast.

EVIDENCE OF ARCHITECTURE