Lessons from Growing a Software Leadership Team

Lessons from Growing a Software Leadership Team

Lessons from Growing a Software Leadership Team

Why Building a Resilient Leadership Group Matters

Growing a software leadership team isn’t just about hiring managers—it’s about creating a culture of collaboration, accountability, and shared vision. Thiago Ghisi, in his talk at QCon London, shared actionable strategies for building a leadership group that multiplies organizational performance. From regular syncs to fostering empathy, here’s how to avoid bottlenecks and empower your team.

Key Takeaways from Thiago Ghisi’s Approach

  • Start with trust: Off-sites where managers and senior engineers share personal struggles build empathy and alignment.
  • Align on priorities: Use Lean Inception-style sessions to define team goals and organizational objectives.
  • Weekly syncs: Hold leaders accountable for reallocating resources to critical projects, even if it disrupts their squad’s focus.

How to Avoid Leadership Bottlenecks

Delegate Decision-Making

Ghisi emphasized that leadership shouldn’t be a bottleneck. By empowering managers to give peer feedback and decide promotions, teams become self-sustaining. For example:

  • Managers draft expectations for direct reports and seek peer input.
  • Leadership teams iterate on strategies without waiting for top-down approval.

Document Reorganizations Clearly

Avoid the “telephone game” by documenting the “why” behind reorgs first. A simple one-pager outlining motivations and goals prevents misalignment during brainstorming sessions.

Culture: Walk the Walk, Don’t Talk the Talk

Lead by Example

Culture isn’t defined by rituals—it’s defined by actions. Ghisi highlighted:

  • Encouraging leaders to embrace feedback and admit mistakes.
  • Addressing interpersonal issues before pushing for delivery deadlines.
  • Using RACI matrices to resolve gridlock and clarify decision ownership.

Continuous Improvement Through Experimentation

Iterate, Don’t Settle

Ghisi’s team baked “lessons learned” into every process. For instance, if a reorganization caused unexpected on-call load, they adjusted quickly. This mindset fosters a culture where experimentation is safe and failure is a learning opportunity.

Experiment with Team Topologies

Rather than copying other companies’ structures, test what works for your team. Ghisi advised:

  1. Observe patterns in high-performing squads.
  2. Test new topologies with small, measurable goals.
  3. Retrospect and refine based on outcomes.

Conclusion: Build a Leadership Team That Multiplies Impact

A resilient software leadership team isn’t accidental—it’s intentional. By aligning on goals, fostering trust, and prioritizing culture, you create a group that drives performance and innovation. Ready to apply these lessons? Start with a leadership off-site and document your next steps.

FAQs

1. How do you grow a software leadership team effectively?

Focus on trust-building exercises, regular alignment sessions, and empowering leaders to make decisions without bottlenecks.

2. What role does culture play in leadership growth?

Culture is defined by actions, not policies. Leaders must model transparency, feedback, and adaptability.

3. How can you avoid reorganization misalignment?

Document the “why” first. A clear one-pager prevents confusion and keeps discussions focused on goals.

4. Why is continuous improvement critical for leadership teams?

It ensures teams adapt to challenges and learn from failures, fostering resilience and innovation.

5. What’s the biggest mistake in growing a leadership team?

Assuming consensus is always needed. Define clear decision-making roles to avoid gridlock.