- May 3, 2012
- Posted by: Kate Otto
- Category: Our Team
One of the best parts of Everyday Ambassadorship is shaking up the status quo with fresh perspective – and in my professional space of mHealth and eHealth, I get to see so much of this innovative thinking all the time.
Today, I was given the privilege of sharing some of the best insights I have gleaned from fieldwork so far on a new blog series called Disruptive Women in Health Care. The short article below features my ‘disruptive idea’, originally published online here.
I hope you will check out this series as it rolls out over the next two weeks, and even join the conversation. The site’s goal is to highlight programs that push for a more “sustainable, inclusive and equitable future,” a goal that resounds harmoniously with the Everyday Ambassador community. Thanks for reading and sharing! xo ko
What do you think is the key to a great mHealth tool?
Is it efficiency? Scalability? Interoperability with similar systems?
I would argue none of the above.
I would say that the key to a great mHealth tool is a great health worker at the helm.
My name is Kate Otto and I work with the World Bank and other partners to develop and test the effectiveness of mHealth tools on health outcomes. Based on two recent mHealth experiences – one with health extension workers (HEWs) in rural Ethiopia and another with midwives in urban Indonesia – I have noted a recurring lesson in this emerging field: that technology is not the solution itself but simply a means to arriving at a solution. The people behind the tools are what make the difference between success and failure.
Too often, the sleek and impressive nature of new technologies makes the headlines: how they solve all the problems that human beings tend to mess up so sorely, how they avoid any mishaps in the first place with a fool-proof design.
Yet the truth is, the success of mHealth tools and applications are based largely on the intrinstic motivation of the end user – and how tools can be designed to leverage, not stamp out, that motivation.
Our product in Ethiopia allows HEWs to register expecting mothers and newborns so that they receive back appointment reminders, creating a patient schedule for the HEW and increasing the likelihood that she’ll deliver the proper care at the proper time, ideally decreasing maternal mortality, increasing vaccinations, and decreasing infant and child mortality. But if a HEW does not deeply care about saving lives, if the tool does not work smoothly with her rugged lifestyle, if she cannot see the immediate benefit of using it over the status quo system, then will she take the effort to use it properly or consistently?
In Indonesia, it struck me that most midwives who helped developed the tool cared less about cutting data entry time from their day, and most about having quickly aggregated data fed back to them to compare across other neighborhoods: how did they compare and how could they improve performance? I can’t say I had initially thought to design a feedback report into the system – but it quickly became part of the plan.
I would encourage investors in mHealth to think of the investment not as one in technology, but as one in human capital – if you’re doing it right. This means spending extensive time iterating on design with end users, testing final models to ensure incentives are aligned across all partners, training providers and system administrators to work independently from a donor or innovator, and ensuring that the outcomes desired by the end users are being attained.
We must continue to invest in technology for health, but we must do so wisely: at the hand-holding the phone, and pay attention first to the people behind the tool.