What CTOs Can Learn from Military Discipline: 20 Practical Management Insights

导读： 今天是中国人民解放军建军节，军有军规，那么CTO的管理更是如此。

1. General Management

1.1 Management is pushing, leadership is pulling; leaders set the destination and roadmap, managers find ways to reach it.

1.2 Effective management delivers the expected quality within the expected time at the lowest possible cost.

1.3 Every work produces output; metrics must be defined to measure that output, otherwise nothing changes.

1.4 The earlier a problem is discovered, the lower its resolution cost.

1.5 Managers should focus on high‑leverage activities such as teaching skills, knowledge, and values.

1.6 Meetings are of two types: process‑oriented (regular, efficient) and task‑oriented (ad‑hoc, should be minimized).

1.7 Every meeting participant must keep minutes to avoid distractions.

1.8 All‑hands meetings need a moderator, preferably a senior person, to prevent two‑person side conversations.

1.9 Regular one‑on‑one communication is essential, especially for subordinates who do not initiate contact.

1.10 Establish effective communication mechanisms and problem‑handling patterns (e.g., regular meetings) to give subordinates channels for raising issues.

1.11 Employees can be divided into four quadrants; different management methods apply to each quadrant.

1.12 Provide more opportunities and appropriate supervision for first‑quadrant employees; guide second‑quadrant employees toward the first quadrant; address psychological issues for third‑quadrant employees; have improvement conversations with fourth‑quadrant employees.

1.13 Delegate authority but retain responsibility for outcomes; give praise to the team, acknowledge failures publicly, and own responsibility.

1.14 When introducing a new policy, start with a reduced intensity, then fully roll out after adaptation.

1.15 Agile organizations support scalable structures.

1.16 Amazon’s two‑pizza team rule: a team should be small enough to be fed by two pizzas; larger teams must be split.

1.17 Adopt an “All Know All Things” (AKA) culture of openness and fairness, avoiding secrecy.

1.18 Hybrid organizations with cross‑functional staff require dual reporting lines.

1.19 Decision‑making authority should consider both position and professional expertise.

1.20 If KPI performance reviews encounter scoring or communication issues, switch to OKR‑based assessment.

1.21 Follow Google’s model: semi‑annual performance review (self‑assessment + peer review) combined with OKR scoring, with the final score determined by the direct leader.

2. Technical Management

2.1 Company’s technical focus evolves with its stage: startup (prototype and tech reserve), growth (product upgrades and service体系), maturity (innovation efficiency).

2.2 Brooks’ law: developer productivity decreases as team size grows; effort cost grows quadratically, so keep team size manageable.

2.3 Technology must be tightly integrated with business; train technical experts who understand the business and avoid talking tech in a vacuum.

2.4 Teams larger than ten can use rotation to boost enthusiasm and breadth, but require proper onboarding, especially for high‑threshold roles.

2.5 Distinguish incidents (need immediate resolution) from problems (need root‑cause analysis).

2.6 Build a value‑driven demand‑management loop: assign credit scores to requesters, estimate value, verify post‑launch, and adjust credit based on delivery.

2.7 Use behavioral interviews with real cases to assess problem‑solving and thinking abilities.

2.8 Technical teams over 300 people need career‑development, competency‑development, and training frameworks.

2.9 Technical leaders should develop three capabilities: professional expertise, leadership, and universal skills (communication, execution, teamwork, responsibility).