“I used to think great managers shielded their reports from hard problems, like my grandmother swooping in with Here, let me. Then I realized the best work comes from giving someone the knot to untangle and publicly naming them the owner, while staying on the boat as a coach, not the captain.”

“I ask myself whether someone else could do this at 70 or 80 percent of how I would do it, and if the answer is yes, I hand them the outcome, not the task list. Most things can be undone, and the only way my team builds confidence is if I let them take a path that is not perfectly mine.”

“I used to think delegating meant handing something off and hoping for the best, which usually ended with me swooping in to fix it. Now I spend the extra hour up front defining the output, purpose, inputs, constraints, and next steps, then I trust but verify with scheduled check-ins instead of hovering.”

“I learned the hard way that pulling work back after a rough start wrecks trust more than the rough start itself. Now I hand off a project task first, define what success looks like, set milestones, and let them run it, even when I want to step in.”

“I used to think I had to handle every task myself until my health forced me to build systems and delegate. Now I define the sandbox: what they can do, what they can't, and how I'll know it's working. Then I let them run it and only step back in if the guardrails break.”

“I learned this the hard way managing the Next.js team: the thing that feels like hovering is usually ambiguity, not check-ins. I now hand off outcomes, not tasks, and ask for a single shared update cadence so I can resist the urge to peek.”

“I delegate the outcome, not the method, and I agree the checkpoints before we start so I’m not hovering when anxiety kicks in. The hardest part is keeping my hands off once I’ve handed it over; if I step back in, I’m teaching them I don’t trust them, and next time they wait for me to rescue them.”

“I delegate by deciding up front what good enough looks like and when I’ll check in, not by watching the work happen. The hardest part is sitting with the urge to grab the keyboard back. I still write code partly because it keeps me honest about that urge.”

“I used to answer every question my team brought me until I realised I was training them to delegate the doing while I kept the deciding. Now I just ask, What would you do? before I say anything else. Three weeks of that and the small stuff stops landing on your desk, because you stopped being the answer machine.”