Technical committee, a large software company, should have the organization. Why do we need this organization? What can it bring to the company?

The current situation

First of all, the company has many product lines. For each product line, there are independent development teams, and each team has its own technology stack. Due to different businesses, the technology used is also different, which is from the product perspective. So these developers usually follow their own ideas, let alone what the technology stack is, because as long as it can respond quickly to demand and support business development, it is the right technology. However, in such a long-term development, the technologies of each product line are bound to form a certain “department wall”, just like the “chimney” in our usual architecture. Moreover, with the development, it may become more and more divergent, and finally it is difficult to unify, bringing trouble to management.

Some idea

As a result of the administrative organization structure adjustment, now all developers are classified as research and development center, but still responsible for their own business, the development direction of technology it is hard to go to see, from the perspective of higher is no unified whole coordination and arrangement, so set up technical committee is responsible for organizing, coordinating, technical things like fall to the ground. As I understand it, the specific responsibilities of the Technical Committee are:

  • 1. Grasp the technical direction and study new technologies in line with the company’s business;
  • 2. Training, construction and development of technical personnel echelon, and forming a unified technical specification;
  • 3. Organize technical personnel training, external learning and communication, and implement technology output;
  • 4. Create culture, create technological atmosphere and encourage technological innovation;

In accordance with these responsibilities, there will be technical salons, sharing, external communication and learning, and the establishment of internal specifications.

Difficulties encountered

With regard to the recent implementation:

  • 1. Due to the diversification of the company’s technical language and clients, sometimes it is difficult to have some common points;
  • 2. The overall participation enthusiasm of the staff is not high, and the enthusiasm of sharing is not enough;

At present, these two issues are relatively prominent. In view of the first point, we should divide the different committees at the front and back end to make the sharing and discussion more participatory. The second point is to stimulate everyone’s enthusiasm through regular sharing and praise, but the effect is not obvious.

These contents may be a little different from other enterprises. After all, there is no standard responsibility. Every company has its own situation. Welcome to share!