Early in a discovery call, a product owner says the new claims tool "just has to be simple for adjusters." How should the Architect treat that statement?
Choose an answer to check it. Afterward, select any option to review its explanation.
Experience words such as simple, fast or seamless are preferences. Discovery treats them as a prompt to keep asking (what would make it feel not simple, what must never happen) until a bounded constraint the design can be measured against appears.
Writing the word down feels like capturing the requirement, but a preference gives the team nothing to build or test against. The constraint underneath it still has to be uncovered.
Hiding steps from users is not what an experience word asks for, and pattern choice follows from constraints such as predictability and error cost, not from a stakeholder's adjective.
It is tempting to treat simplicity as cosmetic, but the hidden constraints (latency, handoffs, failure behavior) shape the architecture itself, so deferring them lets the design inherit untested assumptions.
id q7c8621dae0