In the process, you will also find some limitations of the methodology. For example, goal <=> task = behavior. .. + behavior and behavior = motivation + ability + trigger. It is only applicable to product designs such as role-based workbenches, which are not universal enough; One question, two determinations, three quantities, and four determinations: it is not abstract enough and does not have the ability to migrate. It is only applicable to a role or business that is sufficiently segmented and focused; You will also rediscover or refine some "new" methodologies (maybe it's just new to me, but it's actually common sense to you).
This may be seen as a manifestation of industry involution. Taking our korean number phone company as an example, we reconstruct a system almost every year, such as the system, business system, customer service system, teacher time system, teacher management platform, teaching and research system, teacher workbench, etc. The purpose of these reconstructions is to support the development of the business in the next year (mainly reflected in the scalability of the system) and to improve user experience and work efficiency (mainly reflected in interaction design). Each such reconstruction project takes at least half a year to complete. In addition, we will continue to deeply optimize the product functions of core modules such as course product rules, course sales methods, renewal processes, scheduling systems, etc.
These tasks can be seen as part of refined product operations, although some people may jokingly call it "looking for trouble." Therefore, I used to think that the most important ability of a product manager is product planning ability. Only those product managers who can plan products for half a year or even longer can be called senior or expert product managers. However, when I entered the industry, the challenges I faced were completely different from the products in the education industry. When I joined the company, I had a number of needs to be solved.