liveBook · Manning

Delegation

As explained in Think Like a Software Engineering Manager

Delegation is the assignment of responsibility and authority for work to another person while retaining appropriate accountability.

An engineering manager has an urgent dashboard request, deadlines approaching, and performance reviews to complete. Doing everything alone risks making the manager a bottleneck. Delegation means giving someone responsibility and authority to carry out work, while remaining accountable for the outcome. Done well, it creates time for other priorities and gives the other person a meaningful opportunity to grow. section 5.0 section 5.2.2

Delegation is more than handing over a task. In task allocation, the aim is chiefly to get the work done. Delegation adds ownership, coaching, check-ins, and skills that can last beyond the task. It also differs from substitution: when another person permanently replaces you, you no longer remain accountable for that work. A delegated decision can be theirs to make without becoming yours to ignore. section 5.2.1 section 5.2.2

Use four questions to plan a delegation:

  • Why delegate? Look for a capacity constraint, a development opportunity, or a decision better led by a subject-matter expert. Planned delegation gives you time to match work with someone’s goals; an unexpected request may require a quicker choice. section 5.3.1 section 5.0
  • What work fits? Consider risk, confidentiality, deadlines, and whether the task needs your unique perspective. Keep sensitive personnel matters and performance reviews with the appropriate leader. Break suitable work into smaller pieces when that will help someone succeed. section 5.3.2
  • Who should own it? Learn people’s interests, strengths, and career goals through one-on-ones. Match the task to their capacity and aspirations, distribute opportunities fairly, and consider a cross-functional colleague when the work fits their role better. section 5.3.3
  • How will you support them? Explain the purpose, desired outcome, authority, priority, timeline, and available resources. Agree on milestones, check-ins, communication, and what to do if a blocker appears. Ask them to explain the task back to check understanding; offer training and feedback without dictating every step. section 5.3.4 section 5.4.1

Delegate an operational-excellence review

A senior engineer wants experience leading meetings. The manager can entrust them with organizing and running an operational-excellence review, explain the intended outcome, and remain available for support. The engineer gains a chance to facilitate; the manager gains time for strategic work. Simply putting a meeting on someone’s calendar would not create the same development opportunity. section 5.3.2 section 5.3

Trust does not mean disappearing. A hands-off approach can leave junior engineers without enough guidance, while micromanagement undermines ownership. Set expectations, check progress, address blockers, and adapt support to the person’s experience. Share knowledge rather than becoming its sole holder; teaching may cost time now but reduce future bottlenecks. As others take on leadership, help them identify work they can delegate too. section 1.3.3 section 5.1.2 section 5.5

How Think Like a Software Engineering Manager covers it

How deep it goes
Develops a practical why–what–who–how framework with task-selection limits, support agreements, check-ins, and feedback.
Examples
Uses an urgent dashboard request, project reporting, operational-excellence reviews, and temporary management coverage to distinguish delegation choices.
What it assumes
Assumes a team or leadership role, but distinguishes delegation from allocation and substitution before developing the practice.
What you can do after
Practice/perform delegation by choosing suitable work and people, agreeing on outcomes, and supporting progress without taking back ownership.
How it connects
Connects delegation to task allocation, substitution, coaching, career development, and micromanagement.

Also explained in

Compare how 3 books explain delegation →

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.