Pearson VUE · Enterprise Asset Manager

Five role tiers needed one system without one-size-fits-all access.

I redesigned inventory, distribution, assignment, requests, approvals, and reporting around administrator role, permission, and operational intent.

Pearson VUE · Enterprise Asset Manager experience

Overview

The role-tiered redesign made high-volume voucher and digital-product administration clearer across five levels of access.

Goals:

  1. Show each administrator the inventory, requests, and actions that match their role and permissions.
  2. Make distribution, role management, and assignment understandable and traceable through the organization hierarchy.
  3. Reduce navigation and task effort with clear, workflow-specific guidance without forcing every job into one wizard.
Role
Lead Product Designer · end-to-end UX/UI
Responsibilities
End-to-end UX/UI for discovery, role modeling, prioritized workflows, responsive design, implementation handoff, and development QA.
Collaborators
Product, engineering, sales/support, operations, business development, and marketing
Timeline
Discovery through delivery and development QA

Business problem

Administrators managed large voucher and digital-product inventories through a multi-tenant hierarchy, but fragmented inventory, unclear roles, and weak action orientation made routine work harder to complete.

Confusing distribution or assignment could create waste, incorrect access, or uncertainty about where assets went.

Business need

Reduce administrator effort and asset-handling risk while making inventory movement, ownership, and outcomes easier to understand and verify.

User problem

Five role tiers handled different combinations of inventory, requests, distribution, user management, assignment, and reporting.

Unclear hierarchy, inconsistent terminology, and long workflows made it difficult to know which actions were available and what would happen next.

User need

Role-appropriate dashboards and task flows with clear authority, recipients, quantities, remaining balances, status, and confirmation.

Problem to solve

Problem statement

Design one enterprise system that supports distinct administrative jobs while keeping roles, permissions, inventory, and responsibility clear across the hierarchy.

How might we

How might we help each administrator move and assign digital assets confidently across a complex hierarchy without forcing different jobs into one generic workflow?

01 / 03

Three decisions simplified the admin workflow.

Simplify a multi-tenant administration system without flattening real permission, hierarchy, inventory, and accountability differences.

Enterprise Asset Manager shown across desktop and mobile
Dashboard · role and action stay aligned.

Let role determine what the dashboard prioritizes.

Each administrator sees the inventory, requests, progress, and exceptions that match their authority instead of a universal dashboard full of unavailable actions.

Enterprise Asset Manager assignment and distribution workflows
Distribute · inventory movement with visible context.

Treat distribution as a traceable operation.

Allocation and distribution preserve source, destination, balance, and responsibility so global and local administrators can understand what changed.

Enterprise Asset Manager administrator details and inventory view
Assign · asset, candidate, and status together.

Keep assignment close to candidate progress.

Assignment connects inventory to the person and makes follow-up status visible without forcing administrators into separate systems.

02 / 03

Sixteen opportunities became a phased product direction.

Legacy enterprise asset-management workflow before the redesign
Legacy workflow · starting point before phased redesign

Stakeholder interviews, role analysis, journey work, and prioritization narrowed the opportunity set. The role-tiered redesign shipped and reduced administrator task time approximately 50%.

03 / 03

The shared model does not cover every client exception.

Tradeoff

Permission clarity can add visible structure.

Evidence boundary

Enterprise workflows vary by partner and contract; the public case shows the shared product model rather than every client exception.

Next test

Measure which exception paths still force administrators to leave the system or rely on manual reconciliation.

MPM administrator hierarchy
The shared administrator hierarchy clarifies roles while leaving room for client-specific rules.

Go deeper

See the decisions behind the work.

The full case study contains additional project context, iterations, and evidence.

Full case study

Next case study

I had to make palm capture work across a person, a tablet, the biometric system, and an unreliable network.