Designed for Geneva, deployed in Gonaïves: the context problem in device design

A device is a bundle of assumptions: about power quality, ambient temperature, dust, humidity, consumable supply, user training, and how far away the nearest service engineer lives. Designers rarely list these assumptions, but every deployment tests them — and in much of the world, the assumptions fail before the hardware does.

Researchers studying device barriers in developing regions have catalogued the pattern for years: equipment engineered for climate-controlled, grid-stable, service-rich environments arrives somewhere hotter, dustier, and electrically wilder, and its failure curve bends accordingly. The device isn't badly made; it's well made for somewhere else.

The counter-movement is real and growing. Programs like NEST360 have shown what happens when newborn-care technology is selected and engineered specifically for African hospital conditions and paired with local biomedical capability — equipment that stays functional at rates that embarrass many imports. 'Rugged, repairable, and right-sized' is a design philosophy with receipts now.

What buyers and donors can do today: weight environmental tolerance, consumable independence, and repairability in selection decisions as heavily as clinical features. What the industry can do: publish the assumptions. A 'designed-for' disclosure — power range, temperature range, expected service infrastructure — would cost a paragraph and save millions in misdeployment.

Devices don't fail randomly across geographies. They fail where their designers never imagined them living. Imagining better is an industry-sized opportunity.