Case study · Information architecture

Pricing Calendar: thousands of listings, one scannable view.

Revenue managers price hundreds to thousands of listings. I restructured the calendar’s information architecture around how they scan: infinite scroll, an annual view and KPI overlays they can switch on and off.

Role
Product Designer
Team
PM, 2 engineers and me
Timeline
2023 – 2024
Status
Live

Prototypes

Calendar interactions explored as coded prototypes.

Calendar interactions were explored as coded prototypes, where hover, density and edge cases can be felt, not just seen.

Multi-calendar hover columns · interactive prototypeOpen full screen ↗
Preview of Multi-calendar hover columns · interactive prototype
Flow

Check-in / check-out restrictions

Current vs proposed flow for blocking arrivals and departures, with the support cases that motivated it.

Open prototype ↗
Data

Nicknames in the competitor calendar

Readable nicknames instead of long competitor listing titles in Neighbourhood Data.

Open prototype ↗

01 · Problem

The multi-calendar was built for a handful of listings. Portfolio managers with hundreds or thousands paged month by month, lost the column they were reading, and switched pages to compare a listing with its market.

02 · Goals and constraints

Goal
  • Scan a whole portfolio without paging
  • Compare price, occupancy and demand in one place
Constraint
  • Thousands of rows must stay fast
  • Same data model as the existing calendar
Must stay true
  • Overrides stay one click away
  • Small hosts don’t get a harder calendar

03 · Key decisions

Infinite scroll, an annual view and switchable KPI overlays, each tested as a coded prototype.

  • Infinite scroll over paginationMonths load as you scroll, so a manager never loses their place between pages.
  • An annual viewTwelve months at a glance for spotting seasonal gaps before they cost revenue.
  • Modular KPI overlaysOccupancy, ADR and demand can be layered on the grid, or switched off for small hosts who don’t need them.
  • Hover columns for the date you’re readingHighlighting the hovered column keeps your place in a grid of thousands of cells (prototype above).

04 · Outcome

1,000sof listings scannable in one viewinstead of paging month by month
12 monthsvisible at once in the annual view
Far lesspage-switching to compare with the marketKPIs overlaid on the grid
Fewer ticketsabout check-in and check-out restrictionsafter the restrictions flow redesign

After launch

Shipping was the start. How the feature kept evolving from feedback, usage data and support.

Iterations
  1. v1.12024Customer feedback

    Keep your place in a dense grid

    What we heard
    Managers lost track of the date column they were reading across hundreds of rows.
    What we changed
    Hover columns that highlight the whole date, prototyped in code before build.
    Result
    Easier scanning of long portfolios.
  2. v1.22024Support tickets

    Clearer check-in and check-out restrictions

    What we heard
    Support cases showed hosts struggling to block arrivals or departures on specific days.
    What we changed
    A redesigned restrictions flow, compared current vs proposed in a prototype.
    Result
    Fewer restriction mistakes and related tickets.
  3. v1.32025Usage data

    Readable competitor names

    What we heard
    Long competitor listing titles made the competitor calendar hard to read.
    What we changed
    Short nicknames in place of full titles in Neighbourhood Data.
    Result
    Faster comparison against the comp set.
What’s next
  • A scrolling calendar on mobile
  • Editing customizations from the calendar