PLATFORM FOUNDATION · 2023 TO 2024
BEST BUY CONNECT · SHARED EMPLOYEE SYSTEM
Designing a shared employee directory and profile system
I designed the shared roster, profile, and permission model that employee experiences could reuse across Best Buy Connect.
Context
Best Buy Connect · internal employee platform
My role
I defined the shared roster and profile architecture, viewer relationships, permission rules, and boundaries between the platform and product tools.
ROLE • SENIOR UX DESIGNER
SCOPE • SHARED PLATFORM
PLATFORM • MULTI-PRODUCT
Defined once. Employee experiences can start from the same foundation.
Best Buy Connect · Roster 360 and Profile 360
- 2
- shared foundations
- 1
- shared permission model
- 3
- profile versions, based on who is looking
At discovery, four products needed the same list, profile, and permission rules
4
products were each rebuilding a list, a profile, and permission rules
Coaching
Search
Learning
Scheduling
1
shared layer, built once
People360
One list, one profile, one permission model
The question changed from how coaching should display a list to what every Connect tool should be able to reuse.
The project in one minute
People360 was the internal name for a reusable employee directory and profile system inside Best Buy Connect.
I designed the shared list, profile, permission model, and cross-tool boundaries so employee experiences could reuse one foundation instead of rebuilding the same screens.
- ROLE
- Senior UX Designer · platform architecture, viewer relationships, permissions, and flows
- TIMELINE
- 2023 to 2024
- FOCUS
- Reusable roster, profile, permissions, and governance
- STATUS
- Shared roster and profile foundation; reuse shown at different stages across product contexts
One shared foundation for repeated employee screens
2
shared foundations: roster and profile
1
shared permission model
3
viewer relationships: employee, leader, and general manager
Product contexts referenced in this study
How to read this
The profile container shipped. The six product contexts shown here were at different stages, so this reflects reuse scope, not six launches.
THE DECISIONS THAT SHAPED THE PRODUCT
Three platform decisions replaced repeated employee screens
REPEATED PROBLEM
Several products were rebuilding the same employee path.
Each team needed a list, a profile, permission rules, and a route into specialized work.
SHARED ARCHITECTURE
The list and profile each received one clear job.
The list found people. The profile revealed context. Product tools owned the actions that followed.
GOVERNANCE
Reusable did not mean identical.
Viewer relationships and source products changed what appeared without breaking the shared structure.
Platform rules, made visible in one list
Search and browse are equals
Some leaders search a name. Others browse a team. One list serves both.
Location is a choice, not an assumption
District and multi-unit leaders change stores in place. The list never binds a leader to one building.
Work context rides along
Shift window and clock status show who is reachable right now, without opening a single profile.
Every row is a handoff
The list finds the person, then hands off. What follows belongs to the profile and the product tools.
The platform, drawn as one layer
Roster 360
Shared employee list
Finds the right person or team, at any location the leader supports.
Profile 360
Shared employee profile
Reveals what this viewer can know and do, then hands off to the owning tool.
Runs on identity · permissions · source systems
Find, reveal, hand off: the platform ends where the tool begins
Find
Roster 360 answers who is here.
Reveal
Profile 360 shows what this viewer can know and do.
Hand off
The task remains in the owning product. The shared profile sends the user there.
The same profile changes with the viewer’s relationship
EMPLOYEE
Own record
LEADER
Team context
GENERAL MANAGER
Aggregate view
The container stays consistent. The revealed content changes with the viewer relationship.
One list pattern supports different ways of finding people
The entry point and question change; the list structure does not.
Store roster
OPENS FROM EMPLOYEE FINDERWho is at this location?
Coaching participants
OPENS FROM COACHINGWho is taking part right now?
Certification candidates
OPENS FROM SALES CERTIFICATIONWho is ready to be observed?
Each tool keeps its own filters and follow-on actions. The platform keeps the pattern.
REFLECTION
Repeated employee screens revealed one platform problem.
The contribution was recognizing the shared problem, defining the reusable layer, and setting ownership boundaries so multiple products could improve without becoming one giant profile.