liveBook · Manning

Underperforming team

As explained in Think Like a Software Engineering Manager

An underperforming team is a team whose results or working practices consistently fall below expected standards.

An underperforming team consistently falls below expected standards in results or working practices. Treat underperformance as a problem to investigate, not a label to assign: root causes may include ineffective leadership, skill gaps, low motivation, or unhealthy team dynamics. section 4.5.4

Repeated sprint spillovers

Repeated task spillovers revealed communication problems: two engineers duplicated work, an uncommunicated vacation caused delays, and slow code reviews reflected weak collaboration. The practical response was to improve communication, teamwork, and obstructing processes. section 4.5.4

Turnaround starts with a systematic management process:

  • Observe team dynamics and listen to members before intervening. section 4.5.4
  • Set clear expectations for goals, gaps, timelines, and speaking up. section 4.5.4
  • Seek secondary input, including anonymous surveys when useful, to uncover differing perspectives. section 4.5.4
  • Remove process blockers such as lengthy pipelines, unreliable tests, technical debt, and ineffective cross-team communication. section 4.5.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides a systematic checklist and workplace example, but stops short of a complete performance-management framework.
Examples
Uses sprint spillovers, duplicated engineering work, an uncommunicated vacation, missed deadlines, and prolonged code reviews.
What it assumes
Assumes responsibility for team leadership while teaching observation, listening, expectation-setting, and process improvement from practical situations.
What you can do after
Diagnose team underperformance, clarify expectations, gather perspectives, and remove productivity blockers.
How it connects
Connects underperformance with leadership, team dynamics, motivation, skill gaps, communication, collaboration, and technical debt.
Cover of Think Like a Software Engineering Manager
liveBookmanning.com
Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

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.