" Improving the quality of humanitarian assistance. "
Background
Humanitarian workers rely heavily on handbook information to plan/assess crisis situations and to measure the impact of their program. There is immense pressure on them to locate this information in a timely manner.
Sphere is an international humanitarian aid organization with the goal of improving the quality of humanitarian assistance. Sphere’s widely used flagship publication, The Sphere Handbook, provides a set of humanitarian standards and guidelines for aid programs. The handbook has been used for 20 plus years in its printed form, but there is growing demand from Sphere users for a more robust digital publication.
Goal
Redesign the Sphere handbook in a digital form to reduce information overload and with the goal to increase the adoption of Sphere Standards and quality of humanitarian aid amongst international NGOs.
Target audience
Humanitarian workers and educators.
Client
Sphere
Solution
A web platform which intuitively organizes and highlights key Sphere handbook content, creating links between related topics. The platform enables users to customize their humanitarian program targets and to export this information into a report format.
Introduction

The Sphere Handbook, a 500+ page print publication, is likely the mostly widely known tool in the field of humanitarian standards. Due to the handbook's length and complexity, it can take significant time to locate essential information. The handbook is meant to serve as a reference guide and its information must be carefully adapted to fit the crisis context.

Our team discussed ideal project purpose, successful outcomes and target users with our client at Sphere before beginning with user research.

A photo of four members of the Sphere design team (two men and two women) standing in front of a white board with sticky notes on it.
sphere team
Desk research

To better understand the design problem space I began locating previous research on the usage of Sphere standards for humanitarian response. I soon located two comprehensive survey studies which outline: who uses the handbook, what sections of the handbook are considered most important, what its criticisms are and how internationally impactful it is.

I presented my research findings in a table summarizing the study method, findings, conclusions and ideas that I had while reading the article. I also organized my thoughts into three key themes:

  • Fast access
  • Context is key
  • Pertinent information
A blue and black chart showing a desk research summary from the Sphere UX project.
Discovery

While I conducted desk research, my teammates arranged a user interview with a Red Cross employee. Our interview questions focused around the topic of how humanitarian programs are organized and how the Sphere handbook is meant to help facilitate this process. Below are some examples of interview questions we asked:

  • What is your background in humanitarian work and what experience do you have with Sphere standards?
  • What is your approach to navigating the handbook. Can you walk us through an example?
  • How does the handbook supplement humanitarian programs during different phases?
  • Are there handbook sections that you use more than others and why?

We used an empathy map to organize our interview findings. This map helped our team to create a shared understanding of user actions, needs, pain points and emotions.

Image of Sphere user testing empathy map depicting user needs, emotions, and goals.

Next, my team and I created an experience map which depicts the stages of the humanitarian program cycle, when the handbook is most often used as well as user mindsets. We learned from our interviewee that users consult the handbook most during the 'needs assessment and analysis' stage and that its technical chapters are most important during this time.

Journey map depicting how Sphere handbook users use the book throughout the humanitarian program phases.
Ideation & validation

After spending significant time orienting ourselves with humanitarian work we were eager to start brainstorming solutions. Each of us sketched our own idea of what a digital version of the Sphere handbook might look like. We created enough sketches to show a basic user flow and conducted user walkthrough tests to see if they could perform simple tasks such as locating a specific piece of information from the handbook.

We discovered that users desired visual clues to show current location within the handbook structure and how they might navigate backwards (or forwards) if necessary. We also discovered that these users would prefer to drill down to information by category rather than by keyword search because they lacked knowledge of Sphere terminology.

A photo of three persons pointing to a paper prototype sketch of Sphere digital platform.
sphere user testing

Our team had important decisions to make about what handbook content to highlight and which additional features to include. We used a prioritization matrix to visualize overlap between client and user needs so that our design would appease all stakeholders.

This visualization helped us to realize that our design should:

  • Highlight technical information from the handbook
  • Focus on creating a simple platform navigation scheme
  • Offer users customization options
Platform feature prioritization matrix for Sphere platform depicting user /client needs and goals.
Design

Our final design has a simple, but professional aesthetic which draws user attention to the key handbook content needed to assess crisis situations. The colour palette uses the same attractive and recognizable Sphere branding, and we used plenty of negative white space to avoid user fatigue and information overload.

Our design caters to beginner and intermediate users of the Sphere handbook. Expectations for information finding are different from what they used to be when the Sphere handbook was first published - users want quick, digestible, and interactive information. Our Sphere design focuses on these requirements.

A photo of a paper mockup of Sphere UI style-guide

Our platform uses a beginner-friendly, sidebar navigation and filter design to highlight handbook structure. Users can modify or delete filter selections from any screen. Intermediate or advanced users can skip directly to the handbook content that they require. Tables are used to show relations between the handbook targets and categories, and Wikipedia-style in-text hyperlinks are used for cross referencing.

Users have the ability to edit suggested program targets when these cannot be met or where the situation allows them to achieve a higher standard. Users can also export handbook content, edited targets and notes into a standard report format to be shared with other humanitarian agencies.

Sphere web platform displaying on an iMac computer which sits on top of a wooden desk with a lamp next to it.
sphere interface