What humanitarian work taught me about clarity, trust, and risk

The first serious writing I ever did was a situation report.

A sitrep, in the language of the sector. A short document pulled together under pressure, summarising what had happened in a specific place over a specific window of time, for readers who were usually several time zones away and were making decisions on the strength of it.

That kind of writing changes you.

You learn very quickly that a sentence is not just a sentence. It is a proxy for a decision. Somebody reads what you wrote and, on the basis of what you wrote, moves money, moves staff, or chooses not to. If you overstate the situation, the response is distorted one way. If you understate it, it is distorted the other. If you are vague — the most common failure — nothing moves at all, and people on the ground pay the cost of your imprecision.

Three things stayed with me from that environment, and all three show up now in how I think about crypto.

Clarity is a form of respect.

When you write for readers who are busy, tired, and responsible for decisions that matter, vague writing is not a neutral choice. It is a way of transferring your own lack of thinking into their workload. The communicator’s job is to do the hard part first — to wrestle with what is actually going on — so the reader does not have to reconstruct it.

In humanitarian work, this meant stripping a situation down until what was true stood clearly on its own. In crypto writing, it means exactly the same thing. The fields are full of sentences that sound technical but do not say anything specific. You can read three paragraphs of a project’s own documentation and come away with no new information about what the project actually does. That is a communication failure presented as sophistication.

Clarity is what you owe the reader when you are asking them to make a decision.

Trust is built in small increments and lost all at once.

You see this pattern most clearly in places where communication has gone wrong before. A community that has been told one thing by one agency and a different thing by another does not give their attention cheaply the next time. They test you. They check what you said last month against what you are saying now. They watch whether your sources are real and whether you stand behind them when it is uncomfortable to do so.

Crypto does this too, just faster. The users who have survived a few cycles carry a similar kind of wariness. They can smell when a communicator is out of their depth. They notice the difference between a writer who read the documentation and a writer who summarised someone else’s summary. Trust in this space is not built with confidence. It is built with accuracy, consistency, and a willingness to say “I do not know” in writing.

Risk is not a number. It is a set of assumptions.

The field where I trained was saturated with numbers — caseloads, funding gaps, timelines. But every useful conversation about risk came back to the same question: what are we assuming that we have not verified?

That habit transfers almost directly into crypto. Most losses in this space do not come from bad information. They come from a chain of quiet assumptions that nobody tested — that a bridge is secure, that a yield is sustainable, that a team is who they say they are, that a frontend has not been tampered with, that a seed phrase is safely stored somewhere the user will remember. Each assumption looks small. Each failure looks sudden. The actual failure happened much earlier, quietly, in the assumption that was never examined.

The discipline of writing about risk well is the discipline of naming those assumptions before they become headlines.

None of this is particular to crypto. But it is unusually needed here.

This is a field with enormous consequences for ordinary users, a thin communication infrastructure, and a culture that rewards confident performance over careful work.

The lessons I carry in from humanitarian communication are not decorative.

They are the work.