Three ways to get a reflection past the surface

The reasonable reply that changes nothing

Here is the pattern. You describe what happened — the meeting, the argument, the weekend — and you get something back that is reasonable, warm and entirely correct. Nothing in it is wrong. And nothing moves. You close it thinking, well, that was fine, and it did not help.

The temptation is to conclude the tool is shallow. Sometimes it is. Most of the time something duller is going on: you handed over a summary, and a summary is all there was to work with. A summary is already the conclusion of your own thinking. You did the compressing before you typed, and what you compressed out is precisely the part that had anything in it.

None of that is a failing. Summarising is what we do when we tell anyone anything; it is polite and it is efficient. It is just the wrong shape for this particular job. The fix is not to try harder or feel more. It is to hand over different material.

There is a related trap worth catching. If you have told this story before — to a friend, to yourself in the shower, to a previous reflection — the version you type is a rehearsed one. Rehearsed accounts are smooth, they arrive with a moral already attached, and they are very hard to get anything new out of, because every rough edge has been sanded off by retelling. If you notice you are typing something you have said several times, say that too: “I have told this story a lot.”

Two things worth adding to a message

These two are the whole post. Each is a specific thing you can add to a message, and each changes what comes back.

One. Give the moment, not the account. Instead of “the meeting went badly and I felt undermined,” give the minute it turned. What was the last sentence before you felt it? Who said it, and what were the actual words? Where were you looking? “He said we already went over this, and I stopped talking for the rest of the hour” is a different object from “the meeting went badly.” One of them can be examined. The other can only be agreed with.

This feels excessive while you are typing it. It is not, and it is usually shorter than the summary you were going to write instead. The specific minute is where the information lives.

Two. Say what you expected to feel, and did not. Underrated, and one sentence long. “I thought I would be relieved when it was over and I was not.” “I assumed I would be angry and mostly I just felt tired.” “I expected to mind much less than I did.” The gap between the reaction you predicted and the one you got is among the most informative things you own, and you are the only person with access to it — nobody can infer your prediction from the event.

One note on both. You do not have to use them together, and doing so in a single message is a lot to type. Either one changes what comes back. If you only ever use one, use the first — the specific minute is also the easiest to write.

The third one people skip: say what you have already ruled out

There is a third and hardly anybody does it, because it sounds like withholding. Say what you have already ruled out. “It is not about the money.” “This is not about him being late.” “I know it is not really the job.”

Two things happen. The obvious one is that you save an exchange: whatever the first sensible question would have been is now already answered, and you skip past it. The less obvious one is that ruling something out in writing forces you to be specific about what you are ruling it out in favour of, and people often discover mid-sentence that they were wrong. “It is not about the money, it is about being the one who has to ask” arrives fully formed and was not available thirty seconds earlier.

Ruling something out is not the same as being closed to it, and it is worth saying so in the same breath. “I have already been round the money version of this and it is not that” leaves the door open while still clearing the ground.

Say all of it plainly, even where it sounds blunt. You are not managing anybody’s feelings here and there is nothing to be tactful about.

Why this helps

The reason is unremarkable: specific material has more to grip. A general account can only produce a general response, in the same way that “I have been feeling off” cannot be answered by a doctor without more to go on. Adding a minute, a prediction and an irrelevance roughly triples the number of things there are to ask about.

It also does something for you before anything comes back. Writing the exact sentence somebody said, instead of your verdict on the meeting, is a slower and more honest pass over the event — and a fair number of people find they no longer need the reply.

Depth is not the goal every time

One correction to all of the above, because a post like this is easy to read as an instruction to make every reflection deep. Most should not be. Plenty of days need somewhere to put the day down and nothing else, and the reflection where you listed four annoyances and went to bed was not a failed one.

Depth on demand is not really available anyway. You cannot decide on a Tuesday to reach the bottom of something. What you can do is bring better material and see what happens, which some days is nothing much. A reflection that stayed on the surface cost you nine minutes and produced a written record of a Tuesday. That is a fine outcome, not a wasted session.

Depth is also not the same thing as usefulness. Some of the most useful reflections are entirely practical: you worked out what to say to somebody, or which of three things to do first, and nothing was excavated at all. Treating those as second-rate is how people end up performing depth, which reliably produces the worst reflections of the lot — full of insight, connected to nothing.

And when it does not move, the interesting question is usually not what the software should have done differently. It is whether you were willing to hand over the specific minute — and whether, this week, you would honestly rather not.