Statement
P02 Experience is also functionality
If it works but wears you down, it does not yet work well.
Tension
Explanation
Two products may deliver the same outcome and leave their users in very different states: one with the energy to continue, the other with doubts, errors, and the desire to give up. That toll rarely appears in a technical specification.
Go deeper: Tension
Two products can deliver the same result and yield different levels of performance. A burdensome experience causes abandonment, errors, dependence on support and loss of trust. That cost is functional, even though it does not appear in the technical specification.
Meaning
Explanation
A product's outcome includes how much effort, uncertainty, and attention it takes to obtain it. If something works but wears people down, it still does not work well.
Go deeper: Meaning
A product is not defined solely by the accuracy of its output. How much effort, uncertainty and attention it demands in order to obtain that output also matters. Whether the experience feels fluid or frustrating alters a person's real capacity to complete their work.
Consequence
Explanation
Effort, clarity, and trust are part of the acceptance criteria, just as accuracy is. The complete journey is tested, not each screen separately.
Go deeper: Consequence
Include effort, clarity and trust within the acceptance criteria.
Test the complete flow, not just each screen or endpoint in isolation.
Consider the emotional and cognitive state that accompanies the situation defined by the product and, where one exists, by the Job Story.
Example
Two search engines return the same results. One immediately shows why each result matches; the other forces people to open them one by one to find out. Both are accurate; only one saves the work of verifying.
Counterexample
Considering a requirement fulfilled because all the text is technically available, even though reaching it requires struggling with navigation, typography, or motion.
Sign of non-compliance. A technically valid form that wipes the data after an error turns correction into punishment. The validation works; the experience does not.
Decision test
These questions measure what a technical test does not see: the cost of using the product.
Can the person concentrate on their objective, or must they manage the tool?
Which moments provoke doubt, tension or interruption?
Does a task done correctly leave the user with energy to carry on?
Source
Manifesto core v2.1, section PRINCIPLE 2 · P02. Download the core