Case Study - AI adoption strategy for humanitarian and development organizations

Over the past year we have helped multiple humanitarian and development organizations adopt AI responsibly. We reviewed digital readiness, evaluated tools like Copilot and Claude against real workflows, delivered hands-on training, and built staged adoption plans tailored to each organization's capacity and existing environment.

4 min read
Client
Multiple organizations
Location
Global
Services
AI Adoption, Digital Strategy, Capacity Building
Organizations supported
0
AI tools evaluated
0
Usage policies published
0
Use cases developed
0

The challenge

Over the past year we have worked with several humanitarian and development organizations navigating AI adoption. Across each we saw the same starting point: staff were already using ChatGPT, Claude, or Copilot informally, but there was no shared understanding of what was safe, what was useful, or how AI fit the wider digital strategy. Many were paying for Microsoft 365 licenses with AI capabilities built in but weren't using them.

These organizations handle sensitive programmatic and operational data, and adopting AI without clear boundaries introduces real risk. At the same time, teams stretched thin managing complex programs stand to benefit significantly from AI if the adoption is structured around their actual needs and capacity.

Our approach

We meet each organization where they are and build from there.

1. Understanding where things stand

We review how teams work: the tools they use, how data flows between them, where things break down, and what's going unused. We talk to staff across functions and place the organization on our AI Maturity Ladder (Crawl, Walk, Run) so everyone shares a language for readiness.

Most organizations sit in early-to-mid Crawl: some experience with AI tools, but no governance, shared practice, or clear path forward.

Key insight

The organizations that adopt AI successfully aren't the ones with the best tools. They're the ones that understood their own workflows well enough to know where AI fits and where it doesn't.

2. Defining the path forward

From the review we build a staged plan sequenced around the organization's capacity, existing licenses, and priority workflows. This includes identifying which processes benefit most from AI or automation, setting data boundaries through a usage policy, and recommending tools grounded in what the organization already has.

We evaluate tools against real use cases rather than vendor marketing. Some of the use cases we have helped organizations develop:

  • Building and maintaining integrations. Tools like Power Automate can be technical and time-consuming to configure. AI helps staff develop and troubleshoot automations without deep technical skills for every change.
  • Developing on-brand design systems. Using AI design tools like Claude Design, we help organizations turn their brand book into an interactive system for producing on-brand slide decks, reports, and visuals without a designer in the loop every time.
  • Prototyping ideas before building them. Non-technical staff use AI to mock up what they want, making it easier to communicate requirements to developers or vendors.
  • Managing vendor delivery. AI helps teams groom project boards, identify completed tasks, flag gaps, and keep vendor accountability clear.

Watch out

For organizations handling data about vulnerable people, the fastest way to lose trust is to feed sensitive information into a tool that retains or trains on it. The use cases above work because they don't require sensitive data. An AI policy starts with what stays out, then builds use cases around what's safe to put in.

3. Building capability that lasts

AI moves too fast for one-time training to be enough. What matters more is changing how people work: building the habit of experimenting with prompts to solve everyday challenges, learning what AI is good at (identifying patterns, summarizing, drafting) and what it's not (judgment, sensitive decisions, anything requiring institutional memory it doesn't have).

We help teams develop this mindset and the discipline around it. When someone finds a prompt or workflow that works, we help them document it so the AI can reference it in future work and others can build on it. Over time this creates a shared library of proven approaches that grows with the organization.

Tip

Don't try to train everyone on everything at once. Pick one or two use cases that are easy to adopt and clearly useful, let people see the value, then expand from there.

What we have learned

These engagements have shaped principles we bring to every new partnership:

  • Meet organizations where they are. The maturity ladder gives us a shared language for readiness.
  • Start with data, not features. What must never enter an AI tool shapes everything else.
  • Leverage what you already pay for. Most organizations are underusing AI capabilities already in their Microsoft 365 licenses.
  • Build habits before systems. Weekly comfort with AI matters more than rushing to connect tools to organizational data.
  • Plan for sustainability. Anything we introduce has to survive without us.

From the field

One of the most useful outcomes across these engagements has been giving staff permission to use AI for the right tasks. A clear policy turns quiet, ad hoc experimentation into something the organization can support and scale.

We share what we learn publicly. Our AI Maturity Ladder for NGOs blog post distills the adoption framework that underpins this work, and future posts will cover building prompt libraries, configuring AI tools for data protection, and designing AI governance for distributed teams.

  • AI readiness reviews
  • Tool evaluation and recommendations
  • Staff training and onboarding
  • Staged adoption roadmaps

Technologies used

  • ChatGPT
  • Claude
  • Microsoft Copilot
  • Google Gemini
  • Model context protocol
  • Microsoft 365
  • Power Automate
  • Power BI

At Hikaya, we help NGOs and nonprofits adopt AI at a pace that fits, with honest reviews of where you stand, practical policies, tool evaluations, and staged plans that respect the sensitivity of your data and the capacity of your team.

If your teams are already experimenting with AI but you don't yet have a clear position on what's safe and what's worthwhile, start a conversation with us, or explore how we work.

More case studies

Digital framework review and IT service delivery for a global humanitarian organization

We reviewed and restructured the digital service delivery model for LWF World Service, covering team structure, application governance, and IT operations.

Read more3 min read

Tracking land restoration progress across the Sahel for the Great Green Wall

We designed a monitoring framework and knowledge management strategy for the Great Green Wall Initiative, connecting restoration indicators to the GGW Observatory platform.

Read more2 min read

User discovery for improved project management

We helped LWF World Service map user journeys, define requirements, and evaluate 56 project management tools to replace an outdated reporting system.

Read more3 min read

Independent evaluation of shared IT services for a global medical humanitarian organization

We ran an independent evaluation of MSF's Shared IT Services, benchmarking cost and performance against market alternatives across 14 criteria.

Read more2 min read

Tell us about your project

Partner with our team to develop tailored digital solutions for your organization.


Locations

  • Portland
    Oregon, USA
  • Berlin
    Germany
  • Nairobi
    Kenya