.jpg)
Communicating with products, communicating with users, and even looking for information online are some good ways to understand needs. For example, executive email list the requirement of this design is about permission allocation. This article "100 Solutions for Role Permission Design" has helped me understand the design logic behind permission allocation. executive email list Including proper nouns in understanding requirements and establishing special logo styles for them is also a way to help yourself, your team, and users better understand product requirements. Glossary 2.
Demand structuring I'm an emotionless logic designer When we first think about requirements, we will definitely start from the scenario/problem, and think about executive email list how to solve this problem. We think about this problem with the "human" thinking, which is inevitable and correct. But at this time, our thinking is scattered. For example, when we think about the executive email list need for permission allocation, we may say: "This time we will add a concept of "post", so that permissions and positions are bound, not with people Binding", "
By the way, the problem of personnel resignation has plagued the business for a long time, and this time we will xxxxxx when the personnel resign." So, after the initial executive email list requirement framework was determined, what I got was two paragraphs of text: It seems to be very comprehensive, but since we collect requirements in a scattered manner, we may still miss it in many cases, or incorrectly associate the internal logic, resulting in some logical conflicts and loopholes executive email list . At this point, we need to change our thinking from "scattered collection" to "structured sorting".