Moja
If a user has to read a manual, the software is probably badly designed.
Moja came from a different conviction. Technology should simplify life, not complicate it.
The sentence sounds obvious. It is contradicted every day by software that demands a two-hour training session to accomplish a task the user previously did faster on paper.
I am involved in building moja-app, a platform designed to make digital tools genuinely reachable for organisations.
If a user has to read a manual, the software is probably badly designed.
The design rules
The function must explain itself
An interface that needs an explanation has already failed. The test is simple: someone who has never seen the screen should know what to do within ten seconds.
Fewer options, more decisions made
Every setting left to the user is a decision handed off to them. Most settings should have a good default and disappear.
Training is a symptom
When a rollout requires lengthy training, the user is almost never the problem. The design is.
Design for the person in a hurry
Real users are interrupted, tired and rushed. Software that only works for an attentive user does not work.
This standard comes from forty years of watching organisations buy excellent tools nobody uses. The gap between what software makes possible and what teams actually do with it is the most common and least measured waste in enterprise IT.
A question on this?
Describe the context in a few lines. I answer with a proposed angle, not a brochure.