Why it is Hard to Identify Technical Research Problems in ICT4D and How to Make it Easier

My position is that a shortage of detailed and compelling prob- lem statements is the primary bottleneck that prevents most com- puter scientists from conducting research in ICT4D. While inter- esting problems exist, they are usually discovered via months of fieldwork, and there is little incentive to formalize and dis semi- nate problems for the benefit of other researchers. To addres s this bottleneck, I argue that we should create a prestigious venue for publishing problem descriptions, rather than problem solutions. I also propose that we establish problem-exchange websites to solicit problems from practitioners; organize structured design contests that aggregate knowledge in a problem area; and leverage the do- main knowledge of funding agencies in defining technical res earch problems.