How do I write about something I find obvious?

This effect has a name in psychology and a practical consequence for anybody producing content. Once you know something well, it becomes difficult to remember not knowing it, and the assumption that everybody else shares the knowledge follows automatically. That assumption is why experts write badly for beginners and why the most useful material in any field is frequently produced by somebody one step ahead rather than twenty.

The test is not whether it feels obvious. It is whether you have explained it more than twice. If a question keeps arriving, the answer is not obvious to the people asking regardless of how routine it has become for you, and each repetition is evidence rather than a reason to skip it.

Look in your sent items rather than trying to identify these by reflection. Every explanation you have typed to a customer, every objection you have handled, and every question that preceded a sale is material you already produced once. Reading three months of correspondence produces a longer list of topics than any brainstorm, and each one arrived with proof that somebody wanted the answer.

Write it exactly as you would explain it in conversation, which is the second reason this works. The version you produce for a specific person is clearer than the version you compose for an audience, because you are answering rather than performing. If the writing feels stiff, the fix is usually to imagine one customer and address them.

Include the reasoning rather than only the conclusion. What makes expert content valuable is not the answer, which is frequently available elsewhere, but why the answer is what it is and when it does not apply. That is the part that cannot be found by searching and the part that demonstrates you know the subject rather than having read about it.

Add the specifics that make it yours. The number from a job you did, the mistake a customer made that you now warn people about, the local condition that changes the standard advice. A model can produce a general explanation of anything, and it cannot produce what you have seen, which is exactly what distinguishes your version from everything else on the topic.

Do not qualify it into uselessness. Experts frequently hedge every statement because they can see the exceptions, and the result is writing that commits to nothing. State the general case plainly, then name the exception separately. A reader who needs the exception will recognise it, and everybody else gets an answer.

Then notice which pieces produce responses, because the pattern is informative. The material that surprises you by performing well is almost always something you considered too basic to bother with, and that reaction is the clearest signal available that you are systematically underestimating what is worth explaining.

Ask somebody outside your field to read a draft and mark where they stopped following, which surfaces the assumptions you cannot see. The point where a reader loses the thread is almost always a place where you skipped a step that felt too basic to state, and one reader is enough to find several.

Keep a note of every question you answer in a week, without judging whether it is worth writing about. The judging is what stops this, and the list produced without it is invariably longer and more useful than the one produced by deciding in advance what counts as a topic.