A dashboard that works the way teams do
Peek's leasing dashboard is where property owners and operators manage their tours and see whether those tours lease units faster and cut vacant days. It was already live and growing, so instead of one big redesign, I fixed the problems the data pointed to, one stage at a time.
Product
Peek leasing dashboard
Role
Sole designer
Team
Rotating PMs and engineers
When
’23 → ’25
Platform
B2B web app
22%
higher Analytics adoption
95%
fewer tour setup tickets
3.4×
more self-serve scan updates
The Issue
Each stage started from a different signal: operator interviews, support tickets and customer emails.
→ 01
What worked
Customers could see how often renters viewed their tours
What was missing
Proof: nothing showed whether those views led to leases
→ 02
What worked
Leasing teams could offer self-guided tours in their buildings
What was missing
Easy setup: every unit was added by hand through a long form
→ 03
What worked
Customers could request scans of their units
What was missing
Visibility: shoots were tracked by email, one request at a time
Feature
Analytics
Let customers validate Peek in their own data.
For portfolio leaders and the account teams who report on Peek's value. Customers struggled to prove Peek was working: tour views were hard to translate into applications, leasing speed or vacancy. Each user group needed different data, but it all sat on one page. I pitched and led a refresh to show the right data to the right teams, interviewed three operators and split it into three tabs: Conversion, Engagement and Content Creation.
The pivot
The leasing data wasn't ready yet, but the core problem couldn't wait: the data was too granular to read. So part one shipped aggregate data, filters and export, and part two added leasing results in the new tabs.
Result
It became a retention point and a sales tool, and the share of dashboard users opening it grew 22%.
Conversion, Engagement and Content Creation: each tab answers a different team's questions.
Feature
Self-guided tour management
Streamline tour setup so turning on a unit takes one toggle.
For leasing teams running self-guided tours. The setup workflow was unintuitive, and support tickets kept coming. I pitched and led a rebuild that cut most of the steps: units come in automatically and turn on with one toggle, with its access device in the same row.
The pivot
My first concept turned units on automatically when they became available. But not every property management system keeps availability current, and some teams tour a model unit that never counts as available. So enabling stayed a manual toggle.
Result
A few months after launch, support tickets on tour setup were down 95%.
Before
After
Before: nine steps across tabs and a form, for every unit. After: automated unit pull and a toggle to activate.
Feature
Scan tracking
Organize by photoshoot, the way customers plan.
For onsite teams and the admins checking on them. Customers weren't ready when scanners arrived: they couldn't keep track of changes to their photoshoot, and every update came as the same email. I moved requests into the dashboard, then reorganized it by photoshoot so everything for a shoot sits in one place, upcoming shoots first.
The pivot
We cut resubmitting from inside the flow to keep the focus on confusing updates.
Result
Monthly users grew 43%, and customers made 3.4× more self-serve scan updates.
One shoot, every unit in it, so teams can make changes before the photographer arrives.
In their words
“
Product manager, on the scan tracking launch
Scan tracking's share of dashboard users grew 1.5×.
What I learned
The same data means something different to each reader. A portfolio leader needs the aggregate to judge whether Peek is working, while an onsite team needs unit-level detail to act today. Matching the level of detail to the reader is what turns data into a decision.
Also shipped
Export presets · Scan notifications · Autoscan settings · PMS data setup tool · Prospect Intelligence
