Skip to content
Nhial Wei

About this site

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 is where the discipline started. It is still the discipline I carry today, even though the subject matter has shifted from food distributions in Juba to protocol risk, wallet safety, and investor education.

From humanitarian communication to crypto research, with the same commitment to clarity.

I am a former humanitarian communicator documenting the shift into crypto research, operations, investor education, and product thinking, with a bias for clarity, safety, and lifelong learning.

For more than fifteen years, I worked across humanitarian and development programs in East Africa, with the majority of that time spent between South Sudan, Kenya, and Uganda. My work covered research coordination, communication support, information products, reporting, and cross-team collaboration that stretched from field offices to global headquarters.

Today, I am applying the same discipline to crypto: learning deeply, supporting clearer user guidance, contributing to better understanding of products and markets, and documenting the transition in public so that the work, including its uncertainty, is part of the record.

Quick facts

Places worked

South Sudan (Juba), Kenya (Nairobi), Uganda (Kampala), with remote collaboration in Geneva, New York, Washington, London, Australia, and New Zealand.

Organisations

World Vision  ·  AECOM  ·  Management Sciences for Health  ·  DT Global  ·  REACH  ·  IMPACT Initiatives  ·  Nile Capital

Fields

Humanitarian and development communication  ·  Assessment and research coordination  ·  Pharmaceutical supply systems  ·  Media and cultural studies  ·  Crypto research and investor education  ·  Operations for distributed teams

My background

My professional foundation was built in humanitarian and development communication, and it was built at a desk, on a deadline, under editors who returned drafts with notes like "this paragraph does not tell me anything I can act on."

I remember the specific Monday it became clear to me what actionable writing actually was. It was 2016, Juba, and I was producing a situation report that had to carry the most recent displacement figures, the status of a pending emergency escalation, a summary of access restrictions in three counties, and a note about a rumoured attack in a fourth. The country director needed it by nightfall. What I learned at that desk was that my job was not to wait for the information to stabilise. It was to write clearly about what was known, explicitly about what was uncertain, and usefully about what was still being verified. A sentence that looked thorough but required a clarifying phone call had failed. A sentence that was accurate but buried the decision the reader needed to make had also failed.

The REACH February 2017 Briefing Paper, which remains the clearest single specimen of that discipline I produced, was not written on company time. Before REACH offered me the position, they sent raw field data and asked me to produce a situation report within a set timeframe. What I submitted earned me the job.

The environments were demanding. Displacement responses, cross-border coordination, emergency information needs, and long-cycle development programs, each with different stakeholders, different timelines, and different tolerances for ambiguity. I worked with colleagues and partners connected to teams in Geneva, New York, Washington, London, Australia, and New Zealand.

Over fifteen years I held roles that covered research design and assessment (REACH, IMPACT Initiatives), field-level communication and reporting (World Vision, AECOM), pharmaceutical supply and systems communication (Management Sciences for Health, SIAPS program), and development program reporting (DT Global). Each organisation taught something slightly different. The common thread was handling complexity under deadline, turning field realities into clear communication products, and keeping distant decision-makers honestly informed.

Clarity is not cosmetic. It is operational. A sentence is a proxy for a decision. Writing that is careless, vague, or unclear quietly costs the people who depend on it.

The pivot into crypto

My move into crypto did not begin with hype. It began with a cousin.

He has spent most of his professional life in the technology industry, and when I started paying attention, he was willing to teach me everything he knew. What drew me in was the technology itself. The architecture, the efficiency, what it was actually doing underneath the price chart. The market came second, and the communication problem came right alongside it.

Too many people enter crypto through noise, confusion, and weak guidance. Too much is said quickly, and too little is said carefully. People are being asked to make irreversible financial decisions on the basis of material that was often written to sell them something rather than to help them understand. The field already has enough people performing expertise. It has fewer people doing the slower work of helping ordinary users navigate it with less risk and more understanding.

When USAID closed the tap and the humanitarian sector shed staff overnight, colleagues who had built entire careers around the aid system found themselves without income and without a clear path forward. I had a head start only because I had already begun the transition before the funding collapse arrived. That head start was not a plan. It was a relationship with a family member who took the question seriously, and a stretch of my own time spent doing the reading.

Three years on the other side now confirm it. Across fifteen years in the sector with World Vision, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, and now three years into the transition at Nile Capital, the skills I thought I was leaving behind turned out to be the exact skills a serious crypto team is short on. The gap I am working toward, through Nile Capital, through this site, and through research and operations work in crypto-adjacent teams, is the slower work of making that bridge visible and useful for the next person.

What I have built

In 2023 the CEO of Nile Capital gave me a brief that sounded simple. Take Betzone, an online betting startup the company was developing, and build it into a business. Not manage the communications for it. Build the business.

The first thing I did was what I had always done in the humanitarian sector: research the environment before moving. Betzone's original concept was a crypto-based lottery platform. I approached the industry the way I had approached food-security dynamics in Jonglei State, triangulating primary sources, working with partial and sometimes conflicting information, and being explicit about what I knew, what I was inferring, and what I did not yet have good evidence for. The research pointed away from the original concept. We pivoted to a sports betting platform, built in-house after third-party licensing costs proved prohibitive.

The functions I was running simultaneously were: marketing to bring users to the platform, developer coordination to keep the product on schedule, government engagement to secure the licences the business could not operate without, and internal reporting back to Nile Capital's leadership. None of those were new skills. Each one was a humanitarian skill, re-pointed. Regulator engagement looked a great deal like donor engagement. Developer coordination looked a great deal like inter-agency coordination in a field response. Marketing in Juba looked a great deal like information-product dissemination in a humanitarian context, including going out with posters and stickers and working with the raksha drivers who carry most of the city's daily traffic, so that their vehicles became a mobile advertising layer across the city.

As of today, the Betzone website is live. The mobile app is running. The shopfront is operational in Juba. The product that began as a brief in a Nairobi office is a licensed, functioning business with a physical presence. What it does not yet have is the scale at which a betting business becomes self-sustaining; that is still in front of us. But the thing I can say cleanly is that a former humanitarian communicator, working inside a small crypto firm, built a regulated consumer product from architecture to launch. That is the evidence I trust the most when I am asked whether the humanitarian toolbox actually travels.

What I am working on

The work I am building toward sits at the intersection of research, communication, and operations.

  • Market and protocol research
  • Investor education and user guidance
  • Product testing and process feedback
  • Operations coordination across remote teams
  • Workflow support for research and developer-facing environments
  • Clearer communication around wallets, transactions, and risk-aware user behaviour

The aim is not to become a louder voice in the space. It is to become a useful one, the kind of contributor who raises the quality of the work around them.

Editorial principles

Clarity over performance

If something is worth saying, it should be understandable. Confidence is not the same as competence. Every piece on this site gets a final read with one question in mind: could a smart reader with no background in the topic follow this without feeling talked down to?

Safety over hype

In crypto, poor guidance can become expensive very quickly. The cost of getting a wallet setup wrong is not a footnote; it is a household outcome. I would rather be useful than loud, and I would rather explain a risk in the same sentence as an opportunity than in a disclaimer at the bottom of the page.

Learning over posturing

This site documents serious learning in progress, not expertise performed for effect. The uncomfortable middle of learning stays visible on purpose. If you want a feed of confident takes, you will be better served elsewhere.

Substance over speed

Not everything needs a hot take. Some ideas deserve slower writing, and some decisions deserve slower readers. Essays go out when they are ready, not on a schedule.

Lifelong growth

A career does not have to remain locked inside one field. Skills transfer, deepen, and evolve, and the transition itself is often where the most useful thinking happens. This site is built around that conviction.

Who this is for

This site is for readers who care about signal over noise.

  • People entering crypto and trying to learn responsibly
  • Researchers and operators working across distributed teams
  • Communicators trying to explain complex systems clearly
  • Humanitarian and development professionals considering a private-sector move
  • Builders who value practical thinking over empty visibility

If you have ever read a confident piece of crypto content and come away less clear than before, or sat through a meeting where everyone agreed without quite agreeing on the same thing, this site is probably for you.

How to get in touch

I take on selective research, investor education, and communication work, mostly with teams building products or communities in crypto, distributed work, and adjacent fields. If you think a conversation would be useful, the most direct way to reach me is email.

Response time

Usually within a few days. Slower during writing cycles.

If you are reaching out about collaboration, please include one or two sentences on what you are working on, what you think I could help with, and any timelines. It makes the first reply useful rather than a round of "what are you thinking."

Closing note

I am still learning, still building, and still refining the bridge between past experience and new work.

This site is part record, part laboratory, and part public notebook. The goal is not to look finished. It is to be useful, to the reader, and to the version of myself who will read this back in a few years and see exactly where the work stood on this particular day.