A Lesson from DHIS2 Implementations: Don't Design in a Vacuum

One thing I’m learning to value more through my work is the opportunity to visit different sites and see how people actually work.

These experiences are changing the way I think about DHIS2 implementations.

Whether we’re designing data entry forms, configuring metadata, building dashboards, or implementing new features in DHIS2, the principle is the same:

The best solutions start with understanding the people who use them.

Some of the most valuable insights don’t come from a dashboard or a requirements document. They come from observing workflows, listening to users, and understanding the realities of their day-to-day work.

I recorded a short reflection on this idea, and I’d love to hear what others in the community think.

:movie_camera: YouTube:

Discussion

Has spending time with end users ever changed the way you approached a DHIS2 implementation?

3 Likes