Delegating work I could not believe in

In 2010, I accepted a project I could not put my heart into. I remember being awake at 2 a.m., not because the work was unusually difficult, but because I did not care enough about it to do it well.

That is uncomfortable to admit. A lack of interest does not erase a commitment. The sponsor had trusted me with an outcome, and my private resistance did not transfer the risk back to them.

I first treated the situation as a choice between endurance and refusal. I could force myself through the work and probably deliver something mediocre, or I could walk away and damage the relationship. A third option emerged: find someone better suited to the work, make the case for the change, and remain responsible for a clean handoff.

The important part was not delegation as a clever escape. It was the transfer of trust. The other person needed the ability, capacity, and willingness to take it on. The sponsor needed to understand and approve the arrangement. Context, decisions, expectations, and accountability had to move with the task. If any of those conditions were missing, passing the work would simply move the problem.

I learned to treat resistance as information, not authority. Sometimes resistance means I am avoiding necessary work. Sometimes it reveals a genuine mismatch between the work and the person holding it. Judgment lies in telling those situations apart.

Delegation also has limits. There may be no suitable person. A contract may require direct performance. The unwanted part may be inseparable from a responsibility I chose. In those cases, the answer is not to rename abandonment as leadership.

What changed for me in 2010 was the project I believed I was doing. I was no longer trying to manufacture enthusiasm. I was trying to protect the promised outcome by finding a more honest arrangement for the work. That shift helped, but it did not remove my responsibility. It clarified it.