Lessons from Growing a Software Leadership Team

2026-02-26 · Source: InfoQ · Field: Business & Management — Corporate Strategy & Leadership, Operations & Process Management, Human Resources & Workforce Development · Depth: Intermediate, short

Summary

Thiago Ghisi, in his QCon London talk "Lessons from Growing Engineering Organizations," detailed his approach to cultivating a resilient software leadership team. He emphasized intentionally building a leadership group beneath him, starting with an off-site for managers and senior Individual Contributors (ICs) to align on priorities and foster trust. Key practices included consistent weekly or biweekly syncs for accountability and resource reallocation, and expectation calibrations where managers draft and peer-review direct report expectations. Ghisi highlighted that culture is defined by actions, not words, and stressed the importance of documenting reorganizations with a clear "Why" to prevent miscommunication. He also advocated for addressing people's issues before pushing delivery and establishing clear tie-breakers for decision-making to avoid gridlock. His methods fostered a culture of continuous improvement and iterative experimentation with team topologies.

Key takeaway

For CTOs and engineering VPs focused on scaling their organizations, your primary role extends beyond direct leadership to intentionally cultivating a resilient leadership group beneath you. Prioritize clear communication, consistent accountability mechanisms, and a culture of continuous, documented experimentation. This approach will transform your managers and senior ICs into multipliers of performance and culture, preventing bottlenecks and fostering adaptability.

Key insights

Intentional leadership team building, clear communication, and continuous improvement drive organizational resilience and performance.

Principles

• Culture is defined by actions, not stated values.
• Address people issues before prioritizing delivery.
• Not all decisions require consensus.

Method

Build leadership teams through off-sites for alignment, consistent syncs for accountability, and peer-reviewed expectation calibrations. Document reorganizations with a "Why" and experiment with team topologies, labeling changes as temporary.

In practice

• Conduct off-sites for leadership alignment.
• Implement weekly/biweekly leadership syncs.
• Use RACI matrix for decision-making clarity.

Topics

• Software Leadership
• Team Building
• Organizational Culture
• Continuous Improvement
• Team Topologies

Best for: CTO, Software Engineer, Director of AI/ML, VP of Engineering/Data

Related on AIssential

• How CX Leaders Build Resilience In A Volatile World — Resilience in CX stems from adaptable culture, clear decision rights, and outcome-focused ways of working, not rigid processes.
• Presentation: Scaling to 100+ as a Director: Lessons From Growing Engineering Organizations — Effective engineering leadership scales by adapting strategies across organizational levels and continuously reinventing leadership approaches.
• Thai Vong: Bringing Clarity to Enterprise Tech Leadership — Effective technology leadership hinges on clarity, execution, and guiding people through uncertainty to achieve business outcomes.
• Building a global engineering team (plus AI agents) with Netlify — Effective global engineering leadership balances intentional in-person connections with a strong written culture and strategic AI integration.
• The Hard Thing About Being #1 — Sustaining market leadership demands continuous innovation, strategic cannibalization, and a culture of radical alignment.
• Why Hybrid Leaders Are Winning at AI — Successful AI adoption hinges on team-centric learning, shared goals, and high employee engagement.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.