Saying that Young Master Ah Qiang is angry, he is angry. After 10 seconds of thinking, he has decided to build a brand-new WeChat applet mall, which will be operated separately from the original APP and public account malls. Re-established the operation team and parted ways with his old sister.
Just such a proposition, as a product manager, you are also acting as the think tank of Young Master Ah Qiang, how do you do this?
1. Understand and meet the boss's purpose
I think this matter is too simple. Anyone who listens to wages in the face of right and wrong is always right.
Master Ah Qiang's purpose has been very clear, just two points: WeChat mini program mall, rebuilding the operation and operation team.
1. Low-level thinking
For the products of the e-commerce mall, I have vomited over the years. I have saved 80 to 90 kilograms just for the interactive draft.
So simple, take an inventory and interact with consumer email list it and change it, and that's it; then hold a review meeting with the strong and young, so that everyone can see my beautiful interactive manuscript!
Before that, I should just give him a liao for this matter. Isn't the product manager just meeting the customer's expectations? The same is true for me, as long as he manages the effect he wants to see, it will be fine; as for the development implementation consumer email list and operation plan, there are technical idiots and operation idiots. I'm just a product maker!
What a shameful low-level product person thinking.
2. Three Laws of Product Implementation
When it comes to products, three laws must always be followed: high quality, high efficiency, and execution.
High quality is reflected in the project execution process, including demand research, solution evaluation, development process and online acceptance.
High efficiency is reflected in the need to respond quickly to business market needs, and take operation and market needs as the first task.
It is executable, and there should be no unpredictable uncertainty during the execution process. It is best to filter out the uncertainty as much as possible before doing things, such as colorful black and changing the theme of the mobile phone according to the color of the mobile phone case.
3. Be realistic
Products like the mall are no longer a technical difficulty, but from 0 to 1, the development cycle is indispensable:
The main process of the mall: browse products, search products, register and log in, add to shopping cart, place an order, pay, order review, delivery, after-sales, customer service, etc.
Marketing process: full discount, multiple discounts, coupons, membership points, etc.
When planning products, the concept should be large and the business should be complete. This is not wrong. However, after weighing it, you will find that it violates the principle of "high efficiency". So why should the project pay attention to the way of staging and iteration.
Is it possible to first divide the main process of the mall and the marketing section into two large versions?
The answer is yes. But it can't meet the needs of the business! Yes, from the perspective of product development, it can be done next year, but if it is out of the market and the product is launched a year later, will the team have been disbanded!
And the business scenario of this pure mall is different from other combined product business scenarios. The purpose of a pure mall is to sell things. Users can buy if they feel enough discounts. Otherwise, users will leave JD.com and Tmall.
For integrated products, the mall is only one of the subsidiary functions, and its main business flow is not the mall. I personally think that the main process of the mall can be used as the first phase, and the discount can be used as the second phase, such as Xiaohongshu. This kind of product, the main presentation is still the content flow...
Fact: The company's mall system already exists, but a WeChat applet port needs to be added. The shopping process and discount functions have been in operation for a long time; through research, because the previous product planning did not take into account the split operation. Therefore, there is no column distinction in the background order management and marketing function configuration, that is, the scenario of sub-team is not supported.
4. My solution
In this plan, I consider two points:
High efficiency is to land quickly;
The product is independent, and the project and product cannot be sold to the original project team (the previous mall products were rotten and rotten, I don’t want to build a high-rise building on top of the unfinished building).
So in the early stage, I still planned two phases for my mall:
Phase 1: Main process development + direct use of available resources in the original mall.
It is feasible for the original mall team to transform the mall structure they have done before, but it is not recommended. At least it needs to be carefully evaluated. After all, the project has been in operation for so long, and changing these things will affect the normal business of the mall:
Phase 2: Independent work.
Gradually cut off the original secondary docking, especially the preferential promotion. The docking of products can be retained. After all, the company's product file maintenance, procurement, etc. are all unified. It is not good to have another team to do these things again, unless the new mall sells things completely different from the previous mall. And it is also a new field of supply chain.
There is a difficulty in the docking of the first issue above, which is the docking of preferential promotions.
But if you have read my previous article about coupons, this is not a problem:
Promotional offers need to be offered to people. Taking coupons as an example, the coupons delivered by the system need to be delivered to people. Therefore, it is required that users of the new mall need to use the ID of the users of the new mall to receive them in the old mall system. One user registration, so that coupons can be delivered to people.
As for the ID, using a mobile phone number should not be a problem. After all, the WeChat applet can obtain the mobile phone number through authorization.
In the write-off link of coupons, here is a detailed question: should the user pay first and then write off the coupon, or write off the coupon first and then let the user pay? The logic of coupon write-off can be considered in combination with the scenario where users operate multiple terminals at the same time, and then add a "lock" concept to solve this problem.
Drawing this flow chart is not to prove how good I am, but to facilitate the follow-up project, product review, and chat with technology, there are more powerful tools.
Second, the project execution decomposition
1. Major item decomposition
According to the goals of Qiang Shao and the plan I made, in addition to the self-built team, there are also many third-party participants in the project, mainly the development team of the original mall and the development team of the storage system WMS.
It is important that identifying these stakeholders is the first step in carrying out the project.
The current plan only lists the major items, and each specific party needs a detailed task breakdown plan; such as the mall development plan of your own team, the development plan of the original mall development team, and warehouse development The team's development schedule needs to be refined.
2. Breakdown of items: give a detailed list of tasks to
Relatively speaking, my own people are generally easy to talk about. The key is the third party in it. It’s okay to have the same system, different systems, or simply a third-party company. It’s very difficult!
For example, a mantra: I don't even know what your needs are?
Yes, no matter how detailed you describe your business to them, as long as you "don't know what the demand is", it's all for nothing! Therefore, as a product manager, you also need to have a skill, that is, know how to provide demand to third parties, the premise is that you must be very clear about what you want! This skill is: system interaction logic.
Take the coupon section above as an example:
Sequence diagram is an extremely powerful tool for system interaction, which tests a person's logical ability to interact with multiple systems; the above is just the thoughts of the positive process, the process of exception handling is not expressed, and can be supplemented by yourself.
If you don't know how to draw or don't have the ability to draw, you can ask a technical help to solve it. After such an idea comes out, next, for the functions of each section, which interfaces need to be developed by the other party, it will naturally come out.
Specific interface requirements, according to the scene, and then do similar specific refinement, the detailed requirements come out. At this point, there shouldn't be such a stupid third-party development, right?
But don’t be afraid, we can be more detailed, just like the WeChat public account open platform, write a guide document, including the usage scenarios of the interface, interface fields, and then paste the interaction sequence diagram.
There is no problem. Tencent's documents are also written by their product managers in conjunction with the developers. They should be in line with these product people:
Give these third parties a nanny service -- service at home.
In order to achieve my purpose, the clearer these people are about our demands, the more efficient the promotion will be.
3. Segment with your family
Understanding which interfaces are required for project docking is just more convenient for us to promote the efficiency of product construction.
Of course, if there is a technology around you to help you do these things, it is naturally better, but we must understand the 80/20 law of communication, direct communication must be the most efficient, and it can best reflect a person's professionalism .
But when you do things with your own family (the technology of your own team), you don't need to worry about it so much, such as the task decomposition of the development process, let the technical manager do it. If you can also decompose, you can also control the mouse, and the decomposition list made can be used as a reference for the technology.
3. Do things the right way
1. The role of officials
Try to describe a conclusion in an objective way. In the face of things that are not clear to each other, or when you are clear and others do not believe you, too many disputes will only increase the cost of solving the problem.
For example, when sharing small programs, can you share a personalized interface to users?
We don't need to give a conclusion right away, just go to a small program and try it out; but we still don't know if we can achieve a personalized interface. You can choose to ask someone who is better than you, such as a certain technology.
However, there is absolutely no way to go to the WeChat platform to find official documents to explain more convincingly: