Back
ASUS - IT console
ASUS Expert Device Center
Give IT Clarity
at Every Step
Helping enterprise IT stay informed from device onboarding to task completion.
WORK AT
ASUS
TYPE OF WORK
Enterprise UX
DURATION
2025-2026
CONTEXT
ASUS Expert Device Center helps enterprise IT teams monitor devices, deploy applications, and schedule system updates.
We focused on creating a consistent management experience, defining what IT needs to know, confirm, and track across three key stages:
MY ROLE & COLLABORATION
1
UX Design & Team Coordination
Designed core flows for device management and the dashboard. As the design team coordinator, facilitated daily syncs and tracked issues and follow-up actions with the Project Lead.
2
Design Standards & Cross-Team Alignment
Consolidated team decisions into UX guidelines and the Design System. Collaborated with engineers on design tokens and aligned visuals and interaction behaviors across design teams.
THE CHALLENGE
User interviews highlighted a need for clearer visibility into management tasks: what is still running, what has actually completed, and which devices need attention. This becomes especially important when IT manages multiple devices and switches between tasks.
The challenge was to make these workflows easier to understand and track, helping IT stay in control from device onboarding to deployment verification.
KEY DESIGN DECISIONS
1
Clarified stages and completion criteria
Distinguished installer readiness, device readiness for management, task creation, and execution completion, with clear next steps at each stage.
2
Balanced confirmation with background execution
Kept target-device and scheduling checks before deployment, while making progress and status accessible as time-consuming tasks continued in the background.
3
Connected tasks to per-device results
Organized results by status so IT could identify completed, ongoing, and failed tasks across devices.
DESIGN OUTCOMES
3
Connected Workflow Stages
Connected onboarding confirmation, background execution, and outcome verification, with clear statuses and next actions.
46+
Features Using Shared UX Rules
Applied shared interaction guidelines across 46+ features, aligning confirmation, feedback, and page behavior.
38+
Reusable UI Components
Built and maintained 38+ shared components to support consistent visuals and interactions across core features.
PRODUCT PREVIEW
A preview of the core interfaces for monitoring devices, managing deployments, and tracking results.
Dashboard
Bring device health, alerts, and deployment information into one overview to highlight items that need attention.
The decisions behind the experience
3 min read · 4 sections
THE FULL CASE STUDY
01
Help IT distinguish installer readiness from device readiness.
Downloading the installer does not complete onboarding. IT must still deploy it, complete installation, and verify device status in the platform.
01
Design Focus
Make the next steps explicit
The design guides IT through setup, explains what to do after download, and provides device statuses for verification.
1
Guide onboarding setup
Guide IT from adding devices to choosing an onboarding method and setting installer expiration and device limits.
2
Explain what comes after download
The confirmation message explains how to deploy the installer and return to check device status, making it clear that onboarding is still in progress.
3
Verify device readiness
Management, connection, and license statuses help IT assess whether a device is ready for further management.
WORKFLOW WALKTHROUGH
" IT can distinguish installer readiness from device readiness and understand what to do next. "
02
Let IT continue working while tasks run.
Uploads and deployments take time. IT needs to move on to other work without losing access to progress or mistaking task submission for completion.
01
Design Focus
Let uploads continue without blocking navigation
Keep upload feedback available across pages so IT can continue working and check progress when needed.
1
Keep upload progress visible
A persistent panel shows the file name, upload status, and estimated time remaining, helping IT understand what is still running.
2
Confirm completion across pages
Upload feedback remains available when IT switches pages. A completion message confirms that the file has been uploaded without requiring a return to the original screen.
WORKFLOW WALKTHROUGH
"IT can continue other work while staying informed about upload progress and completion."
03
Help IT identify which devices still need attention
A single deployment can succeed on some devices, remain in progress on others, or fail. IT needs per-device results to understand what is complete and what needs follow-up.
01
Design Focus
Show overall status, then support per-device review
Distinguish task creation from installation completion. Present a status summary and let IT filter device results to find those that need follow-up.
1
Distinguish task creation from completion
The confirmation message indicates that the deployment task has been created. Installation results are checked separately in the deployment report.
2
Review results across devices
The report presents successful, in-progress, and failed installations, helping IT understand the overall deployment status and review individual device results.
3
Narrow the list for follow-up
Status filters help IT focus on failed devices or track those still in progress without reviewing the entire list.
WORKFLOW WALKTHROUGH
" IT can continue other work while staying informed about upload progress and completion."
04
Turn individual design decisions into shared team practices.
Different designers worked on different features across the platform. Alongside my feature responsibilities, I took on my first role as a design team coordinator, supporting the Project Lead and helping the team align on shared interaction behaviors.
01
Design Focus
Make decisions clear, documented, and reusable
Connect daily discussions with UX guidelines, shared components, and engineering implementation so team agreements can be applied across features.
1
Keep discussions focused on decisions
I facilitated daily syncs, consolidated UX issues, and helped clarify constraints and open questions. Working with the Project Lead, I documented decisions and tracked follow-up actions.
1
Translate agreements into shared UX rules
I consolidated team decisions into UX Design Guidelines, covering page patterns, confirmation behavior, and feedback. These guidelines gave designers a common reference when working on different features.
2
Maintain reusable components and align implementation
I built and maintained the shared component library and worked with engineers on design token definitions and implementation mapping. I also coordinated with other design teams to align visual and interaction behaviors.
THE FULL CASE STUDY
05
Conclusion
This project deepened my understanding of how a sense of control comes from having enough information to make decisions. Across device onboarding, background processing, and per-device results, I connected task status, completion criteria, and next steps to help IT decide when to wait, continue other work, or investigate a device.
Taking on my first role as a design team coordinator also expanded my responsibility beyond individual features. I helped clarify issues, document decisions, and translate team agreements into shared guidelines and components.
What I'd do differently
I would test the design earlier through a complete work scenario, letting IT submit a task, switch to other work, and return to check the results.
I would focus on whether administrators can understand the task’s current stage and find where to resume after their attention has shifted. This would help assess whether progress feedback and results entry points are clear enough in the multitasking situations the design aims to support.
What I'd still defend
I would still keep essential checks before deployment, allow time-consuming operations to continue in the background, and clearly distinguish preparation, task creation, and completion on devices.
Batch operations require careful confirmation, while waiting should leave room for other work. These decisions let IT review the scope, move on, and return to verify actual results. I would also preserve this logic in shared interaction guidelines so administrators can understand tasks consistently across features.