Conceptualization

—  An overview of Sufficient - A mobile/tablet application developed from the ground up to solve the problem of resource management

The Idea

During the course of a one day hackathon I worked with a small group of talented individuals from various backgrounds - some creative,some technology,some academic - to create a unique product that would assist humanitarian agencies with an ever growing problem - resource management.

The Problem

A lot of large scale humanitarian agencies operating on the ground in various parts of the world constantly face the struggle of ensuring that resources are adequately provisioned. for the families and communities, they need to be served fairly in order to ensure all members basic needs are being met. For the agencies, its important to ensure a sense of accountability and efficiency.

The Approach

The entire process began with quick ideation - an affinity map was built to create the user journey to illustrate the current user journey and define the context of how humanitarian organizations go about distributing resources based on our conversations with members of World Vision present. This map also revealed the concept for our initial userflow with regards to what information was needed to give an accurate diagnosis for each registered member.

The scope was narrowed down to two scenarios that would hopefully provide a preview of the wider applications of the product. The process of scoping for size involved looking at what current databases and resources could be leveraged while providing cost effective existing solutions that could also be implemented in order to ensure potential investors were not scared away by high entry costs.

Once this size was determined we needed to look into a framework within which to work. Goals, opportunities, risks and context were determined in order to ensure a streamlined work flow that followed the overarching narrative being told while allowing us to respect timelines.

Once this was complete the first wireframes were produced - this was done fairly quickly in order to allow for quick user testing allowing us a rapid proof of concept. Subjects were selected from a local Starbucks and using Balsamiq and InVision an early prototype was used to determine usability and comprehension of concept. The results obtained from this testing were then used to further refine the concept and resize journeys to ensure only the required concepts were being detailed in a quick digestible presentation.

After 7 hours of work including wireframing, visual design, journey map creation and business analysis, Sufficient was presented to the judges with a great reception.

 

Some Key Challenges

 

Visual

The application was required to be user friendly, visually engaging and detailed. The challenge was in presenting sufficient information to field partners to ensure they are able to at a glance access all the required details for the community they are serving.

Using vibrant, engaging graphs and menus we were able to allow the user to engage in a manner that would be encouraging and informative.

Intuitive

One of the challenges while creating a product of this nature is the rate of adoption. The product has to be intuitive enough that it can be picked up and quickly leanred by the user so that they dont feel impeded in their work. To work to solve this, we created several iterations of the user flow to ensure the fewest number of steps while ensuring all functions that could be required were included.

This process was validated through user testing and reviews to ensure that needs of general users as well as the potential business were both met.

Collaboration

Fixed timelines would be difficult to meet without teamwork. Our team consisted of a variety of backgrounds which was a great strength as it allowed us to be able to access various repositories of information.

At the same time, it was difficult to assign work as everyone's' talents had to be quickly made known in order for them to be allocated to tasks that would maximize their skill set.

The process of sizing allowed us to do this in an efficient manner. Having tasks broken up in a manner that was detailed and well outlined in terms of work effort allowed us to quickly assign tasks to responsible parties. This meant that everyone on the team was "able" and therefore ready to contribute.

 

(Opens a new window)