As a UX and Product Designer, I handled three features end-to-end and contributed to another one and a half.
11.2023 – 3.2024 | Hybrid
1. UX and UI design for the Custom Roles feature
2. UX and UI design for the User Migration feature
3. UX and UI design for the Custom Domain feature
4. Best practices research: where and how to implement documentation
1. UX and UI design for the Custom Roles feature
Designing the user experience and interface for the Custom Roles feature was my first project with Frontegg, a platform serving B2B2B SaaS companies.
When I joined the team, the product manager had already gathered about 80% of the required information to enable smooth creation of custom roles.
My mission?
To bring the feature to life — mapping two distinct user journeys:
• One for Vendors, who configure role customization for their clients
• And one for Tenants, who define and manage the custom roles themselves
👉 [Link to Frontegg documentation – here]
It was a fascinating journey. Here’s how it unfolded:
The Challenge
When I joined the project, Tenants could only create custom roles via API, with no UI-based way to manage or edit them. This meant manual setup, often requiring assistance from the Vendor side.
Our goal was clear:
Empower both Vendors and their clients to manage roles independently, reduce support overhead, and give each company full control over how their product behaves.
But bringing this feature to life came with complexity:
• It had to integrate seamlessly into multiple areas of the system
• It had to align with existing backend constraints
• It had to work across three key interfaces: the Backend, the Builder, and the Administrator panel
So how did we crack it?
👇 Let’s walk through the process and solution.
The process
The project unfolded in clear stages, each focused on aligning user needs with system logic.
• Understanding the system
I began by learning the architecture and flows in depth, to understand how the new feature would need to fit in.
• Mapping relevant personas and pain points
I gathered insights about the key user types involved and documented the obstacles they faced when managing roles.
• Defining success with the product manager
We aligned on clear success criteria. I also suggested specific UX recommendations, such as “How many users have this role?”, to guide development priorities.
• Conducting best practices research
I explored role management patterns across similar platforms to inform our approach and avoid known usability issues.
⸻
In parallel, I mapped two critical user journeys:
• Vendors needed a way to configure and offer role customization to their clients.
• Tenants would now gain the ability to create, manage, and apply custom roles independently, as needed.
From there, I translated all findings into clear UX proposals, outlining exactly which changes we should introduce and how they aligned with our success criteria.
This was a dynamic process that included ongoing conversations with the PM, design lead, and development team. The result included valuable improvements like the introduction of Bulk Actions and full support for QA and launch.
The Solution
• Seamless integration
Instead of adding a new button that opens a crowded drawer, we embedded the custom roles directly into the existing permissions page. The experience stayed familiar, and the flow remained smooth.
• Thoughtful UI enhancements
We introduced a new column in the permissions table and added a bulk action capability. Power users can now manage roles with ease, without adding visual noise or complexity.
• User-focused design decisions
We made sure tenants could activate and use the feature easily, without confusing other user types or complicating the interface. Everything stayed clean and intentional.
• A powerful feature, gracefully embedded
Custom roles now feel like a natural part of the product. The functionality expanded, but the system’s complexity didn’t.
The result
The last time I checked, there wasn’t yet enough data to draw clear conclusions. However, the absence of support tickets or user complaints was a promising early signal that the experience was intuitive and friction-free.
Frontegg | UX and UI design services for a B2B2B platform and a digital product in the developer tools space
• Rapid and in-depth understanding of the system and company
• Building on existing research and conducting quick-turnaround research when needed
• Grasping multiple user perspectives within B2B2B contexts
• Thoughtfully integrating new features into existing workflows
2. UX and UI design for the User Migration feature
UX and UI Design for Bulk User Transfers in the Backend
I had the opportunity to work with Frontegg during a pivotal time, when the team decided to introduce a new feature within the Backend’s User Management area. The goal was to enable bulk migration of user groups into the platform through a streamlined and efficient process.
In close collaboration with the product manager and Frontegg’s excellent development team, we designed an intuitive and focused user experience for the migration flow.
⸻
What I Learned
This was my first hands-on exposure to the world of user migration, and it significantly deepened my understanding of the operational and technical challenges involved.
As part of this project, I was also given the opportunity to define the key performance indicators (KPIs) that would eventually be surfaced on the migration screen. I tailored those metrics to balance user needs with broader business goals.
👉 [Link to Frontegg documentation – here]
⸻
Strategic UX Highlights
• I made sure to communicate the UX thinking and value behind each design decision to the PM throughout the process.
• I focused on translating and mapping product requirements into clear user flows, surfacing pain points and identifying opportunities early in the journey.
• Once we gathered enough context from business, product, and user angles, we were able to make smart, focused UX optimizations that served both usability and scalability.
The Challenge
The core challenge in this project was designing an intuitive and efficient user experience for the migration process, starting from the initial requirements and early wireframes provided by the product manager.
The original concept was too abstract. It lacked clarity around the real concerns and expectations of the users who would carry out this process. I needed to dig deeper to identify specific pain points and decision moments where clear guidance, feedback, or reassurance would make a difference.
Another key challenge was integrating this new feature seamlessly into Frontegg’s existing system. Most users would only go through the migration process once, so the design had to strike a balance between making the flow easily accessible and minimizing its presence within the broader interface to avoid disrupting the core experience.
To address both challenges, I conducted focused UX research and system analysis. I worked closely with the product manager and the head of product to define exactly what users would need at each step — and how the system should respond.
The process
From Research to Decisions
The first step was to dive deep into the research. I reviewed all the links, read every doc, and made sure I fully understood the context. But I didn’t stop there — to avoid staying in the abstract, I translated everything into a detailed user journey map.
That map became my compass. It helped me work independently, spot gaps, and make smarter decisions.
For example:
• I proposed that we define and display clear KPIs as part of the experience.
• I also realized we didn’t just need a migration wizard, but a dedicated dashboard to monitor and manage the process after it’s done.
The Solution
This insight came not only from the journey mapping, but also from competitive research. I explored how other large platforms approached similar features and adapted relevant patterns.
The result
I took the product manager’s initial research and transformed it into a concrete foundation — defining the user journey, sketching early UX concepts, iterating through feedback, and ultimately delivering a solution that felt so natural, it looked like it had always belonged in the product.
3. UX and UI design for the Custom Domain feature
UX and UI Design for Seamless Domain Updates
At first glance, designing the Custom Domain Update feature seemed straightforward. But beneath the surface, it presented a real UX challenge — crafting a flow that would let users update their custom domain smoothly, without triggering downtime or frustration during the migration.
To get this right, I had to map out every possible user behavior, not just the ideal flow. The development team flagged a serious risk: without clear guidance, users might skip critical steps, leading to unexpected system failures and a poor experience.
This meant every part of the flow needed to be thoughtfully planned, clearly worded, and easy to follow — even for users unfamiliar with DNS settings or backend configurations.
I focused on creating an experience that:
• Guided users step by step, with no ambiguity
• Surfaced only relevant actions and warnings at the right time
• Prevented missteps by design, not just explanation
After a user-centered design process, the feature was implemented successfully — delivering a clear, intuitive, and frustration-free experience across all possible use cases.
4. Best practices research: where and how to implement documentation
Comparative analysis of developer documentation tools and structures
As a UX and product strategy expert, my final research project at Frontegg focused on how leading software companies structure and present their developer documentation.
The goal was twofold:
1. Identify key competitors and analyze how their documentation platforms are built
2. Discover which tools they use to deliver structured, scalable documentation
After receiving an initial competitor list from the CEO, I expanded it by sourcing additional relevant companies. I then conducted a deep analysis of each documentation platform, studying layout, structure, tone, and technical underpinnings.
To my surprise, the biggest challenge wasn’t comparing the UX — it was identifying the tools powering each documentation site, since this information wasn’t always publicly available. With strategic investigation, I was able to uncover the tech stacks behind most platforms and distinguish common patterns across the market.
The outcome:
• A clear mapping of documentation structures across similar companies
• Insight into which tools were most commonly used (and why)
• A set of actionable recommendations and selection criteria to guide Frontegg’s next steps
Frontegg decided to move forward with one of my top tool suggestions and began a proof of concept (POC) shortly after the research concluded.
Final Takeaways
During any research process, there’s often a moment where doubt creeps in — when the data collected feels messy, inconclusive, or somehow not “enough.”
At that point, it’s important to pause, return to the core research question and success criteria, and simply breathe.
One powerful tactic is to talk through the findings with someone else. Saying the insights out loud helps organize thoughts, clarify what truly matters, and separate signal from noise. It also reveals what still needs attention and what’s already solid.
Letting go of pressure for a moment, revisiting your foundation, and seeking outside perspective are key steps in overcoming uncertainty — and in moving the research forward with focus and clarity.
👉 Check out the posts I wrote about this project [here] and [here].