Keeping field notes next to the numbers
The situation
Managers hold two kinds of knowledge and keep them in two places. The numbers live in a system; the impressions live in your head and evaporate within a week. By the time the pattern matters — at program review, at a budget hearing, in a scheduling fight — all you have left is the half that was easy to store. This is a cheap habit that keeps the other half.
Steps
-
Pick one beat and one rhythm you will actually keep
Your calendar
One recurring observation, one fixed cadence: Friday afternoons, or after every class visit. Narrow and sustained beats broad and abandoned. A log kept for three years is worth more than a thorough one kept for five weeks.
What you only learn by doing it: Set the recurring reminder now, in the same minute you decide to do this. The habit dies in the gap between deciding and scheduling.
-
Dictate in the moment, not back at your desk
Speak it where you are, while the detail is still specific. Thirty seconds of voice in the hallway captures what twenty minutes of recollection on Friday cannot.
What you only learn by doing it: Say the date and place first, every time. Future-you will forgive bad grammar and will not forgive not knowing which week this was.
-
File it into the same table, as its own column
Gemini Notebook (formerly NotebookLM)
The note goes beside the numbers for that period, not into a separate document. One table, two kinds of column: what was measured, and what was seen. The whole value is in the adjacency.
What you only learn by doing it: Name the column something plainly descriptive — what it looked like — so a colleague opening the file in two years knows what they are reading.
-
Read both columns together and name where they disagree
Claude or ChatGPT, with the table attached
Once a term, read the numbers and the notes side by side and look for the places they tell different stories. Disagreement is the useful signal: a healthy fill rate beside three notes about a room that does not work is a finding.
What you only learn by doing it: Ask specifically where the two columns conflict. Ask for a summary and you will get an agreeable blend of both, which is the one output with no information in it.
-
Once a year, read the notes with the numbers hidden
Just you, reading
Read a year of observations on their own. Patterns show up in the prose that no column captures, because you were not tracking them when you wrote them down.
What you only learn by doing it: This is also the moment to retire the beat if it has stopped earning its thirty seconds a week. A log you have outgrown is allowed to end.
Where this breaks down
This can become a personnel file by accident, and that is the serious risk. Keep notes about conditions, not people: “third week, lab stations short of working units” rather than anything about who was running the lab. An unofficial log of observations about employees creates obligations, and discoverability, you did not intend.
If the notes concern students, they are education records the moment they are identifiable, with everything FERPA implies. Write about the room and the work, not the individuals in it.
Do not let the model tidy your wording. Ask it to transcribe and file, not to improve. Smoothed-out notes lose the specific detail that made them worth keeping, and six months later generic notes are indistinguishable from no notes.
Provenance: adapted from Dan Petroski, interviewed in OpenAI’s ChatGPT for Pros newsletter, 1 October 2026, who dictates what he sees walking the vines into the same record as his instrument data — in his words, overlaying “a human perspective on the data, adding color to the black-and-white facts we find in spreadsheets.” The sequence, the checkpoints and the cautions below are our construction, written for a classroom. Treat the source as one practitioner’s documented experience in a vendor publication, not as evidence that this works generally.