Monthly Archives: November 2013

Weekly T4D/Innovation Insights & Updates #5

Over the last couple of weeks, the Weekly T4D/Innovation Friday posts have covered some of the ins and outs of scaling innovation, worst practices in ICT4D, and challenges and opportunities of T4D application in programme delivery. Some of the themes that have emerged are the need to think about scale from the beginning, fail fast, and involve the end-user in the design process.

This week we’re going to focus on the why and how to involve the end-user in T4D and Innovation initiatives with a look at the blog post, “Building Human-Centered Design into ICT4D Projects.”

https://bestict4d.wordpress.com/2013/07/18/human-centered-design/

KEY TAKEAWAYS:

What is human-centered design?

  • “A problem-solving process that puts humans at the very center.”
  • 3 components: 1) learn from a community/end-user to understand the problem; 2) ideate and prototype rapidly; 3) feedback from real users quickly and frequently.

Why is human-centered design important in the social sector?

  • “In international development you have projects being implemented thousands of miles away from where decisions are made. Frequently, there’s no feedback loop so it’s hard to say: Is it working, and are people choosing to use this?”

Why is human-centered design important to the field of ICT4D?

  • “In general the development community is very risk averse…One of the benefits of human-centered design is to mitigate risk by testing early and failing fast.”
  • “In the context of ICT4D, human-centered design can help with the design of a technology, and the context around it, long before the technology is ready for launch.”

Is failure at certain times not only acceptable but important?

When you learn from it, failure can be a very positive part of the process. You want to try to get some of the failing out early so that you can learn from it and let it influence the design of a better more successful project.”

In October ESARO facilitated a T4D Capacity Building Workshop, and one of the sessions focused on human centered design. After learning some of the basics, participants discussed how human-centered design can be incorporated into UNICEF T4D programming, two conclusions emerged:

  • Human-centered design can be used internally to identify priority areas for T4D application;
  • Understanding the process can help manage external vendors such as software developers during the iterative software design process.

For a closer look at the human-centered design session, please see page 12 of the conference report.

https://drive.google.com/file/d/0B101gFvV4LzKRXVHenlWeTlOZXc/edit?usp=sharing

 

Advertisements

Weekly T4D/Innovation Insights & Updates #4

Wishing everyone a Happy Friday. For this week’s installment of ESARO’s T4D/Innovation Insights and Updates, we’ll take a look at some of the worst practices of using ICT in programme sections.

http://blogs.worldbank.org/edutech/worst-practice

While this blog post specifically focuses on using ICT in education, the lessons can be applied across all UNICEF programme sections.

  A quick look at the worst practices:

1.     Dump hardware in schools, hope for magic to happen

2.     Design for OECD learning environments, implement elsewhere

3.     Think about education content only after you have rolled out your hardware

4.     Assume you can import content from somewhere else

5.     Don’t monitor, don’t evaluate

6.     Make a big bet on an unproven technology (especially one based on a closed/proprietary standard) or single vendor

7.     Don’t think about (or acknowledge) total cost of ownership/operation issues or calculations

8.     Assume away equity issues

9.     Don’t train your teachers (nor school headmasters, for that matter)

10.   _________(No. 10 is purposefully left blank to reinforce that many other worst practices exist.)

However, knowing the “what not to dos” is only part of the learning process as we become more familiar with integrating T4D in programme delivery. Last month Global Innovations launched the Child Friendly Technology Framework to help programme sections think through some of the challenges that arise when designing a new project with a tech component. With the help of 52 worksheets to stimulate thinking and discussion, the framework helps guide a new project from the idea stage through producing a Concept Note and Executive Summary to guide project implementation..

http://unicefstories.org/2013/08/06/child-friendly-technology-framework/ 

 Hopefully, by utilizing some of the planning tools such as the Child Friendly Technology Framework, we can avoid committing some of the “worst practices” mentioned.

 

Weekly T4D/Innovation Insights & Updates #3

This week as we continue learning about the ins and outs of Innovation and T4D, I am pleased to share with you the blog post, “Innovation for development: what is really different?”

http://europeandcis.undp.org/blog/2013/03/18/innovation-for-development-what-is-really-different/ 

“One of the biggest challenges for innovation evangelists in development organizations is…to clearly articulate ‘what is different’ in the approaches they are advocating for as opposed to ‘business as usual.’” 

The author is the Project Lead for UNDP’s Knowledge and Innovation team in Europe and Central Asia, and he explored what innovation means for development while visiting UNICEF Innovation Labs in Uganda and Burundi. Using UNICEF’s Innovation Principles as a framework, he highlights the impact of innovation and the differences with business as usual (BAU) practices. For more information on UNICEF’s Innovation Principles please see: http://unicefstories.org/principles/ 

Below are some brief takeaways for each principle. However, be sure to check out the link for more many more examples as well as the “money quotes” from UNICEF’s very own, Chris Fabian and Sharad Shapra. 

1.    User Centered and Equity Focused: 

      a.    BAU: Projects are often designed by people spending the majority of their                    time in offices, many times far away from end users

      b.    What is different: Solutions are designed in the field, co-developed with end                 users.

2.    Built on Experience: 

      a.    BAU: Projects are talked about publicly only at the end, focusing on                                 showcasing results

      b.    Innovation: Projects are talked about from the ideation stage, focusing on                    process to encourage inputs from the outside.


3.
    Sustainable: 

     a.    BAU: Solutions are often developed and/or maintained by international                         experts

     b.    Innovation: Local developers are involved in the development of solutions                   from the very beginning


4.
    Open and Inclusive: 

     a.    BAU: Solutions are developed using proprietary technology

     b.    Innovation: Solutions are developed to be open sources so that they can be                 shared with others

5.    Scalable: 

     a.    BAU: Localised solutions designed to reach, say, 10% of a given population are           often “good enough” to get started

     b.    Innovation: No solution is financed that is not designed to 100% scalable and             replicable in other contexts.

 

Weekly T4D/Innovation Insights & Update #2

Happy Friday! The Regional T4D team has begun sending out a weekly article or two about T4D and Innovation to showcase interesting insights, opportunities and challenges faced in this space.

This week we turn to an interview by Aleem Walji, Director of Innovation Labs at the World Bank Institute, on how the World Bank thinks about scaling innovation. In this interview at the Skoll World Forum in April 2013, Mr. Walji highlights ways development organizations can leverage technology and innovation initiatives to positively impact humanitarian efforts.

http://www.forbes.com/sites/skollworldforum/2013/09/04/how-does-the-world-bank-think-about-scaling-innovation/

Some quick takeaways from the interview:

  • Solving humanitarian challenges requires solutions where “multiple actors experiment together, learn together, and iterate fast.” We need to push for evidence-based solutions and multi-stakeholder problem solving.
  •  Move towards an agile development model where“instead of minimizing risk we need to manage risk and navigate uncertainty intelligently.”
  • “Fail fast and fail forward. You learn and iterate. You document what you learn, share it with the world and look for insights form wherever you find them.”
  • Be bold in experimentation and think big in programme delivery. “What we need to scale is not a particular solution or development prescription but a repeatable process that is end-user centric, disciplined and data driven.

This interview provides some great insights into the challenges and opportunities facing UNICEF as we begin and continue thinking about and discussing the possibilities for T4D and Innovation in programme delivery.

Also, UNICEF’s own Chris Fabian gave a great interview on this same subject for the World We Want. For Chris and the Global Innovations

team, scaling innovation means “working with open source solutions, with technologies that are readily available in community so we don’t have to bring things from outside, and with products that can be built locally, adopted locally, and scaled globally.”

Here’s the link to the full interview: http://www.worldwewant2015.org/node/398622

I hope you enjoy reading.

 

Weekly T4D/Innovation Insight & Update #1

In an effort to support and advance learning and knowledge about T4D in the region, the Regional T4D team is beginning to share articles and links on a weekly basis to stimulate discussion and thinking.

To begin, here is a link to a blog post that talks about the challenges within the T4D community. http://www.kiwanja.net/blog/?s=ICT4D+challenges.

I am also including a link to an article outlining some of the opportunities that T4D can offer the humanitarian world. http://www.theguardian.com/global-development/poverty-matters/2012/jan/04/technology-make-difference-2012 .

These two links highlight some important points when thinking about the opportunities, as well as challenges, when integrating T4D into programme delivery. Applying T4D tools and strategies is much less about the technology and much more about the programming, and some even venture to say that T4D is only 5% technology and 95% programme. Therefore, thinking through all the stages of programme planning is necessary to design, implement and scale a successful project.

The Kiwanja blog outlines some important questions to think about in their post “ICT4D Challenges”:

  • How do we replicate and scale?
  • How do we measure impact?
  • How do we stop the reinventing of wheels?
  • How do we avoid being “technology lead?”
  • How do we break out of silos?
  • What is the business/sustainability model?
  • How do we make sense of the countless pilots?

Some of these questions are easier than others to answer. But, as ESAR becomes more comfortable with T4D,  we should continually refer back to some of these larger issues and challenges to help inform how we move forward.

Stay tuned for more weekly insights and updates!

 

mHealth Framework WebEx

In our efforts to increase capacity across the region for the improved management of Technology for Development initiatives, the Regional ICT team is hosting a series of WebEx sessions on relevant T4D topics including: tools and technology solutions, useful innovations for Programme challenges, and methodologies for project management.

For our first session, we were very pleased to have Erica Kochi from UNICEF’s Global Innovations unit in New York join us to explain the mHealth Framework.  She was joined by a number of key partners who were involved in the mHealth Framework from its inception. The mHealth Framework has been developed in collaboration with Johns Hopkins University, the World Health Organization, and frog Design. The mHealth Framework is a tool for helping governments, donors, implementing partners or other stakeholders understand how to determine appropriate technology solutions for health interventions, and how mobile technologies can improve health outcomes.  The framework aids practitioners in conceptualizing the larger “health system”, so that challenges, constraints, and key actors are better incorporated into project design and implementation. For more background on the mHealth Framework, please see this paper.

See below for the mHealth Framework.

Erica Kochi gave the introduction to the session, and discussed some of the opportunities in East Africa for integrating technology and innovation in design into health programming.  mHealth aims to make connections and bridge gaps across the continuum of care, and the mHealth framework was developed, “somewhat organically,” she says, to guide practitioners in navigating this evolving space.

Peter Benjamin, who is Director of mHelp, the Capacity Building unit of the mHealth Alliance, gave us some background on mHealth and how it has evolved in the last few years.  While mHealth has come a long way, there are still many challenges in health systems that mHealth, as a tool, is not yet able to solve.  The challenges for mHealth solutions include improving interoperability, determining financially sustainable business models for scaling mHealth solutions, and improving the evidence to determine its tangible benefits. When it comes to scaling mHealth solutions, Peter emphasized that it is important to keep in mind the end-user, to plan for scale from the beginning, and to invest in evaluation so that lessons learned can be fed into future projects.

Alain Labrique is Director of mHealth Initiatives at Johns Hopkins University and focuses on Health Systems in Asia and East Africa.  He discussed how mHealth technologies improve coverage of over-stretched health systems. Johns Hopkins and WHO have been working to develop a mHealth Taxonomy in order to standardize the language around mHealth interventions.  Alain highlighted how using a common language will help practitioners identify complementary efforts and existing gaps. The mHealth Framework takes this one step further, by identifying and visualizing common constraints faced by actors in the system.

Garret Mehl conducts research on reproductive health and innovations for strengthening health systems at WHO.  He took us through the different components of the mHealth Framework and gave examples of how it can be applied.  The framework acts as a planning and communication tool, to help illustrate health projects to stakeholders and governments. It consists of validated interventions along the continuum of care (for now it focuses solely on Reproductive, Maternal, Newborn and Child Health), constraints and challenges, and possible mHealth applications (clustered by their different utilities). Garrett explained that the Framework allows for the “when, what, how and why a mHealth strategy is being deployed.”

Finally, Sean Blaschke (Health Systems Specialist, UNICEF Uganda) and Nick Oliphant (Health Specialist, UNICEF HQ) discussed their work on health systems strengthening at the Country Office level. Sean discussed the importance of working with government partners to implement national policies or strategies around the use of technology, and to focus on building the capacity of the Ministry of Health to manage and maintain a national health information system. He noted that one of the challenges to scaling mHealth initiatives can often be related to the enabling environment including legislative or regulatory frameworks.    Nick has been spearheading work with the University of Oslo to prototype the new features of the DHIS2, or District Health Information System. DHIS2 is being rapidly adopted in over 40 countries, 20 of which are national deployments, and can easily be mapped onto the mHealth Framework.

Thank you to those of you who joined this session on the mHealth Framework.  Once again, we’d like to extend huge appreciation to our presenters and to Erica Kochi for leading the call.  In addition, all of the documents and presentations referenced during the session can be downloaded here:

https://www.dropbox.com/sh/kq914f9lz2mqusn/R-1A3uxviY

Below are the two components of the framework from a blog post written by our friends at Global Innovation for UNICEF Stories a few months back. The visualizations and descriptions provide a helpful conceptualization of how the mHealth framework can be applied to strengthen health systems, and ultimately, improve access to health services.

Source: http://unicefstories.org/2013/08/08/mhealth-innovations-as-health-system-strengthening-tools-12-common-applications-and-a-visual-framework/

  1. A place to depict the specifics of the mHealth intervention, described as one or more common mHealth or information and communications technology (ICT) applications used to target specific health system challenges or constraints within specific areas of the RMNCH continuum of care.

Image

2. A visual depiction of mHealth implementation through the concept of ‘‘touch points,’’ or points of contact, which describe the specific mHealth interactions across health system actors (for example, clients, providers), locations (such as clinics or hospitals), and timings of interactions and data exchange.

GHSP-13-00031-Mehl_Figure 2

 

In the coming weeks we will be sharing an edited version of the session for those who missed it. And stay tuned for more WebEx sessions in the future!

The Beginnings of Data Collection – The First Baby Steps in a Marathon

Data. Information. Data collection. Good data. Big data. Data-for-development.

More and more, data is becoming an important tool within the humanitarian world to aid project design and define programme objectives. Data allows for real-time monitoring and evaluation, adapting projects to changing circumstances, and ultimately making projects and initiatives more effective. Everyday it seems a new tool or platform is developed to collect, analyze, and visualize data. But, for those of us that aren’t as experienced as the techies developing these (cool) tools, navigating the data collection waters can be overwhelming. Decisions need to be made about what data to collect, how to collect it, and  how it will be used and shared.

Below is quick, three-step process to begin thinking about data collection. The questions are not intended to provide a comprehensive “how to guide,” but should instead begin to stimulate thinking about the data collection process.

1) Deciding what data to collect is the first step when thinking about data collection. It’s true that a myriad of tool exists to collect data from FrontlineSMS to Formhub to Data Winners to TextIt to RapidSMS, and it is difficult to know which tool to choose. However, choosing the right technology is not the first step. Instead, knowing what information is desired and how it will be used is the first, and moreover, most important step.

Questions to think about when deciding what data to collect?

  • Is a specific piece of information desired? (Structured data collection)
  • Do you want to conduct an interactive poll that modifies questions based on previous answers? This is known as the skip logic method.
  • Who will benefit from this information?
  • Are partners involved?

2) Figure out the logistics of the project. Like all project design, context matters and solutions need to be designed around the situation on the ground. Many times understanding the contextual environment is the difference between a successful initiative and a so-called “failure.” For example, designing a Smartphone app for Community Health Workers and then learning that continual electricity doesn’t exist nor an Internet connection, could have been easily avoided if research had been completed about the end-users. Thinking about the following questions will not only contribute to the project design but will also help decide the appropriate technology to choose later on in the process.

Logistical and context questions to ponder:

  • Do you want continual data collection? At what interval and frequency?
  • Who will be doing the data collection?
  • Small-scale? Large scale?
  • Is there infrastructure to support SMS? Internet connections? Electricity to charge phones?

3) Choosing the best technology for the situation. The final step when thinking about data collection is the technology selection, and this happens only after the project designer knows what data is wanted and understands the working environment. Choosing technology can be a slightly daunting task as many tools and platforms exist. Answering a few questions will help guide the selection process.

Questions to help think about when making tech choices:

  • SMS or smartphone? Web? Interactive voice response (IVR)? Excel? (A useful list for SMS pros and cons is below.)
  • Which vendor to choose?
  • If a partner is involved will platforms be compatible?
  • Is an interactive feedback loop desired?
  • Do you want to visualize data and conduct analysis?
  • Would a cloud based system be suitable?

Pros and Cons to SMS outlined by Matt Berg:

Pros:

  • Any phone
  • Any network (no data required)
  • Messages queued (don’t drop messages when out of network or phone is dead)
  • Toll-free (defray cost of end-user but difficult to set-up)
  • Effective for monitoring. Users can trained to effectively use structured SMS
  • East to broadcast. Good for reminders/alerts

Cons:

  • Data quality / User error
  • Best effort delivery (message occasionally drop)
  • Not ideal for larger surveys
  • Literacy
  • Cost (high vs. data on wifi)
  • Data security

A multitude of data collection tools exist, and in order to choose the correct one understanding what is desired from the data collection is the first step before researching the tech landscape to make informed decision.

At the end of the day, data is supposed to enhance decision making by providing information that was previously unknown. Despite all of the various tools and methods for data collection, we should remember to strive for common data, and ultimately common knowledge. Data collection is a very powerful tool, and creating common awareness around the basics of the collection process is crucial if data is to have maximum impact in the humanitarian world.

Source:

“Getting to Common Awareness.” Matt Berg. Presentation given for T4D Capacity Building Workshop in Nairobi, Kenya. October 2013.