Utilizing an API for large scale user management
The goal of this requirement is to develop a streamlined process that allows users to create and manage departments effectively, empowering them to add relevant topics and assign ownership to each department.
The goal is to enhance the user management settings by implementing a user-friendly interface that enables easy identification and tracking of changes made through the User Provisioning API.
Each topic possesses its own designated owner, any change event affecting that owner would need to trigger an automatic reassignment of ownership to the department owner, ensuring that no topic is left without ownership.
This project presented a unique challenge in balancing acceptance criteria with much-needed UI/UX updates. While the user management page required a facelift, a complete redesign would exceed the project's scope. As we transitioned to an agile project management system, it was crucial to prioritize tasks that could be completed within 1-2 sprints. Implementing the search and filter bar was a battle I chose to address first, as it provided an expected and trusted user experience across the platform. Considering our clients' future expansions, a user management page without search and filter functionality was not viable. Throughout the design and review process, I constantly evaluated whether changes were within scope and adhered to deadlines. Some items were backlogged for future improvements.
Notifications have been integrated into the notification center, added as indicators within the menu, badges within the settings submenus, and toasters for urgent settings, ensuring prompt user attention and action.
While this project is still under development and much will be learned post-launch, our team underwent leadership changes that resulted in process alterations. The project allowed me to evaluate our strategies - what worked and what didn't. A highly effective practice was consistently asking, "Is this within the project scope?" This allowed me to document ideas and revisit them in the project management system to decide their place on the roadmap during post-mortem discussions. The most significant lesson learned was the importance of extensive research early in the project, not just for comparative analysis, but also into pre-built codes and assets available to developers. This approach enabled me and my team of designers to make decisions that accelerated the design process rather than impeding it.
