By building, monetizing, and distributing ad-filtering technologies, eyeo creates solutions that allow all members of the online ecosystem to prosper.

Due to professional restrictions and / or the collaborative nature of these projects, specific research artifacts (e.g., user flows and interviews, heatmaps, internal documentation) cannot be shared; illustrative artifacts will be used instead. This case study focuses on design rationale, visual direction, and my role in the creative process.

---

1. Project Start

The eyeo hub was a custom-built internal project management tool created by the IT department at eyeo. Used primarily for ticketing, task tracking, and team coordination, it was the operational backbone of internal workflows across departments like Legal, HR, IT, and Product. By mid-2016, the interface was considered outdated and unintuitive. I was brought in to deliver a complete visual refresh while maintaining the existing backend functionality. The redesign aimed to improve usability, structure, and visual cohesion across all views without rebuilding core logic.

eyeo hub home

2. Research

I began by auditing the existing Eyeo Hub interface, mapping its structure and identifying user friction points in key flows: ticket creation, progress tracking, and activity overview. Since there was no official UX research team on this project, I conducted informal interviews with frequent users from different departments. The most common feedback centered on poor information hierarchy and visual clutter.

Having previously worked with Active Collab at MED-EL, I used it as a primary inspiration point. Its clarity, modular layout, and focus on functional minimalism aligned well with what Eyeo Hub needed. This reference helped establish a benchmark for layout structure, spacing, and typographic rhythm.

Active Collab UI references

3. Ideation

Based on research findings, I proposed a minimal, grid-based layout with a consistent typographic scale and clearly separated modules. The primary goals were:

• Improve readability and reduce visual overload
• Clarify relationships between tickets, projects, and users
• Streamline primary actions like ticket creation, editing, and filtering

Instead of forcing a new design system, I created a lightweight design language tailored to the product’s structure. I prioritized simplicity and clarity over aesthetics, knowing the audience was internal and heavily task-oriented.

early user flow diagram

4. Concepts

I explored multiple wireframes and UI directions focused on scalable components:

wireframes

These concepts were presented to the IT team and key stakeholders in live walkthroughs using InVision prototypes, allowing feedback before implementation.

5. IMPLEMENTATION & DELIVERY

The final design introduced a lightweight dark sidebar, clear table structures, and consistent UI patterns across all views. Each module maintained a sense of hierarchy through careful use of font weights, iconography, and white space.

6. Retrospective

While the project succeeded in modernizing Eyeo Hub’s interface and significantly improved daily usability, its lifespan was limited. About a year later, eyeo transitioned to Jira for its superior scalability, integrations, and ecosystem support. Still, Eyeo Hub served as a crucial bridge during a time of growth and complexity.

From a personal perspective, this project was a valuable early opportunity to work on a dashboard-like platform—an experience I underestimated in its importance until recently. It taught me how to make practical design decisions under strict functional constraints and how to align a visual refresh with legacy systems without causing friction for developers or users.