A lot of well-meaning hackathons I've read about that tackle problems such as world health/hunger crisises usually look at how they can better disseminate vital information, such as where the nearest shelters/hospitals are, etc., which is usually done in a beautifully designed site/app. But I suspect that's of limited use to those in the impacted zones, not because they lack phones/computers (though...that's not a bad assumption)...but because an app/site is probably not much better than a printed poster...and the well-meaning developers lack access to information and real-time data that is essential for adding value to a digital versus paper product.
But focusing on payroll? I know the adage, "an army marches on its stomach" is centuries old (and similarly, the less old adage "Amateurs talk about tactics, but professionals study logistics")...but I don't think I would have ever zeroed on that as a pain point that was both potentially fatal to the greater mission and one in which software developers could easily tackle...and I wonder how such an insight could've been reached by the head developers if they were either working remotely, or relying on a non-programming administrator to convey the medical staffs' needs?
A post-mortem on this would be great :)