The word you circle in the margin (2026)

It is Thursday, and the meeting is twenty minutes in.

Somebody says the word again — the one that has been in every deck since the spring.

Around the table, three heads move. Yours moves with them.

Your pen has already drawn a small circle around it in the margin.

The gap is one step wide

Whatever sits inside that circle is small. One definition, one step in the process, one setting in the tool.

Small enough that the person beside you could cover it in a sentence.

So the work goes around it. The task gets handed to whoever built the file last time.

The long way through the tool becomes your way through the tool. The figure gets copied from last quarter, since it was already sitting there.

Each one looks like the quickest way to keep the day moving. That is the trouble with it.

Three bills arrive later.

The first is the work. A number built on a guess holds up until it meets the person who built the original.

Then a Thursday afternoon goes to the rebuild, and one more conversation.

The second is the road around. The step you skip stays shut, and the way round it gets shorter with every use.

In March, the job you hand off is the one you were given to own.

The third is the listening. While the word is in the room, part of you tracks whether the gap will surface.

The meeting gets the rest.

The gap costs one sentence. Keeping it costs the morning.

Why the question waits

The moment this was meant to be learned has gone past. The first week, the handover, the Tuesday training, the colleague who left in June.

Asking now turns a small gap into a story about all the months since.

In your head, the question sounds like this: I should know this by now.

Here is the same question from the other side of the table.

The person answering drew a circle of their own in their own margin, in a meeting you both sat through.

They hear interest in the work, which most people in a Thursday meeting would take gladly.

And the answer takes them about as long as reading a message.

Ask it the way you would ask about the weather

Pick the one. The word from the meeting, the step in the file, the setting in the tool, or the figure you inherited.

Write the question in plain words, and put where you are standing on the end of it.

Show me the step where the export becomes the summary. I have been working from last quarter's file.

That second sentence is the useful half. It tells the person where to start.

Then say it out loud at the first gap in the conversation. A question asked across a table sounds like somebody doing the work.

Some rooms make it expensive to ask in the open: the client call, the room where you are the new one, the week somebody above you is already unhappy.

Those get the same question by message an hour later, to the one person who would know, with a time offered. Five minutes tomorrow morning?

Then the second half of it. Some piece of this week's work is standing on the guess: the figure, the section, the order of the steps.

Open that piece today and check the one part. Twenty minutes, and the guess gets replaced with the thing itself.

There is a version of this that runs the other way, and it costs the same ten minutes.

Somebody near you is holding a question they think they should have asked in March.

Answer it in the plainest words you have, including the part that feels obvious to you.

Some gaps want a proper hour: a walkthrough, a screen share, the file open at both ends. Book the hour by name, and keep the question written down until then.

Some of them belong to somebody else's desk. Ask what the gap costs your work, and let the rest stay where it is.

The thing I keep nodding along to: ___ Who I ask today, and the question in plain words: ___ The work built on the guess, and the part I check: ___

The question costs the other person half a minute and buys back the hours you spend walking around it. Ask it before the second coffee.