A week on Friday

It's Sunday evening. The proposal is due a week on Friday at five o'clock. You've had the brief for three weeks.

There is a document. It has a title, your name and one heading that says "Background". You made it the day the brief arrived, in a burst of good intentions, and you've opened it four or five times since. Each time you read the heading, felt something you didn't stop to name, and found yourself doing something else. You answered email. You read around the subject. Once you reorganised the folder the document lives in.

You know how the next twelve days will go, because you've lived them before. This week you'll think about the proposal every day and do very little. Next weekend you'll plan to break the back of it, and you'll do an hour. On Wednesday the fear will arrive, the real kind that sits in the stomach. On Thursday you'll work until two in the morning, and at some point in that night you'll be astonished at how much you're getting done. On Friday at ten to five you'll send it, with a paragraph you know is weak and a budget you didn't have time to check. Then comes the relief, and the promise that next time you'll start earlier.

And it will probably be fine. That's what makes the pattern so hard to shift. You aren't failing. People think of you as capable, and you are. You may have a whole degree, or a whole career, built out of Thursday nights.

What nobody sees is the cost. They don't see twelve days of low dread, or the weekend you couldn't enjoy because the proposal was in the room with you. They don't see the version you'd have written with three more days. You don't see it either, which is part of the trouble. You only ever get to meet the rushed one.

Let me describe the pattern more exactly, because the details matter later.

It's selective. You don't put everything off. You answer messages quickly. You do favours for colleagues the same day. Dull admin often gets done without fuss. The things that wait are the things that count, where the result says something about you or could change something for you. I'll call that "work that matters" all the way through, and chapter 5 is about why that's the work that waits.

It isn't idleness. While the proposal waits, you're rarely lying on the sofa. You're doing smaller work, or getting ready to work, and you end most days tired.

It doesn't feel like a decision. You never sat down and chose to write the proposal on the last night. You chose, a dozen separate times, not to write it this afternoon. Each of those choices was small and reasonable. Added up, they hand the big decisions to the calendar. That's what I mean by the deadline deciding for you, and chapter 4 lists what it decides.

And it turns on a moment. You open the document, or think about opening it, and something in you swerves. It takes a second or two. I'm going to call that moment the swerve, and most of this book is about what happens inside it.

The usual explanations fit badly. If you were lazy, you wouldn't be working at two in the morning. If you couldn't manage time, you wouldn't hit the deadline so reliably. If you didn't care, the twelve days wouldn't hurt. Something else is going on, and it's easier to understand than any of those.

Here's something to try this week, if you have work waiting. The next time you go to it and swerve, don't fight. Catch the feeling that came a second before, and give it a rough name. It might be dread, or boredom, or confusion about where to begin, or a quick sinking thought that this won't be any good. You don't have to do anything about it yet. Knowing which feeling it is will be useful in the next chapter.