When I open an empty document, the easiest paragraph to write is usually background. The subject sounds broad, the sentences sound composed, and nothing specific has happened yet. I would rather begin with an unfinished note that keeps a question alive. If it later meets another observation, there may be enough material for an article. This fictional writing example describes that modest habit, without presenting it as a schedule or a method that every writer needs to follow.
Keep the situation with the thought
A useful note does not need a conclusion. While adjusting a list, I might notice that a date seems to belong to the next entry whenever the title wraps to three lines. Moving the date above the title solves one ambiguity but interrupts the reading order. That note contains a situation, an attempt, and an unresolved relationship. When I return to it, I can understand what bothered me without reconstructing the whole afternoon from a vague sentence about improving spacing.
I try to avoid keeping only an abstract verdict. A sentence such as “space matters” can fit almost any interface, which makes it a poor place to continue working. A screenshot, the window width, and the unusually long title give the thought somewhere to return. The note can be rough. It only needs to carry enough of the original situation that a future draft can ask a precise question instead of inventing a convenient example after the conclusion has already been written.
Leave a place for uncertainty
I use this shape as a reminder rather than a form that must be completed. Some notes contain one question. Others run for a page. The distinction I most want to preserve is between an explanation I suspect and an event I observed. “The gap may be too small” is a hypothesis. “A larger gap still looked ambiguous” is an observation. When those two ideas collapse into one confident sentence, the note becomes less useful and the later article can inherit confidence it has not earned.
Begin between two notes
When I am ready to draft, I look for records that have something to say to each other. Two different interface problems might both concern reading order. That connection suggests a manageable question: why can an arrangement look tidy and still be difficult to read? I do not need to include every note about typography in the same article. Following one question gives the draft a boundary, and that boundary makes it easier to decide which examples belong together and which can wait.
A draft can make the question clear before it knows how to end.
After the first version, I remove passages that provide background without helping the reader follow the actual problem. Then I check each example against the claim that comes after it. If the article concerns order but an example only explains color, I either explain the connection or put the example back in the notebook. Removing a polished paragraph does not destroy its material. The note remains available for another question that can use it more honestly.
At the end of a draft, I sometimes leave a next step instead of trying to summarize the whole subject. I may want to try the card with a keyboard, or ask another reader which date belongs to which title. Publishing does not have to end that investigation. For me, the practical part of a writing habit is giving unfinished observations a dependable home. A later article can then begin with something already worth examining, instead of asking an empty page to supply both the question and the answer.
