liveBook · Manning

Coaching

As explained in Think Like a Software Engineering Manager

Coaching and mentoring are development practices that guide people, address skill gaps, and support professional growth.

An engineer misses a milestone and becomes defensive in technical discussions. A manager can treat the gap as a coaching opportunity: understand what is getting in the way, share specific feedback, and help the engineer improve. Coaching is part of developing talent, alongside mentoring, career conversations, and performance management. section 3.2.6 section 1.1.1

A practical coaching cycle:

  • Start with a one-on-one conversation. Ask about the person’s goals or difficulties, and make room for an open discussion. section 1.3.6 section 3.2.6
  • Describe the gap with specific examples or peer feedback. Explain its effect on the work or team without comparing the person with colleagues. section 3.1.4 section 4.3.4
  • Agree on goals and useful support, such as training, learning resources, or a mentor. Remove blockers where possible. section 3.1.4 section 3.2.6 section 4.7
  • Check in regularly, seek fresh feedback, and adjust the support if progress is slow. section 3.1.4 section 3.2.6

Turning conflict into growth

When an engineer missed meetings and clashed with a junior colleague, their manager discussed the behavior privately and explained its effect on team morale. The manager then set up a mentor–mentee relationship with goals and regular check-ins. The engineer became more engaged and began mentoring others. section 3.1.4

Coaching supports growth, but it does not replace clear decisions or accountability. A people-first manager still needs to resolve conflicts assertively. If an underperformer does not improve with coaching and support, a performance improvement plan may be needed; serious sensitive incidents may require human resources. section 1.3.6 section 4.7 section 3.1.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Illustrates conversations, goals, support, and follow-up through workplace cases rather than prescribing a single coaching script.
Examples
Uses an interpersonal conflict redirected into mentorship and a missed project milestone addressed with training, mentoring, and follow-up feedback.
What it assumes
Addresses first-time engineering managers facing difficult conversations without assuming they already know how to handle them.
What you can do after
Practice coaching by discussing specific gaps privately, agreeing on support and goals, and checking whether performance improves.
How it connects
Links coaching to one-on-ones, mentoring, constructive feedback, career development, and performance management.

Also explained in

Compare how 2 books explain coaching →

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.