Skip to content
Came In For This All fifty notes

The hours

Sorting an hour while it is happening

One letter at the end of each hour, four words of context, and nothing else. Why the method has to be this small, and what it looks like after a fortnight.

Days this part is about, hour by hour

The dayEach working hour, in orderNeeded it

Wednesday, the second week

3 of 7

Planning day, the densest of the quarter

Thursday, the third week

0 of 7

Seven hours of solo work at a hot desk

Wednesday, the fourth week

3 of 7

The new starter's first day in the building

Could only have happened there: 6Possible anywhere, better there: 4Identical anywhere: 9Made worse by being there: 2

three days · 21 hours logged · six of them were only possible there · one of the three days contained no such hour at all · two were made worse by being there

Three of the twelve days drawn in full on this site.

Home / The hours

Method

A team evaluating remote employee productivity data should define purpose, access, and interpretation first, then use the data to improve planning rather than reward visible busyness.

An independent source worth checking for this subject is Partnership on AI.

The method is a letter. Not a time sheet, not an app, not a weekly reflection: one character written at the end of each hour, with about four words so that you can recognise it later.

09:00  n  whiteboard, the import argument
10:00  s  wrote the plan up
11:00  w  call to the Berlin three, from a corridor
12:00  —  lunch
13:00  s  reviewing
14:00  b  caught M about the schema, five minutes
15:00  s  reviewing
16:00  w  packing up early for the 16:40

Four letters:

  • n — could only have happened here
  • b — possible anywhere, better here
  • s — identical anywhere
  • w — made worse by being here

Why it has to be this small

Because anything larger does not get done, and a method that does not get done produces nothing.

Every richer version of this has been tried by somebody and abandoned in the second week. Rating each hour out of five requires a judgement you do not have at four o'clock. Categorising by activity produces a list of activities, which you already knew. Writing a sentence per hour is fifteen minutes a day and feels like homework.

One letter is about three seconds. It survives a bad day, which is the only real test, and bad days are the ones the record most needs.

The one hard case, and the rule for it

The hard case is the hour that was pleasant. Lunch with three colleagues; twenty minutes in the kitchen; the walk to the station with somebody you like.

The rule is that pleasant is not a category. The question is whether the building was required, and for most of those hours the honest answer is yes — they could not have happened anywhere else. They are n, and they should be, and the record is more honest for it.

What they are not is a work argument dressed as one. If a quarter's n hours turn out to be mostly lunches and corridors, that is a finding, not an embarrassment: it says the building is doing something real and social rather than something operational, and that is worth knowing before anybody writes a policy about collaboration.

What a fortnight looks like

Ten days, seventy hours, about three minutes of effort in total. Two things usually emerge, and they emerged here.

The n hours cluster. They do not spread evenly across the days. On this record seventeen of the thirty-one fell on Wednesdays, which was the day most of the team happened to pick.

There are more w hours than expected. Nearly everybody who has kept this record is surprised by the fourth column, and the surprise is always in the same direction.

What to do with it afterwards

Keep it to yourself first, and read it before showing it to anybody. The point is not evidence for an argument; it is finding out what your own quarter actually contained, which most people cannot say.

If it does become evidence, the thing that makes it usable is that it is specific and small. "Seventeen of my thirty-one useful hours last quarter were on Wednesdays, and I was required in on Tuesdays" is a sentence a manager can act on. "The office does not work for me" is not.

Ten days of one record

The raw material, as it was actually written, for one week:

Mon  (home)   s s s s s s s
Tue  (office) n s s b s s w
Wed  (office) n n b s s s w
Thu  (office) s s s w s s s
Fri  (home)   s s b s s s s

Five lines. The thing that jumps out of even one week is the fourth column, which appears three times in three office days and not once in the two days at home.

The two mistakes people make in the first week

Classifying the day instead of the hour. The whole method depends on the hour being the unit; a day is too coarse and the answer comes out as a mood. If you find yourself writing the same letter seven times without thinking, you are rating the day.

Rewriting the morning in the afternoon. The letter has to be written at the end of the hour it describes. Reconstructed at five o'clock, the morning is remembered through whatever the afternoon was like, and the error runs in the direction of whatever you currently feel about the office.

When to break the rule about not reflecting

Once, at the end of the fortnight, for about ten minutes.

Look at the n hours and ask what each of them needed. The answers come out as a short list — a specific person, something to stand in front of, an afternoon that was not full — and that list is more useful than the totals, because it is what you would have to arrange to get more of them.

On this record the list came to four items and they are the four conditions set out elsewhere on this site. They were not designed; they were what was left after reading thirty-one hours and asking what each had required.