Sometimes I create programs or physical gadgets. This is a checklist, based on experience, to help ensure the intended purpose is achieved. Create a branch named after what you're building, and delete any clutter you don't need (it can always be added later).
Remember: Don’t overdo it — we’re working with basic affordance and experience, not the final product (that’s for another branch).
An attempt to systematically verify that a function clearly expresses affordance, communicates the choice you are about to make, and ensures that your selected action is executed. The spirit of this repository is summed up in the line:
"When our brains fail; make one out of paper — in this case, digital."
— Me
A checklist's main intent is to keep you focused on what really matters.
In case of a motor stop in a single-engine plane, the first item states:
- Keep flying the plane.
The equivalent in usability should probably be something like:
- Do you really need this function?