You put off the job.
Now you avoid the calls.

The phone rings. You know what they want before you answer.

An update on the job you agreed to do.

You know how to do it. You have what you need. You just have no interest in doing this particular job today. Yesterday was much the same. Tomorrow was supposed to be different.

Now someone is waiting for an answer, and the honest one is uncomfortable: you have not started.

"I'm working on it."

The answer that buys time.

Except you aren't. You have just given them a reason to keep waiting.

Where the problem grows

When does delay become a trust problem?

Delay becomes a trust problem when you give a false update and someone else plans around it. Each follow-up then involves the unfinished job and the story you told. Close the commitment honestly, correct any false impression, and set a clear boundary before accepting the next task you already know you will avoid.

The lie may feel small. You expect to catch up before it matters. If you finish quickly, perhaps nobody will need to know.

But the person calling may have their own deadline. They might have found someone else, changed the sequence, or warned their customer. Your reassuring answer makes those choices look unnecessary.

Now the task comes with a history.

They call again. You still have no result.

Admitting that now means explaining the previous update too. So you find another answer. Perhaps you blame a detail, an interruption, or someone you are supposedly waiting for.

Then you start avoiding the calls altogether. Their name on your screen feels like a problem. You become irritated that they keep asking about the thing you told them was underway.

The job itself has barely changed. Your relationship with it has become worse.

At first, doing it meant dealing with something boring. Now it also means facing the delay, the lie, and the possibility that the other person has stopped believing you. Opening the file brings all of that back.

So you avoid it again.

Do it while you still don't feel like it.

Sometimes Nike's instruction is enough: "Just Do It."

This is the task you can do, have agreed to do, and keep postponing because you would rather do almost anything else. Waiting to like it is giving that mood a lot of authority over your promises.

If you have already lied, completing the work does not make the earlier update true. Correct it plainly. "I told you it was underway. It wasn't. I should have told you that." Then give a completion time you can actually meet.

Open the actual work. Make the call the job requires. Complete the piece the other person needs. Stay with it long enough to produce something you can honestly hand over.

Moving the task to a fresh list does not count. Neither does writing a more impressive update about when you intend to begin.

Do it. Close it. Let it stop occupying your day.

If you genuinely cannot deliver, say so while the other person can still make another arrangement. Agree a handover or a changed commitment. Disappearing leaves them carrying the uncertainty.

Next time, say no before it becomes their problem.

Finishing this job does not mean you should keep accepting more like it.

If you already know you do not want this kind of work, set the boundary when the request arrives. You can be perfectly capable of doing something and still decide it does not belong in the work you accept.

"I don't take on that kind of work."

That answer lets the other person look elsewhere. A reluctant yes lets them believe the search is over.

Be specific about the boundary. Perhaps you accept the main project but not the recurring administration. Perhaps you can help once but will not own it every month. State that before the agreement, while it is still useful information.

And if the same unwanted work keeps arriving, look at what you keep agreeing to. I explored that larger question in When Procrastination Points to the Wrong Business Model. Today's unfinished promise still needs an honest ending.

Do the job you promised. Say no to the next one you already know you don't want.