How deeply does Think Like a Software Engineering Manager cover underperformance?

Develops an observation-and-root-cause framework, then outlines coaching and possible escalation without detailing performance improvement plan procedures.

Underperformance

As explained in Think Like a Software Engineering Manager

An underperforming employee is an employee whose demonstrated performance does not meet the expectations of their role.

A software engineer starts missing deadlines, and the quality of their work changes. Underperformance means falling below a role’s expected standards for delivery, quality, or behavior. Identify it early so the employee has a chance to improve and the team can plan around the impact. section 4.5 section 4.5.1

For an individual, move from observation to support rather than jumping to a conclusion:

Identify specific changes, such as missed deadlines, lower work quality, or reduced engagement. Use one-on-ones and performance reviews to give continuous, actionable feedback; the concern should not come as a surprise. section 4.5.1
Investigate the root cause without personal bias. Consider skill gaps, personal concerns, role fit, missing resources, unclear expectations, or changing interests. section 4.5.1
Match support to the cause. Mentorship and training may address a skill gap; a different role may better fit changed interests. Use a coaching plan to track improvement, and consider a performance improvement plan if performance does not improve. section 4.5.2 section 4.7

Two different outcomes

An engineer whose interests had shifted toward project delivery shadowed a technical program manager and moved into that role within three months. Another engineer improved technical skills through mentorship and training in a 60-day coaching plan. Underperformance does not always end in termination. section 4.5.2

If a whole team misses commitments, investigate the system as well as individual performance. Repeated sprint spillovers, for example, traced to duplicate work, poorly communicated absence, and slow code reviews. Observe team dynamics, clarify expectations, seek other perspectives, and remove process blockers. section 4.5.4

A cross-functional partner may also be struggling, even when you are not their manager. Validate the concern through feedback, offer resources or mentorship, and work with their manager on concrete goals. Ask: what have I observed, what might be causing it, and what support can I offer? section 9.1.7 section 4.5.1

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Related concepts

resource overcommitmentproduced by · Resource overcommitment is allocating or accepting resource demands whose aggregate exceeds available capacity, relying on demands not reaching their peaks simultaneously.
terminationcontrasts with · Termination is the ending of an employee’s employment relationship with an organization, whether voluntary or involuntary.
cause analysisaddressed by · Cause analysis is a systematic investigation of the underlying factors that produced a problem, failure, incident, or other outcome.
performance improvement planaddressed by · A performance improvement plan is a formal documented plan specifying an employee’s performance deficiencies, improvement objectives, support, measures, deadlines, and consequences.
high performercontrasts with · A high performer is an employee who consistently exceeds role expectations, contributes strongly to team outcomes, and supports the success of others.

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.