liveBook · Manning

Performance management

As explained in Think Like a Software Engineering Manager

Performance management is the process of supporting employee performance through expectations, assistance, feedback, and improvement.

Two engineers are contributing in different ways: one meets deadlines and takes on extra work; the other improves technical processes but misses critical deliverables. Managing their performance means recognizing what each does well while addressing the missed commitments before they become a larger problem. section 4.0

Performance management is the ongoing work of setting expectations, checking progress, giving feedback, and helping employees grow. It is not just a performance review or a response to poor results. For an engineering manager, it connects each person’s work and career development to team and business goals. section 4.2 section 4.1

A practical cycle is:

  • Agree on clear goals and how progress will be measured, so individual work supports team priorities. section 4.1.4
  • Hold regular check-ins and one-on-ones. Ask about progress, concerns, motivations, and blockers; listen as well as give feedback. section 2.5.9 section 4.1.3
  • Give timely, constructive feedback. Recognize strong performance and help someone whose work has drifted from expectations make a course correction. section 2.5.9 section 4.1.1
  • Plan, coach, and review progress consistently. Use a fair process, but adapt support to the person’s circumstances rather than assuming one approach fits everyone. section 4.2.7 section 4.2
  • When difficulties persist, look for root causes and offer support. A coaching plan—and potentially a performance improvement plan if performance does not improve—provides a more deliberate path. section 4.7

Correct priorities before a deadline slips

An engineer’s process improvements may help the team in the long run, yet still leave a promised feature unfinished. A check-in can surface the conflict early. The manager can acknowledge the improvement work, clarify which deliverable is critical, and coach the engineer on priorities and timely communication. section 4.0 section 4.1.3

Clear expectations alone are not enough: managers also help remove blockers and improve how the team works. Regular, fair support can sustain productivity, strengthen career development, and give both employees and managers a chance to act before problems grow. section 4.7 section 4.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Describes an ongoing cycle of check-ins, feedback, planning, and coaching, with escalation to improvement plans when needed.
Examples
Contrasts an engineer meeting deadlines with one improving technical processes while missing critical deliverables.
What it assumes
Situates the practice in engineering management, including the transition from software developer to manager.
What you can do after
Practice/perform it through regular check-ins, constructive feedback, recognition, and early support when performance diverges from expectations.
How it connects
Connects goal setting and career planning with feedback, performance reviews, coaching, and performance improvement plans.

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.