The Friday file whose reader moved teams in March

It is Friday morning, and the file you have just opened is the one you opened last Friday and the Friday before that. The form holds nine fields, three of them copies of last week's, and the run takes eleven minutes from the first field to the save. The manager who asked for this file changed teams in March. Her name still sits at the top of the form, above a list that has lost two people since.

Seven months of the same page sit in that folder, one for each week.

Standing work carries two qualities that keep it running after its reason has gone. Each instance costs minutes, and minutes sit under the level where a question about them feels worth the fuss. The job also carries an author: somebody, on some day, asked for it. When that person changes team, changes job, or stops opening the page, the reason leaves and the job stays.

Your eleven minutes bought something real in March. The trouble is that they still cost eleven minutes, plus the minutes spent deciding when to run it, the file carried until Friday, and the small drop in mood when the reminder appears.

Time the job once, then multiply by fifty-two. Eleven minutes a week comes to nine and a half hours a year, a day of work, taken out of the hours the week's real work needed. Multiply the whole row of standing jobs and the figure explains the feeling that the week has run out of room. The room went to work that made sense to somebody in March.

Sort your week's standing jobs and the piles separate.

The first pile has a reader outside your line: an audit file, a client's weekly figures, a report with a contract behind it. Miss the job and the absence arrives with your name on it inside a week. Keep it, and learn who reads it; that name is worth holding.

The second pile can be traced to a person and a moment: the tracker you built when the team had four clients, the format a client asked for in her first month. Each of these earns one sentence before it earns any more of your time, sent to whoever can still answer it. "I have been sending the Friday file since March. Is it still doing a job for you?"

The third pile costs most to look at: the job you keep because the hour is calm, or because stopping feels like dropping something. Keep it and write it down as a thing you chose. The hour was always fine; what weighs is carrying it as a debt.

A question does more than an announcement, and its shape decides how it lands. Name the job, its rhythm, the hour it takes, and hand the answer to the person the job was built for. She reads the line in ten seconds, and tells you either to keep going or what the page does for her now.

You will worry the file gets missed the week you stop it. Put that worry into the same line, as a question: "The Friday file has run since March. Does anything downstream depend on it?"

An honest limit: some standing work sits under somebody outside the building, a regulator, an insurer, a client's auditor, and the question still pays, because it names the person behind the job.

Send the line this morning, while the file is open and its author is a name at the top of a page. Then put the freed hour into this week, in a place you will meet it on Monday.