liveBook · Manning

Consolidated feedback

As explained in Think Like a Software Engineering Manager

Consolidated feedback is an objectively synthesized account of performance and behavior gathered from multiple observations or sources.

When someone underperforms, avoid guessing at the cause. Consolidated feedback combines objective observations from peers, cross-functional partners, and other managers into a fuller view of the person’s work and behavior. section 4.5.1

Use consolidated feedback to:

  • Highlight strengths as well as areas for improvement. section 4.5.1
  • Discuss observable behavior, its effects, and its consequences rather than making personal assumptions. section 4.5.1
  • Help the employee recognize knowledge gaps and agree on coaching or next actions. section 4.5.1
  • Support claims with a dated record of one-on-one conversations and previously discussed performance concerns. section 4.5.1

A candid performance conversation

After discussing possible personal or role-related causes of John’s underperformance, the manager found no compelling explanation. The manager then reviewed documented one-on-one discussions, shared 360-degree feedback, explained the effect of the work, and offered coaching with specific next actions. section 4.5.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains feedback sources, documentation, discussion focus, coaching, and next actions without detailing a complete performance process.
Examples
Uses John’s underperformance, a paper trail, one-on-one records, and 360-degree peer feedback as concrete examples.
What it assumes
Assumes responsibility for one-on-ones and teaches managers to replace assumptions with documented, data-driven discussion.
What you can do after
Apply it via one-on-one conversations to explain performance gaps and agree on coaching and next actions.
How it connects
Connects performance management with one-on-one meetings, 360-degree feedback, coaching, documentation, and underperformance.

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.