Restructuring workflows and interface patterns within a fragmented enterprise system.
[TYPE] Enterprise / Resource Portal / Web Platform / 2025
[ROLE] Product Designer
[SCOPE] Flow restructuring / UI refinement
Project Overview: Enterprise Portal
The platform is an internal resource portal used by insurance professionals to access policy forms, rules, and regulatory materials across different product lines and jurisdictions.
Users rely on the system to search, filter, and navigate large volumes of documentation to support underwriting, compliance, and product-related workflows. Due to the complexity of insurance data—spanning multiple states, product variations, and document types—the experience requires clear structure and efficient navigation to remain usable.
Certain details have been generalized and original system screens are not shown due to the nature of the project.
[01] PROBLEM
Fragmented system state
The platform existed across both a legacy system and an in-progress redesign, each introducing its own inconsistencies. Despite iteration, core usability issues persisted across versions.
Dense, text-heavy layouts made scanning difficult
Weak hierarchy reduced clarity and prioritization
Navigation patterns varied across flows
Redesign efforts improved visuals but did not resolve structural issues
[ISSUES] high content density / competing sections / fragmented navigation / unclear hierarchy / disconnected filtering / competing actions
[02] APPROACH
Aligning and refining existing system patterns rather than introducing new ones
Given the fragmented state across both legacy and in-progress versions, I focused on improving structure and consistency within what already existed. With limited access to direct user research, I relied on domain experts to understand how workflows were expected to function, translating their mental models into clearer, more consistent user-facing patterns. This meant clarifying core workflows before redefining them, reducing cognitive load through stronger hierarchy and grouping, standardizing interaction and layout patterns across screens, and prioritizing consistency across the system.
[04] EXECUTION
Reconciling multiple system inputs into unified workflows
The work involved consolidating flows derived from legacy interfaces, in-progress redesigns, and early internal explorations into more consistent navigation patterns. This meant aligning entry points, simplifying user progression across tasks, and establishing shared structures that could be applied across the system.
[04.1] EXECUTION
Simplifying navigation and aligning core workflows across the systems
Navigation and workflows varied significantly across legacy screens, in-progress redesigns, and internal explorations, making it difficult to understand where to begin and how to move between related tasks.
I focused on simplifying navigation by establishing clearer entry points, reducing variation between similar flows, and aligning actions under consistent structures.
Starting with the home experience, I introduced a more task-oriented layout inspired by systems like Microsoft SharePoint. This created a clearer progression from high-level entry points into scoped views such as state-specific packages and forms, making movement through the system more predictable.
[04.2] EXECUTION
Improving filtering flexibility and data interaction for large result sets
Filtering and search interactions were overly rigid, making it difficult to balance precise results with broader exploration. Exact matches often removed useful context, while existing filters lacked the flexibility needed to refine results effectively.
I improved the experience by making filtering more flexible and adjustable, allowing users to narrow results without losing visibility into related data. At the same time, I simplified how information was presented by improving table hierarchy and spacing, making large result sets easier to scan.
Interaction patterns were also clarified by introducing more consistent selection behaviors for working with multiple results, supporting bulk actions without adding unnecessary complexity.
[04.3] EXECUTION
Structuring complex product information into a more scannable and cohesive layout
Exploring product information required navigating multiple dimensions, including product lines, state-specific availability, and related resources. In the legacy system, this information was fragmented across lists and sections, making it difficult to understand how everything connected.
I introduced a more cohesive structure that balanced high-level overview with detailed information. A visual map provided quick insight into state-level coverage, while supporting lists retained precision and control. This made it easier to understand relationships between data without overwhelming the interface.
By organizing these elements into a more consistent layout, the experience became easier to scan and navigate while preserving the depth of information required for domain-specific workflows.
[ISSUES] dense chip groupings / repetitive state listings / fragmented categorization / low scannability
Availability was distributed across multiple repeated sections, requiring users to scan and mentally piece together coverage across states and product types.
[CHANGES] visual overview / centralized structure / clearer hierarchy / reduced cognitive load
Availability is consolidated into a map-based system with supporting lists, allowing users to quickly understand coverage at a glance and navigate into details more predictably.
[05] REFLECTION
Establishing a clearer structural direction despite evolving project constraints
The redesign work was well received internally, particularly in how it brought more structure and consistency to a previously fragmented system. While the project was ultimately discontinued due to organizational changes, the work helped establish a clearer direction for how the platform could be organized moving forward.
Working within a complex domain without direct user research required relying on domain experts to define ideal workflows, then translating those into structured, user-facing patterns. This reinforced the importance of balancing expert input with clear, consistent interaction design.
Overall, this project strengthened my ability to work within ambiguous constraints, align multiple inputs into a cohesive system, and prioritize structure as a foundation for usability.