Keeping the question

A notebook can hold a question without needing to answer it. A report is less comfortable with that arrangement. Reports want headings, findings and a sense of arrival. Somewhere between the notebook and the report, a tentative observation can become a confident statement. The change is often so small that nobody notices. A person said this becomes people need this. An uncertainty has quietly acquired a title.

I have been trying to preserve more of the original question in my research notes. Not because every conclusion is suspicious, but because a conclusion becomes more useful when its route is still visible. What prompted the observation? Who was present? What was the person trying to do? Was this the first time the situation occurred, or part of a pattern? These details do not all belong in the headline, but they should remain within reach.

Consider a participant who cannot find a document. It is tempting to record that search is broken. Yet the difficulty might come from an unfamiliar title, a missing permission, a document that was never uploaded or an expectation that the system cannot meet. The visible struggle is real. Its explanation is not yet settled. Good notes can distinguish the event from the interpretation without making either disappear.

One practice that helps is writing the observation and the interpretation in separate sentences. The participant opened three folders before asking a colleague for the file. I wonder whether the folder names match the language used by the team. The first sentence records something witnessed. The second offers a question to investigate. Together they are more informative than a label such as poor information architecture, which compresses the uncertainty before it has been examined.

This separation also makes collaboration easier. Another researcher can agree with the observation and disagree with the interpretation. A designer can suggest a different explanation. A developer can reveal a technical constraint that changes the picture. If the note presents only a finished finding, those conversations become arguments over a conclusion. If it preserves the question, they can become a shared investigation.

There is a practical limit. A team cannot carry every possibility forever. Decisions still have to be made, and a report that refuses to distinguish strong evidence from weak evidence is not especially helpful. Keeping the question does not mean avoiding judgment. It means making the judgment legible: here is what we saw, here is what we think it means, and here is what would change our mind.

I use a small margin note for that last part. It names the next observation that would strengthen or weaken the interpretation. Sometimes it is another conversation. Sometimes it is a review of the actual document names. Sometimes the answer is already available in a support log or a piece of product behavior we have not inspected. The note turns uncertainty into a direction for work instead of a vague disclaimer.

The final report can still be clear. It can recommend a change and explain why that change is worth trying. But it should leave a thread back to the original material. When the circumstances change, that thread helps the next person revise the conclusion without starting from nothing. A good research artifact is not only a record of what we decided. It is a way to continue thinking after the meeting is over.