Serena Zhang
All selected work
Microsoft · Azure DevOps

Making people management easier

Designing a clearer way to manage people, roles, access, invitations, and subscriptions inside a developer platform.

My role
Product design · Design iteration
Collaboration
Product managers and engineers
Scope
People management and access workflows

Enterprise product design

Marketing composition based on selected interface designs. Original design work is presented below.
The design challenge

Make a complex system
easier to administer.

Inside Azure DevOps, administrators needed to understand people’s roles, access, status, and activity. I iterated the People Hub with product managers and engineers, covering summary information, invitations, subscriptions, and group rules.

01 / Information architecture

The table is the overview.
The panel carries the detail.

Original design · People, roles, access, and last-access information in one view
01

Find the relevant people

Keyword and access filters sit above the people list.

02

Compare the right attributes

Names, organization roles, access levels, and timing share a consistent row structure.

03

Open detail deliberately

Summary and Add users give administrative tasks distinct entry points.

Design decision

Keep the summary available without crowding every row.

I explored summary treatments alongside the landing view. The side-panel direction separates overall access and subscription information from the per-person table, while keeping the administrator in the same context.

Original design · Access and extension details in a side panel
Compare the summary explorationsView original designs
Summary exploration 1
Summary exploration 2
Summary exploration 3
Summary exploration 4
Summary and expandable side-panel study
02 / Administrative workflows

Make invitations
more than an email field.

Original flow study · Invitation settings
Connected decisions

Who gets access,
and what kind?

Invitation design brings identity, access level, organization role, and project permissions into one task. These choices shape what happens after the invitation is accepted.

01

Identity

Select the people who should receive access.

02

Scope

Define organization role and project-level permissions together.

03

Completion

Keep invitation delivery and the final action explicit.

Explore invitation and subscription flow studiesView original designs
Invite user flow — starting state
Invite user flow — access choices
Subscription management
03 / Interaction consistency

Scale the action.
Keep the structure familiar.

Multiple people
Original design · Shared actions for a selection of users
Group-based access
Original design · Group, access and project assignment
Design rationale

Individual invitations, multi-selection, and group rules address different scales of administration while sharing a consistent interaction language.

View the additional final interfacesView original designs
Final invitation interface
Adding a group rule
04 / Contribution

From exploration
to final interface designs.

I explored and iterated the interface with product managers and engineers, then delivered the final designs. This case focuses on the design decisions and administrative workflows; the figures inside the original screens are example product data.

Open full image