.png)
Redesigning navigation and data-heavy workflows for a credit and political risk insurance platform.
2023–2024
Solo Product Designer
Product Manager, Business Analyst, Frontend and Backend Engineers, QA
.png)
As Zenik expanded, crowded navigation and inconsistent UI patterns made complex workflows harder to find, use, and scale.
As the solo Product Designer, I led the work from research and information architecture to final UI and handoff.
I reorganised navigation, introduced reusable patterns for dense data, and designed new risk, reporting, finance, and operational workflows.
The redesign created a clearer product structure and a reusable foundation for future modules.
As Zenik expanded, users struggled to find frequent tools, scan dense data, and work with inconsistent interface patterns.
Frequent tools were buried across multiple modules and menu levels.
Complex tables made important data difficult to scan and compare.
Actions, statuses, and controls behaved differently across workflows.
01 – Simplify navigation
02 – Clarify data and status
03 – Standardise interactions
I mapped overlapping destinations and deep paths, then grouped related areas into a clearer structure for current and future modules.
Frequent tools were buried in a long, multi-level sidebar.
I regrouped destinations and added search, quick links, and breadcrumbs to make navigation clearer and scalable.
Clear module grouping
Search and quick links
Visible navigation context
Scalable structure
.png)
Related tools are grouped into clear, expandable navigation areas.
Dense tables made ratings, trends, and data versions difficult to compare.
I kept the table compact but clarified hierarchy, risk scales, trend indicators, and version controls.
Consistent risk scale
Visible data version
Scannable trends and ratings
Version-aware editing
.png)
Finance and operational workflows required both high-level monitoring and access to detailed records.
Report parameters appear before summary metrics and charts, while expandable rows reveal detailed records without taking users away from the list.
Filters before results
Clear KPI hierarchy
Expandable row details
Contextual actions
Filters lead into summary metrics and detailed financial charts.
.png)
Expandable rows reveal record details and actions without leaving the list.
.png)
To keep new modules consistent, I created shared foundations for navigation, tables, filters, cards, form controls, and system states.
Reusable interaction rules helped design and engineering extend the platform without introducing another one-off solution.
Across selected core workflows.
After clearer navigation and shared interaction patterns.
Through reusable components and interaction rules.
Based on internal usability testing and delivery estimates.
The new foundation supported six core product areas, including Finance, Risk Ratings, Claims, and Approvals.
The main challenge was balancing information density with scanability across modules. I learned that enterprise consistency depends as much on shared interaction rules as on visual tokens.
Next, I would track navigation errors, task time, and adoption of search and quick links.