Process, product and people

Has been kept before a question: Alipay page so little, why are we all so busy?

With this question, there are a dozen people in the team, including three on the other side of Shanghai. At that time I also occasionally hear other people saying how the process is not good, how the process changed, and so on. Just as a new person just listen to it. That is no way, even the process do not know, how to advise, how to change. In addition, an upgrade package was also being made at the time and all 163 mail templates were completely new. The situation is an upgrade package to change 163 pages (in retrospect this TMD is not a project what, but to a completely unfamiliar with the new side), then did not think about it, just think that even an upgrade package are so troublesome, Well, it is only natural that 10 front-ends are so busy.

result. There are already many people in the team. Still looks particularly busy. There are always people who tell you he is particularly busy. what's the situation?!

First, my process

Put aside the company process, talk about their own processes. In fact, it has been a long time since the product flow was not completed for a single company http://www.aliyun.com/zixun/aggregation/8345.html "Having left the business group for almost a year, the architecture group is typically a front-end project . Project development process by their own or group project team planning, time is also mainly made by the development of their own head to know that there is no problem that there is any problem, because in general we will analyze the project, such as when doing the style library about Process specification is this:

Pre-Analysis Target Reach Knowledge Retention Staff Legacy and New Upgrade Program Decomposition Project Deconstruction, Refinement Work Development Work Distribution Development / Follow-up Start Code Development / Documentation Follow-up and Adjustments Released / Presenter Phases Reporting Stage Sex release / preaching another process begins the next cycle

For such a process, are based on the project to do the planning. There will not be any problem. However, the company is not the case. Everyone has a common process, which is a process that someone or a group of people pre-set for you sometime in history.

Second, the company process

As for the specific process, I do not elaborate, in fact, no need to be so fine. Use three things to describe it. Things like this: First, a worker let me help fixed a bug, he said is using a new version of Alice (our internal style [CSS] library), the results of debug found bug caused by the previous version of Alice caused; Second, a co-worker suddenly things go away, there is a new product is doing, as a project support for me, took over his work, two days to complete 20+ pages. Third, there is a very necessary point to change, but not a bug, no one thought of emergency release. So, here are two things:

Case 1: The product "upgrade" package and no upgrade plan. Case two: the new product project did not leave time for technical upgrades. Case Three: The process score and product experience are not necessarily proportional.

Of course, there are situations one, two situations such situation, it can be said that they are not enough hard work. How should I say, in fact, even if the old style, not in Alipay front-end team such a maintenance style library team will do enough to choke. As for the upgrade to the latest version, overtime, it is not impossible to complete, but QA team how the test can have time? Then we say QA also work overtime, things can be done, but this is always not a long-term plan for companies and employees.

As for the situation three. In fact, we are in a big environment, a team with the slogan of "for a better experience", and a company that has a special emphasis on usability for making customers more secure and stable. There are also many levels of boss relationships. As a result, it is possible (and probably possible) that the score calculated by the process does not have to be proportional to the experience (because I actually almost agreed with it).

To sum up, these three conditions actually need us to solve two things:

Time is only 365 days, not long or short, can not add province. How to ensure that the process of distribution of time. How to ensure that the process of product development better.

Here it comes. I have to talk about people.

Third, people

Think about how you usually do one thing. In particular, do what you like and do not like the situation what will be the difference. You miss yourself, here are two examples of myself.

Example 1, when interviewing Alipay, Zhou Aimin teacher asked, "What tea that you CSS good, you can say 5 IE and Firefox in CSS different?", I said at the time, this is nothing. Only some bugs can be solved, but it is hard to state. He said that you are missing a conclusion;

Case two, a recent product classmate invited me to know in the know, "Why foreign web pages such as Amazon is the user choose to adapt to the width, while most of the domestic are fixed-width central?" In fact, I did not have this problem Thinking too, but still based on the experience of the point of view, and then actually have to praise themselves, TM, even summed up in an orderly manner (just to find a not a particularly appropriate example, why the so specific people ignore this).

Say these two examples, just to draw two points:

Summary can be in-depth. If you have been on the surface, it is difficult to find the law, it is difficult to go deep. In fact, people are inert, do not force yourself difficult to know how much their potential.

Yes, we are like that. Is it not? If you are front-end, think you are not a lot of BUG can solve, but can not be seen at first glance (often asked me why someone can see at a glance, why do you know, there is no secret); think you met To Ma Yun, he gives you a point of view, whether you will work harder to think, not like your mother suddenly thrown a point of view (such as my mom always said that I forgot to forget the big, and later thought, The original really a lot of things that do not love to remember) as to think.

Fourth, the process and people

Just said the process halfway, began to say "people" this topic. Yes, as you often hear people saying, rules are dead and people are living. People can create these things, but also to modify such things. But I did not want to say this. But to do this requires a deep user, to sum up, to think in depth with the actual. In the architecture group, most of the time we are responsible for only one project, the process is customized according to this project, think of the problem is difficult. But in a department with a quick 1,000 people, in a multi-line development of multi-product, there are numerous projects of the Ministry of Technology. How to go in-depth, to solve the process, not a deep user, not based on actual situation to think, it is difficult to solve the problem. Give a less appropriate pigeon, we write the program, will pay special attention to reuse:

List all points, analyze the logic of the program to write reusable modules used in various pages. Put a special solo Hack.

The same process. Group to sum up, the team to sum up, then rise to a small department, to most. Categorize projects that can use the same processes, develop one or more general processes, and even have special processes to deal with important special cases. Of course, this is not his mother nonsense, I believe that everyone thinks so.

In fact, things are not stuck at this point. Instead:

Who to summarize, collect these information, and in the end there is no person in charge of the process responsible person who, he fly it? Is the depth of the process user? Have you concluded? Or just see the functional upgrade, do not take care of technical upgrades Blind (Xia). Fifth, how to ensure the distribution of time process

Let us think about a very long time ago, Facebook enviable engineer-led product development. Why should they be led by engineers? Is the product manager useless?

The question is not answered directly, but what is certain is that an Internet product that does not upgrade technology is difficult to sustain over the long term. Take Alipay, he slowly come out a lot of products, more and more easy to use, more and more users. If we are not upgrading students, but also upgrade the technical support of our backstage, how to deal with so many concurrent flow of people, how to ensure that the machine can smoothly flow to another flow cut to another server.

In fact, so much, that is, to lead: If the product manager can not understand their own responsibility for the product life cycle, can fully grasp the distribution of products at various points, such as technology does not know this life cycle. Go tell him. Let him arrange for you to get your time guaranteed.

Sixth, how to ensure that the process of product development better

When it comes to BCD (Boss Centered Design) everyone will be very excited, as if everyone has a very unreasonable boss, as if each company's hierarchical relations are not optimistic. Actually, it's actually not that serious, usually only one or two things happen, or even inevitably happen, and then someone will find a word to sum up (of course, there are disgusting, but I believe these well-developed companies Should be few).

To talk a digression, why are so many people afraid of the boss? Because they are asking for it. No desire is just, begging nothing. If you are concerned about the product, then you will go to make your product better, and let others know that doing so will be better for the product and him. Instead of simply afraid of the boss, afraid he does not give you a bowl of rice hides.

Well, yes, how to make the boss think it is better for him, at the same time, the product is good?

If the algorithm inside the process is more reasonable. If the promotion product score is plus 10 points, emergency release score is deducted 5 points. Then your boss will not let you emergency release? One can imagine. Just now I also said that sometimes the so-called boss-centered "inevitably" took place. At that time, we thought the boss would not let the release. In fact, the boss wanted to improve the product, but he felt his boss might not want to. But too many levels, poor mind guess, ah, everyone knows that thinking is straight, or hard to survive. Can only say that this situation is helpless. And once there is a standard, then everyone has a bar in the heart, there is no need to guess other people's thoughts.

As for what algorithm is reasonable? It is a philosophical issue to say so. But when we have a real product, then the role of the boss decision-making came, decide what should be added, plus how many points.

7, products and people

In addition, for a product, it will not be busy all year long. After all, we now have so many people, almost everyone is responsible for a product, or more than one person in charge of a product. It is also a problem to have people assign time to do good things.

Just as you often hear people say they are busy, or show themselves busy. In fact, they also privately said that they are very busy this quarter, I feel like do not know what to do. Yes, when busy, no need to upgrade the technology, when not busy, I think I should take a good rest. Product pressure people, but also holding people, not people to grasp this product, to enhance this product. What can we do to save these blind (busy, "busy" heads, blind) people?

Sometimes think that the team has a business group, with the structure of the group. Architecture group can have a test group to test the front-end framework; business group which can also be responsible for the project technology upgrade, page improvement. Many people may ask, to improve the product is always the responsibility of each engineer, why should set up a dedicated team to do these things. Obviously, if the duties are not clear enough and no problem is done, then there is still inertness and many people will choose not to do so. And no one of us can guarantee that the product that everyone in our company is responsible for is our own children. Obviously, looking forward to everyone like this, it is impossible. At this time, the division of duties more detailed, coupled with the traditional responsibility system, will enhance the product there is a better guarantee.

Products need architecture, people also need. And in the end we have to do is let people go inert, the product as a child to raise, which for the company and the people themselves are good.

Eight, summary

Ok, let's conclude. To write more to meet their own desire to express, but see people will be tired.

About this article While asking questions and simply providing ideas for solutions, my goal is not to illustrate the "thinking" itself, but rather to indicate what kind of approach is to be used. It is not to say which place is not good, but to say what we can not expect to encounter in the encounter. Alipay involved in the issue, it is only personal feelings, does not represent the public opinion.

About processes, products and people, just to lead to such a sentence: to find a reliable person to do things, and do a good job of people's structure. Also want to say to myself, more to think, to go to the conclusion. Life is short, do not waste thinking days.

Source; http://sofish.de/1731