Move from your calendar to a context-rich handoff, then challenge a fixed management style. Finish with a manager’s account of repeatedly recalibrating as the team’s needs became clearer.
Who this is for: New engineering managers, team leads and founders who keep taking work back because explaining it seems slower than doing it. The examples lean toward software teams.
Take away: A handoff with clear authority, useful support and a signal for adjusting your involvement.
Estimates use 250 words per minute, rounded up for each piece. Allow extra time for the reflection at the end. Open a piece for its selection note and available summary, then continue to the original.
Ben Kuhn shifts a new manager's attention from personal output to team capacity. Use his prioritisation and delegation advice to identify work that only you can do—and work you keep doing out of habit.
Ben Kuhn · About 6 min
Pause here: Which work builds the team’s capacity rather than just your own output?
Wes Kao turns delegation into six questions about context, expectations, resources and risks. Apply them to one responsibility you identified in the first reading.
Wes Kao · About 6 min
Pause here: What decision context have you kept in your head?
Will Larson argues that expectations of engineering managers change with business conditions. Test the earlier advice against your actual environment instead of treating hands-off management as a universal ideal.
Will Larson — Irrational Exuberance · About 9 min
Pause here: What does your current business environment require from a manager?
An incoming engineering manager describes abandoning an onboarding plan, pushing delivery too hard and later engaging with neglected support work. The value is the sequence of corrections, not a new rule for every manager’s first month.
Manager.dev · About 8 min
Pause here: What signal from the team would make you change how involved you are?
How the pieces fit together
Kuhn changes the unit of progress from personal output to the team's capacity. Kao makes delegation concrete by asking what another person needs to understand and act. Larson complicates any universal rule about how hands-on a manager should be: expectations shift with the business environment. The useful tension is not delegation versus involvement. It is whether your involvement builds capacity or preserves dependence on you. A context-rich handoff may still need close support when the task is unfamiliar or the stakes are high. Conversely, stepping back without transferring decision context is not evidence of trust. Use these readings to negotiate the support a particular task needs, not to adopt a fixed hands-off identity. The final first-person account makes that adjustment concrete: too little involvement and too much pressure can follow one another. Treat feedback from the team as a reason to recalibrate, not as proof that one universal management style wins.
Digna Legi synthesis of the linked readings, not a claim that the authors endorse this combined approach.
Put five minutes aside
Put the readings to work
Use paper or your own notes app. These prompts are Digna Legi’s exercise, drawn from the readings.
Pick one responsibility you repeatedly take back. Record the intended outcome and the decisions the other person can make.
Add the constraints, an example of acceptable work and a check-in point. Ask what remains unclear and what support they want.
At the check-in, distinguish missing information, unclear authority and a skill gap. Adjust the support rather than assuming delegation itself failed.
Before you leave: What is one responsibility you could hand over this week, and what context would let the other person make a good decision without waiting for you?
Help improve Digna Legi?
Allow Google Analytics to measure visits and reading-link clicks using cookies. Optional; the site works without it. Privacy details