Table of contents
The difference between traditional enterprises and the Internet
The challenges of traditional enterprise landing technology system
The idea that engineering practice promotes the implementation of technical systems
The ultimate goal of technology is to solve the problem of efficiency and income
The difference between traditional enterprises and the Internet
If one word can be used to describe the characteristics of Internet companies, it would be Xiaoping Kuaixin. How do you understand it?
- Small: For a less complicated project, a small team with a few key roles can generally start working quickly.
- Flat: flat management, short reporting and decision-making paths, no long waiting for approval and complicated preliminary research.
- Fast: The pursuit of efficiency, whether it is fast iterative verification of the mvp plan, or meetings to communicate certain matters, rarely hold large meetings.
- New: Willing to try new technical means, tools and methods, keep curiosity about new things, and have ideas and actions to try.
Of course, these characteristics are compared with traditional enterprises that I know well. I have worked in two different types of retail companies for several years. Whether it is the team size of the project, the efficiency of reporting and decision-making, or even the awareness and acceptance of new technologies, they are far behind Internet companies.
Taking the traditional retail industry I have come into contact with as an example, they have the following characteristics:
- The composition of the team is complex: some traditional enterprises still adopt the method of self-management and system outsourcing procurement. To do a project, sometimes several suppliers are collaborating, the team is large, the cost of communication is high, and each has its own interests.
- Inefficient reporting and decision-making: An idea or plan, from proposal to research to review to approval, often takes a week. There are even several research and review meetings in the middle. Of course, this will be more rigorous and meticulous, but from a certain perspective, the delivery of new requirements or the attempt of new ideas will undoubtedly pour a basin of cold water.
- Conservative technical architecture and organizational methods: On the one hand, there are many old systems, and the system architecture is even a single service type, and the iteration frequency is rarely less than half a month; Email takes precedence over face-to-face communication.
The challenges of traditional enterprise landing technology system
Taking the company I consulted as an example, let me introduce the background of the entire case:
- There is a major system refactoring and service launch, and the time is relatively tight, less than a month;
- From the time when the consulting needs were passed on to me, to when I came up with the plan and had the first interview with the supplier, it was passed within a week;
- It took more than half a month for the CTO of Party A to communicate and report, and there were various temporary needs and pulls in the middle;
- In the end, I found out that Party A is only responsible for the management personnel, and the normal work is carried out mainly by the supplier's personnel;
- Whether the plan is implemented needs to be reviewed and approved by Party A, but technical practice needs time to be implemented and verified, and the risk is constantly being delayed;
Of course, this case does not represent all traditional companies. I also know that some companies that have done a good job in digital transformation have done a good job in terms of technical practice and efficiency.
What surprised me was that the company I worked for was well-known, and they also realized that the previous technical architecture was too backward, and after reconstruction, they had to undertake a large amount of traffic. The purpose of asking me for consultation is also to hope that I can help them build a complete technical system for performance testing and capacity assurance.
But in the actual project implementation process, the cumbersome and lengthy decision-making process, complex team composition and inefficient management made me realize one thing:
Traditional enterprises need a good implementation of the technical system to solve the problems of old systems and business development. The biggest challenge is not technical problems, but organizational management methods and decision-making efficiency .
The idea that engineering practice promotes the implementation of technical systems
In fact, whether it is a traditional enterprise or an Internet enterprise, there is not much difference in building performance testing and capacity assurance technology systems from scratch.
In many cases, technical engineering practice cannot be implemented to solve problems. The main reasons are as follows:
Moreover, the performance testing system itself is a very mature solution. From demand to online delivery, the main points are as follows:
Using mature technical solutions to solve business problems actually requires adjustments in organizational and management decisions. Otherwise, no matter how good the technology is, it cannot solve the influencing factors other than technology.
The ultimate goal of technology is to solve the problem of efficiency and income
The emergence of many new technologies is due to the inability of previous technologies to solve problems better, which forced the technology to undergo iterative evolution.
Of course, when the mature technology is implemented, what needs to be solved in the enterprise is actually the problem of efficiency and income. Whether technical transformation can bring better benefits to the business and whether it can improve the iterative efficiency of the business is the first consideration of many people.
However, the development of business can not only be solved by technology, but also the optimization of organizational management and the recognition of concepts. Otherwise, you will only become a person holding a hammer and seeing nails in your eyes, trapped in a corner.
Summarize
Thanks to everyone who read my article carefully! ! !
I personally sorted out some technical materials I have compiled in my software testing career in the past few years, including: e-books, resume modules, various job templates, interview books, self-study projects, etc. Welcome everyone to click on the business card below to get it for free, don't miss it.
