In the past, at the company level, there was a meeting mechanism - VOC (Voice of Users).
This meeting has a relatively high standard, and the email list top leaders of various businesses and some VPs of the company will participate.
Why is it so important?
I think that in most cases, it is because the investment-return ratio of solving user problems is not high, and it is not effective in the short term, which is contrary to the growth goal pursued by the business.
Therefore, it is necessary for higher managers to stand in the perspective of long-term interests, make decisions and push hard.
Therefore, I think that in order to solve these "small problems", we must first establish such a management mechanism, otherwise it will be difficult to achieve results.
After insight into this logic, we also started the refined operation of the middle and Taiwan in the last bimonthly okr, and established a "problem" back-drive mechanism.
The above is the architecture diagram of the back-drive mechanism of our middle platform.
Next, I will explain in 3 steps:
Step 1: Identify the problem
At first, we need to define the problem classification that the whole mechanism is to solve.
Based on the experience accumulated in the past, we have basically identified 5 types, and combined each type of problem to construct the information source of the problem: