Transitions
A standing resource for humanitarian, development, and public-sector professionals in the middle of a private-sector move. Concrete skills from fifteen years in the sector, plain-language translations into product, research, operations, and investor work, and the CV vocabulary that lets the market read what you actually bring.
When USAID closed the tap, the humanitarian sector shed staff overnight, and 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. This page is what I wish I had then.
The thesis, said plainly
Three years into a transition out of the humanitarian sector, across fifteen years of field practice in World Vision, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, and now three years into work at Nile Capital, I can tell you with some confidence that the skills you think you are leaving behind are almost always the exact skills the private sector is short on.
The difficulty is not that the skills do not travel. The difficulty is that the vocabulary does not. A humanitarian CV written in the language of the humanitarian sector reads to a private-sector hiring manager as a list of unfamiliar acronyms, unfamiliar programme names, and unfamiliar geographies. The reader skims, finds nothing that matches the shape of a role they understand, and moves on. The skills are still there. The market has simply not been shown how to read them.
This page, and the essays it routes to, do the translation work. Not by inventing experience, but by describing the experience you already have in the vocabulary the reader can use.
None of that is starting over. All of it is the humanitarian toolbox, applied to a domain that uses different words.
The three flagship essays
Each essay stands alone. Each can be read in a single sitting. Read them in any order.
Read if: You are thinking about the move and want the underlying thesis before anything tactical.
The case for why the humanitarian toolbox is almost always the exact toolbox the private sector is short on, and why the translation is a vocabulary problem rather than a capability problem. Written as the introduction a mid-career humanitarian professional can hand to a skeptical hiring manager, or to themselves on a hard week.
Read the essayRead if: You want to see the transition in motion. One week, five days, in the voice of someone on the other side.
A Monday-to-Friday account of what the humanitarian toolbox looks like applied to crypto research, investor education, developer coordination, and regulatory engagement, inside a small firm. The essay that made it clear to me, in retrospect, that none of this was starting over.
Read the essayRead if: You want a case study. One brief, from architecture to launch, with the honest account of what worked and what did not.
A start-to-finish account of being handed a brief to build a business, Betzone, inside Nile Capital, and what the humanitarian toolbox did and did not cover. The hard weeks are named. The case study is about whether the work you have already done can do this work; it is not a claim that every such venture succeeds.
Read the essayFour worked examples
The full set is twenty skills. Naming and treating all twenty on one page collapses the argument into an inventory. Four worked examples are enough to make the shape visible. The short-form map sits in the CV translation table below. The long-form treatments arrive one at a time, monthly, through the Guidance archive and the newsletter.
01. Actionable writing under uncertainty
What it is: Sitreps written at REACH under the condition that the data was partial, the deadline did not wait, and the recommendation had to survive being forwarded to a donor representative who had not read the source. The sentence is not a style; it is a discipline. You triangulate what you can verify, you name the gap between what you know and what you had to infer, and you present a finding the reader can actually act on.
Where it travels: Executive communications. Product requirement documents. Post-mortems. Investor updates. Incident reports. Anywhere the sentence has to survive being forwarded.
05. Translating technical content for non-expert audiences
What it is: A drug-resistance advisory at MSH meant one thing to a senior technical officer in Juba and something very different to a district health worker in Yambio. The sentence had to do both jobs at once without losing either. That is the same discipline that carries clinical, legal, or engineering content across to a reader on the other side of the specialist line.
Where it travels: Investor education. Content strategy. Developer relations. UX writing. Founder and reporter interfaces.
06. Information management, SOPs, and process design
What it is: On arriving into almost every humanitarian role I held, the first work was writing the procedure that did not exist. 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 the person about to rotate out. The craft is building the system so the work survives being handed to a stranger.
Where it travels: Knowledge management. Research ops. Product ops. Technical documentation. Any role responsible for continuity past a single person.
20. Leadership without authority
What it is: In a humanitarian cluster meeting, no one reports to you. In a coordination role between ministries, donors, and implementing partners, no one reports to you. The work moves because you convene, you name the decision, and you carry the rationale between rooms. That habit, practised for years, is what a private-sector firm hires a chief of staff or a program manager to do.
Where it travels: Chief of staff. Cross-functional leadership. Program management. Executive partnership.
The other sixteen sit across research under partial information, coordination across stakeholders, crisis communication, cross-cultural and cross-language fluency, operating under infrastructure constraint, measurement and closing the loop, visual storytelling, learning agility, negotiation and diplomacy, project planning, professional ethics and dignity in communication, theoretical grounding in communications, systems literacy, owning a communications strategy, local context literacy, and the generalist's burden. Each one is named in the CV translation table below with the private-sector roles it maps to. Each one, in turn, receives a longer treatment in the Guidance archive or the newsletter as the series moves through the list.
The CV translation table
The short-form conversion of each of the twenty skills into the role titles a private-sector hiring manager will recognise. Built to be lifted, shortened, and pasted during an active job search. Use the language that fits the role you are applying for; do not use all of it at once.
| Humanitarian skill | Private-sector roles and capability labels |
|---|---|
| 01. Writing that drives decisions under uncertainty | Actionable writing. Executive briefing. PRDs and post-mortems. |
| 02. Research design and assessment in information-poor environments | Research analyst. Due diligence. Market intelligence. User research. |
| 03. Coordination across stakeholders who do not share context | Program management. Chief of staff. Ecosystem partnerships. |
| 04. Crisis communication, media relations, and spokesperson craft | Corporate communications. Crisis and incident communications. Executive communications. Investor relations. |
| 05. Translating technical content for non-expert audiences | Investor education. Content strategy. Developer relations. UX writing. |
| 06. Information management, SOPs, and process design | Knowledge management. Research ops. Product ops. Technical documentation. |
| 07. Cross-cultural and cross-language fluency | International expansion. Localisation. Emerging-markets operations. |
| 08. Operating under logistical, security, and infrastructure constraint | Startup operations. Business continuity. Incident operations. |
| 09. Measurement thinking and closing the loop between publication and impact | Measurement strategy. Impact measurement. Analytics. ESG reporting. |
| 10. Visual storytelling and narrative craft | Brand and editorial. Founder and executive storytelling. Long-form content. |
| 11. Learning agility | Generalist operator. Frontier-domain research. T-shaped contributor. |
| 12. Negotiation, diplomacy, and conflict resolution | Sales and partnerships. Procurement. Policy and regulatory engagement. |
| 13. Project planning and project management | Program management. Technical program management. Production management. |
| 14. Professional ethics, safeguarding, and dignity in communication | Trust and safety. Responsible AI. Privacy and data governance. User safety. |
| 15. Theoretical grounding in communications | Brand strategy. Editorial and content strategy. Narrative strategy. |
| 16. Systems literacy | Public policy. Government affairs. Geopolitical risk. Regulatory affairs. |
| 17. Developing and owning a communications strategy | Head of Communications. VP Communications. Brand strategy leadership. |
| 18. Local context literacy and the informal ambassador role | Community relations. Stakeholder engagement. Country manager. Social license to operate. |
| 19. The generalist's burden | Chief of staff. Executive communications. First communications hire. |
| 20. Leadership without authority | Chief of staff. Cross-functional leadership. Program management. Executive partnership. |
Reading paths
Start with the Toolbox essay. Then read the About page. The goal at this stage is not to take action; it is to recalibrate your sense of what you already carry. Most people who end up making the move well spend several months here before anything tactical.
Open the CV translation table above, then go straight to Guidance Note 18, “Translating a humanitarian CV for the private sector.” Rewrite the top three bullets of your CV using that vocabulary today. Come back tomorrow for the next three. The work is not complicated; it is unfamiliar, and the unfamiliarity passes with practice.
Open the CV translation table above and find the row that matches the role you are interviewing for. Read the four worked examples in the section above to hear how one capability can be described in the private-sector register without overclaiming. Then rehearse the sentence you want the interviewer to walk away with. Two or three practised sentences carry a conversation further than a fluent monologue; the practised sentence is also what survives into a hiring manager's notes after the call.
Read the Week at Nile Capital essay. Most people who are six to eighteen months into a private-sector role after a humanitarian career have quietly concluded, in the hard weeks, that they made a mistake and are behind. They have almost always not made a mistake and are almost never as behind as the sector's hiring vocabulary would make them feel. The essay is a mirror, held up on purpose.
Who this page is for
FAQ
No. The market is slow to read humanitarian CVs, and much of what feels like “too late” is the translation problem rather than the calendar problem. Start with the CV translation table and rewrite the top section of your CV this week. The specific, plain-language descriptions of your capability will change how often you are contacted more than another month of searching will.
No. The translations on this page cover research, communications, policy, operations, product, trust and safety, and regulatory work across almost every private-sector industry. Crypto is the industry I happen to be working in now, but most of what is described here is industry-agnostic. Pick the industry whose problems you actually want to work on.
Often, in the short term, yes. Not always. The pay cut is usually concentrated in the first role; the compounding after that is much steeper than the humanitarian sector offers, and the optionality (roles, industries, geographies) is wider. The honest framing is that the first eighteen months may pay less and the decade after may not.
Yes, with adjustments. Look at row 02 in the CV translation table above (research in information-poor environments). The vocabulary for applied-research, policy research, and intelligence work is often closer to a PhD than to a humanitarian assessment officer, and the translation table can be adapted accordingly.
Yes. This page in particular is industry-agnostic. The crypto work is the writer's current context, not a requirement for the reader. The Transitions essays, the CV translation table, and the relevant Guidance notes are useful regardless of whether your next role is in tech, in policy, in a foundation, or in consulting.
Not individually at scale, but the reply address in the newsletter is real, and I read everything that comes through. If a specific sentence in your CV is not translating the way you want it to, sending it over with the role title you are targeting is a useful way to sharpen it.
If this page is useful, the newsletter carries the continuing version of the work. The skills series arrives one at a time, monthly, with a full treatment of a single capability and the private-sector rooms it travels into. Guidance notes on transitions arrive alongside. Roughly one to three dispatches a month, led by the work.
You can unsubscribe any time. Your email will not be shared, and you will not receive promotional content.
Thanks — you’re on the list. First dispatch will arrive when the writing is worth your attention.
Something went wrong. Try again, or email me directly and I’ll add you by hand.
Closing note
I wrote this page because the version of it I needed did not exist when I started the transition. The essays, the Guidance notes, and the CV translation table are the practical materials I wish I had been handed in 2022, when I was starting to read crypto seriously, and did not yet know that every skill I had built in the sector was already doing the work I thought I had to learn from scratch.
None of this is starting over. All of it is the humanitarian toolbox, applied to a domain that uses different words. If that sentence is useful to you this week, the page has done its job.