User Behavior Monitoring Kanban for Front-End Monitoring (End)

After getting the statistics, we need to make a user penetration dashboard to present the data.

There are many issues to consider when creating a Kanban board. For example, how to design data presentation? What metrics do we need to consider? After discussing with the product manager, I have a deeper understanding of this problem.

The product manager decomposes the function of the entire Kanban into the following parts:

1. Overview of this week

In this part, we need to pay attention to the daily PV and UV, and also need to analyze the changes from last week.

2. Current user distribution

We need to know how many users come from different departments this week, and the change from last week.

3. Users focus on content

In this part, we need to focus on the Top5 of the current Kanban and the Top5 of the report. At the same time, we also need to pay attention to the situation of PV and UV. If the PV is high and the UV is low, it means that the current function may only be used by some high-frequency users. If both PV and UV are high, it means that the current function is the core function.

4. Kanban value

In this part, we need to understand how much PV per capita is and whether it is valuable. If the per capita PV is relatively high, it means that the overall value of the function is relatively good.

In addition to this, we also need to consider other factors, such as how the board is designed and presented, and how to make the data better understandable for users. Therefore, when making kanban, we need to fully consider these issues in order to make the kanban more perfect and close to the needs of users.

Guess you like

Origin blog.csdn.net/qq_34539486/article/details/129847512