The International NGO Safety Organisation

Keeping humanitarian workers informed on the move

Watch: How does INSO alerts help humanitarian workers stay safe on the job?

INSO shares real-time safety alerts with NGOs working in high-risk areas, traditionally by SMS and email. This is the mobile app that brings them into one place, as an alternative to SMS and email, and how I designed it as the only designer in a small engineering team.

Role
Product designer
Team
Ramin Daqiq – Software engineer
Raúl Castro – Software engineer
Austin Weidler – Department lead
Timeline
Dec 2022 – 2023 + updates in 2025
Deliverables
Heuristic evaluation, interviews
UI design, prototypes, in-app tutorials
Usability testing, post-launch survey
Launch assets, promotional website

  • 100,000+ alerts opened from notifications in three years
  • 85% of monthly users are returning users
  • 1 in 6 people who used the app also opened a map, a layer SMS never had

This is the 3-minute version. The full case study (13 min) also covers login, the alert list, alert details and Geofence step by step.

The problem

SMS and email gave people little say over which alerts they got and from where, and SMS was costly for INSO

An alert by SMS or email already said what happened, where and what to do. What people couldn't do was shape what reached them.

Only whole regions. Each NGO has one or two people managing its INSO account in the Partners Portal, on a laptop, who activate regions for teams. Nothing finer than a region existed: no area around you, no route, no single compound.

Costly, and easy to miss. SMS was also costly, and alerts got lost among every other SMS and email.

Composing and sending meant a laptop. INSO staff needed a laptop to compose and send alerts.

The app is an alternative to SMS and email, which are still the only way in some regions. It brings both sides into one place: composing and sending alerts, and seeing how they appear in the feed.

Before

The app when I joined: a dense dark list of alerts in capitals, an alert detail packed with text under a small map, and a map that shows a single alert pin.
Before: The app when I joined the project team.

The first version was an engineers' initiative, built from conversations with country offices and nothing documented. I joined as the only designer, with no access to partners, so country office colleagues stood in for them. I combined a heuristic evaluation with interviews and Maze tests, and checked with partners after launch.

Users

Three groups, one sending and two receiving

Receive – user groups

WhoNeedsPains before the app
An NGO field worker with a backpack walking across a car park

NGO field workersIn the field, on the move, exposed to risk, sometimes with no internet

Stay updated while movingFocus only on what affects their safety: the road, where they're going, where they sleepOnly whole regions, activated by their NGO's account admin on a laptopAlerts lost among every other SMS and email
A security officer on a satellite phone next to a field vehicle

Security and operations staffIn an office, keeping an eye on teams who travel, advising them by SMS or a call

Monitor specific areas remotelyTrack patterns and ongoing situationsCouldn't follow a place they weren't inNo radius or custom area, like the compound where staff live

SharedBoth groups

Quickly understand what's happening nearbyTrust the accuracy of alertsStay updated in real timeHigh pressure, little time to readUnclear alerts reduce trustPhone checks are a security risk

Send – user group

WhoNeedsPains before the app
An INSO staff member writing an alert on a laptop

INSO staff in the country officesCollect, validate, compose and send the alerts

Compose and send quickly, from anywhere, with or without dataReduce the cost of SMSComposing and sending meant a laptop and the Partners Portal, hard from the fieldSMS was costly

Maps

A map adds the where, for people who need it

Most people never open the map. By default the app does what SMS and email did: it sends you the alerts from the regions you subscribed to, and that is the main use. On top of that it adds a map layer and more control, like choosing the areas you want alerts from and the map mode that fits what you're doing. The map is for people who need to see where an alert comes from, follow one area, or explore during a mission, and who would otherwise need another map tool. About 1 in 6 people who used the app have opened a map.

The old map had two tools, Proximity and Polygon. To look anywhere else, you had to open a single alert from the list and jump to its location. A heuristic evaluation turned up three gaps:

  • You couldn't explore freely: the map only opened as a tool for setting a radius or drawing an area.
  • You couldn't select an alert on the map and read it there.
  • You couldn't move around the map, then switch back to the list to see only the alerts from that place.
The old alerts list.
1 of 6

Before: The former map: a tool for setting a radius or drawing an area, not for exploring.

Explore: what's happening along my route?

Explore fixes all three. You can move around the map freely, tap an alert to read it there, and go to any place and switch back to the list to load the alerts from that area. The idea came from colleagues in the country offices, who raised it when we tested.

The alerts list, with a Map button at the bottom.
1 of 6

After: Explore: move around the map freely, tap an alert to read it there, and switch back to the list for that area.

Testers found the map from the alerts list and explored it freely, with no drop-offs.

8 of 8 completed · 33 s on average · ease 8.6/10 · Maze test with country office colleagues

Proximity: understanding it isn't the same as using it

Proximity shows alerts within a radius of your live location, or of a pin you drop somewhere else. In the first version, one pop-up explained it.

Testers set a radius around a place they weren't in, but it was slow, and some couldn't tell live location from custom location.

6 participants · 53 s on average · ease 6.8/10 · Maze test with country office colleagues

While they were thinking aloud, most of them read the pop-up and explained the mode back to me correctly. But it's one thing to understand something and another to know how to put it into practice. So the pop-up became a short three-step tutorial: nothing too long, to avoid killing engagement, but enough to show how to use the mode.

Proximity, with Your location and Custom location.
1 of 6

After: The redesign: a three-step tutorial shows how to use live and custom location.

The tutorial cleared up the difference between live and custom location, and colleagues were more satisfied with the feature.

Interviews with 5 country office colleagues who hadn't seen the app before · updated design and prototype

Across releases, Explore takes most of the map traffic, with Proximity and Geofence well behind. That matches what partners ranked as most important.

Also in this app

Login, the alert list, alert details and Geofence

  • Login. The app asked for location before anyone had logged in and never said what it was for. Two short onboarding screens now come first, and location is asked after.
  • Alert list. Eight dense alerts per screen became a list built for scanning: location first, then a short title, then time, with search at the top. 10 of 10 testers filtered alerts by location in 22 seconds on average (ease 9.3/10).
  • Saved alerts. Not in the first draft. We asked country office colleagues how people could keep track of the alerts they care about when everything mixes together, and landed on pinning them to a Saved page in the bottom menu.
  • Alert detail. A summary first (what, where, when, how far), then the latest update and advice, in the order the interviews showed.
  • Geofence. Saving meant pressing Back. It now has a Confirm button, a three-step tutorial, and a name that says what it does.
Onboarding: stay informed and safe while on the move.
1 of 4

After: Login: two short onboarding screens say what the app is for before anything is asked.

Want the detail behind login, the alert list, alert details and Geofence? Read the full case study (13 min).

Outcome

Used, and people keep coming back

After the launch peak of about 1,600 users, a steady base settled in: around 800 a month through 2024, and 450 to 630 through 2026. About 8 in 10 of them are returning users, and alerts have been opened from notifications over 100,000 times in three years.

Monthly active and returning users since launch, rounded. Test and visitor traffic left out.
Table view
MonthActive usersReturning users
Jun 20231,6301,160
Jul 20231,2701,080
Aug 20231,000900
Sept 2023890800
Oct 2023870780
Nov 2023830770
Dec 2023900760
Jan 2024860740
Feb 2024820730
Mar 2024780700
Apr 2024800700
May 2024790670
Jun 2024810690
Jul 2024760660
Aug 2024720620
Sept 2024840680
Oct 2024740630
Nov 2024740630
Dec 2024740650
Jan 2025730640
Feb 2025690600
Mar 2025710630
Apr 2025700620
May 2025680580
Jun 2025660580
Jul 2025740630
Aug 2025690590
Sept 2025650530
Oct 2025640530
Nov 2025530470
Dec 2025500420
Jan 2026480400
Feb 2026480410
Mar 2026530440
Apr 2026500420
May 2026460400
Jun 2026460380
Jul 2026460370
Aug 2026450380
Sept 2026630450

Most partners found the app easy to use.

23 of 29 rated ease of use 4 or 5 (average 4.1/5) · post-launch survey of 31 partners

What I can't say. Nothing was measured before the new design, so I can't say whether it made the app better, only that it's used and that people keep coming back.

Take a look at app.ngosafety.org (opens in a new tab)

Takeaway

Test whether people can do it, not whether they understand it

Proximity taught me the most: testers explained the mode back to me correctly and still struggled to use it. Next time I'd also set baseline metrics before designing, so the outcome can be compared, not just observed.

Read the full case study (13 min)

Do you have a project in mind?
Let's connect.

Open to perm roles & new projects