{"id":3226,"date":"2015-11-26T10:41:27","date_gmt":"2015-11-26T10:41:27","guid":{"rendered":"http:\/\/innovation.unhcr.org\/?p=3226"},"modified":"2017-06-29T09:55:37","modified_gmt":"2017-06-29T09:55:37","slug":"how-to-turn-setbacks-into-progress-for-innovation-projects","status":"publish","type":"post","link":"https:\/\/www.unhcr.org\/innovation\/how-to-turn-setbacks-into-progress-for-innovation-projects\/","title":{"rendered":"How to turn setbacks into progress for innovation projects"},"content":{"rendered":"

There are many ways to arrange the proverbial \u201clast mile\u201d before relief reaches people. Since 2014, UNHCR has been testing software created together with the UPS Foundation to speed up the distribution of goods and services to refugees, and to link distribution data with registration data.<\/span><\/p>\n

The software, called ReliefLink<\/a>, tracks who has received which support, replacing a multitude of paper records that may cause errors and delays, not to mention breaches in confidentiality.<\/span><\/p>\n

Initial field tests have gleaned mixed results. In Lebanon, testing was cut short as the number of Syrian refugees soared and UNHCR\u2019s entire focus was on response. Tests in Dollo Ado, Ethiopia were scheduled for 2015. However they have been delayed for a variety of reasons, including personnel changes, security concerns, and unforeseen coding needs.<\/span><\/p>\n

Results have been more promising in Bassikounou, Mauritania, where ReliefLink has so far helped to distribute shelter to more than 300 families, and food to more than 100,000 individuals. Distribution times have been cut in half, and the software is increasingly being used in lieu of the laptop and scanner UNHCR staff members usually carry around for registration and distribution.<\/span><\/p>\n

UNHCR will build on this success \u2014 and lessons learned from Lebanon and Ethiopia \u2014 to improve and where appropriate, expand the use of ReliefLink in 2016. Already, a series of small errors in data output, device configuration and server synchronization have been fixed. Software has been updated to allow usage on Android devices and to resolve hang-ups in the synchronization of large pools of information. Screen resolution has been increased and new ways to input and filter data have been added.<\/span><\/p>\n

Lessons Learned<\/span><\/h2>\n

Delays and setbacks have brought with them invaluable lessons learned, however. Here are three of them:<\/span><\/p>\n

    \n
  1. Projects should be field-led from inception: <\/span><\/i>Innovation<\/span> projects need to be strongly driven by the field operation based on a clear challenge that they\u2019ve identified. Solving this challenge remains a clear motivation for testing possible solutions. This holds true for ReliefLink testing.<\/span><\/li>\n
  2. Testing should be timed appropriately to avoid conflicting priorities<\/span><\/i>: Sometimes during emergencies, people cannot, and should not prioritise testing new technology solutions. The priority is to respond to the emergency. More care must be applied to the scheduling of tests so that ongoing emergency support is always prioritized.<\/span><\/li>\n
  3. The focus should always be on the process, not the tool<\/span><\/i>: Sometimes, even with the best of intentions, we engage in push innovation. That means we put the focus on (what we think) is a newer, better tool, and then try to find an operation that wants to test it. In fact, we should focus on the process: working together with an operation to identify a challenge and then find the most appropriate solution.<\/span><\/li>\n<\/ol>\n

    Looking ahead<\/span><\/h2>\n

    Taking into account key lessons learned from testing ReliefLink, future plans for the project include:<\/span><\/p>\n