The specific demand is that when users create new permissions, the interaction efficiency is low and the usability is poor. The following figure is the executive email list finalized interaction design scheme. The following explains why it is designed in this way, how to think of such a design scheme, and what value such a design brings to users, so as to extract some executive email list interactive experience that can enhance the authority. ideas and methods. Figure: T-PaaS Platform New Permission Interaction Optimization
The overall design process is divided into three stages, namely defining the problem, solving the problem and outputting the interactive prototype design scheme. Stage 1: Problem Diagnosis Analyze user pain points and identify specific problems to be solved. How executive email list do you know it's a bad experience? Why is it bad? Therefore, we must first find and verify the pain points of user needs. By analyzing the user's mental model and comparing and executive email list matching with the online design model, we can find and verify the user's specific pain points, instead of analyzing the user's pain points based on the designer's own experience. Figure: Model matching User mental model analysis:
Through detailed communication with the product manager, we learned that the user of the user authority function is the system administrator, and only the system executive email list administrator can see the user authority function module, so the locked target user is the administrator. The user requirement scenario is: when administrators set permissions for system users, they executive email list usually assign permissions to multiple services, and each service contains multiple resource permissions. Scenario description: The administrator sets permissions for a user on multiple different instances, and the instances are scattered in different clusters for different applications.