Over the course of this semester, we have looked at ICT4D from many angles. Each framework, case study and sector investigation that we were presented with provided a lesson or prescription for how an ICT4D project should be conducted or, more often, how it should not be conducted. With such a high proportion of ICT4D projects ending in failure, it is important to recognize the value of these failures and try to tease out the lessons to be learned, something that we focused on a lot in this class. One of the lessons that struck me the most from this course was the importance of communicating with the target population. In many cases where ICT projects fail, it seems that closer examination of the realities of day-to-day life in the recipient community would have been beneficial and could perhaps have saved the project. The best example is probably the infamous One Laptop Per Child project. Without implementing a pilot project, Negroponte was unable to get any feedback from the technology’s end-user. This meant that both the set up of the initiative and the laptops themselves were riddled with problems.
Obviously, hindsight is 20-20, and it can be very easy to look back on projects that have failed and point out what went wrong. However, in my opinion, attempting to provide a service that is either not needed or not applicable to the lives of the people you are trying to help is one of the worst ways to fail, because it is essentially a failure of arrogance. It’s these types of projects that cause some people to view ICT4D as condescending.
In one class we watched a Youtube video called “Top 7 Reasons Why Most ICT4D Fails”. In one part, a man talks about a trend in projects that try to help rural farmers by providing them with market information via text message, the idea being that awareness of price trends will allow the farmers to get the best price for their crops. On the surface, this sounds like a great idea. However, as the man points out, many agricultural products have to be sold exactly when they are ready. A tomato farmer cannot hold on to his tomatoes until the prices improve, he/she has to sell them when they are ripe. This example really stuck out to me, because as first glance I thought the project would really work. I think, more than anything else, this is the lesson that I will take away from the class. Listen to your end user. They know what they want, and they know what works.




