Neuron is an internal enterprise platform used by one of the biggest insurance groups in Central Europe. The goal is to unify and streamline daily work across teams and roles, from internal staff to external agents.
I've been part of this product team full time since early 2024. Alongside 10 designers and 2 design system maintainers, I contributed to 3 out of 7 core domains: Product Modelator, Tasklist, and Reporting. Each of these tools required a different mindset and problem solving approach.
My main responsibility was designing complex interfaces that are predictable, scalable, and easy to use, even in systems that have to accommodate thousands of data points and constant business changes.
Product Modelator
This was the first domain I worked on and the one I spent the most time with. I joined the project while the analysis was still ongoing. At first glance, it looked like a simple tool with a few screens. But as the requirements evolved, we quickly realized the original concept wouldn't scale.
After a few months, we decided to rethink everything. That's when I proposed using a tree-based layout to reflect the product's deep, parameter-based structure. Each product can contain thousands of attributes, all nested in a hierarchy. The goal was to help users navigate this structure without feeling overwhelmed.
I designed a tree table with breadcrumb navigation and scoped views. This allows users to focus on a specific section of the structure while always understanding where they are. It reduced errors and improved the mental model of the interface.
Another challenge was how often the business logic changed. We redesigned the core forms many times. Eventually, I proposed a modular approach where individual sections of the form could adapt independently. That made us much more agile and saved time across the team.
Lately, our focus has shifted to helping users work with large sets of parameters at once, often in multiple dimensions. It's a constant balancing act between flexibility and clarity.
Tasklist
The Tasklist started as a simple list of tasks. Over time, it became a core tool used across different domains in the platform. I've been working on it for about a year and have seen it evolve into a more complex and powerful feature.
The challenge was to support different levels of detail. Some users need to browse tasks quickly, others want to open full details. I designed a layout that supports both. Tasks are presented in expandable cards, with metadata upfront and full content available on click.
We also added sorting, filtering, and bulk actions to support power users. These features had to be simple to use and fast to access. One of the biggest design sprints focused on making the tool responsive. That meant redesigning parts of the layout, rethinking navigation, and aligning on a shared version used by multiple domains.
I worked closely with analysts and developers throughout. We tested each step and iterated together, making sure it worked not just in theory but in practice.
Reporting Dashboards
I designed dashboards for supervisors to track how well tasks are being completed across teams. The goal was to show task completion rates and compare performance by week, team, or individual.
Dashboards visualize completed, ongoing, and incomplete tasks. Charts follow a consistent style and include clear labels to help users understand what they're seeing. We tested with supervisors and adjusted layout and terminology to better fit their mental models.
Design System
We used the VIGo design system with dynamic tokens via Token Studio. Each domain had to follow brand guidelines (e.g., Kooperativa, ČPP) while maintaining UX consistency. I contributed components and collaborated on theming logic that supports multiple brands.
Reflection
Working on Neuron taught me a lot about designing long term, for systems that are constantly evolving and cannot afford to break. It pushed me to think beyond screens and flows and instead focus on adaptability, logic, and resilience.
Whether it was rethinking a tree based parameter editor or redesigning task management for multiple domains, I learned how to build structures that can flex without falling apart.
It also reinforced the importance of close collaboration. Weekly handoffs, workshops with analysts, and regular syncs with developers helped us make decisions quickly and validate them early.
This is the kind of project where good UX does not mean glossy visuals. It means clarity, consistency, and letting people get their work done without friction.