liveBook · Manning

Team performance

As explained in Think Like a Software Engineering Manager

Team performance is the effectiveness and results produced by a team in achieving its work objectives.

Team performance describes how effectively a team achieves its work objectives. A manager improves it by understanding team dynamics, clarifying expectations, removing blockers, and supporting collaboration. section 4.5.4 section 4.7

Assess performance across several dimensions rather than relying on a single number:

  • Timely milestone achievement and team velocity show delivery capacity. section 9.2.6
  • Quality standards, customer satisfaction, and stakeholder satisfaction show whether delivery is valuable and reliable. section 9.2.6
  • Collaboration, communication, transparency about risks, and knowledge sharing reveal how sustainably the team works. section 9.2.6
  • Resource use, innovation, upskilling, and return on investment add broader measures of effectiveness. section 9.2.6

Turn around underperformance through a systematic process:

  • Observe team dynamics and listen before intervening. section 4.5.4
  • Find root causes such as ineffective leadership, skill gaps, motivation problems, communication failures, or inefficient processes. section 4.5.4
  • Set clear goals, timelines, expectations, and communication channels. section 4.5.4
  • Provide tools, resources, mentorship, and process improvements while removing blockers. section 4.5.4

Repeated task spillovers

Repeated sprint spillovers exposed duplicate work, missed deadlines, poor vacation handoffs, and slow code reviews. Better communication and collaboration addressed the underlying performance problem. section 4.5.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides metrics and a practical turnaround sequence, stopping short of prescribing one universal solution.
Examples
Uses sprint spillovers, duplicate engineering work, missed deadlines, vacation handoffs, and prolonged code reviews as diagnostic examples.
What it assumes
Assumes familiarity with basic team dynamics while teaching managers to observe, listen, clarify expectations, and support improvement.
What you can do after
Diagnose/debug with it by identifying performance causes, selecting appropriate metrics, improving processes, and removing team blockers.
How it connects
Connects team performance with performance management, communication, collaboration, team velocity, knowledge sharing, and return on investment.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.