30 Commandments for Effective Technical Management

30 Commandments for Effective Technical Management

1. Form a minimum combat unit of about 12 people; larger teams often add unnecessary overhead.

2. Run a two‑week iteration cycle and continuously align product direction to create a killer application, especially in a VUCA environment.

3. Hold efficient meetings: share agenda in advance, ensure conclusions, track execution, and communicate respectfully.

4. Use time‑management tools (e.g., Pomodoro, GTD apps) and share daily plans with direct leaders.

5. Conduct weekly team‑efficiency analysis, measuring resource utilization, output, and KPI completion.

6. Organize internal knowledge sharing and update best practices to the team Wiki.

7. Adopt Scrum or Kanban to raise team maturity; leaders act as agile coaches and facilitate retrospectives.

8. Hold weekly team meetings to highlight highs, lows, improvement points, and upcoming actions.

9. Practice proper email etiquette, use filtering, and apply Pyramid Principle or MECE for clear communication.

10. Keep Sprint task granularity within 0.5–1 day to maintain focus.

11. Leaders should ensure the team is operating smoothly before writing code themselves.

12. Maintain a product backlog with at least one month of work ready, enabling zero‑wait iterations and smooth handoffs.

13. For distributed teams, appoint an interface person for one‑to‑one communication and avoid mesh‑style discussions; observe video‑call etiquette.

14. Double‑check Scrum time estimates; resolve disputes via technical leaders using story points or planning poker.

15. Enforce code‑review standards and use static analysis tools such as SonarQube or FindBugs.

16. Leverage project‑management tools like Jira or Redmine for transparency and data‑driven efficiency.

17. Conduct weekly bug‑analysis and code‑quality reviews; developers own quality, not testers.

18. Use weekly showcases for design, algorithm, or other work to boost employee sense of achievement.

19. Maintain daily communication with team members, share meals, and use voice calls for remote colleagues.

20. Publicly recognize high‑performing employees via email and reward them promptly.

21. Hold monthly one‑on‑one sessions to address work and personal concerns.

22. Organize monthly team activities (board games, sports) and encourage personal relationships.

23. Celebrate birthdays with meaningful gifts to strengthen belonging.

24. Refresh the team “culture wall” regularly with logos, slogans, and team apparel.

25. Conduct quarterly department meetings to summarize results and reward outstanding contributors.

26. Arrange quarterly department outings to build cohesion.

27. Implement a backup (A/B) mechanism for key roles to prevent project delays.

28. Apply situational leadership and nine‑box talent grids to develop employees at different levels.

29. Help employees create career development plans and monitor monthly progress.

30. Encourage bottom‑up feedback, promote a positive attitude, and remind teams to stay resilient.

Reader feedback: after reading "30 Rules for Technical Leaders," many found that shedding excessive ego made life easier.

IDCF FDCC Public‑Welfare Training Camp – First Broadcast Tonight , a 10‑day, 10‑session live series with four instructors covering eight major domains, offering intensive Q&A and a certification after one month. Scan the QR code below to register.