0 min read

Optimizing Affiliates Management app

PRODUCT DESIGN

PRM

The short version

I led this as the sole designer, assigned by the Head of Design following a request from the Head of Affiliates.
Four weeks total - two in research and design, two in testing and iteration.

Results:

IT support tickets for password resets down an estimated 80-85%, based on IT management feedback

IT support tickets for password resets down an estimated 80-85%, based on IT management feedback

Onboarding time cut from 3 weeks to 1 week

Onboarding time cut from 3 weeks to 1 week

Errors when creating and editing affiliate links dropped from roughly 15% to under 5%, based on team leads feedback

Errors when creating and editing affiliate links dropped from roughly 15% to under 5%, based on team leads feedback

Estimated 30-45 minutes saved per manager per day on brand switching and re-authentication

Estimated 30-45 minutes saved per manager per day on brand switching and re-authentication

The context

NTTool was an internal CRM used by affiliate managers to run partnerships across CyberGhost, Private Internet Access, ExpressVPN, and Intego Antivirus - connecting campaign data, landing pages, and financial transactions for paid user acquisition across all brands.

The tool was built by engineering without design involvement, and the UX reflected that honestly. It functioned when each brand ran separately and managers stayed within one. When the backend unified into a single data source and cross-brand work became standard, the app-reload-per-brand model broke down, a new cybersecurity mandate required 2FA the app couldn't support, and complaint volume from the affiliate team reached the Head of Affiliates' desk.

The story

What was broken

The problems came through clearly in research. One manager had spent hours over a weekend with IT trying to restore affiliate data he'd accidentally deleted. Another said onboarding new team members was taking weeks - the app was too cluttered, people got lost in it. A third complained that the contrast made long sessions physically uncomfortable.

The structural problem was underneath all of it. The app had been built as separate instances per brand - switching meant logging out, loading a different version, logging back in. That worked when managers stuck to one brand. When cross-brand work became standard and the backend unified into a single data source, the model collapsed. The app couldn't support 2FA, had no password recovery flow, and its dashboards had no filtering, sorting, or bulk actions. Every workaround ran through IT.

What I decided and why

Four weeks was the entire window - two for research and design, two for testing and iteration. Internal tool, not directly tied to product revenue. The timeline forced a clear call: fix the core workflows properly, update everything else visually without a full redesign. Some screens got rebuilt. Others got cleaned up and made usable. That trade-off was deliberate.

Keeping the old multi-instance architecture was never a serious option. The backend had already changed - designing around a problem that no longer existed made no sense. Working with IT on authentication and engineering on everything else, we mapped the new model during research and design: a unified login with an in-app brand filter. Log in once, switch brands via a dropdown, data stays separated by brand. Authentication was later replaced by SSO entirely, but that came after this project.

The brand-specific color schemes had a logic originally - when each manager worked in one brand, visual differentiation made sense. When the same person switches between three brands in a day, an interface that changes appearance each time adds noise, not clarity. A unified dark system removed it. The brand logo in the sidebar does the same job without the confusion.

The 2FA integration was mandatory - the cybersecurity team required it and the old app simply couldn't support it. Working with IT, we mapped it into the standard login sequence using an established pattern: login, verify, done. It added one step. As expected, in the first few days after rollout IT tickets spiked as the team completed 2FA setup - then dropped to their eventual 80-85% reduction. The password recovery flow was built the same way: an existing IT module handling the mechanics, mapped into a self-service flow directly in the app.

What shipped

Unified login with a brand filter replaced the multi-instance model. Self-service password recovery and integrated 2FA replaced the IT Slack queue. Dashboards got sortable columns, filtering, pagination, and bulk actions - the data was always there, it just needed to be made manageable. Two-step deletion and inline validation reduced errors in the affiliate link creation flow. A unified dark/light color system replaced the brand-specific schemes, with dark set as default based on unanimous team preference.

The screens that didn't get fully redesigned got cleaned up enough to stop causing friction. Not everything was perfect at handoff. But the core workflows worked the way they should have from the start.

As you made it so far

Login and authentication: Before and after: the original multi-instance login flow versus the unified login with brand filter, password recovery flow, and integrated 2FA. Dark and light mode versions.

Brand switching: The in-app brand dropdown in context. Before: the logout/reload cycle. After: instant switching within a single session.

Dashboard and data management: Before and after: dense unfiltered data blocks versus the redesigned tables with sorting, filtering, pagination, and bulk actions.

Destructive action handling: Two-step deletion flow and inline validation feedback for affiliate link creation and editing.

Visual system: The unified dark/light color system applied across brands. Before: brand-specific color schemes. After: consistent visual language regardless of brand context.

Alex Dihel | Product & Marketing Design Leadership | Design Operations   www.alexdihel.com © | Privacy

Alex Dihel | Product & Marketing Design Leadership | Design Operations   www.alexdihel.com © | Privacy

Alex Dihel | Product & Marketing Design Leadership | Design Operations   www.alexdihel.com © | Privacy