Selected product and system decisions

As we developed new portal features, we made decisions at both the product and system levels. These examples show how we clarified complex product logic while building reusable patterns across the portal.

Product-level decision

Separating capability from role

“Admin” was initially treated as a fixed user role, but administrative access could apply to users across different organizations and subscription plans. We reframed Admin as a capability, creating a more flexible permission model without adding unnecessary roles.

Showing each user what they need

The portal serves four distinct role groups, each with different access levels across organizational and personal plans. Early flows surfaced everything to everyone. We mapped each role's core tasks and built a modular sidebar that scopes navigation to exactly what each user needs.

Mapped role-based navigation and restructured dense flows into clearer, task-specific experiences

System-level decision

Balancing global consistency with feature flexibility

We separated the library into shared UI patterns and feature-specific variants. This kept core interactions consistent while allowing individual product workflows to evolve without overloading the central library.

Built a scalable UI kit in Figma and organized components into shared style variants and feature-specific content variants

Turning product logic into reusable patterns

As new features were designed, recurring behaviors—such as permissions, tables, forms, navigation states, and system feedback—were converted into reusable components and documented interaction patterns.