Product
Holafly B2B Center
Client
Holafly
Area
User management and plan assignment
Responsibilities
Platforms
Desktop and Mobile
The context
The existing experience relied on a contextual bulk action that only appeared after selecting users.
The flow required users to:
Although the functionality existed, the action had low discoverability because users could not see it before interacting with the table.
Some users were unsure whether they needed to filter, select users, or open the individual Assign one action first. This increased support requests and made a common administrative task feel harder than necessary.
Our User
Operations managers need to assign connectivity plans to multiple users quickly and accurately.
The primary user is an operations manager responsible for managing connectivity plans across multiple teams and user accounts.
They work with large user lists, handle repetitive administrative tasks, and need to make changes that may affect many people at once. Their work requires speed, accuracy, and confidence, especially when plan availability is limited or when several groups must be managed simultaneously.
I proposed focusing the redesign on the following areas:
Discoverability of the bulk assignment action
Identification of users without a plan
Selection of eligible recipients
Visibility of plan availability
Review of affected users before confirmation
Feedback after completing the assignment
The project did not redefine plan pricing, inventory rules, user eligibility criteria, or the individual assignment flow. Those areas remained outside the design scope.
This distinction kept the work focused on the interaction model for bulk assignments and prevented the redesign from expanding into a broader user-management or billing initiative.
Before exploring solutions, I defined the following design success criteria.
Make all available plans discoverable.
Help users understand the main differences between plans.
Reduce duplicated information.
Avoid displaying several configuration forms simultaneously.
Separate product selection from product configuration.
Preserve the commercial visibility of the Annual plan.
Support plan-specific rules and fields.
Create a clear transition from comparison to checkout.
Remain scalable as the product offering grows.
Because the project did not yet have post-launch analytics, these criteria were used as design evaluation principles rather than claimed performance results.
I used AI as a design partner to accelerate exploration, visualize early concepts, refine interaction rules, and build a functional prototype.
I used AI throughout the project as a design partner to accelerate exploration, visualize early concepts, refine interaction rules, and build a functional prototype.
AI helped me compare alternative flows, identify conflicting behaviors, generate initial interface concepts, and improve the project documentation. I reviewed and challenged each output, rejecting proposals that did not match the user’s mental model or product constraints.
The final interaction model, design decisions, edge cases, and visual execution were defined and refined by me in Figma. AI shortened the iteration cycle, but it did not replace the design reasoning behind the solution.
A functional prototype of the final bulk assignment flow, including filtering, user selection, plan availability, review, confirmation, and success feedback.
A functional prototype of the final bulk assignment flow, including filtering, user selection, plan availability, review, confirmation, and success feedback.
Using Figma Make, I transformed the final screens into a functional prototype that reproduced the key interactions, system states, and business rules, including user eligibility, plan availability, selection behavior, review, and confirmation.
During testing, participants were able to complete the assignment flow from end to end. The persistent action improved discoverability, the Without Plan filter helped users quickly identify eligible recipients, and the review step gave them confidence before confirming a bulk change.
The prototype allowed the team to validate the interaction model, identify usability issues early, and refine the experience before implementation.
