Discover — Kaili Miyamoto
Protected
This case study is password protected

Enter the access phrase to read the full study — or request it.

That phrase isn't right — try again.
← Work Discover Next →
Microsoft · DISCOVER 

A campus full of amenities almost nobody could find.

Microsoft's campus is full of nap pods, walking trails, courts and quiet rooms. Discover was the product that would let an employee find them — and let RE&S finally see which ones anyone used.

I owned the end-to-end design: the discovery experience inside MyHub, the curation layer above it, and the admin tooling underneath.

Role
Product Designer
Timeline
2024
Type
MyHub · Mobile + admin web
Wellness
Badge
Recreation
Sports
Food
The problem

The spaces existed. The awareness didn't.

A Studio Wellness Study had already run when I picked this up, so I didn't have to prove the problem. I had to decide which part of it the product was answering.

01
Invisible
Employees didn't know what already existed. Discoverability was the study's headline finding.
02
Unmeasured
RE&S had no utilization data on wellness spaces. Investment ran on anecdote.
03
Stigma
At some sites, spaces sat empty because of cultural stigma. Nobody wants to be seen heading to a nap pod.
The vision

You can't search for something you don't know exists.

So the entry point can't assume you already know the words. Discover took a playlist approach — spaces grouped by how you want to feel in them, not by what facilities calls them. "Somewhere quiet near Building 34 before a 2pm," not "nap pods."

That framing is what made this a product instead of a list. It also closes a loop RE&S never had: playlists give people a reason to show up, and showing up is what finally produces data worth investing against.

The call

Catalog first, curate second.

Playlists sort spaces by mood, and there was no reliable list of spaces to sort. Half the amenities weren't in any system, and the ones that were had no photos, no hours, no location detail. Building the taste layer on an incomplete catalog would have shipped something that felt smart and answered nothing.

So the catalog went first. Not instead of the vision — underneath it. A searchable directory of what the campus actually has, with the detail an employee needs to go: categories, photos, locations. That's the version that shipped — mobile first, everything else staged behind it.

MyHub dashboard
Discover, with Nearby and Featured
The Nearby list
The Sunrise Room, selected
The Sunrise Room: a low-light room with floor cushions
Sunrise Room
One Esterra, Floor 3 · Relaxation
M–F, 9:00 am – 5:00 pm
Description

Take time to relax and reset in the Sunrise Room! Designed for anyone and everyone who loves yoga and dancing. Intended to boost your mood and energy, allowing you to reconnect with your body and mind.

Show me directions

Find it, then go.

A catalog only earns its place if the last screen answers "can I go, and where is it." Tap through it.

Also shipped

Someone has to keep it current.

Landmarks Admin Tool: a landmark record with category, status, description, photos and hours of operation
The Landmarks Admin Tool — where RE&S adds a space, its category, hours and photos.
What didn't

The staging was the risk, and the risk paid out.

The playlists and the utilization view were scoped out of the MVP and never picked back up. The next phase never got funded, and attention moved elsewhere.

So RE&S got an inventory of what it owns, and still has no read on how any of it gets used.

0
amenity categories mapped, nap pods to EV charging. Eight shipped.
0
utilization metrics RE&S had before Discover. Still zero after.
Takeaway

The catalog was the right thing to ship first. It just wasn’t the whole thing.

What held

The directory shipped to mobile and gave RE&S its first real inventory of what it actually owns.

What I'd change

I did propose shipping a check-in with the directory, exactly so the loop would exist on day one. It got cut with everything else in the scope-down, and once it was a separate phase it was never funded. What I'd change is the argument: I let measurement be presented as a feature, when it was the thing that would have paid for the next round.

More work All projects →
{{ r.num }}
{{ r.name }}