Transitions 19 April 2026 7 min read

A week at Nile Capital

A Monday-to-Friday account of the humanitarian toolbox, applied to crypto research, product, and investor education

A week at Nile Capital, the crypto investment and research firm where I now work, starts with a research brief and ends with something published. In between, there is enough of the humanitarian toolkit at work that, most weeks, I notice it.

Monday

On a Monday morning in early 2024, I was reviewing the tokenomics of a new decentralised-finance protocol that a portfolio company was considering. The brief required assessing the token distribution model, the emission schedule, the governance structure, and the execution credibility of the team. I was looking at primary sources. The whitepaper. The GitHub activity. The community forum. The on-chain analytics. I was working across partial and sometimes adversarial information, with a deadline that did not wait for certainty to arrive.

By lunchtime, I had produced a short memo. Two paragraphs on the thesis. One paragraph on the risk. One clear recommendation, expressed in the register of a decision, not a description.

This is the same work I did at REACH. The sources are different: token documentation, block explorers, governance forums, and on-chain analytics, rather than household surveys, key informant interviews, and displacement tracking. The discipline is the same. You triangulate what you can verify. You name the gap between what you know and what you had to infer. You present findings in a form the reader can actually use, which in a humanitarian context was a cluster coordinator and is, at Nile Capital, a capital allocator. The sentence has to survive being forwarded.

Tuesday

On Tuesday afternoon, I was in a call with a developer about a quality assurance issue in a wallet integration. The issue affected how transaction confirmations were displayed to users in a way that could confuse them into thinking a transaction had failed when it had not.

The developer understood the technical issue immediately. My job was to describe the user experience in terms that made the severity of the confusion visible to the engineering side, and to translate the developer’s technical constraints into a language the product team could work with. By the end of the call, the fix was scoped and the timeline was agreed.

This is translation between specialists. I spent years doing this work between clinical advisers and district health workers, between programme managers and donors, between field teams and a country director who needed to make a decision by nightfall. The Juba training room and the Tuesday call at Nile Capital are the same room. The knowledge has to cross a boundary in a form the person on the other side can use.

Wednesday

On Wednesday afternoon, I was updating a quality assurance documentation template that had never been formally written. The software team had an informal testing process, each developer carrying their own piece of it, but no document that captured the cycle from build to release. When someone new joined the team, there was nothing to hand them.

I had been through this before, at the start of more than one humanitarian assignment. The assessment methodology was in people’s heads. The contact list was in someone’s private spreadsheet. The reporting schedule lived in the inbox of one person who was about to rotate out. The first work of a new communications or research role was almost always to write the procedure, so the procedure could survive being handed to a stranger.

The document I wrote on Wednesday had a version number, a defined flow from code commit to user acceptance, a short list of what each stage produced, and a named owner for each stage. It was the same shape as a humanitarian standard operating procedure. The content was different. The craft was identical.

Thursday

On Thursday, I was finishing a piece of investor-education content about a new layer-two chain that had just launched on mainnet. The piece was for new and intermediate crypto users, people who understood the basic mechanics of blockchain but had not been following the layer-two landscape closely.

The frame I chose was not “here is what this new protocol does,” which would have positioned the content as promotional. The frame was “here is how to decide whether this protocol is relevant to you,” which positioned the content around the reader’s decision rather than the protocol’s marketing. That framing choice is not neutral. It carries an ethical instinct.

A humanitarian communicator makes that kind of framing decision constantly. Which truth to lead with. Whose interests the headline serves. What the subject line of the email will do when it lands in a donor’s inbox. The dignity-preserving discipline of choosing a quote that carries the truthful weight of an interview rather than the most quotable line. That discipline does not stay inside the humanitarian sector when you leave it. It travels with you, and in a field like crypto, where ordinary users are being asked to make irreversible financial decisions on the basis of material often written to sell them something, it is more valuable than the market has fully priced.

Friday

On Friday, I went back through the previous month’s investor-education content and tried to answer a question the team had rarely asked formally: which pieces brought readers back?

The platform metrics were shallow. Views. Shares. Follower movement. But a pattern was visible. Content that framed a decision clearly outperformed content that explained a mechanism. That finding changed the editorial approach for the following month. Fewer explainer pieces. More decision-support pieces.

This is the measurement loop. It is not glamorous. It is the discipline of asking, after publication, what the work actually changed, and updating practice accordingly. At REACH, we built coverage thresholds and modal-response rules into the monthly situation overviews, and we excluded settlements where data was too thin to support conclusions. The rule kept the work honest. Friday afternoon, staring at a shallow set of engagement metrics, I was applying the same instinct. The point of measurement is not to prove the work succeeded. The point is to learn whether it did.

The sentence underneath the week

None of that is starting over. All of it is the humanitarian toolbox, applied to a domain that uses different words.

The research on Monday is from the same discipline I built across years of REACH and IMPACT Initiatives assessment cycles. The memo it produced is from the same discipline I built writing sitreps in Juba for country directors who needed the decision before nightfall. The developer call on Tuesday is the translation work I did for years between specialists and the people their work affected. Wednesday’s documentation is the standard operating procedure discipline from half a dozen humanitarian roles where the procedure was in people’s heads and the first job was to put it on paper. Thursday’s editorial frame carries the ethical instinct that the humanitarian sector teaches before anyone calls it ethics. Friday’s measurement loop is what I was doing inside assessment cycles, under coverage thresholds, against external triangulation, for years.

Those are not vague parallels. They are the same skills, re-pointed to different subject matter.

What this week is not

I should be careful. This is one week. It is a good week. There have been hard weeks.

There was a stretch in 2024 when a product we had built, a betting platform called Betzone, went live and the software kept failing. There was an influencer campaign that brought users to a product that was not ready for them. There were months when the costs kept rising and the scale did not arrive. Eventually, we had to reduce staff significantly. Roselyn, one of my Kenyan colleagues from the content team, the person I had worked alongside every day for more than a year, was not among those who stayed.

I am describing a week that illustrates the carry-over. I am not describing a week that proves the transition is free. It is not free. Private-sector work, especially at an early-stage firm in a volatile industry, comes with business risk that a humanitarian salary, for all the sector’s funding volatility, partially insulated me from. That is an honest part of this record. I owe it to anyone reading who is weighing the move.

Two things to hold at once

If you are a humanitarian professional thinking about this transition, into tech, into crypto, into product, into research, into operations, into anywhere the private sector offers a landing, I want you to hold two things at once.

The first is that the transition is real work. You will need to learn new vocabularies. You will need to accept that your sector experience is not automatically legible to hiring managers outside it, and you will need to do the translation yourself until the market catches up.

The second is that the foundation you are standing on is stronger than the sector tends to tell you it is. The habits that make a humanitarian professional effective, actionable writing, research discipline under uncertainty, multi-stakeholder coordination, crisis-tested communication, technical translation, information-management architecture, operational realism under constraint, measurement thinking, ethical framing, and the capacity to lead without authority, are the same habits the private sector is short on and is quietly paying a great deal to develop elsewhere.

You have spent years building these capabilities under conditions that almost no other professional setting can replicate. A Monday in Juba and a Monday at Nile Capital are not the same room. The skill that walks between them is.