The skills you think you are leaving behind are the ones that will carry you
A humanitarian's field guide to the private-sector transition
The first time I told a colleague I was considering a move out of the humanitarian sector, the response was kind and slightly worried.
“But what would you even do?”
It is a question I have heard a version of from almost every humanitarian professional I know who has thought about making a similar shift. Underneath it sits a belief I want to name plainly, because it is wrong and it is expensive: the belief that humanitarian skills are a closed system. That they only make sense in the sector they were built in. That moving out means starting over.
Fifteen years in the sector — with World Vision, AECOM, Management Sciences for Health, DT Global, REACH, IMPACT Initiatives — and three years into the other side of the transition at Nile Capital, I can tell you with some confidence: 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 transfer. It is that the vocabulary does not. Humanitarians describe what they do in sector-specific language — “cluster coordination,” “assessment cycles,” “Level 3 response,” “protection monitoring” — and private-sector hiring managers cannot decode it without help. The skills are real. The translation is missing.
This essay is the translation I wish I had when I started thinking about the move.
I have picked twenty concrete skills from my own humanitarian career, described what each one actually involves, shown how I applied it in specific roles, and laid out how it becomes a private-sector capability once the labels change. These are not abstract competencies pulled from a job description. They are habits built by doing the work — the kind of habits that take years of field practice to solidify, and that most people in the private sector have no structured way to acquire. At the end, I have included a short section on what the bridging role at Nile Capital has actually looked like — because if you are standing at the edge of this transition, it may be useful to see what the other side of it can be.
The goal is simple: if you are a humanitarian professional contemplating a similar move, I want you to see that the years you spent in the sector were not a detour. They were preparation for work you have not yet named.
Skill 1: Writing that drives decisions under uncertainty
What it is in humanitarian work
In the humanitarian sector, a sentence is a proxy for a decision. A situation report written on Monday in Juba becomes the basis, by Friday, for whether an emergency response escalates, how much funding is moved, or which stakeholders are briefed. You are rarely writing for readers who will be in the room to ask a clarifying question. You are writing for people three time zones away who have thirty seconds and a budget meeting.
That teaches a very specific discipline: the ability to compress complex, shifting, incomplete information into writing that is accurate enough to be trusted and clear enough to be acted on — without overstating what you know or hiding what you do not.
How field experience solidifies it
You cannot acquire this skill from a template. You acquire it by writing the same kind of report every week, for years, under editors who will tell you exactly where the reader will lose the thread. You learn to put the decision first and the context second. You learn to separate verified fact from working assumption in the same sentence. You learn to write a headline that survives being forwarded to a director who will not read past the subject line.
How I applied it
At DT Global in South Sudan, I worked with field teams and the database manager to compile, edit, and produce weekly activity reports and monthly reports on a strict reporting schedule, and contributed to quarterly and annual reports that went all the way up the chain to the Deputy Chief of Party and Senior Technical Advisor. Every report was a small bridge between what was actually happening in the field and what needed to be understood by decision-makers who could not see it directly.
At AECOM, working under USAID’s Office of Transition and Conflict Mitigation standards, the writing discipline was even more explicit: information sheets, success stories, press releases, weekly and quarterly reports, each produced under compliance expectations that did not leave much room for drift.
At Management Sciences for Health, editing project reports, writing fact sheets, and producing technical briefs for senior leadership meant consistently packaging complex programmatic work into documents that non-technical stakeholders — USAID, Ministry of Health partners — could actually use.
At REACH, as Communications Manager, I developed and implemented the organisation’s communications plan and managed external communications end to end — writing web articles, producing product dissemination emails, and drafting presentations for partners and donors. Each of those outputs was a different vehicle for the same underlying discipline: turning research findings into writing that decision-makers would actually read and use.
The craft underneath all of that work is not “writing.” It is decision-ready communication — the discipline of making sure the reader has exactly what they need to choose, in the order they need it, without having to guess at what the writer meant.
How it transfers to the private sector
Every private-sector environment I have touched is structurally hungry for this skill. Consider four concrete patterns.
Early-stage startups run on weekly investor updates, internal strategy memos, and all-hands briefs, and most of the people writing them have never been edited by someone who would return the draft with the sentence “your reader cannot make a decision from this.” A humanitarian writer walks into that gap with fifteen years of exactly that editing.
Consulting firms charge premium rates for what they call “executive communication” — which is almost exactly the sitrep discipline with a different audience. A two-page deck for a board is structurally identical to a two-page sitrep for a country director. The skill is not new. The client is.
Product and engineering organisations run on documents called PRDs, RFCs, and post-mortems. Each of those is a decision-ready document under uncertainty. The teams that write them well ship faster and miscommunicate less. The teams that write them badly burn quarters.
In crypto specifically — the area I work in now — investor updates, protocol announcements, risk disclosures, and incident reports all fall into the same category. Every time a protocol fails to communicate clearly with its users during an incident, you can trace the failure back to a missing writing discipline that a humanitarian professional would consider baseline.
Private-sector translation: “Decision-ready communication. Executive briefing. Internal comms. Strategic writing. PRDs and post-mortems.”
Skill 2: Research design and assessment in information-poor environments
What it is in humanitarian work
Humanitarian research does not happen in clean conditions. Your sample is skewed because you cannot reach the most affected areas. Your sources are partial because people have reasons to misrepresent. Your timeline is compressed because decisions are already being made. Your verification options are limited because the infrastructure that would let you triangulate quickly does not exist.
What you learn, doing research in that environment, is a very particular kind of epistemic hygiene: how to reach defensible conclusions from imperfect information, how to be explicit about what you know and what you are inferring, and how to present findings in a way that supports decision-makers without pretending to more certainty than you actually have.
How field experience solidifies it
You learn this by producing research that will be audited by peers, donors, and affected populations, each of whom has a different reason to challenge it. You learn to anticipate the question “how do you know?” before it is asked. You learn to separate the headline number from the confidence interval without hiding either. You learn that a conclusion you cannot defend in a room with a hostile reviewer is a conclusion you should not have written.
How I applied it
At REACH, as an Assessment Officer, I contributed to research design and the implementation of full assessment cycles — coordinating with the Country Coordinator, Country Assessment Manager, the GIS team, and REACH headquarters in Geneva. The work included ensuring timely data collection, analysis, geo-referencing of datasets, and writing of assessment reports — situation overviews and factsheets — that then had to be disseminated to humanitarian partners and donors on time.
At IMPACT Initiatives, that work deepened: designing and implementing research activities in coordination with the country team and HQ in Geneva, developing and deploying data collection tools, analysing data, and producing research outputs including reports and standard operating procedures for data collection.
The habit that this builds — always naming the assumption underneath the claim, always being honest about the limits of the data, always leaving the reader in a position to disagree with the conclusion if they see something you missed — is genuinely rare.
How it transfers to the private sector
The roles that most resemble humanitarian research in the private sector are not always labelled “research.” Consider several concrete examples.
In venture and crypto diligence, the analyst’s job is to produce a defensible view of a team, a product, a token model, or a protocol on the basis of scattered, partial, often adversarial information. The discipline is the same as assessing food security in a contested region: you triangulate what you can, you flag what you cannot, and you write a recommendation your reader can act on without having to redo the work.
In market research and competitive intelligence, the task is to characterise a landscape from fragmented signals — user forums, pricing pages, press coverage, hiring patterns, product changes. The humanitarian assessment officer who has built an understanding of an operational environment from similarly fragmented signals knows how to do this and how to avoid the common failure modes — over-weighting recent information, confusing volume with significance, confusing visibility with importance.
In user research and customer research, the job is to produce a faithful representation of a population you cannot fully sample, working through gatekeepers, on short timelines, for decisions that will be made regardless of the quality of your work. That is the exact operating environment of a humanitarian assessment.
In investigative work — due diligence, fraud investigation, compliance research — the reward structure is identical to protection monitoring: careful conclusions, clearly sourced, defensible under review. Any role where the job is to produce a trustworthy view of a situation that resists easy verification is a role a trained humanitarian researcher is set up to do well.
Private-sector translation: “Research analyst. Market intelligence. Due diligence. Strategy. Investor research. User research. Compliance.”
Skill 3: Coordination across stakeholders who do not share context
What it is in humanitarian work
Humanitarian coordination is one of the most underrated forms of operational skill in existence. You are working with teams that do not share language, do not share institutional culture, do not share incentives, and frequently do not share an understanding of what success looks like. Field offices, national governments, UN agencies, INGOs, local NGOs, donors, affected communities — each group has its own vocabulary, its own reporting cycles, its own pressure points.
The coordinator’s job is to hold a shared picture together that none of the individual actors would construct on their own.
How field experience solidifies it
You learn this by sitting in the meeting where two organisations with the same stated mission are actively talking past each other, and recognising that the problem is not bad faith but different definitions of four of the key words in the room. You learn to write a joint document that both organisations will sign without either feeling misrepresented. You learn that a shared artefact — a common dataset, a joint plan, a single weekly update — is usually more effective than another meeting.
How I applied it
As Communications Manager at World Vision South Sudan, I served as the strategic link and focal point for National Office communications, connecting the Regional Office, Support Offices, and the Global Centre during humanitarian emergencies — and collaborating with World Vision’s Global Rapid Response Team during Level 3 Emergency Response communications. That was not abstract coordination. It was real-time alignment across four organisational tiers, under emergency conditions, where the cost of misalignment was not a delayed sprint but a compromised response.
At Management Sciences for Health, a significant part of the role was collaborating with MSH technical advisors, the Ministry of Health, and USAID — each of which had different vocabularies, different approval processes, and different expectations — and producing a joint Malaria Newsletter that had to be coherent to all of them.
At AECOM, coordination took another form: working with Regional Program Managers and Program Officers to document projects consistently, organise information across a distributed field operation, and ensure the project record held up to USAID OTCM standards.
Across all of those roles, I was regularly in contact with colleagues and stakeholders connected to teams in Geneva, New York, Washington, London, and further afield. Holding that kind of multi-stakeholder fabric together — across languages, time zones, and institutional cultures — is a skill you do not acquire on a single project. It is a long apprenticeship.
How it transfers to the private sector
Private-sector work is increasingly distributed, increasingly cross-functional, and increasingly dependent on exactly this kind of coordination skill.
Remote-first companies live or die on it. A humanitarian who has held a programme together across Juba, Nairobi, and Geneva does not struggle with a sprint spanning San Francisco, Berlin, and Singapore. The shape of the problem is familiar.
Crypto protocols with contributors across a dozen jurisdictions need this skill acutely. The typical protocol has a core team, an operations team, a marketing team, a community team, a foundation board, and a distributed contributor base, each operating with different incentives. The work of keeping that fabric aligned — shared narratives, shared roadmaps, shared priorities — is structurally identical to humanitarian cluster coordination.
Product organisations with engineering, design, research, legal, compliance, and go-to-market teams in different locations run on whoever can hold the shared picture together. That person is usually called a chief of staff, a program manager, or a product operations lead. A humanitarian coordinator walking into that role is walking in with years of high-stakes practice at the hardest version of the problem.
In ecosystem and partnerships roles — managing a relationship between your company and an exchange, a custodian, a regulator, a major customer, or a portfolio company — the work is explicitly about translating between institutions that do not share context. That translation layer is exactly the humanitarian coordinator’s craft.
Private-sector translation: “Program management. Chief of staff. Operations lead. Ecosystem partnerships. Product operations. Integrations lead.”
Skill 4: Crisis communication, media relations, and spokesperson craft
What it is in humanitarian work
Private-sector professionals talk about working under pressure. Humanitarians live in it. The sector runs on emergency cycles, displacement surges, funding windows that open and close unpredictably, and political situations that can shift overnight. You learn to make reasonable decisions with partial information, revise them as new information arrives, and keep the people around you from freezing when the environment is moving faster than the plan.
In communications specifically, this is two adjacent disciplines that sit in the same person. Crisis communication covers what you produce during an active incident — public statements during emergencies, consolidated information for media releases when operations are affected, and external messaging while internal facts are still being verified. Media relations covers the ongoing relationship with the press that exists before, during, and after every incident — being a reliable source for journalists, preparing organisational spokespeople to be credible in public, and managing the long arc of how the organisation is represented in the media. The two disciplines are inseparable in the field: the relationship you build with journalists between incidents is what lets the crisis statement land well during one.
How field experience solidifies it
You learn crisis communication by writing a statement at two in the morning, with the country director on the phone, while the situation on the ground is still evolving — and watching that statement be forwarded, quoted, and sometimes mis-quoted within the next six hours. You learn the difference between a sentence that is accurate and a sentence that is useful. You learn to hold a line on what is known and what is not, even when every stakeholder in the room is pushing you to say more than you can support.
You learn media relations by answering enough inquiries to recognise the pattern of the question underneath the question, by preparing enough spokespeople to know what they need to hear before they step in front of a camera, and by managing enough field visits for journalists to understand what goes wrong when you do not. The skill compounds; by your second decade in it, you are reading a request for comment the way a lawyer reads a contract.
How I applied it
At World Vision South Sudan, my role explicitly included reviewing and consolidating information for public and media statements during complex humanitarian emergencies, and serving as a focal point for communications when the Global Rapid Response Team was mobilised for Level 3 responses. That meant producing accurate, on-message, time-sensitive communication while the situation on the ground was still evolving — and while multiple internal tiers of the organisation needed to be aligned on what was being said externally.
In that same role, I managed media inquiries, facilitated field visits for journalists, prepared press statements, and arranged press conferences for an organisation operating in one of the most fragile political environments in the world — under conditions where the coverage decisions made that month would shape how the organisation’s work was understood for much longer than that. That is not a training ground you can replicate through a course. At AECOM, producing success stories and briefing materials meant packaging work in a way that met the needs of the funder, the public, and the press simultaneously. Across roles, being the reliable interface between the organisation and the press — and preparing the people who had to speak publicly on its behalf, often country directors and programme directors — was a continuous part of the job.
How it transfers to the private sector
This is the skill profile that early-stage companies explicitly hire for and struggle to find.
In corporate communications, public relations, and crisis PR, the work is structured around both the quiet arc — managing an ongoing relationship with press and analysts, preparing executives for public moments, shaping coverage over the long arc rather than reacting inside a single news cycle — and the loud arc: moments when the organisation’s story is temporarily out of the organisation’s control, like a data breach, a leadership departure, a product failure, or a regulatory action. The humanitarian communicator arrives with the muscle memory for both.
In incident response — for a security team, a trust and safety team, a platform operations team — the communication discipline during an active incident is indistinguishable from an emergency response. Clear internal alignment, clean external messaging, disciplined updates on a cadence, and an honest accounting once the dust settles. All of that is humanitarian crisis comms with different vocabulary.
In crypto specifically, the ambiguity is acute — bridge exploits, depegged stablecoins, frontend compromises, protocol failures, governance attacks. The organisations that handle those moments well are almost always the ones with a communicator who has done something like this before. Founders and protocols are often one exploit or one regulatory action away from becoming a story; a communicator with genuine crisis and media-relations experience is a structural risk reduction, and most crypto teams do not have one. A humanitarian communicator who has worked through a Level 3 response is not going to freeze during a smart-contract exploit.
In executive communications and investor relations, preparing a founder or CEO to be credible in public — what to say, what not to say, which interviews to take, which to decline, how to handle a tough question — is a distinct craft that humanitarian communicators have been practising for years with country directors and regional comms teams as their subjects.
In policy, government affairs, and regulatory communications, where the environment shifts because a government body issues a ruling, introduces a bill, or opens an enforcement action, the skill is the same: absorbing new information quickly, aligning internal stakeholders, managing the press and the regulator as audiences alongside each other, and producing a calm, defensible external position on a short clock.
Private-sector translation: “Corporate comms. Public relations. Crisis communications. Incident response. Investor relations. Policy and government affairs. Executive communications. Spokesperson preparation. Trust and safety.”
Skill 5: Translating technical content for non-expert audiences
What it is in humanitarian work
The entire humanitarian communication discipline rests on a principle that most private-sector communication has quietly abandoned: the people most affected by a decision are usually not the people in the room where it is being made.
Humanitarian communicators are trained to write for beneficiaries they will never meet, advocate for populations who cannot represent themselves in the meetings that matter, and translate complex technical work — public health, protection, nutrition, WASH, governance — into language that donors, policymakers, and the public can actually understand. The craft underneath that work is disciplined empathy: the ability to centre a reader who is absent, under-represented, or unfamiliar with the subject matter.
How field experience solidifies it
You learn this by writing a donor report on a nutrition programme, realising it is unreadable to someone without a public-health background, and rewriting it until a generalist can follow it without losing the substance. You learn the difference between simplifying and dumbing down. You learn that jargon is usually a symptom of an author who has not yet decided who they are writing for.
How I applied it
At Management Sciences for Health, producing the Malaria Newsletter meant working with technical advisors whose expertise sat deep in epidemiology, treatment protocols, and health systems — and editing their content into publishable material that MSH’s full stakeholder audience could read without a clinical background. Technical briefs and fact sheets produced in that role had to translate programmatic work into short, readable documents for USAID and Ministry of Health partners.
At AECOM, producing information sheets, success stories, and briefing packets for USAID’s Office of Transition and Conflict Mitigation required the same skill: taking the programmatic reality of conflict mitigation work and rendering it into documents that funders, policymakers, and the public could absorb.
At REACH, in the Communications Manager role, the translation task was continuous: assessment findings from the field had to become web articles for public audiences, dissemination emails for humanitarian partners, and presentations that would travel into meetings I would never sit in. The underlying research was highly technical — geo-referenced datasets, multi-round assessment cycles, sectoral analysis — and the audience was mixed. The job was to make the findings legible without flattening the rigour.
At World Vision, across two separate roles, the discipline ran through everything — news features, photographic reports, newsletters, annual reports — all designed to carry complex humanitarian work into the attention of audiences who did not have the context of the people doing it.
How it transfers to the private sector
This is one of the most valuable and most under-hired capabilities in the market.
In crypto, where ordinary users are being asked to make irreversible financial decisions on the basis of material written by people much closer to the technology than to them, the shortage of this skill is acute and the cost of the shortage is measurable in real money lost by real people. An investor-education function run by someone with humanitarian communication training is an immediate upgrade for most protocols.
In developer relations, the job is to translate between product teams and external developers building on their platform — which is the exact same problem as translating between technical advisors and donor audiences, with a different vocabulary. Humanitarian communicators who have edited technical specialists for generalist audiences have already trained the muscle.
In content strategy and content marketing, the difference between a team that produces material readers actually use and a team that produces material readers skim is almost always about audience empathy — the discipline of centring a reader who is not in the room. Humanitarians spend a decade building that discipline.
In product marketing and UX writing, the work is to carry complex product capability into language and interface copy that a user can act on without reading documentation. Same muscle, different surface.
In regulatory communications, policy explainers, and public-interest technology writing, the challenge is to translate technical policy into language that legislators, journalists, and the public can use. Humanitarian policy communicators have been doing this work for decades.
Private-sector translation: “Investor education. Content strategy. UX writing. Developer relations. Product marketing. Policy and public-interest comms.”
Skill 6: Information management, SOPs, and process design — the operational architecture that lets work repeat
What it is in humanitarian work
The less glamorous half of humanitarian work is the operational architecture underneath it. Two adjacent disciplines sit here: information management — the artefacts that turn field data into institutional knowledge (databases, reporting templates, SOPs, runbooks, document repositories, verification protocols) — and process design — the workflow underneath the work itself (who does what, in what order, with what handoffs, under what approvals, on what cadence). Information management answers what you store and how you organise it. Process design answers how the work itself is structured. In the field, the same person usually holds both; the SOP and the workflow it governs are built together, revised together, and fail together.
Without this layer, the rest of the sector’s work collapses back into anecdote every time staff turn over. This is quiet, unloved work that shows up clearly only when it is missing. It is also the work that distinguishes functional organisations from ones that keep rediscovering the same mistakes.
How field experience solidifies it
You learn this by inheriting a programme where the previous staff have left and the institutional memory has left with them — and realising that the artefacts they built or failed to build determine whether the next six months are a continuation or a reconstruction. You learn that a good SOP is a gift to your successor, and a missing SOP is a tax on everyone who comes next.
You learn the process side by inheriting a workflow that is not producing usable outputs, diagnosing the specific step that is failing, and redesigning it so that the overall system behaves. You learn that most process problems are coordination problems dressed up as documentation problems, and that the best-written SOP in the world will not save a workflow whose handoffs are broken. What emerges is a particular kind of operational thinking: the ability to look at a piece of work and see the workflow underneath it, to name the steps that matter and remove the ones that do not, and to build systems that continue to function when specific individuals leave the team.
How I applied it
At AECOM, I contributed to the management of an information database for USAID’s OTCM program — collecting and inputting up-to-date information on activity implementation progress and outcomes, in compliance with OTCM standards, and coordinating the documentation of projects across regions, including the organisation and storage of project photographs and materials. That work was not only documentation; it was process work, ensuring information from across regions entered the system consistently and met compliance expectations end to end.
At IMPACT Initiatives, I produced standard operating procedures for data collection in support of ongoing research activities — documents that turned one-off work into repeatable work, and individual competence into team capacity. That was explicit process design: defining how a research activity moved from instrument design, through field deployment, through analysis, through reporting, in a way that could be executed by the team and repeated across cycles.
At REACH, across both the Assessment Officer and Communications Manager roles, the coordination of timely dissemination of information products — situation overviews, factsheets, web articles, product dissemination emails — to humanitarian partners and donors was information management operating inside a publishing process that had to work reliably month after month across a distributed team. The Communications Manager role also included monitoring and evaluation through regular tracking of how REACH’s research products were being referenced and used, and feeding that back to the organisation — a closed loop between publication and impact that most private-sector content and research teams aspire to and rarely build.
At DT Global, monitoring online and daily newspapers for news relevant to the organisation, scanning, cataloguing, and saving relevant articles, was a form of media intelligence built on the same underlying discipline. And the weekly, monthly, quarterly, and annual reporting cadences across reporting-heavy roles were processes that needed to be designed and maintained as much as executed.
How it transfers to the private sector
This layer is called many things in the private sector — knowledge management, documentation, technical writing, internal tooling, operations engineering, research ops, QA, program management, revenue ops, product ops, business operations — and the craft underneath all of those names is the humanitarian operational architect’s craft.
In research operations for any private-sector research function — user research, market research, competitive intelligence — the job is to build the artefacts that let one researcher’s work become the team’s work, and to design the cadence under which it happens. Repositories, templates, tagging systems, synthesis cycles. A humanitarian who has run an assessment cycle has done a version of this.
In engineering and product operations, the runbooks that handle incidents, the documentation that onboards new engineers, and the SOPs that keep deployments safe are all instances of the same discipline — as are the workflows that govern how releases actually move through the team. Organisations that treat this work as junior work ship worse software. Organisations that treat it as senior work ship better software.
In program management, revenue ops, product ops, and business operations, the central job is to look at how work moves through the organisation and make it move better. In startup scaling, the transition from a twenty-person company to a hundred-person company is almost entirely a process-design problem layered on top of an information-management problem, and the people who can do both at once at the early stage are rare.
In crypto specifically, where I now work, the operational memory and the operating cadence of a research and product team live in exactly these artefacts: SOPs for investigating new projects, runbooks for handling incidents, documented criteria for how a project gets a thumbs-up or a thumbs-down, and an institutional record of why past decisions were made the way they were — plus the processes that govern how grants get made, how governance runs, and how incidents get handled. Most of that layer is currently held together by heroic individual effort that would collapse without a proper design underneath it.
In compliance, audit, and regulated environments, both disciplines are not optional — they are the deliverable. Humanitarian professionals who have worked under USAID or UN compliance standards have already operated in environments where the record of why you did what you did is as important as the outcome itself.
Private-sector translation: “Knowledge management. Technical writing. Research ops. Product ops. Revenue ops. Program management. Business operations. Documentation. Internal tooling. QA. Compliance. Scaling operations.”
Skill 7: Cross-cultural and cross-language fluency
What it is in humanitarian work
Humanitarian work is a daily exercise in working across cultures, languages, and institutional worlds. You sit in meetings where three or four languages are being used in parallel, where colleagues are code-switching between donor vocabulary and community vocabulary inside a single sentence, where what sounds like agreement is in fact polite deflection, and where what sounds like conflict is in fact genuine engagement. Reading those environments correctly is not a soft skill. It is a core operational skill, and getting it wrong costs time, trust, and occasionally more than that.
How field experience solidifies it
You learn this by being the only non-native speaker in a room and realising that the meeting is going to continue whether you can follow it or not. You learn to notice when a translation has lost the nuance — or has preserved the word and lost the meaning. You learn that “we will see” means different things in different cultural contexts, and that reading the room is as important as reading the document.
How I applied it
Across roles with World Vision South Sudan, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, almost every working day involved coordinating across multiple languages and multiple institutional cultures — South Sudanese, Sudanese, Kenyan, Ugandan, Ethiopian, and international colleagues working in English with Arabic, Juba Arabic, Dinka, Nuer, French, and other languages moving around in the background of the work. Donor stakeholders in Washington, Geneva, London, and New York each brought their own institutional culture. Local government partners brought another. Communities brought another.
The skill that emerges from working in that environment for fifteen years is not “international experience” in the CV sense. It is a practical capacity to read a room that is operating across several languages and institutional cultures, and to act in a way that is legible to each of them without losing the shared thread.
How it transfers to the private sector
The private sector has quietly become a cross-cultural environment and has not updated its language for it.
Global product and engineering teams are functionally multi-cultural, multi-lingual, multi-time-zone operations. The people who keep those teams aligned are the people who can read cultural signal — who notice when a design review in San Francisco is producing different unspoken conclusions than the same review in Berlin or Bengaluru.
International expansion and localisation is a field that depends entirely on this skill and usually does not name it. Launching a product in a new market requires more than translated strings. It requires someone on the team who can read the cultural and regulatory context of the market well enough to anticipate the friction a localisation-only approach will miss.
In crypto, where communities span continents and regulatory environments are wildly inconsistent across jurisdictions, the team members who can navigate a conversation with a Singaporean exchange, a European regulator, and a Brazilian community lead in the same week without misreading any of them are scarce and valuable.
In partnerships, sales, and customer success roles targeting international customers or cross-border institutional clients, cultural fluency is the difference between relationships that compound and relationships that quietly stall.
In Africa-focused investing and operating roles specifically — a space where the private sector is increasingly active and where the humanitarian sector has spent decades — the cross-cultural credibility a humanitarian professional brings is a genuine competitive advantage. You have already done the work of earning trust in environments that the sector has not yet figured out how to staff for.
Private-sector translation: “International expansion. Localisation. Global partnerships. Emerging-markets investing. Community operations.”
Skill 8: Operating under logistical, security, and infrastructure constraint
What it is in humanitarian work
Humanitarian work happens where infrastructure does not. The road is unreliable. The power is unreliable. The bandwidth is unreliable. The visas are uncertain. The security situation can change in an afternoon. You learn to plan for an environment where the plan is a starting point, not a contract — and to build operations that degrade gracefully rather than collapse when a single link fails.
The habit this produces is a particular kind of operational realism. You plan for the thing that usually happens, not the thing that should happen. You assume at least one of your inputs will fail, and you design around that. You build redundancy into the parts of the system that cannot fail, and tolerance for chaos into the parts that can.
How field experience solidifies it
You learn this by running a deployment where the satellite internet is down, the generator is low on fuel, and the survey is due tomorrow, and realising that the work still has to come out. You learn which decisions can be made over a weak voice connection and which cannot. You learn to write SOPs that a colleague can execute without you if your phone stops working.
How I applied it
At World Vision South Sudan, communications work during humanitarian emergencies meant producing media-ready outputs from an environment where many of the inputs — electricity, bandwidth, travel, access — could not be assumed. Facilitating field visits, arranging press conferences, and preparing press statements in that context required thinking through the operational chain in advance, because a missed link in the field could not be recovered from head office.
At REACH and IMPACT, running assessment cycles to schedule meant planning data collection in places where the logistical reality was its own constraint. Timely dissemination of situation overviews and factsheets to humanitarian partners and donors depended on operations that worked even when the conditions did not.
At DT Global and AECOM, managing reporting cycles across distributed field teams meant building in enough redundancy — templates, schedules, backups — that the monthly or quarterly cycle did not collapse when any one input was late.
The habit across all of it is the same: plan the work so that the work happens, in a world where the environment will not cooperate.
How it transfers to the private sector
This is the skill that early-stage companies, crypto protocols, and operations teams explicitly need and do not have a vocabulary for.
Startup operations is, at heart, the discipline of doing the work under constraint — not enough people, not enough systems, not enough time, and often not enough clarity about what the right work is. The humanitarian professional who has run a programme under far tighter constraint walks into a startup operations role with a settled relationship to scarcity that most private-sector professionals have to learn on the job.
Crypto operations, especially around incidents, has the same texture. When an exploit happens, the environment is not cooperative. Information is partial, systems are under stress, and the team has to coordinate a response that holds up regardless. The operational reflexes built by humanitarian emergency response translate directly.
In field operations for any company that operates physical infrastructure — logistics, energy, last-mile delivery, clinical trials, on-site services — the humanitarian toolbox applies almost unchanged. You are planning for an environment that resists the plan, and you are building systems that degrade gracefully.
In business continuity, disaster recovery, and resilience engineering, the explicit job is to design for failure. Humanitarians have been designing for failure as a default condition for decades.
Private-sector translation: “Startup operations. Field operations. Business continuity. Incident operations. Resilience engineering.”
Skill 9: Measurement thinking and closing the loop between publication and impact
What it is in humanitarian work
The humanitarian sector is a monitoring and evaluation culture. Every programme, every product, every report is expected to be connected to a theory of change — an argument for why producing this output will move the needle on a specified outcome, and a system for checking whether it actually does. Not every programme lives up to that standard, but the discipline is present in the air.
What this produces is a habit of mind: the reflex to ask, for any piece of work, “how will we know if this worked?” — and to build the answer to that question into the design of the work itself, not as an afterthought bolted on at the end.
How field experience solidifies it
You learn this by writing a beautiful report, publishing it, and then being asked three months later whether it changed anything — and realising that no one built the measurement layer that would let you answer honestly. You learn to build that layer from the start. You learn that outputs without tracked outcomes eventually lose the argument for their own existence, and that the teams that measure their own impact, honestly, are the teams that earn the room to keep doing the work.
How I applied it
At REACH, as Communications Manager, my role explicitly included contributing to monitoring and evaluation through regular tracking of how REACH’s products were being referenced and used, and providing that feedback back to the organisation. That is a closed loop between publication and impact — rare in the humanitarian sector, rarer still in the private sector.
At IMPACT Initiatives, producing SOPs for data collection was itself a form of measurement thinking — building the artefacts that would let future work be assessed against a consistent standard.
At AECOM, working under USAID’s OTCM standards meant operating inside a compliance environment that was fundamentally an M&E framework: activities were tracked against objectives, outputs against indicators, and the database of information was the scaffolding that made that measurement possible.
At Management Sciences for Health, the broader culture of USAID-funded health programming is saturated with measurement thinking — logframes, indicators, quarterly reviews — and working inside that culture for a sustained period reshapes the default question you bring to any piece of work: not “what are we doing?” but “what are we moving, and how will we know?”
How it transfers to the private sector
Measurement thinking is genuinely under-priced in the private sector, particularly in content, communications, and research functions.
In content strategy and content marketing, most teams produce material without a disciplined measurement layer — they measure traffic rather than decisions, impressions rather than behaviour change. A content lead arriving from a humanitarian background instinctively asks the question “what outcome is this output meant to move, and how will we track it?” That shift alone transforms a team.
In product analytics and growth work, the discipline is explicitly measurement — but the reflex to tie outputs to outcomes, to build the tracking before the launch, and to report honestly when the hypothesis did not survive contact with users is exactly the M&E reflex, ported to a new subject.
In research operations, the loop between what the research team publishes and what the organisation does with that research is almost always underbuilt. A researcher who has operated in a humanitarian M&E culture knows how to build that loop and why it matters.
In crypto investor-education work specifically, the question “did the educational content actually change behaviour, or did it just get read?” is one most teams never ask. The humanitarian M&E reflex is a direct upgrade.
In impact and sustainability functions — ESG reporting, impact investing, mission-aligned operating roles — the discipline is an explicit match. The humanitarian M&E toolkit is what the field is trying to import, usually without realising it has a decades-deep bench of practitioners trained in exactly this.
Private-sector translation: “Analytics. Measurement strategy. Impact measurement. Research ops. Content measurement. ESG and impact reporting.”
Skill 10: Visual storytelling and narrative craft
What it is in humanitarian work
Humanitarian communication is, in the end, storytelling. Numbers move donors. Stories move everyone else. The discipline that sits underneath successful humanitarian communication is the ability to find the human story inside a programme, render it with dignity, and carry it to audiences in a way that does not exploit the people it is about.
That is a craft. It involves a point of view about which stories are yours to tell and which are not, an editorial instinct for what belongs in the frame and what does not, and a working understanding of how narrative, image, and written copy combine into a finished product that holds together for a reader who is encountering the subject for the first time.
How field experience solidifies it
You learn this by producing a news feature where the photograph is more honest than the copy, and rewriting the copy until the two match. You learn to sit with a subject long enough to understand the story rather than long enough to extract a quote. You learn the difference between the story that is easy to tell and the story that is true. You learn to edit yourself out of the frame so that the subject can be seen clearly.
How I applied it
At World Vision, across two separate roles, the work involved producing news features, photographic reports, newsletters, and annual reports that carried humanitarian programming into audiences who had no direct contact with the people the programmes served. That was not a publishing pipeline bolted onto a programme. It was an editorial operation — choosing stories, shaping narratives, pairing images with copy, deciding what the reader needed to see first and what belonged deeper in the piece.
At AECOM, producing success stories for USAID’s Office of Transition and Conflict Mitigation was an exercise in the same craft, with a different audience and a tighter compliance frame. A success story is a short, finished narrative object. Writing a good one requires editorial judgment about what the story is actually about, not just what happened.
At Management Sciences for Health, shaping the Malaria Newsletter issue after issue was, among other things, an exercise in narrative curation across contributors — deciding which pieces belonged together in a given issue, how a section flowed into the next, and how the whole publication felt when read in sequence.
Across those roles, I was consistently producing finished communications products — not raw material for someone else to assemble, but work a reader could pick up, read end to end, and put down with a clear impression.
How it transfers to the private sector
Narrative craft is one of the most valuable and most misunderstood capabilities in the private sector, and it is chronically under-supplied.
In brand and marketing communications, the difference between a company that audiences trust and a company they tune out is almost entirely a narrative-craft problem. The companies that get this right have someone on the team who can shape a story, pair it with image and tone, and hold an editorial line across channels. The companies that get it wrong have a marketing team producing fragmented outputs without a shared voice. A humanitarian communicator who has shaped narratives across annual reports, newsletters, and feature stories has already done the reps.
In founder storytelling, investor storytelling, and executive communications, the work is to turn a company’s real history, decisions, and trade-offs into a narrative that outsiders can follow and trust. This is close kin to writing a programme’s story for a donor, and the discipline transfers cleanly.
In content marketing, documentary content, and long-form editorial, the capacity to produce finished pieces — not posts, but pieces — is in short supply. Most content teams produce in volume and under-invest in craft. A humanitarian editor arriving with fifteen years of finished-product discipline is, immediately, the most editorially mature person in most of those rooms.
In social impact communications, mission-aligned marketing, and public-interest media, the overlap is direct. The audiences are different, the subjects are different, but the craft is the same.
In crypto specifically, where most communication defaults to announcements, threads, and jargon, the teams that invest in narrative craft — the ones that treat a protocol launch as an editorial moment rather than a press release — are visibly ahead of the rest. A humanitarian storyteller walking into that environment arrives with a muscle most of the field does not yet have.
Private-sector translation: “Brand and editorial. Content marketing. Founder and executive storytelling. Documentary content. Mission-aligned marketing. Long-form editorial.”
Skill 11: Learning agility — acquiring new tools, vocabularies, and domains under working conditions
What it is in humanitarian work
Humanitarian communication is, at its core, a learning discipline. To do the job well you have to become functional — fast, and under working conditions — in technical domains you did not train in. A single month can require you to write credibly about malaria treatment protocols, WASH infrastructure, protection programming, food-security indicators, governance reform, and shelter standards. You are not pretending to be a doctor, an engineer, a social worker, a water technician, or a health economist. You are becoming competent enough to talk to one, understand what they are saying, and translate it for a reader who has none of that background.
That is one half of the learning agility the sector demands. The other half is tools. The craft of communication is in constant technical motion — cameras, phones, audio kits, video equipment, editing software, web publishing platforms, email systems, presentation tools, analytics dashboards, assessment software, data-collection tools, GIS systems — and a communications professional who cannot keep up with the tools is a communications professional who quietly loses range.
Put together, these two demands — learning technical vocabularies across expert disciplines, and learning and adopting the tools needed to do the work — produce one of the most underrated capabilities a humanitarian develops: the habit of learning into competence quickly, without waiting for a course.
How field experience solidifies it
You learn this by sitting across from a clinician who is explaining a treatment protocol, realising you do not have the background to follow it fully, and developing a working grasp of it quickly enough to write about it accurately by the end of the week. You learn to ask the question that gets the expert to explain their own field in a way that is usable. You learn the difference between understanding the jargon and understanding the underlying logic — and you learn that only the second one lets you write well about it.
On the tools side, you learn it by being handed a new camera, a new audio kit, a new editing environment, a new publishing platform, or a new data-collection tool, and being expected to produce finished work with it this week, not after a quarterly training. You learn to read documentation when you have to, watch a tutorial when that is faster, and lean on a colleague when that is the right call. The reflex that builds is the willingness to become functional in a new tool on short notice, without drama.
How I applied it
Across roles at World Vision, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, the work required becoming conversationally competent in a long list of technical domains — public health, epidemiology, malaria programming, WASH, protection, food security, conflict mitigation, governance, assessment methodology, GIS — and then translating that competence into writing that non-experts could read. The craft was not mastery of each field. It was the repeated exercise of closing the gap between an expert and a general reader, with enough rigour in the middle to be trusted by both.
On the tools side, communications work across those years ran across cameras and photographic production, audio and video, web publishing, presentation software, email systems, social platforms, data-collection tools, GIS outputs, and donor-compliance reporting systems. Each role required picking up whichever tools the job demanded and getting to usable output quickly.
The most decisive proof of learning agility, though, is the transition itself. Three years ago I moved from a field I had been building craft in for more than a decade into crypto — a domain with an entirely new technical vocabulary (tokenomics, consensus mechanisms, smart-contract architecture, custody, MEV, bridges, governance tokens), an entirely new tool set (block explorers, on-chain analytics, developer documentation, project tracking tools, QA and testing environments), and a working culture that is much closer to technology than to humanitarian operations. That shift was a real learning task, and it was executed in the role — while doing the work — rather than deferred to a training window.
How it transfers to the private sector
Learning agility is the skill that fast-moving companies hire for and cannot reliably identify.
In startups and scaleups, the job description changes faster than the job description gets updated. The contributors who thrive are the ones who can absorb a new responsibility, a new tool, or a new domain and become productive in it before the quarter ends. A humanitarian professional who has repeatedly become competent in a new technical field under deadline arrives with that habit already built.
In frontier domains — crypto, AI, biotech, climate tech, deep tech — the half-life of your technical knowledge is short and the premium on fast, disciplined learning is high. The professionals who succeed in these spaces are not the ones who arrived fully trained. They are the ones who can learn into competence in real time, on the job, while producing usable work. That is exactly the learning mode humanitarians have been practising for a decade.
In internal mobility at larger companies, the people who can move between product, research, marketing, operations, and strategy without starting over at each move are the people who compound most in value. The reflex to step into a new function and become functional quickly is the same reflex a humanitarian uses when a new emergency puts them into an unfamiliar sector.
In communications, brand, and content functions specifically, tool adoption is a continuous requirement — new publishing platforms, new analytics tools, new content management systems, new video and audio production stacks, new AI-assisted workflows. The humanitarian communicator who has absorbed camera, audio, video, editing, and publishing tools as the job evolved is already comfortable living in a toolset that keeps changing.
In research, analytics, and operations roles, working with a new data tool, a new dashboard, a new database, or a new research platform is a weekly occurrence. The humanitarian who has worked across Kobo, ODK, GIS systems, Excel, SPSS, donor reporting platforms, and document management systems is not going to struggle with Notion, Linear, Mixpanel, or Dune.
And in any role that sits at the boundary between experts and non-experts — developer relations, investor education, product marketing, policy communications, technical writing — the humanitarian reflex of learning a specialist’s domain well enough to translate it faithfully is exactly the muscle the job requires.
Private-sector translation: “Generalist operator. T-shaped contributor. Frontier-domain research. Internal mobility. Technical translator. Tooling-fluent communicator.”
Skill 12: Negotiation, diplomacy, and conflict resolution
What it is in humanitarian work
Coordination assumes that the parties in the room want the same outcome and only need alignment. Negotiation is what you do when they do not. In humanitarian settings, that is most of the time. Donors want visibility on a specific sector. Host governments want influence over what gets said publicly and what does not. Field teams want programming that fits the reality of the environment. Communities want voice and dignity. Implementing partners want credit. These interests are legitimate, and they do not always converge on their own.
The skill that emerges from working inside that environment is a quiet, practical kind of diplomacy. You learn to find the shape of an agreement that each party can defend inside its own institution, to name a disagreement honestly without inflaming it, and to choose the moment and the medium for a hard conversation so that the conversation can actually land.
How field experience solidifies it
You learn this by sitting in the meeting where two partners who share a mission are an hour into talking past each other, and working out — in real time, in writing, often by reframing a single sentence — a version of the conversation they can both accept. You learn that a successful negotiation rarely looks like a victory; it looks like a document each party is willing to sign.
How I applied it
Working across World Vision’s National Office, Regional Office, Support Offices, and Global Centre during emergencies, and alongside the Global Rapid Response Team, meant continually brokering between tiers of an organisation whose priorities were not identical. Working with MSH technical advisors, the Ministry of Health, and USAID on a joint Malaria Newsletter meant producing a publication each party could stand behind, without any of them feeling the product represented someone else’s programme. Across REACH, IMPACT, AECOM, and DT Global, engagement with donors, partner agencies, and government counterparts produced a steady, years-long apprenticeship in working out positions that multiple institutions could hold at once.
How it transfers to the private sector
Negotiation and diplomacy are near-universal private-sector currencies, and the humanitarian version is a particularly disciplined one because the stakes tend to be higher and the room for posturing tends to be lower.
In sales and partnerships, the core skill is finding the shape of a deal two institutions can defend internally. Humanitarian diplomats recognise that problem immediately. In ecosystem work — managing relationships with exchanges, custodians, regulators, co-investors, or portfolio companies — the craft of holding a relationship together across misaligned incentives is the exact humanitarian muscle. In vendor management, procurement, and enterprise deal work, the patience and editorial precision required to land an agreement are traits humanitarians practise as a default. In internal conflict — between product and engineering, between sales and operations, between research and leadership — the ability to name the disagreement cleanly and move the conversation towards a workable resolution is one of the most prized and most under-supplied capabilities in any company.
Private-sector translation: “Sales. Partnerships. BD. Procurement. Vendor management. Mediation. Policy and regulatory engagement.”
Skill 13: Project planning and project management
What it is in humanitarian work
Every communications and research task in the humanitarian sector is, underneath, a project. A sitrep has inputs, contributors, review steps, a deadline, and an audience. An assessment cycle has a scope, a team, a timeline, a budget, a set of deliverables, and a dissemination plan. A newsletter issue is a small production project with writers, editors, designers, contributors, and a publication date. An emergency response communications plan is a multi-workstream project executed under pressure. The work does not happen by itself. Someone has to plan it, staff it, sequence it, track it, and land it.
Project management in the humanitarian sector is not usually labelled “project management.” It is called programme coordination, communications planning, assessment implementation, reporting cycle management, response coordination. The underlying discipline is the same: defining scope, estimating effort, sequencing work, managing dependencies, tracking progress, adjusting when reality diverges from the plan, and delivering on time to stakeholders who will notice if you do not.
How field experience solidifies it
You learn this by running the same kinds of projects long enough to recognise the failure modes before they fail. You learn which contributors need reminding three days early and which need reminding three hours early. You learn that a deadline without a clear scope is not a deadline, that a scope without a clear owner is not a project, and that a project without a clear decision about what is in and what is out will consume far more effort than the work itself requires. You learn to build a simple plan that a team can actually follow, to resist the temptation to over-specify, and to adjust the plan honestly when the environment shifts rather than pretending the original plan is still in motion.
How I applied it
At REACH, the Assessment Officer role was explicit project management: contributing to research design, coordinating data collection across timelines, ensuring analysis and geo-referencing were completed to schedule, writing assessment reports, and coordinating their dissemination to humanitarian partners and donors on time. Each assessment cycle was a discrete project with defined outputs, a defined timeline, and defined stakeholders. At IMPACT Initiatives, the same discipline applied, extended by the work of producing SOPs that made the underlying projects repeatable.
At REACH as Communications Manager, developing and implementing the communications plan was an ongoing programme of projects — campaigns, product disseminations, presentation series — each with its own scope, contributors, timeline, and success criteria, running in parallel with the M&E discipline that tracked how those products were used after delivery.
At Management Sciences for Health, the Malaria Newsletter ran on a predictable cadence that required project management across every issue — commissioning contributions, editing, design, stakeholder approvals, publication, distribution. At AECOM, documenting projects under USAID OTCM standards meant operating inside a compliance-driven project framework end to end: activity tracking, progress reporting, outcome documentation, and the associated information flow.
At DT Global, the weekly, monthly, quarterly, and annual reporting cycles were themselves recurring projects — each with inputs, contributors, review steps, and a delivery deadline that could not move. At World Vision South Sudan, supporting communications during Level 3 emergency responses meant managing multiple workstreams at once — press statements, media inquiries, field visits, press conferences, internal briefings, support for regional and global teams — under time pressure, where project management was the difference between a coherent response and a scattered one.
Every single one of the communications and research tasks I have described in this essay was, in practice, a project that had to be planned and delivered. The skill is invisible when it is working, which is one reason it is under-credited.
How it transfers to the private sector
Project planning and project management is one of the most portable and most consistently in-demand skills in any private-sector environment.
In dedicated project and program management roles, the fit is immediate. Humanitarians who have run assessment cycles, reporting cadences, or emergency response comms plans are doing the same kind of work that a technical program manager does at a technology company — coordinating contributors across functions to land defined outputs on defined timelines. In agile product development, the rhythm of sprints, releases, and retrospectives is a shortened version of reporting cycles and assessment cycles, with tighter iteration and different language.
In marketing and communications planning, every campaign, every launch, every content calendar, every editorial production schedule is a project. Teams that do this well have someone on them who can plan a quarter’s worth of work, hold contributors to their commitments, and adjust gracefully when a piece of work takes longer than expected. Humanitarian communicators have been doing this for years.
In research operations, running a research programme — from study design through fieldwork, analysis, write-up, and dissemination — is the same loop as an assessment cycle. In consulting and client-services environments, the core unit of work is a project with a scope, a team, a timeline, and a deliverable — which is exactly the shape of humanitarian communications and research projects, with a different kind of client.
In crypto specifically, where I now work, almost everything the team does is a project: a research write-up on a new protocol, an investor education series, a market-research study, a product release with its communication wrap-around, a QA cycle, a developer workflow with a defined scope and timeline. The Nile Capital work relies on project management as a continuous discipline, and the muscle for it was built across reporting cycles at DT Global, assessment cycles at REACH and IMPACT, newsletter cycles at MSH, and emergency response communications at World Vision.
The deeper point is this. Project management is not a separate skill that sits alongside communications and research. It is the scaffolding that lets every communications and research task actually happen. A humanitarian who has done the work has already been the project manager on every task they have completed — and that is a capability the private sector pays for explicitly, often in roles dedicated to nothing else.
Private-sector translation: “Project management. Program management. Technical program management. Campaign management. Production management. Research operations. Client-services and consulting delivery.”
Skill 14: Professional ethics, safeguarding, and dignity in communication
What it is in humanitarian work
Humanitarian communication is, before it is anything else, an ethical practice. You are working with populations in their most vulnerable moments — displaced families, survivors of violence, women and children in crisis, communities under siege — and the question of how their stories are told, who has the right to tell them, and on what terms, is not an optional sensitivity layer on top of the craft. It is the craft.
The humanitarian sector has spent decades building an ethical framework around this — the humanitarian principles of humanity, impartiality, neutrality, and independence; the Do No Harm principle, which says the first test of any intervention is whether it makes things worse for the people it is supposed to help; safeguarding policies, which set explicit standards for how organisations and their staff treat the people they serve; child protection standards, which define how children are to be represented in communication, if at all; and informed-consent protocols, which require that the subjects of a story understand what they are agreeing to and retain the right to withdraw.
These are not abstract commitments. They are operational constraints on every piece of communication a humanitarian professional produces.
How field experience solidifies it
You learn this by sitting with a mother in a displacement camp, realising that her situation will move donors if you tell it a certain way, and choosing not to tell it that way because telling it that way is a kind of theft. You learn the difference between a story that honours its subject and a story that uses its subject. You learn to walk away from photographs that would work editorially and would cost the person in them something they did not agree to pay. You learn that a signed consent form is a starting point, not a permission slip, because the person signing it often cannot fully anticipate the afterlife of the image or the quote.
You also learn that ethics is not about saying no. It is about building the craft so that the answer is more often yes — yes to stories told with dignity, yes to photographs that strengthen rather than diminish the person in them, yes to communication that the subject would recognise as accurate and fair if they encountered it a year later.
How I applied it
Across roles with World Vision, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, the populations at the centre of the work were, in almost every case, people in structurally vulnerable situations — displaced families, women and children in humanitarian emergencies, communities affected by conflict, patients navigating fragile health systems. The professional ethics required to communicate about their lives honestly and safely was a daily discipline, not a policy document.
At World Vision South Sudan specifically — including during Level 3 Emergency Response communications alongside the Global Rapid Response Team — the work involved producing news features, photographic reports, and media content during active emergencies. Each product required an ethical judgement: whose story is this, who has consented to what, what is in the frame and what should not be, what protects the dignity of the subject and what does not, what is accurate and what is sensational, and what serves the audience’s understanding versus what merely serves the organisation’s visibility. Child protection standards in particular set non-negotiable limits on how children could be represented, and the discipline of working inside those limits shapes how you think about every other subject too.
At REACH and IMPACT Initiatives, the ethics extended into data. Research with affected populations required careful attention to how data was collected, how subjects were represented in outputs, and how findings were disseminated in a way that did not expose individuals or communities to further harm.
At MSH and AECOM, producing material about public-health programming and conflict-mitigation work involved a steady practice of deciding what was in the frame, what was not, and why.
The underlying reflex across all of this — always ask who this story belongs to, and whether the way you are telling it is a way the subject would endorse — is one of the most important things the humanitarian sector teaches, and one of the least visible on a CV.
How it transfers to the private sector
Professional ethics and safeguarding translate into a cluster of private-sector functions that are growing in importance and chronically under-staffed by people with the relevant instincts.
In trust and safety, content policy, and platform integrity, the core work is deciding what a platform will and will not host, how vulnerable users are protected, how bad actors are identified and removed, and how the rules are written and applied. Humanitarians who have spent years making judgement calls about representation and harm are strong candidates for this work, because they arrive with an ethical framework already in place.
In responsible AI, AI safety, and model policy work, questions about harm, consent, representation, and power are the central questions of the field. A humanitarian communicator who has worked through Do No Harm as a daily practice is asking the same kinds of questions these teams are asking, with years more practice at answering them.
In privacy, data protection, and data governance, the humanitarian instinct for protecting data about vulnerable populations maps almost unchanged onto corporate privacy programmes — GDPR compliance, data-minimisation reviews, consent architecture, data-retention policies.
In research ethics — user research, clinical-adjacent research, sensitive-subject research — the frameworks humanitarians work inside (informed consent, minimising harm, accurate representation) are the same frameworks research ethics boards and IRBs apply. A humanitarian researcher is already operating inside this discipline.
In brand integrity and marketing ethics, the question of how a company represents its customers, its communities, and the people whose stories it uses in marketing is increasingly consequential. A humanitarian communicator brings an instinct for dignity and consent that brand teams rarely have on staff.
In crypto specifically, where I work now, user safety and ethical communication are direct responsibilities — communicating accurately about risk, not sensationalising markets, not using fear to drive engagement, protecting users from content that pushes them into decisions they do not fully understand, and treating the new investor with the same respect a humanitarian communicator would bring to any audience that did not have full context. Investor education done with humanitarian ethics in the room is a measurably different product from investor education done without it.
And in ESG, sustainability, and corporate responsibility functions, the humanitarian framework is directly relevant — not as soft advocacy, but as practical governance.
Private-sector translation: “Trust and safety. Responsible AI. Privacy and data governance. Research ethics. Brand integrity. User safety. ESG and corporate responsibility.”
Skill 15: Theoretical grounding in communications — frameworks that shape how stories get told
What it is in humanitarian work
Good communication is not instinct. It is craft sitting on top of a body of theory that shapes, often invisibly, every editorial choice a communicator makes. How an issue is framed, which story leads, what goes in the first image and what does not, how information is sequenced, which audiences are addressed in which register, what is said explicitly and what is left to inference — these decisions are made better when the communicator understands the theoretical frameworks that describe how communication actually works on the human beings on the other end of it.
Humanitarian communication draws on a wide intellectual base. Framing theory, which describes how the way an issue is presented shapes how it is understood and acted on. Agenda-setting theory, which describes how media attention influences which issues the public treats as important. Narrative theory and narrative transportation, which describe how stories move people differently from data. Diffusion of innovations, which shapes how new public-health practices or behaviours move through populations. Social and behaviour change communication, which underlies a large share of humanitarian health and protection work. Participatory communication and communication for development, which place affected populations as authors of their own story rather than subjects of it. Visual rhetoric and semiotics, which describe how images carry meaning. Audience theory, uses and gratifications, and persuasion models, which describe how different audiences engage with different kinds of material. Crisis communication theory, which describes how organisations and audiences behave when the story is out of anyone’s control.
A humanitarian communicator who has worked across multiple organisations, multiple emergencies, and multiple sectors has usually been inside several of these frameworks in practice, whether they used the academic terms or not. The theoretical grounding is what lets you recognise, when you are editing a piece, why one version works and another does not — and to make the next piece stronger because of it.
How field experience solidifies it
You learn this by choosing a frame for a story, watching the story land a particular way, and observing the connection between the framing decision and the outcome. You learn that a headline built around loss performs differently from a headline built around resilience, and that the choice is not neutral. You learn that a story told from a first-person subject’s perspective is received differently from a story told about them in the third person. You learn that the opening image of a piece sets the frame more durably than any sentence that follows. Over years, these observations accumulate into a working theoretical model — one that is richer than any textbook treatment because it has been calibrated against real audiences responding to real stories.
How I applied it
At World Vision, producing news features, photographic reports, and annual reports about complex humanitarian emergencies required constant framing decisions — which stories led, which subjects were visible, which emotional register was used, and how the work of the organisation was positioned relative to the agency of the communities it served. Each decision drew, implicitly or explicitly, on framing theory, narrative theory, and participatory-communication principles.
At Management Sciences for Health, working on a malaria programme meant operating inside a field that has been shaped for decades by social and behaviour change communication — how messages reach caregivers, how trusted sources influence treatment-seeking behaviour, how materials are designed for literacy levels, language, and cultural context. The Malaria Newsletter sat inside that broader theoretical ecosystem.
At AECOM, producing success stories for USAID’s Office of Transition and Conflict Mitigation meant working inside a framing tradition specific to conflict-mitigation communication — where the choice of frame carries political weight, and where the difference between a “stabilisation” framing and a “peacebuilding” framing can change how a programme is understood upstream and downstream.
At REACH and IMPACT, research communications lived at the intersection of evidence and narrative — where the theoretical question of how to communicate findings honestly and usefully, without over-framing the evidence, is a daily practical question.
At World Vision again, during Level 3 responses, crisis communication theory was operationally present: the arc of how an emergency story enters public attention, how it moves through cycles, how an organisation’s communication posture shifts across those cycles, and how audiences shift their own engagement with the story over time.
Across all of these roles, the practical outcome of theoretical grounding was a quieter and more disciplined editorial voice — one that resisted sensationalism, kept the subject at the centre of the story, and understood why a particular editorial choice was being made, not just that it felt right.
How it transfers to the private sector
Theoretical grounding in communications is one of the most quietly valuable skills a humanitarian professional can carry into the private sector, because most private-sector communications work is done by people who are craft-fluent but theory-light.
In brand strategy, the central task is to build and maintain a consistent framing of the company across every surface the audience encounters. Teams that do this well have at least one person who is thinking in framing-theory terms, even if the vocabulary is different. A humanitarian communicator arrives with that vocabulary and with years of practice applying it.
In content strategy and editorial leadership, the ability to design a content programme around a coherent theory of audience and message — rather than around whichever topic is trending that week — is the difference between a content function that compounds and one that dissipates. Audience theory, uses-and-gratifications thinking, and narrative theory are all directly applicable here.
In growth and behavioural product work, social and behaviour change communication is a near-direct ancestor of what product teams now call behavioural design and growth experimentation. The humanitarian practitioner who has worked on SBCC interventions has been doing behavioural work with far higher stakes than most growth teams have ever faced.
In public policy and issue advocacy, framing and agenda-setting theory are the core disciplines of the field. Teams working on AI policy, climate policy, financial-regulation policy, or technology policy rely on exactly these frameworks to shape how their issues are understood.
In investor relations and corporate narrative, the question of how a company is framed — story of growth versus story of resilience, story of innovation versus story of reliability — is a framing-theory question, applied to a financial audience.
In crypto communications specifically, where I now work, the theoretical grounding shows up in several places. How a protocol’s story is framed to users. How risk is communicated without sensationalising it. How educational content is structured to reach non-expert audiences without condescension. How a launch is positioned relative to the broader narrative of the space. How an incident is communicated when the story is temporarily out of the team’s control. Each of these is a theoretical choice, whether the team making it recognises that or not — and a communicator with the grounding makes those choices with more intention and fewer accidents.
The point is not that a humanitarian communicator arrives able to lecture the team on McCombs and Shaw or Entman. It is that they arrive with a mental model of how communication actually works — what frames do, how audiences receive, why some stories travel and others do not — and that mental model quietly improves the team’s work every week it is applied.
Private-sector translation: “Brand strategy. Editorial and content strategy. Behavioural design. Policy and advocacy communications. Investor relations. Crisis communications strategy. Narrative strategy.”
Skill 16: Systems literacy — the political economy of humanitarian and development work
What it is in humanitarian work
Humanitarian and development work does not happen in a vacuum. It happens inside a dense, historically accumulated architecture of institutions, funding flows, policy frameworks, and political relationships — and a professional who works in this space for any length of time ends up carrying a mental map of how the whole system fits together.
That map includes the United Nations system and its constellation of agencies — OCHA as the coordination spine, UNHCR on refugees and displacement, UNICEF on children, WHO on health, WFP on food, UNDP on development, FAO on food security, and the humanitarian cluster system that organises operational response across sectors. It includes the Inter-Agency Standing Committee, the Humanitarian Response Plans, the Consolidated Appeals, and the logic of pooled funds. It includes the Red Cross and Red Crescent Movement — the ICRC, the IFRC, and the national societies — and the distinctive legal and ethical position they occupy in international humanitarian law. It includes the major donor governments and their bilateral agencies: USAID, ECHO, FCDO, GIZ, SIDA, DFAT, JICA, and others, each with their own doctrines, priorities, compliance frameworks, and political pressures. It includes international non-governmental organisations — World Vision, Save the Children, Oxfam, IRC, MSF, and dozens of others — and the layered relationships those INGOs hold with local and national NGOs, host governments, and affected communities. It includes private foundations and increasingly consequential philanthropic actors. And it includes the political systems of host countries — the ministries, the civil-military relationships, the local governance structures, the informal power brokers — whose decisions shape what is actually possible in any given context.
Around all of this sits a body of development and humanitarian theory and policy: debates about aid effectiveness, localisation, the humanitarian-development-peace nexus, the participation revolution, anti-corruption frameworks, human-rights-based programming, gender-transformative approaches, the Sustainable Development Goals, and the longer intellectual history running through modernisation theory, dependency theory, capabilities approaches, and post-development critique.
A humanitarian professional does not work from inside this system without absorbing it. Even without a formal IR or development-studies background, the sector teaches systems literacy the way the sector teaches everything else — through repetition, through consequence, and through the steady, years-long experience of watching decisions in one part of the system produce outcomes in another.
How field experience solidifies it
You learn this by watching a funding shift in Washington change what a country programme can deliver in Juba within months. You learn it by watching a policy paper published in Geneva rewrite the approach of a cluster in a country where that paper will never be read in its original form. You learn it by watching a national government’s political calculus quietly reshape what an INGO can say publicly. You learn it by watching the same crisis produce different operational responses across agencies because of different institutional mandates and different donor relationships. Over time, you stop seeing a single humanitarian operation and start seeing the system of institutions, incentives, and power relationships that produced it.
How I applied it
Across roles at World Vision, AECOM, Management Sciences for Health, DT Global, REACH, and IMPACT Initiatives, the work sat inside this system, and every communications and research output depended on reading it correctly.
At AECOM, working under USAID’s Office of Transition and Conflict Mitigation meant operating inside a specific corner of the US foreign-assistance architecture — a corner with its own doctrine, its own political visibility, its own compliance standards, and its own relationship to broader US policy. Communications that did not understand that context produced outputs that landed badly. Communications that did understand it produced outputs that travelled.
At Management Sciences for Health, working on malaria programming meant operating inside the global health architecture — Global Fund, PMI, WHO, national Ministries of Health, and the wider ecosystem of public-health donors and implementers. The Malaria Newsletter was not a neutral publication. It sat inside a system of actors whose interests and vocabularies it had to respect.
At DT Global in South Sudan, contributing to reporting across weekly, monthly, quarterly, and annual cycles meant producing material that would be read not just by the Deputy Chief of Party and Senior Technical Advisor, but — up the chain — by donor counterparts whose decisions would shape the programme’s future. The reporting had to understand that audience.
At REACH and IMPACT Initiatives, coordinating with HQs in Geneva, with country teams, with the GIS team, and with humanitarian partners and donors meant operating inside the humanitarian information architecture — the Humanitarian Needs Overviews, the Humanitarian Response Plans, the cluster system, the evidence base that humanitarian operational decisions rest on. The research products were inputs into that system, and producing them well required understanding the system they were feeding.
At World Vision South Sudan, serving as a communications focal point connecting the National Office with the Regional Office, Support Offices, and Global Centre — and collaborating with the Global Rapid Response Team during Level 3 Emergency Responses — was a sustained exercise in working inside a large INGO’s internal political economy, while the organisation itself operated inside the broader humanitarian system and the particular political reality of South Sudan.
Across all of this, the habit that compounds is the reflex to ask, for any decision, “what is the wider system this sits inside, and what does that system reward, resist, or require?”
How it transfers to the private sector
Systems literacy is a quietly decisive skill in any private-sector role where the organisation does not operate in isolation — which is almost all of them.
In public policy and government affairs, the fundamental requirement is the ability to read the institutional landscape the company operates inside — regulators, legislators, agencies, courts, industry associations, civil-society actors, the press. A humanitarian professional who has mapped the UN system, donor architecture, and national political systems for a living has already built that muscle at a far larger scale than most corporate public-affairs teams operate at.
In international expansion and emerging-markets operations, understanding the political, regulatory, and institutional context of a new market is the difference between expansion that compounds and expansion that stalls. Humanitarians who have worked across fragile and emerging environments arrive with calibrated instincts for these contexts that most private-sector operators do not have.
In geopolitical risk and strategic intelligence — now a first-class function at serious companies — the job is to read how political, economic, and institutional shifts in one part of the world will reshape operating conditions in another. That is the exact reflex a humanitarian professional develops as a side effect of the job.
In ESG, impact investing, and mission-aligned business, the institutional ecosystem of the work — development-finance institutions, multilaterals, philanthropic capital, UN frameworks — is directly continuous with the one humanitarians operate inside, and a humanitarian arrives already fluent in it.
In crypto and Web3 specifically, where I now work, the industry is undergoing a rapid encounter with the broader institutional world it used to pretend it was outside — regulators, central banks, international standards bodies, national governments, and the long-running debates in financial and development policy about inclusion, surveillance, sovereignty, and access. A communicator or researcher who can read that institutional context — who can situate a stablecoin regulation inside the history of financial-policy debates, or a crypto-for-remittances narrative inside the real architecture of cross-border flows — produces better, more durable work than one who cannot.
In consulting, strategy, and corporate development roles, the ability to read the wider system a client or acquisition target operates inside is, in practice, what senior strategists are being paid for. Humanitarians who have operated as working analysts inside one of the largest and most complex institutional systems on earth arrive with that analytical muscle already built.
The deeper point is that systems literacy is almost always learned by working inside a system, not by studying it. The humanitarian sector is, accidentally, one of the best places on earth to acquire the reflex.
Private-sector translation: “Public policy. Government affairs. Geopolitical risk. International expansion. Emerging markets. ESG and impact investing. Strategy. Corporate development. Regulatory affairs.”
Skill 17: Developing and owning a communications strategy that supports the whole organisation
What it is in humanitarian work
There is a meaningful step up from producing communications products to owning a communications strategy. Producing communications is the craft of executing against a brief. Owning a strategy is the work of deciding, at the organisational level, what the communications function exists to do, who it exists to serve, where its capacity should sit, and how it should connect with every other part of the organisation that depends on it.
A communications strategy, done properly, starts with the organisation’s objectives — what it is trying to achieve over the next year or three — and works backwards to the communications choices that will support those objectives. It maps the audiences the organisation needs to reach. It names the messages that matter and the ones that do not. It designs the channels and cadences the function will use. It decides which sectors and programmes inside the organisation receive which kinds of communications support. It sets the standards and the editorial line the whole organisation will be held to. And it builds the mechanisms — working groups, planning cycles, review structures, feedback loops — that keep communications aligned with programmes as both evolve.
The underlying skill is consultative and architectural. You are not the author of every output; you are the person who decides what outputs the organisation should be producing, which ones it should stop producing, and how the function should be organised to support everyone who needs it.
How field experience solidifies it
You learn this by sitting down with programme leads across an organisation, one by one, asking them what they need to communicate, to whom, and for what purpose — and then looking at the answers as a whole and seeing where the pattern is. You learn that every programme head believes their work should be the communications priority of the organisation, and that the communications strategist’s job is to hold the whole picture and decide, fairly, where effort actually goes. You learn to separate the communications requests that are well-formed from the ones that are really programme problems in disguise, and to address each appropriately. You learn that a communications strategy that is not budgeted, staffed, and sequenced is not a strategy — it is a wish list.
How I applied it
At REACH, as Communications Manager, I developed and implemented the organisation’s communications plan — not as a document that sat on a shelf, but as a working strategy that shaped what the external communications function actually produced, how it connected to the research programmes it supported, and how its outputs were tracked and evaluated once they were in the world. That work required ongoing engagement with research teams across the organisation, understanding what each team needed to communicate, to whom, and why, and translating those needs into web articles, product dissemination emails, presentations, and an editorial calendar the whole organisation could rely on.
At World Vision South Sudan, serving as a strategic link and focal point for National Office communications, connecting the Regional Office, Support Offices, and the Global Centre, was functionally a strategy role as much as an execution role. The job was to hold the communications architecture of a national office together — across sectors, across regional tiers, across emergency and non-emergency periods — in a way that served every part of the organisation that depended on it.
At Management Sciences for Health, working with technical advisors, the Ministry of Health, and USAID to produce the Malaria Newsletter was a sustained exercise in understanding the communications needs of different sectors within and around the programme — epidemiology, treatment, case management, health-systems strengthening, policy — and designing a publication that supported each of them without becoming fragmented. The strategic choice was where to sit on the editorial line: technical enough for specialists to take seriously, accessible enough for generalist audiences to use.
At AECOM, working under USAID OTCM’s standards across a distributed field operation meant engaging with Regional Program Managers and Program Officers to understand what each part of the programme needed to communicate about its work, and producing information sheets, success stories, press releases, and reports that supported all of them inside a consistent framework.
Across these roles, the skill underneath the work was always the same: treating the rest of the organisation as the internal client of the communications function, building the relationships needed to understand what each part of it actually required, and designing a strategy that supported the whole rather than any single piece.
How it transfers to the private sector
This is a direct match to several senior private-sector functions, most of which are explicitly hiring for exactly this capability and routinely hiring badly.
In corporate communications leadership — Head of Communications, VP Communications, CCO — the job is to develop and own the organisation’s communications strategy, align it with the business strategy, and build the function that supports every department that depends on communications. A humanitarian communications manager who has already done this at organisational scale, under harder conditions, is walking into a role whose core work they have been practising for years.
In internal communications, the central requirement is to understand what each function inside the company needs communicated — to employees, to leadership, across offices — and to design the internal-comms programme that serves them all. The humanitarian discipline of engaging sectors across an organisation to understand their needs is the same discipline, applied to an internal audience.
In content strategy and editorial leadership at scale, the role is to build and maintain an editorial programme that serves multiple internal stakeholders — marketing, product, sales, research, executive — without fragmenting under the weight of competing priorities. That is exactly the humanitarian communications strategist’s problem.
In brand strategy and brand management, owning the company’s external voice and ensuring every team that communicates under it is supported, aligned, and held to a consistent standard is the same architectural work, with a commercial frame around it.
In product marketing leadership, the job of understanding what each product team needs to communicate to the market, and building the marketing function that supports all of them, is a version of the same problem — and humanitarian strategists who have supported multiple programmes across an organisation arrive with the relevant instincts.
In public relations and agency-side strategy, the work of sitting with clients to understand their communications needs, then designing a strategy and a production plan to meet them, is structurally identical. Agencies are chronically short of senior strategists who can do this well.
In crypto and technology organisations specifically, where communications is frequently organised as a set of disconnected outputs rather than as a strategy — a podcast here, a Twitter presence there, a blog somewhere else, a newsletter with no clear audience — the discipline of owning a real strategy, sitting with every internal sector to understand its needs, and building a coherent programme that supports the whole organisation is one of the highest-leverage improvements a company can make. The humanitarian communications strategist walks into that work with the exact muscle the company is missing.
The point that is worth holding on to is this. Most private-sector communications teams are not short of talented writers. They are short of senior professionals who can own a strategy, engage with the rest of the organisation as an internal client, and build the function that serves the whole business. Humanitarians who have done this work at REACH, at INGOs like World Vision, or inside USAID-funded programmes have been doing precisely that — usually without calling it strategy, and often without the pay grade that would accompany the same work in the private sector.
Private-sector translation: “Head of Communications. VP Communications. Chief Communications Officer. Internal communications leadership. Content strategy leadership. Brand strategy. Product marketing leadership. Agency strategy.”
Skill 18: Local context literacy and the informal ambassador role
What it is in humanitarian work
Every humanitarian operation runs on a layer of work that rarely appears in a job description and is almost never formally titled. It is the ongoing task of understanding the local context an organisation is operating in — the political economy of the area, the formal and informal power structures, the traditional authorities, the youth associations, the women’s groups, the religious leaders, the community elders, the local media, the local businesses, the host-community-to-displaced-community dynamics — and using that understanding to represent the organisation well in the places where its official representatives are not present.
A humanitarian staff member working in this layer is, in practice, an ambassador for their organisation. Not in any appointed sense. In the sense that every conversation they have in a market, at a community meeting, in a church or a mosque, at a chief’s compound, with a youth group, with a women’s committee, or on the radio carries the organisation’s name with it. The reputation of the organisation inside the community is being built, maintained, or damaged in those conversations. And a well-functioning humanitarian staff member learns, early, that they are not a neutral observer in those interactions. They are part of how the community decides whether the organisation deserves its trust.
This role layers on top of the formal job. The person holds it because they have the local fluency to do so, not because they were hired for it explicitly. And the quality with which they do it shapes, over time, whether the organisation is welcomed, tolerated, or resisted in the places it is trying to work.
How field experience solidifies it
You learn this by spending time, over years, with local stakeholders who are not part of any formal coordination mechanism — traditional leaders, youth groups, women’s groups, teachers, church and mosque leaders, local journalists — and developing a working sense of the power relationships and histories that shape what happens in an area. You learn that a meeting with a county commissioner is one layer of a conversation; a meeting with a paramount chief is another layer; a meeting with a women’s association leader is a third; and the organisation only operates well when all three layers are understood.
You learn that arriving in a community with a project plan is not the same as being welcomed. You learn that a rushed or disrespectful interaction with a local leader at the start of an engagement can shape what happens six months later in ways that no communications output can repair. You learn that a thoughtful and patient engagement early — sitting, listening, acknowledging, asking the right elders the right questions — creates a foundation that the rest of the work can actually stand on.
And you learn that your personal conduct matters. You are not just representing yourself. You are the organisation’s face in any room you are in, and the community will remember you long after the project cycle ends.
How I applied it
Across roles in South Sudan — at World Vision, DT Global, and with AECOM under USAID’s OTCM programme — the work depended on the ability to operate with fluency in local context. Communications during humanitarian emergencies, media engagement, field visits, assessment work, and project documentation all happened inside communities whose political, cultural, and social structures had to be respected and understood for the work to be possible.
At World Vision South Sudan specifically, representing the organisation in communities during Level 3 emergency responses required the informal-ambassador posture the work demands. You cannot walk into a displacement site and produce honest, dignified communication about the people there without first doing the relational work — with the camp leadership, with the traditional authorities operating inside the camp, with the women’s groups organising water points and food distribution, with the youth associations, with the local administration, and often with religious leaders whose influence over how an intervention is received is substantial. That relational work is not the story; it is the precondition for any honest story being possible.
At AECOM, working under USAID OTCM’s conflict-mitigation programming, the local-context layer was explicitly part of the operating logic. The work was about strengthening social cohesion in fragile environments, which meant operating alongside local leaders — traditional, political, religious, and civic — whose authority shaped whether a project landed well or did not. Documenting projects, organising materials, and producing the information sheets, success stories, and reports that USAID and the wider public saw meant consistently operating inside an environment where the organisation’s reputation was being built in real time through the conduct of its staff.
At REACH and IMPACT, assessment work required engaging local communities as respected sources of information, not as passive subjects. The quality of the assessment depended on the quality of the engagement, and the quality of the engagement depended on whether the team was willing to do the context work — understanding who the relevant local actors were, how to approach them, who should not be skipped, and who should not be centred at others’ expense.
At Management Sciences for Health, producing the Malaria Newsletter and supporting malaria programming inside Ministry of Health and USAID frameworks meant operating across national and local health systems, working with local Ministry of Health officials, community health workers, and traditional actors in health-seeking behaviour. The communications function was not separate from that ecosystem. It sat inside it.
Across all of these roles, the informal-ambassador layer was present continuously. No one formally designated me as the organisation’s face in any of those contexts. The role emerged from the nature of the work — from being on the ground, in the rooms, with the local stakeholders who formed the organisation’s real social license to operate.
How it transfers to the private sector
This is one of the most quietly valuable skills a humanitarian professional can bring into the private sector, because most private-sector organisations are discovering — often painfully — that they cannot operate in complex local environments without exactly this capability.
In community relations and stakeholder engagement, which every company operating physical infrastructure or sensitive services eventually builds a function around, the core skill is the local-context literacy a humanitarian carries. Mining companies, energy companies, telecoms operators, logistics companies, last-mile delivery companies, fintech platforms operating in emerging markets, and agribusinesses all depend on the quality of their relationships with local communities. The companies that do this well have someone on staff who understands the difference between a county commissioner, a paramount chief, and a women’s association leader, and treats each appropriately. Humanitarian professionals are trained in this.
In corporate social responsibility, social performance, and social license to operate — increasingly serious functions in resource-dependent industries — the humanitarian skill set maps almost unchanged. Designing interventions that communities welcome rather than resent, engaging local stakeholders as partners rather than as beneficiaries, and building reputational capital with local authorities is work humanitarians have been doing for decades.
In emerging-markets expansion and field operations, companies that enter new markets without someone who can read local context burn an enormous amount of money reinventing lessons the humanitarian sector has long since learned. A humanitarian professional arriving into a country manager, head of operations, or community lead role in a new market arrives with most of the necessary instincts already in place.
In government affairs and public affairs at the sub-national level, the relationships with local administrators, councillors, traditional leaders, and community organisations are often the determining variable in whether a project gets approved, blocked, or stalled. Humanitarians have usually built the relational muscle for this long before the private-sector public-affairs function has any experience of operating at that altitude.
In community management and community operations in crypto and technology — a function that companies now hire for heavily — the informal-ambassador role humanitarians know so well translates with very little adjustment. A protocol’s reputation inside its user community, its contributor community, and its developer community is being built in every interaction the core team has, and the people who do this well are the ones who understand they are always on duty as ambassadors. That is a posture humanitarians already hold.
In ESG, impact investing, and mission-aligned operating roles, the capacity to operate in local contexts with respect, patience, and authentic engagement is, increasingly, a competitive edge rather than a soft skill. Humanitarians arrive with that edge as their default operating mode.
In trust and reputation functions more broadly, the reflex to treat every interaction as a reputation-building moment, rather than as a transaction, is a mindset private-sector organisations struggle to instil. Humanitarians carry it as a working habit.
The deeper point is this. In any environment where the organisation’s social license to operate is contested, earned, or otherwise non-automatic, a humanitarian professional who has done this work in some of the most demanding local contexts on earth is a disproportionately valuable hire. They have practised the informal ambassador role — without the title, without the training budget, and without the clean organisational boundaries the private sector assumes — for years. In the private sector, the same posture, applied with the same patience, tends to quietly transform how an organisation is received.
Private-sector translation: “Community relations. Stakeholder engagement. Corporate social responsibility. Social license to operate. Country manager and emerging-markets operations. Community management. Public affairs at sub-national level. Trust and reputation.”
Skill 19: The generalist’s burden — knowing the whole organisation while mastering your own craft, under visibility most roles do not carry
What it is in humanitarian work
This is the most overlooked skill in humanitarian communications and one of the hardest to name cleanly, because it is not a technique — it is a condition of the job.
A humanitarian communications professional is expected, at any given moment, to know the whole organisation. What every programme is doing, what each one has recently achieved, what each one is currently struggling with, what each donor is funding, what the policy position of the organisation is on any live issue, what a senior leader said in a meeting last week, what is appropriate to say externally today and what is not, what the legal and safeguarding lines are around any given story, and what is happening in the wider sector that might inflect any of it. You are expected to hold this picture in your head continuously — and at the same time, to be excellent at the specific craft of communications itself.
That is the jack-of-all-trades-and-master-of-one shape of the role. Generalist breadth is not a nice-to-have; it is a working requirement. And it comes with a second requirement that is rarely made explicit: an unusually high visibility, where your mistakes are public, your outputs are scrutinised by many audiences at once — staff, leadership, donors, partners, host governments, journalists, affected communities — and the cost of a single error can be out of all proportion to the size of the role that produced it.
A programme officer who miscalculates a budget line by five percent makes a contained mistake. A communications professional who mis-words a statement, mis-frames a story, or publishes the wrong photograph can create a reputational, legal, or safeguarding incident that the organisation spends months recovering from. The work is high-leverage in both directions. The best outputs disproportionately elevate the organisation. The worst ones disproportionately damage it.
The skill, held steadily over years, is the capacity to keep the whole picture in your head, remain excellent at the craft, and operate under that visibility without letting the pressure degrade the judgement.
How field experience solidifies it
You learn this by being the person everyone in the organisation expects to already know things you have not been formally briefed on — because you are the communications person, and the assumption is that the communications person knows. You learn to build the habits that make that expectation survivable: paying attention in meetings that are technically not yours, reading the documents that are technically not your responsibility, knowing where every department keeps its current information, and keeping the map up to date in your own head without being asked.
You learn that the visibility of the role is not negotiable. A statement you wrote at three in the morning will be read by people you have never met. A photograph you approved will appear in places you cannot retract it from. A paragraph you edited for a report may be quoted at a donor meeting you will never attend. The reflex this produces is not fear; it is a working care. You write and edit as if every output is going to be read by the most informed and the most hostile reader you can imagine, because sooner or later, it will be.
And you learn that the mistakes, when they happen, are not hidden. They are absorbed. The culture of the role is that you own them, correct them cleanly, and absorb the lesson into how you work — because the alternative is to deflect, which costs the organisation more than the original mistake.
How I applied it
This condition was present in every role I have held.
At World Vision South Sudan, being the strategic link for National Office communications across the Regional Office, Support Offices, and Global Centre required holding a continuously-updated mental model of the organisation’s programmes, emergencies, staffing changes, donor relationships, political exposures, and communications posture, across sectors I was not running. During Level 3 Emergency Responses, the visibility intensified — statements, press inquiries, and field visits happened fast, and every output carried organisational weight. The role required both breadth (knowing the whole operation) and craft (producing media-ready communications under time pressure), and it required both simultaneously.
At Management Sciences for Health, producing the Malaria Newsletter meant knowing the technical work of epidemiologists, treatment specialists, health-systems advisors, and policy leads well enough to edit their material accurately — while also holding the donor relationship with USAID, the partnership with the Ministry of Health, and the wider context of the programme in mind with every editorial choice. No single issue of the newsletter was a narrow-craft exercise. It was a breadth-plus-craft exercise under scrutiny.
At AECOM, working under USAID OTCM’s compliance framework meant operating under a form of institutional visibility where every output was evaluated against the donor’s standards. The room for drift was small, and the cost of a mistake was not only reputational but compliance-driven — USAID expectations did not forgive vague, inaccurate, or off-message outputs.
At REACH, as both Assessment Officer and later Communications Manager, the breadth requirement was continuous: holding the research programmes, the country team’s priorities, the Geneva HQ’s expectations, and the partner and donor audiences in mind across every output. And the visibility was real — REACH’s outputs were read by humanitarian decision-makers and donors whose operational choices rested on the trustworthiness of the material.
At IMPACT Initiatives, producing SOPs and research outputs carried the same condition, with the additional weight of documents that would shape how work was done by colleagues who had never worked with me directly.
At DT Global, producing reporting across weekly, monthly, quarterly, and annual cycles meant holding the project’s entire activity picture in mind and turning it into reports that would be read up the chain to the Deputy Chief of Party, Senior Technical Advisor, and beyond, into donor reviews where any inaccuracy would be noticed.
Across all of these roles, the generalist’s burden was constant. Being the communications person meant being the one who was expected to know everything about the organisation, hold the standard of the craft higher than almost anyone else, and carry the cost of visibility as part of the job description.
How it transfers to the private sector
This is one of the most underrated transfers and one of the most relevant to modern private-sector work.
In chief-of-staff roles, the expectation is exactly this: hold the entire organisation in your head, across every function, and remain operationally useful to the principal at any moment on any issue. Humanitarian communications professionals who have held the equivalent position inside their own organisations arrive with the muscle already built.
In executive communications and CEO speechwriting, the role requires knowing the business end to end well enough to represent it accurately in the principal’s voice, while remaining a disciplined writer and editor. Breadth and craft at the same time. The humanitarian analogue is the communications focal point preparing country directors and regional comms teams — the same shape of work.
In founder and executive offices at scale, where one person is expected to follow product, engineering, design, sales, finance, legal, and public affairs well enough to draft memos, handle press moments, and brief the executive — the role is structurally a humanitarian communications role with a different vocabulary.
In corporate communications leadership, the job carries both the breadth requirement (know the company end to end) and the visibility requirement (every output is scrutinised, every mistake compounds) that humanitarians already operate under. Leaders who cannot hold both collapse the function. Leaders who can hold both compound the company’s reputation every year they are in the seat.
In crisis and incident leadership, the role requires knowing every function well enough to coordinate a coherent response, holding a craft standard on the external messaging, and remaining calm under a visibility spike most staff never experience. Humanitarian emergency communicators have been doing this work at the higher-stakes end of the spectrum.
In investor relations and board communications, the breadth-plus-craft-plus-visibility pattern is the full shape of the work. The humanitarian pattern-match is direct.
And in smaller, earlier-stage environments — startups, early-stage crypto teams, founding teams — the generalist-plus-master shape is often what the first communications hire needs to be, because the organisation cannot yet afford a specialised function. Humanitarian communicators, used to holding breadth and craft at the same time under high visibility, are among the best candidates for this shape of role and are chronically undervalued in it.
The deeper point is this. Private-sector organisations often separate breadth from craft — a generalist chief of staff here, a specialist writer or designer there — and struggle to find people who can hold both at once under visibility. Humanitarian communications professionals have been holding both at once under visibility, as a baseline condition of the job, for their entire careers. The private sector is often surprised to discover how rare that combination is and how valuable it becomes in the roles where it is needed.
Private-sector translation: “Chief of staff. Executive communications. Founder’s office. Head of Communications. Incident leadership. Investor relations. First communications hire at early-stage companies.”
Skill 20: Leadership without authority — leading through relationships with seniors, peers, field staff, and external actors
What it is in humanitarian work
The humanitarian communications professional is, in practice, a leader — without most of the formal trappings of leadership. You rarely sit on the senior management team. You often have no direct reports, or a small team whose work depends on colleagues and field staff you do not manage. And yet the work itself cannot happen without leadership: you are the person who has to set the standard for how the organisation represents itself, align colleagues who do not report to you on what gets said externally, and carry the reputational consequences of outputs that pass through many hands before they leave the building.
That shape of role — responsibility without authority, leadership through relationships rather than through org-chart power — is one of the hardest forms of leadership to learn, and one of the most valuable once you have. Success depends entirely on managing relationships in four directions at once: up, with seniors whose guidance, approval, and political cover you depend on; across, with peer managers in programmes, operations, research, finance, and HR whose information and timing you depend on; down, with field staff whose stories, photographs, data, and logistics you depend on; and out, with state authorities, donors, journalists, partner organisations, and community leaders whose permissions, relationships, and goodwill you depend on. You do not issue instructions to any of these groups. You earn the cooperation.
How field experience solidifies it
You learn this by discovering, repeatedly, that every single output you produce is a collaboration with people you cannot instruct. A field photograph you need comes from a colleague in another department whose week is already full. A technical accuracy check you need comes from an advisor three time zones away. A quote you need comes from a country director whose diary is controlled by someone else. A press-access permission comes from a government information ministry whose priorities are not yours. A field visit comes together because the logistics team, the security team, the programme team, and the local authorities have all agreed — independently — that it is a good use of their time.
You learn that the reflex of demanding, escalating, or going over someone’s head works once, and then you have lost the relationship. You learn that the reflex of being patient, clear about what you need, honest about the constraints, and attentive to what the other person is carrying — works forever, and compounds. You learn to build a reputation as someone who does not waste other people’s time, who follows through, who credits colleagues fairly, and who can be trusted with information; and you learn that that reputation is the only source of leadership you have.
You also learn to manage up. You learn how to read when a senior is under pressure and needs a cleaner draft rather than a question, when to bring a problem and when to bring a decision, how to disagree with a country director or a deputy chief of party without undermining them, and how to surface a risk early enough that it can be managed rather than late enough that it becomes an incident. You learn to be a useful person to a busy principal, which is its own skill.
And you learn to represent the organisation to external actors — ministries, donor officials, UN agency counterparts, local authorities — in ways that do not require you to hold a senior title. You carry the organisation’s credibility in the room because your conduct, your preparation, and your reliability have made you someone those actors will take seriously. That is earned, not assigned.
How I applied it
At World Vision South Sudan, as Communications Manager, I was the strategic link across the Regional Office, Support Offices, and Global Centre during emergencies, coordinating with the Global Rapid Response Team on Level 3 responses. None of those tiers reported to me, and I reported to a single line manager inside the National Office — yet the job only worked if colleagues across four organisational tiers cooperated on timing, content, and messaging. Every Level 3 response was a test of whether I could lead without authority across an entire global organisation under emergency pressure.
In that same role, representing the organisation externally — to journalists, to ministries, to donor representatives, to partner INGOs — meant acting with the weight of the organisation in rooms where I was not the most senior person on our side. Preparing the country director and programme directors as spokespeople meant managing up: briefing a senior with the specific lines, the specific questions likely to come, and the specific context they needed, without either over-handling them or leaving them exposed.
At Management Sciences for Health, the Malaria Newsletter depended on the willing participation of technical advisors whose day jobs were demanding and who had no obligation to prioritise my editorial cycle. The newsletter only came out on time because I built relationships with those advisors over cycles — showing up prepared, respecting their expertise, editing their material with care, and producing a product they were proud to be associated with. None of them reported to me. All of them decided, each cycle, whether to engage.
At AECOM, working under USAID’s OTCM programme required coordinating with Regional Program Managers and Program Officers across a distributed field operation, where compliance standards were tight and the room for drift was small. The leadership task was to hold a shared documentation standard across colleagues who had their own workloads and priorities — which was a matter of relationships, not of instructions.
At REACH and IMPACT, the research and communications cycles only moved because field teams produced data, HQ teams produced analysis, partners accepted dissemination, and donors engaged with outputs. In both organisations I was relatively junior on paper and entirely responsible in practice for outputs that many more senior people depended on. The job was daily leadership through credibility: being the person colleagues trusted to carry information accurately, represent their work faithfully, and deliver on time.
At DT Global, the reporting cycles, the media monitoring, and the internal communications depended on a network of relationships with project staff and leadership whom I did not manage, and on external counterparts I had to keep informed without over-stepping. Again, the work was leadership exercised through consistency and relational care.
Across all of these roles, external actors — state authorities, information ministries, security coordinators, UN agency colleagues, partner INGOs, community leaders — had to be engaged with the weight of the organisation behind me but without a senior title in front. That shape of work teaches you, over years, how to lead without a chain of command to lean on.
How it transfers to the private sector
Leadership without authority is the shape of most modern private-sector work, and most organisations are quietly short of people who can do it well.
In chief-of-staff, program management, and product operations roles, the job is explicitly to align functions that do not report to you — engineering, design, research, sales, legal, compliance, finance — around a shared outcome. The humanitarian communications professional walks in with years of practice at the harder version of the problem.
In management and people leadership, even with a team that does report to you, the modern expectation is that you lead far more through influence, clarity, and relational care than through formal authority. The habits humanitarians build are exactly these habits.
In cross-functional product leadership, the person who ships is the one who can make engineers, designers, researchers, and executives want to work on their problem. Humanitarians who have kept a publication cycle alive through the willingness of busy colleagues across an organisation have been practising this for years.
In executive-adjacent roles — chief of staff to a founder, head of comms reporting to a CEO, a senior advisor in a principal’s office — the work is managing up at a professional level. Knowing when to bring a question and when to bring a decision, when to push back and when to absorb, when to protect a principal’s time and when to spend it. Humanitarian communications professionals learn this by preparing country directors under pressure.
In partnerships, investor relations, policy, and government affairs, the ability to represent the organisation credibly to external actors without being the most senior person in the room is exactly the external-leadership muscle humanitarians build in the field.
In early-stage startup environments, where titles mean little and the organisation runs on whoever can get people to cooperate, the whole operating model is leadership without authority. Humanitarians who have been doing this for a decade are among the most natural fits and among the most under-recognised.
The deeper point is this. A great deal of private-sector literature frames leadership as something that arrives with promotion. Humanitarians learn the opposite: that leadership is what you practise for years before anyone formally names you a leader, and that the craft of leading through relationships — up, across, down, and out — is the craft that determines whether anything you are responsible for actually ships.
Private-sector translation: “Chief of staff. Head of Communications. Program management. Product operations. People leadership. Cross-functional leadership. Managing up. Executive partnership. Partnerships. Government and policy affairs. Founding-team leadership.”
What the bridging role can actually look like
If you are standing at the edge of this transition, it may help to see what the other side of it can actually be.
My current role at Nile Capital is the most honest expression of how these skills transfer, because almost nothing in it is new work in principle — it is the same toolbox applied to a different sector.
I research emerging crypto projects to assess investment merit and brief management, focusing on practical diligence signals: thesis, utility, token model, distribution incentives, execution credibility, and key risks. That is the same kind of research discipline I learned at REACH and IMPACT, applied to different primary sources. I produce educational content to help new crypto users and investors understand upcoming projects and core concepts, translating technical topics into clear, user-safe guidance — the same communication discipline I used to write fact sheets and technical briefs at MSH and AECOM, applied to a new technical subject. I conduct market research to identify user needs and product gaps, and translate findings into requirements for developers — the same assessment-to-reporting loop I learned in humanitarian research, applied to software.
I manage developer workflows in a distributed environment: clarifying priorities, assessing execution needs, identifying resources required to deliver on schedule. That is coordination work, learned across years of humanitarian field-to-HQ operations, applied to a new kind of team. I test software applications, collect user feedback, document issues, and coordinate with developers to improve iteratively — the same information management discipline, in a new domain. I support release readiness, contribute to QA thinking, and coordinate user communications when changes affect wallet, transaction, or security-sensitive flows — crisis-aware communication, reshaped around user safety rather than operational safety. I document issues, capture root-cause notes, and update SOPs and runbooks to prevent recurrence — operational learning, the same discipline I practiced at IMPACT, applied to a private-sector context.
None of that is starting over. All of it is the humanitarian toolbox, translated.
What I want you to take from this
If you are a humanitarian professional thinking about moving into the private sector — into tech, into crypto, into product, into research, into operations, into anywhere — 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, accept that your sector experience is not automatically legible to hiring managers outside the sector, and do the translation yourself until the market catches up with what you actually bring.
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 — decision-ready writing, research discipline, multi-stakeholder coordination, crisis-tested communication that doubles as media relations and spokesperson craft, the ability to translate technical work for non-expert audiences, the operational architecture of information management, SOPs, and process design that holds up beyond any individual, cross-cultural fluency, operational realism under constraint, measurement thinking, narrative craft, the learning agility to absorb new tools and domains on the job, negotiation and diplomacy across misaligned interests, the project management that quietly lets every communications and research task actually happen, the professional ethics that protect the dignity of the people whose lives the work depends on, the theoretical grounding that makes every editorial choice intentional rather than accidental, the systems literacy that lets a professional read the wider political and institutional world their work sits inside, the strategic ownership of a communications function that supports the whole organisation, the local-context literacy that lets a professional represent their organisation with credibility in communities whose trust has to be earned rather than assumed, the generalist-plus-master capacity to hold the whole organisation in mind while maintaining the craft under visibility most roles do not carry, and the quiet, durable leadership exercised without formal authority, through relationships up, across, down, and out — are exactly the habits that well-run private-sector teams are quietly starving for.
Your CV is not a list of disappearing skills. It is a list of under-translated ones.
Do the translation. The skills will carry you.
If you are working through this transition and want to compare notes, I am writing about the process in public as it unfolds. The Journal is where the longer reflections live, and Guidance is where the practical notes accumulate over time.