JG Admin Dashboard
Modernizing a fragmented enterprise administration ecosystem into a unified web experience with clearer navigation, dashboard access, and scalable UX patterns.

Unifying multiple internal tools into one cohesive experience.
The existing admin ecosystem included multiple solutions across Windows Forms, Java/Angular, and C#/Angular. The redesign focused on a single web login, unified navigation, role-based access, and easier access to common internal workflows.
Goals
- Create a unified administration experience across fragmented internal tools.
- Improve discoverability of frequently used applications and workflows.
- Support a scalable foundation for future modernization and role-based access.
- Reduce unnecessary navigation friction for daily internal users.
Expectations
- Provide a clearer MVP direction for dashboard and navigation decisions.
- Align application access with real operational usage patterns.
- Make the experience easier to understand without exposing every tool at once.
- Support stakeholder alignment before deeper implementation work.
Internal teams working across benefits administration workflows.
Primary users included internal administration teams, customer inquiry representatives, and operational staff who needed reliable access to multiple applications, plans, and role-based workflows throughout the day.
MVP Strategy
The MVP discussions helped the team focus on what users needed most when first entering the system. Instead of treating the dashboard as a place for every possible feature, the direction focused on validating the most useful entry points and navigation patterns first.
Data-Driven Decisions
Application visibility and dashboard hierarchy were informed by frequently used and least-used applications. This helped prioritize high-value workflows, reduce cognitive load, and avoid giving equal visual weight to tools that users rarely needed.
The challenge
- Fragmented applications and navigation patterns
- Legacy AS400 security dependencies
- Role-based access and plan-based workflows
- Need to support converted and non-converted applications
My contribution
- Explored dashboard and navigation concepts
- Created wireframes and high-fidelity mockups
- Compared chips, sidebar, and navigation rail patterns
- Validated direction with users and stakeholders
The dashboard needed to reduce cognitive load first, not simply expose every available application.
User feedback showed that the chips-based version felt most intuitive because it supported quick recognition and simpler visual grouping.
Selected Screens




A scalable foundation for enterprise modernization.
The project established a clearer direction for unified administration, dashboard access, application launch behavior, and future migration away from fragmented legacy experiences.