Navigate turned a large real-estate dataset — property details and owner contacts for whole neighborhoods — into a tool agents could run outreach campaigns on. The prototype worked, but it had grown faster than its UX: the core actions an agent needs were buried, and the day-to-day workflow wasn't obvious.
This was an audit, not a build. I worked the product the way an agent would — spinning up area campaigns, targeting homes on a map, tracking responses — found where the experience and interface broke down, and delivered a prioritized spec that became the team's build roadmap. The deliverable was judgment about what to fix first, not a finished interface.
Role
I led the UX audit as product designer — reviewing the prototype end to end, recommending experience and interface improvements, and packaging them into a spec the team could build against.
Walkthrough
A closer look, screen by screen.
01 / 05
The first recommendation reorganized the dashboard around campaigns, so an agent's active outreach is what they see on arrival: a grid of cards, each pairing a neighborhood map with its ZIP, home count, start date, and latest response.
02 / 05
The core action is choosing where to reach, so map-based targeting became the central gesture — search a city, neighborhood, or ZIP, draw the area, and build a campaign around it, watching the homes it covers as you go. Location context travels with the campaign instead of living in a separate view.
03 / 05
Outreach is only useful if you can see what it returns, so the spec pulled responses forward — a campaign's replying homes and their revealable owner contact, surfaced where the agent is already working rather than buried a few screens deep.
04 / 05
First-time agents had been dropped into a blank screen. The recommended empty state points them straight at creating their first campaign, so the product teaches its core loop on day one.
05 / 05
Underneath it all is the data that makes outreach possible — property and owner detail — kept legible so an agent can read a home and act on it without leaving the flow.
What shipped
Delivered a prioritized design spec that doubled as a build roadmap.
Recommended targeted UX and UI fixes across the highest-friction flows.
Reframed the dashboard around campaigns, so an agent's active outreach leads.
Aligned the map and campaign views so location context travels with every campaign.
Selected decisions
- 01
Centered the dashboard on a campaign grid — each card pairing a neighborhood map with its ZIP, home count, start date, and latest response.
- 02
Made map-based targeting the core gesture: search a city, neighborhood, or ZIP and build a campaign around that area.
- 03
Surfaced response tracking so agents can see which campaigns are landing at a glance.
- 04
Designed an empty state that points a first-time agent straight to creating their first campaign.