The Wet-Tuesday Audit: What Deserves Another Week of Your Attention

On a wet Tuesday afternoon, the kettle has gone cold, the light is the colour of a dishcloth, and there is a project open on my laptop that I have been calling ‘nearly done’ since August. Nobody is clapping. There is no launch email drafted. There is just me, a mug ring on the desk, and the question I have started asking more often: does this still make sense now, in ordinary time?

That is the Tuesday Test. Not a productivity system, not a five-year plan, not a clever framework with a diagram. Just a way of checking whether a piece of work belongs in my actual life, rather than only in the version of my life where I have limitless evenings and a very good haircut.

Why Tuesday, and not launch day

Launch day is a liar. It is adrenaline, a clean shirt and the brief illusion that everyone is watching. Even a small project feels electric when you have just pressed publish and the first few messages land. But the work has to live after that. It has to survive a Tuesday: a supermarket run, a client email, a dull headache, a train delay between Leeds and Sheffield, and the bit of the afternoon when the day has not quite ended but the energy has.

If a project only makes sense in the glow of starting, that is useful information. If it only makes sense when someone is praising it, that is useful too. The Tuesday Test is not about being grim. It is about being honest in a kinder light.

The three questions I actually use

I keep it short enough to do with a pen and the back of an envelope. No spreadsheet. No colour-coding. Just three questions.

1. Would I do the next forty-five minutes if nobody knew?

Not the whole project. The next physical action. If the answer is yes, the project has a pulse. If the answer is a vague ‘I suppose so, eventually’, it might be a parked idea wearing a deadline as a costume.

2. What would I have to stop believing for this to work?

This one catches me out. Sometimes the answer is ‘that I will suddenly enjoy editing audio’. Sometimes it is ‘that the client will change their mind about the thing they have said no to three times’. If the project depends on a belief I do not actually hold, it is not a project. It is a wish with a folder.

3. Does it make Tuesday better, or just more impressive?

This is the test I care about most. A portfolio piece can be impressive and still be a slog. A small side idea can be unimpressive and still make the week feel more like mine. I am not against ambition. I am against work that only exists to be admired from a distance.

Finish, park, let go

Once I have answered those three, I put the project in one of three boxes. The names are deliberately boring.

Finish means there is a clear next action, it can be done in ordinary time, and I still want to see it exist. It does not mean ‘finish everything’. It means finish the thing that has a real next step, not a fantasy of one.

Park means not now, but not never. I write a short note to myself: what this is, why it stopped, and what would restart it. ‘Parked until I have three good photographs’ is useful. ‘Parked’ on its own is just a drawer with better manners.

Let go means archive it, tell one person, and stop paying it rent in my head. No dramatic deletion. I move the files into a folder called ‘done and not continuing’, which is less romantic than ‘graveyard’ and easier to type.

A worked example from my own desk

Earlier this year I had a portfolio project about the hand-painted signs above chip shops. I loved the idea. I took about forty photographs. I made a hundred notes. On a Tuesday in March, I asked the three questions and realised I was avoiding the next forty-five minutes because the project needed interviews I did not want to arrange. It was not a photograph series. It was a written piece pretending to be one. So I parked it, properly, with a note saying it would restart only if I found three shop owners who wanted to talk. That felt like a small failure at the time. It was actually a relief.

A client project was different. The work was fine, the deadline was clear, and the next action was a single round of revisions. It passed the Tuesday Test because it was ordinary. Not exciting. Ordinary. That is allowed.

And a side idea — a tiny newsletter about bad typography on takeaway menus — failed the third question. It would have been impressive to nobody and fun to nobody but me. I let it go. I still notice the menus. I just do not owe them a project.

The twenty-minute version

If you want to try this, do not make it an event. Set a timer for twenty minutes. Take a sheet of paper and draw three columns: finish, park, let go. List every creative thing currently asking for your attention — client work, portfolio pieces, side ideas, the thing you keep mentioning at parties. Then ask the three questions for each one. Be boring about it. Be kind about it. The aim is not to clear the list. The aim is to stop pretending that every open tab is a promise.

What the test is not

It is not a reason to turn your practice into a factory. Rest is exempt. Play is exempt. The weird thing you make on a Sunday with no audience is exempt. The Tuesday Test is for work that is already asking something of you. It is a way of being a good steward of your own attention, not a way of squeezing more out of it.

As we head into the grey end of 2026, I want fewer projects that need a launch day to feel real. I want a few that make a wet Tuesday afternoon feel a bit more possible. That is the bar now. It is a low one, in the best way.