How much background is worth typing out

Two ways to get the first reply wrong

There are two versions of the opening message, and both make the first reply worse than it needed to be.

The wall. Twelve years of family history, four people introduced with full backstory, three previous attempts to fix it, before you reach the thing that actually happened on Tuesday. It is exhausting to write, which matters more than it sounds: by the time you finish the setup you have spent the energy you arrived with, and the real subject gets two tired sentences at the end.

The bare line. “My sister is being difficult again.” Everything after that is guesswork — who she is to you, what again means, whether difficult means cruel or merely annoying, whether you want to fix it or leave it. You will spend three exchanges filling in what one clause would have covered.

The useful amount sits closer to the bare line than most people expect, and it is not really about volume. It is about which four things.

The four things worth saying up front

Who the people are, in one clause each. Not their history — their role and their relevance. “My sister, who I speak to most days.” “My manager, who I do not trust.” “A friend from university I see twice a year.” That is enough to head off every wrong assumption without writing anybody’s biography.

What has already happened, versus what you are dreading. These get run together constantly and they are completely different problems. “She said it on Sunday” and “I think she is going to say it at Christmas” need different conversations, and a message that blurs the two produces a reply aimed at the wrong one. Separate them explicitly, even crudely: happened, versus might happen.

What you have already tried. The highest-value line in this list and the one most often left out. “I have already talked to her about it twice.” “I tried ignoring it and it got worse.” Without that you get suggestions you exhausted last year, which is the fastest possible route to deciding a tool is useless.

What you do not want discussed. If there is a subject you are not going into — a person, a diagnosis, a period of your life — say so at the start rather than steering around it for twenty minutes. “I do not want to talk about my father in this.” Plain, first message, no explanation required. It costs one sentence and it saves the reflection.

Everything else can wait until it is asked for

Everything not on that list can wait, and most of it will never be needed. You are not filling in a form and you are not being assessed. There is no completeness requirement and no reward for having front-loaded the context properly.

Worth stating, because a lot of people write the wall out of a kind of conscientiousness — a sense that it would be unfair to ask for a reflection without handing over the full picture first. Nobody is being short-changed. If a detail turns out to matter it will get asked for, and answering one specific question is far less work than pre-empting twenty.

The exception is anything that changes the meaning of the whole thing: a death, a diagnosis, a separation, a job loss. Those belong up front in one line, because a reflection built without them is built wrong. Everything else can arrive when it arrives.

There is a related habit worth dropping. People write the background as though it will be judged, so they soften it, contextualise it and pre-justify it — “I know this sounds petty, but she has had a hard year and to be fair I was tired too.” All of that is management and none of it is information. Write the unfair version and add the fairness later, if it turns out to matter.

Why this helps

The target is enough context to stop the guessing and little enough that you still have energy for the actual subject. Those two constraints pull against each other, and the four-item list above is roughly where they balance.

There is a side benefit worth having. Compressing the people in your situation into one clause each is a clarifying exercise in itself. “My manager, who I do not trust” is a sentence some people have never actually written down, and occasionally it turns out to be the subject.

What it holds, and what it does not

Being straight about this without overpromising: a reflection works from what you have told it. It does not know your history unless you put it there, and it cannot infer what you left out. If a reply seems to be missing something obvious, the most likely explanation is that the obvious thing was obvious only to you.

A useful habit if you are unsure how much to give: write the bare version, send it, and add context once a reply shows you which piece was missing. That is a two-message setup rather than a twelve-line one, and the second message is aimed instead of guessed. It also means the context you supply is the context that was actually needed, which is rarely the context you would have picked in advance.

Across separate reflections there is an optional memory that can carry the basics forward, so you are not reintroducing the same four people every week. It is worth understanding rather than assuming — there is a guide here on what a reflection remembers and how to steer it, and a separate one on the privacy side of the same question.