Why Software Architects Must Lead People, Not Just Design Systems

Software architects play a special role in development teams, combining technical design with management duties such as product roadmap planning, resource estimation, task assignment, milestone definition, engineer guidance, and risk assessment.

1. Focus on People, Not the Product

Believe that a group of excellent people doing what they love will succeed, regardless of obstacles or external doubts.

The best software project management is not about strict plans, resource tracking, or carrot‑and‑stick incentives; it is about uncovering each member’s potential, helping everyone understand and love the product’s ultimate vision, and allowing personal value to drive effort.

When this happens, team members become self‑driven, cooperate voluntarily, and seek optimal paths to goals without needing heavy-handed rewards or punishments; the reward is achieving the goal itself.

This is the essence of leadership: finding a shared, inspiring goal and creating an environment where everyone can maximize their value.

2. Uncover People’s Excellence

Instead of relying solely on already‑excellent individuals, create projects that make all participants grow. Excellence emerges in the right environment—through challenging tasks, collaboration with stronger peers, or the courage to surpass oneself.

3. Share a Beautiful Blueprint

Architects should co‑create a clear, vivid, and simple blueprint that the whole team embraces. The blueprint must state what the product will and will not do, the business objectives, the value for users, and a concise description that anyone can repeat.

It should be visible in design documents, email signatures, and team communication channels. Throughout the project, architects must monitor adherence to the blueprint, promptly correct deviations, and ensure any changes are discussed and re‑approved by the team.

4. Involve Everyone in Architecture

Architects must not treat architecture as personal property. Encourage open debate so every participant feels ownership, which increases responsibility and willingness to maintain and improve the software.

5. Learn to Compromise

When opinions differ, architects should openly share their design rationale, strive to understand others’ ideas, and seek common ground while respecting differences.

6. Enable Others to Succeed

Personal fulfillment often comes from helping others succeed. Projects should create value for customers, generate profit, and provide growth opportunities for team members, making each person feel essential and capable.

Architects, as technical leaders, should guide with flexible plans rather than strict control; excessive restrictions erode discipline, autonomy, and confidence.

When a strong team is built, it can face future challenges calmly, generate synergistic ideas, and create a better future blueprint together.

Author: Li Zhihui Source: "Core Principles and Case Studies of Large‑Scale Website Architecture" (Electronic Industry Press), revised.