7월 17일 금요일
7월 17일 금요일
Friday, July 17
BrunchDongseok Lee
AI summary focused on the core points of the original article.
Cheap UX is not about saving budget; it is a way of pushing complexity onto users and employees.
Good situations to read this
When reviewing RFPs, feature lists, or screen design criteria for DX/AX projects
When you need to explain the causes of customer support inquiries, workarounds in spreadsheets used by frontline teams, or repeated redevelopment from a UX perspective
When you need to judge whether AI adoption will actually lead to productivity gains
The UX concerns stripped away early do not disappear; they move to other departments and users.
How the cost shifts
It is passed on as users’ time, customer support labor, complaint handling, and manual work by frontline teams.
A few years later, it comes back as a budget line for next-generation builds or redevelopment.
Especially in AX
If AI is attached without context and fails to solve the user’s task, it only increases the labor needed for review and correction.
Functional requirements are specific, but experience requirements often remain as vague sentences.
Warning signs
There are only expressions like "intuitive UI" or "user-friendly," with no success criteria.
It is not defined which users need to complete which tasks, and how easily they should do so.
When UX criteria are missing
A system is built with many functions but is difficult to actually use.
Users end up in customer support, and employees fall back on Excel and workaround processes.
A good experience is not complete just because a button works and data is saved.
Questions for user success
Can users find the feature?
Can they recover on their own when an error occurs?
Can they complete the task without customer support?
When organizational convenience clashes with user flow
If the DB structure, departmental structure, and security procedures are exposed on the screen as they are, users end up carrying the provider’s complexity.
The larger the DX/AX initiative, the more you need someone responsible for experience quality rather than just screen production.
What a UX PM should look at
Core tasks, failure points, reasons for frontline workarounds, and the essence of customer support inquiries
Screen experiences that allow users to trust and recover from AI results
The standard going forward
As AI increases the speed of output, the standards of the person judging experience quality become even more important.
This article helps us reconsider UX not as "making things look nice," but as a decision-making process that reduces organizational cost. In particular, when reviewing an RFP or an AX proposal, even the small habit of checking whether user tasks and failure-recovery criteria are placed next to the feature list can significantly change the direction of a project.