Someone at the center of your company carries every decision by hand. Read Essay 03, The Operator's Case →
Brief

The Friday routine that should not be a person's job

By Clint Oram

Friday at about four, when the week has stopped generating new problems and nobody expects anything back from me, I do the same forty minutes of work.

I open my sent mail and read backward through the week. Then Slack, starting with direct messages and then the four channels where real decisions get made. Then my calendar, meeting by meeting, because a meeting I attended is a reliable indicator that I agreed to something in it. I keep a running list in a plain text file, and the list has two columns.

What did I say I would do that has gone nowhere. And what did somebody say they would do for me that I have not seen.

It is the most useful block in my week. And to be honest, I'm not as methodical as I would like to be in making it happen every week.

Why I started

The first column exists because I am a person who says yes in conversations. Somebody raises something real, I can see how to help, and I commit before the sentence is finished. Two days later the commitment is gone from my head, and it lives only in the memory of the person I made it to, a customer waiting on a date or a colleague whose own work is now sitting behind mine, who is quietly revising their estimate of whether I am reliable.

The second column took longer to learn, and it cost more. Work I am owed goes quiet. A person who is going to miss a date does not usually send you a message about it. They send you nothing, and nothing is exactly what a person who is on track also sends you.

A customer service director at a food processor described the sharpest version of this I have read. She had promised one of her largest customers a call with an update on an escalated order.

Then I got busy with operational issues, got sick and had to go to the hospital. By the time I returned, the customer was extremely upset that no one called him and the problem got worse.

She owned that commitment and nothing else did. When she was gone it was simply gone, and the person who found out first was the customer.

What forty minutes actually buys

I catch my own misses before the other person has to raise them. There is a real difference between "I owe you that, it slipped, you will have it Monday" arriving from me on Friday, and the same sentence arriving on Tuesday after they asked.

I catch other people's misses while there is still time to do something.

And I get a read on what is actually happening in the company that no status report gives me. The pattern of what slipped tells you where the organization is overloaded, and it tells you before anyone is willing to say so out loud.

What it costs

The routine is not free, and I would not tell anybody to copy it.

It costs forty minutes of a senior person's Friday, every week, permanently. That is roughly thirty-five hours a year of me doing manual retrieval.

It is incomplete. A commitment I made on a phone call is not in my sent mail. A commitment made in a meeting where I did not take notes exists nowhere at all.

It is fragile, because it runs on one person's attention. A Friday where I am on a plane, or closing something, or worn out, is a Friday the routine does not happen. And the weeks I most need it are the weeks busy enough to crowd it out.

And it does not transfer. The routine works because I know which four Slack channels matter and which meetings usually generate commitments. I cannot hand you this system.

I have built software that was supposed to solve exactly this category of problem. On Friday afternoon I am still reading my own sent mail with a text file open.

The part that bothers me

The routine works, and it works because an experienced executive spends forty minutes on something that needs no judgment. And that doesn't include the countless five minute frenzied searches chasing status during the week.

The forty minutes are reading messages I have already read. Extracting the sentences that contain a commitment. Matching each one against whether anything happened afterward. Flagging the ones where nothing did.

Not one of those steps needs me. For most of my career nothing else could do them. Software can now read "I will get you that by Monday" and recognize a promise. They need something that reads the same places I read, follows each commitment for weeks, and notices when one stops moving. Deciding what to do about a stalled commitment is my job. Finding it is the whole forty minutes.

The two columns in my text file are the two halves of the same problem, and both of them sit on the far side of the decision. This is the execution gap, the second stage of the decision-to-done gap: the call got made, the commitment got given, and then nothing carried it.

Every operating executive I talk to has some version of this. A notebook. A Sunday night pass through Outlook. A standing Monday meeting that exists mostly to find out what did not happen. In a plant or a project office the reconstruction happens in Outlook and Teams instead of sent mail and Slack, and nothing else about it changes. We treat these as personal discipline, and we are quietly proud of them.

They are not discipline. Every one of them is a senior person doing by hand, once a week, work that should never have needed a person at all.