How to break through the exhausted front-end business?
Published: 2021-09-22 11:54:51

As a business front-end, while fulfilling business requirements, it also has to deal with various online problems. After working hard and busy for a year, the boss said that "thinking is not enough" and "there is no business scene". I went out for an interview and was asked. The project, I can’t say anything that has highlights or challenges, I want to do something awesome, and I haven’t found any valuable directions. I finally find some directions, and I have to be "suppressed" by various questions from the boss. In the end Maybe it's just a little performance optimization work, and some reusable components are removed... I can't help but sigh, business is difficult, front-end is difficult, and it is even more difficult to do business front-end!

If you have such feelings and predicaments, I want to tell you that this is really normal. There are many thoughts on this issue in Ali’s internal technical forums. Based on my own understanding and research, I have also referenced many A summary of experts in different front-end fields, write this article, I hope it will be helpful to everyone.

#The dilemma of the business front-end#
##1. The front end of the business is "very busy"

The front end of the business, as the name implies, is the front end of the business, directly in contact with the PD and operations of the business, and is directly responsible for the users of the product. In actual work, the front-end business is often busy with various meetings, projects, and Q&A. Even if there are multiple front-end classmates on a business line, they may still feel strenuous in the face of Chengshan's needs. The reasons may include:

> Demand scheduling is inverted , and development time is tight

> I’m not familiar with the business. I only go to the visual review when the project requirements have been determined. There is no way to judge whether the business logic behind the requirements matches the business rhythm, whether the requirements themselves can achieve the business goals, and whether there is a better way to achieve them. Able to accept the demand, and then schedule

> Maintenance costs are high , and I have to be busy solving various online problems every day. For example, there is a problem with the style here, why is there no display... Various trivial problems make your life very "fulfilling"

> Demand response speed is slow . For example, the business technology stack is old, or there are too many custom logics. You have to check the documentation while writing the code. If you can't find it, you may need to check the source code, which greatly reduces the efficiency. Or it may be different from other business technology systems, which are difficult to reuse and accumulate. If you want to use it, you may have to rewrite it again...

##2. Is the front end of the business a "resource"?

Under such pressure, the front end of the business is often reduced to a "resource" . When you become a "resource", you have actually lost the qualification to talk to the business on an equal footing. They will only treat you as a development machine for undeserved feelings. Enter requirements with you and let you spit out the page. In such a relationship, you originally wrote fairly neat code. In order to quickly achieve business requirements, you also began to write messy code, and you have no words about the products you create. Quan, over time also lost his passion and patience.

If you lose your enthusiasm and you are not happy about writing, it’s because you haven’t made anything special, and your boss won’t particularly approve of your hard work. He will also feel that you don’t think enough, don’t have a business scene, don’t help the business, and don’t let the business. It's different because of your existence ...

##3. Want to make a breakthrough in the front end of the business

Okay, then I decided to make some changes , so I put forward a series of ideas with the boss:

> The technical system here is too old, in order to further improve the development efficiency, we want to carry out technical reconstruction

> The front-end and back-end joint debugging is a bit laborious. We want to build a joint data center to improve the efficiency of joint debugging.

> The display speed there is too slow, we need to optimize the performance

> ...

The boss often asks a series of soul questions :

> Why do it? (What is the business value? What is the technical value?)

> Why do it now?

> Why did you do it?

> What about ROI (input-output ratio)?

Before it started, the restless heart was poured cold water by a series of "questions" from the boss.

If you don’t answer these questions well and convince the boss, you won’t be able to win any resources. You can only do it by one person. Often the quality is not good and there is no one to use. In demand.

I was not happy and did not grow up. In the end, I could only leave the job dimly, but would it be okay if I changed a company? It is likely to be a similar process...

This is really the "dilemma" of the front-end business, so how to break through this dilemma? First of all, we must set our mindset and start with understanding the business.

#Understand the business
##1. Business and demand

Before understanding the business, we must first know that business and demand are not the same. Understanding the requirements does not mean understanding the business. The requirements are the products of the business after product digestion, which may have been deduced or disassembled. Therefore, the requirements are not the business itself . Of course, the more you understand the needs, the better you will understand the overall picture of the business.

So what is business? The industry has many definitions of "business", but the main idea remains basically unchanged. Business is a process in which a series of people complete a certain task through a series of activities. Therefore, the business can be large or small, and can be split infinitely.

The business involved in this article generally refers to commercial business, which is the business or its component parts directly related to the business model of the BU or company.

##2. Why should the front-end learn business

Even if the front-end does not learn the business, it does not affect the demand. After all, you only need to tell me what the interaction is like, and the front-end can help you achieve it, and there is already a product manager role. Why does a technologist ask the dog to take the mouse, or do it on his behalf? This is to say:

> Only by understanding the business can you think of things that the business side has never thought of from a technical point of view; if you don’t understand the business, you may not understand what the business side wants, and you can’t even figure out the business logic of the requirements. In this case, there is only one cooperation model. Seed, the demand comes down, you catch it, and then schedule it. Maybe, the design of this requirement is unreasonable , you don’t know; there is a better solution for this requirement, you don’t know; this requirement can be solved through ready-made related product solutions , saving time and manpower, you don’t even know.

> Only by understanding the reasons behind the business can we plan the future of technology from a global perspective. If you don’t understand the business, you will be far away from the real needs of users. The harder it is for you to find some of the pain points and challenges, and you can’t really put forward your thoughts and solutions to solve users’ problems.

> As a product research and development engineer , I naturally hope to personally polish a product that solves user problems and is experience-friendly. If the product can be recognized by users, it will have an impact and will naturally have a special sense of accomplishment.

> As a commercial technology company, Alibaba's requirement for technical people is to combine technology and business . On the basis of meeting business needs, it becomes a bridge between technology and business, actively enters the business, and thinks about how to help the business win and satisfy through technical means. Market and user needs, advance technical planning, talent reserve, technical architecture and technical pre-research.

##3. Do you understand the business?

So do you currently understand the business you are dealing with? Try to answer the following questions:

> What does the business do? Is there a big picture of the product?

> What are the core indicators of the business? What are the KPI goals and what is the meaning behind these numbers? To achieve these goals, what is the business strategy?

> Who are the users of the business? How is traffic stratified? What's the proportion? What is their positioning in the business?

> The business model of the business? How to attract traffic and what is the profit model?

> What are the pages we make? What value does it bring to the business? What can we do to create more value?

##4. How to learn business?

Suggestion 1: Reading of business domain knowledge

Find books with good scores related to the field to concentrate on reading, and quickly form a knowledge framework.

Recommendation 2: Understand the business background and planning

> Just take over a new business, you can invite the business owner or senior operation/product classmates to tell you about the past, present, future, vision, fiscal year planning, and expectations of technical classmates of this business;

> Take the time to read the weekly reports of the partners (operations, products, R&D) to understand what is happening now and whether it is getting closer to the goal;

> Understand the business goals, landing strategies, and the data caliber to measure the goals, pay attention to the data, and pay attention to whether the current project is fighting to achieve the goal, if not, put forward your ideas and suggestions;

> Participate more and establish a product sense. The best way to collect information is to participate in the KO meeting of the boss of the business. Various KOs will disassemble the strategy and the thinking behind it and communicate to the BU or classmates in the department.

Recommendation 3: More exchanges

Chat with server-side classmates, chat with PM, chat with users, and look at the business from multiple angles, but it should be noted that for more professional businesses, you need to do your homework first . At least some English abbreviations must be clear and understandable.

Recommendation 4: Keep the numbers in mind

If it takes a long time before, then this one can be done now, that is, remember the business-related numbers as finely as possible, the more specific the better, and the more comprehensive the better. This has two advantages:

> The recorded digital indicators themselves have already covered this business value direction to a large extent, and you will know which dimension the business focuses on;

> These numbers can be used as the source of "equal dialogue" with business parties and products, otherwise there is no even the most basic basis for dialogue.

Recommendation 5: Start with daily needs

First of all, the needs are endless, so there must be trade-offs and focus on manpower and energy to do the core business needs in order to maximize the value. If your team is currently in a situation where various scattered needs come in and cannot meet , It is necessary to carry out corresponding demand management measures, such as scheduling bi-weekly meetings.

Secondly, for the one-sentence requirement, we need to analyze the purpose and value behind it , what is the expected benefit after doing it, why this benefit can be achieved by doing so, whether it is in line with the overall goal, and whether the points mentioned by the business side are effective The plan, or the plan that is too costly, depends on whether an alternative plan can be given, and the existing plan or a low-cost method can be used to satisfy the business side.

If it is determined that this demand is OK, but you really can’t spare the time to handle this matter for the time being, in this case you can say that I accept this demand, but I may need a longer buffer time or cut some demand ( Partially satisfied), or if the project must be launched on time, the effect and quality of the project after the launch cannot be guaranteed, and the business side can make partial trade-offs .

Finally, after the project is tested and launched, carefully analyze and pay more attention to the business data and effects after the launch. The analysis and summary have the following benefits:

> Improve your understanding of the business . When you pay attention to business data, you will also see from a business perspective whether the value brought by this function meets expectations. When it does not meet expectations, you can The business side will analyze the data funnel together to find the problem and prevent our labor results from becoming a one-time job.

> At the same time, the summary can help you sort out the deficiencies in this project, or what problems exist in the related promotion, and how to improve later, which improves the iterative efficiency and quality of the next project. For example, whether there are problems such as poor understanding of requirements and rework in this project, or low efficiency of communication & joint adjustment, unstable environment, and whether the plan designed by yourself is reasonable, and how to solve it in the future.

> It can also be judged from the data and summary what kind of demand is reliable & what kind of business side is reliable, the business side who frequently strives for resources to go online but does not have a good effect, and the next time there is a demand, it needs to be increased. A process of mind and thinking.

Recommendation 6: Persevere

Business thinking ability, no one will not be effective for at least half a year.

#Boost business
##1. Thinking

Although the business is usually very busy, no matter how busy you are, you have to take time to think . So what should you think about? Here are some examples:

> Develop the habit of memorizing work content every day and analyze where your time is spent.

> In business development, are there any points that make you particularly want to complain? Think about the reason behind the problem. Is there any way to avoid not committing it next time? Can it be refined into a more general solution? How can other students solve it? How can I solve it?

> Constantly input and observe, what are the real needs of the business ? Thinking from the perspective of the business side, where are the pain points and challenges encountered by the business?

##2. Communication

Focus on the boss, teammates, and business side to confirm whether "what I want to do" is "what everyone wants"?

As the knowledge of the business increases, some "immature tips" will gradually be generated for the business:

> The technical system here is too old, in order to further improve the development efficiency, we want to carry out technical reconstruction

> The front-end and back-end joint debugging is a bit laborious. We want to build a joint data center to improve the efficiency of joint debugging.

> The display speed there is too slow, we need to optimize the performance

Usually you will be ruthlessly rejected by your boss or business side, and you will be confused when you ask.

> In the current business context, why do we do it? (What is the business value? What is the technical value?)

> Must it be done now?

> Why did you do it?

> How to do it? (Systematic, full-link, single-point technical challenge)

> What are the business and technical results? Can it be reused?

> Future planning (can it be linked and co-constructed with BU or group plans)

This is often because the things you propose to do are valuable but not necessary, and do not combine with what the current business needs. In other words, the technology you want to do is considered from a personal and purely technical perspective. There is no technical plan based on the current situation and pain points of the business . It is not grounded and the input-output ratio is not high.

Therefore, first find a good business position for technical output, see if there is any place to borrow, and don't repeat the wheel. After quickly verifying the correctness of this direction, gradually increase investment and full technical design. Don't do it by yourself, silently, and there is no business scenario to pay for it.

##3. Technical planning

Business empowerment actually requires us to closely follow our business plans and formulate technical plans and plans. After understanding the key points of the business side’s KPIs this year , the expected dismantling and implementation paths, and combining your own and team situation, think about what you can do to help the business achieve its KPIs. There are two points to note here. Down:

> Grasping the essence from the point and aspect, consider the overall situation : In many cases, the pain points and business needs we receive are single points. At this time, we cannot focus on the single point problem at hand, but need to consider the overall situation, such as the SEO page Very sensitive to performance, and often may receive feedback from some business parties, saying that our SEO has this place and that place needs to be optimized, and single-point solution to these problems may not bring much benefit to the business. There is no growth in his skills.

At this time, if you consider this proposition comprehensively, you will actually find that the optimization of SEO pages is actually to improve the inclusion and ranking of SEO pages. In fact, to improve the inclusion and ranking of SEO pages is not only the path of front-end performance optimization, but also some other paths: such as optimizing keywords & long tail words, using Google's AMP technology to transform SEO pages, and optimizing crawlers to crawl pages Time-consuming to improve the crawl rate and so on. In this way, we can turn the problem of the point into the problem of the face, and then we can develop a more effective and comprehensive handle to empower the business .

> We must not only solve the immediate pain points, but also long-term plan : In many cases, we can not only be satisfied with the KPIs in front of us, but also need to understand the business side's long-term ideas and foreseeable plans. For example, in the pilot new business, the first level of planning is to ensure that the business projects are launched on time. Considering the future, the other level of planning may be how to achieve the reproducibility of technical solutions .

##4. Stand on the shoulders of giants

When you need to develop a productized plan or tool and framework, it is best to look at the group and the industry to conduct a survey to see how the industry and other colleagues solve this problem. Try to stand on the shoulders of others to innovate or participate in co-construction to avoid repetitive and low-quality wheels in small teams.

#Technical depth
##1. Technical knowledge and technical ability

"Technology" cannot be a general term. I think it can at least be divided into two parts: "technical knowledge" and "technical ability".

What is "technical knowledge"? Knowledge is I KNOW

> "TypeScript from entry to abandonment"

> "React from getting started to giving up"

> "Webpack From Entry to Abandonment"

> ......

What is "technical capability"? Ability is I CAN

> I used TypeScript to refactor a large-scale system, and the code robustness and R&D efficiency have been greatly improved.

> I used React Hooks to conduct front-end training for the full stack of students, and the training effect was greatly improved.

> I studied Webpack in depth and optimized the configuration, which greatly improved the system construction speed.

> .....

##2. Cultivate technical vision

> Pay attention to new technologies in the daily industry. It is not necessary to understand in depth, but be curious about the new technology and probably understand what it does. If you encounter a matching landing environment at work, you can consider writing a demo to see if it is valuable.

> Pay attention to the solutions of the group and the industry . When we discover problems in the business and make solutions, we can easily fall into our own design, and we want to make everything ourselves, but the input will be very large, and the value of the output will be the same? do not know. In most cases, you want to do, can be found to the ATA, the first man to step on the pit, or existing mature solution, as long as you communicate to get in touch, you can easily take in, why spend a lot of Time to make wheels? Where you can borrow, let’s borrow it, and spare the time to do the more core and valuable things in your solution.

##3. Technical depth

When you talk about "technical depth", you may naturally think that you have dig deep in a certain technology or solved a technical problem that is recognized by the industry as difficult, but this is only part of the "technical depth":

> Systematization/systematization. Body line of thinking is a way of understanding things, in the face of problems, can for complex issues, and outline key elements of the solution, the problem will be scattered and disorderly, become logical, rule-based . In the embodiment of the positioning and solution of the problem, from the appearance to the essence, the reasons behind the problem are disassembled, and the essential reasons are solved in a targeted manner, instead of treating the symptoms and not the root cause, there are solutions to solve them in a rhythmic manner.

> Full link. In addition to the front-end part, the technology stack forwards and backwards can dig deep.

> Single point of technical challenge. What are your thoughts and solutions on a certain technical challenge?

##4. Win-win technology and business

Really breakthrough business results that bring significant value will inevitably be accompanied by technical in-depth and even innovation. Therefore, when doing business results, there must be scenarios that allow us to increase the depth of technology.

#finally
Cultivating a sense of business is indeed a very difficult thing. He requires you to take business rather than technology as the first perspective. This may violate the inner "technical persistence" of many people, but if you keep working on technology, it is actually very difficult. It is a very big breakthrough. In your work, if you can achieve a win-win situation between technology and business, it will help you reach a higher height.

Change is indeed difficult, but the result is worth the risk.

**FURTHER READING**
▶ [Walkthrough007](https://www.walkthrough007.com/) - https://www.walkthrough007.com/