Use this category only when the content is materially about leading software or development teams through technical expertise, not just managing people or projects.

Definition: Technical Leadership is the practice of guiding development teams’ architecture, design, implementation, and engineering decisions using technical expertise and agile best practices. It focuses on enabling technical excellence, sustainable delivery, shared ownership, and alignment with organisational and customer needs.

Must have:

• Explicit guidance of development teams on technical decisions such as architecture, design, implementation, or engineering trade-offs
• Use of technical expertise to align team work with organisational goals, customer requirements, or product outcomes
• Practices that support predictable, sustainable delivery, such as agile best practices, DevOps context, or continuous improvement
• Emphasis on empowering engineers, shared ownership, collaboration across disciplines, or breaking down silos
• Attention to long-term technical quality, learning, experimentation, or systemic approaches to building adaptable solutions

Strong fit:

• Primary: The category is the main subject and at least two Must have items are discussed.
• Secondary: The category is a substantial supporting theme and at least one Must have item is discussed.

Weak fit:

• Tertiary: Technical leadership is mentioned or adjacent, but the content is mostly about management, agile facilitation, product strategy, or team culture.
• Ignored: The category is absent, only implied, or supported only by generic references to leadership, engineering, delivery, or collaboration.

Exclude:

• Agile Leadership focused mainly on facilitation, ceremonies, team dynamics, or servant leadership without technical decision-making
• Engineering Management focused mainly on hiring, performance management, budgeting, reporting, or task allocation
• Product Management or Product Leadership focused mainly on roadmaps, market needs, prioritisation, or customer discovery
• General software development, DevOps, architecture, or agile delivery content that does not address guiding teams through technical expertise
• Generic terms such as leadership, innovation, collaboration, excellence, sustainability, or continuous improvement are insufficient on their own