Tables are the most commonly used information presentation forms in B-end products, especially data products, such as commodity lists, order lists, user lists, event lists and indicator lists of user behavior analysis systems, and tag lists and scene lists phone number list of DMP platforms. It is said that more than 40% of the pages of B-end products are composed of tables.
The seemingly simple form function is actually designed in the PRD scheme. After the final function is launched, the following problems are often encountered:
If the product plan or interactive explanation function is left over, users will feedback optimization suggestions after the development is launched, and the second iterative development will be carried out;
The product interaction description phone number list in the PRD document is not detailed, the test and acceptance link requires development and function, and the product requirements for development complaints are not clear, and the requirements are changed;
The same product manager has inconsistent styles and functions of different project forms in different periods;
In the same department, different products have different levels of basic capabilities and user experience awareness, and product user experience is inconsistent.
data detail table
First, the table information structure
Starting from the information display function carried by the table and the core demands of users to obtain information, a standardized PRD document specification can be formed for the product design of the table. In different scenarios, the needs of users are as follows:
Result filtering and filtering, according to different conditions, quickly filter to find the data results that meet the conditions;
Add new records or batch operations (data table display details generally do not have this requirement);
Form information display, including core field display, record details viewing, information modification and other operations;