Deb and I interviewed our sales team to understand their biggest challenges, needs, and their most common workflows.
I analyzed several enterprise host accounts to see the scale that we needed to account for.
We also reviewed and user tested our designs with members of the sales team.
Some of our findings…
Many enterprise listings are identical with only slight variations in details.
Some listing information is the same for all listings per location, such as the access frequency and check-in instructions.
After onboarding a host, the sales team rarely makes changes on listings.
The sales team usually searches for users or listings by email address or phone number.
They usually look for groupings of listings with the same location, listing size, listing type, or status.
Design progression
For over a year I had explored designs for this tool on my own time. For that reason, even the early designs were fairly high fidelity.
These slides mostly represent iterations on the journey of understanding the sales team and designing according to their needs.
Final designs
Each enterprise account has users, locations, and reservations:
Global search:
Host:
Location:
Reservation
You can create new organizations, users, and listings.
You can edit listings field by field:
You can also edit a full listing, or even multiple listings at once:
Outcome
The feedback from the sales team was that the tool made it much easier to manage these enterprise accounts.
I don't know the business outcomes for a couple reasons. Neighbor is a young company. They track analytics for customers and app usage, but not internal tools. Also, the build was released gradually. Neighbor only had a few engineers working on internal tools, so the build took months.