What is the problem?
What is frustrating, slow, confusing, risky, or not working right now?
WANTS is my framework for turning frustration into a clearer product, research, or design decision. It starts with what people actually need, then moves toward a testable definition of success.
WANTS is simple on purpose. Each step forces the work to stay connected to the user, the aim, the real need, the test, and the outcome that would prove the solution actually helped.
What is frustrating, slow, confusing, risky, or not working right now?
What should the solution help people do, feel, understand, or decide?
What do users need in the moment: clarity, control, confidence, speed, safety, or trust?
What small version can be tested before the idea becomes expensive, risky, or permanent?
What would prove the solution worked in real behavior, not just in a presentation?
It keeps AERI and other projects grounded in human decisions instead of adding features just because they are technically possible.
It makes hidden assumptions visible: the goal, the human need, the boundary, the test, and the accountability standard.