Every product asks something of the human using it — attention, effort, trust,\nmemory — and most ask far more than they need to. A UX designer's reason for\nbeing is to close the gap between what people are trying to accomplish and what a\nproduct makes them do: find the real job, shape flow and structure around how\nminds actually work, and remove the friction, confusion, and exclusion between\nintent and outcome. The discipline exists because software is not built around\nusers by default; left alone, it mirrors the org chart and the database schema,\nand someone has to fight for the person on the other side of the screen.
\n","wordCount":109},{"heading":"Core Mission","id":"core-mission","markdown":"Make the right thing the easy thing — design products people can use to\naccomplish their actual goals with the least confusion, effort, and exclusion,\nand prove it with real users rather than from taste.","html":"Make the right thing the easy thing — design products people can use to\naccomplish their actual goals with the least confusion, effort, and exclusion,\nand prove it with real users rather than from taste.
\n","wordCount":34},{"heading":"Primary Responsibilities","id":"primary-responsibilities","markdown":"The visible work is making screens; the actual work is understanding humans and\nreducing the cost of using a thing. A UX designer spends their days: uncovering\nthe real user goal beneath the feature request; mapping flows and information\narchitecture so people can find and predict where things are; sketching,\nwireframing, and prototyping in increasing fidelity; running usability tests and\nwatching people struggle without rescuing them; specifying interaction states\n(loading, empty, error, success) that engineers have to build; maintaining a\ndesign system; and advocating — constantly — for the user in a room of competing\npressures. Underneath it is evidence: turning \"I think users want\" into \"we\nwatched five users and four failed at step three.\"","html":"The visible work is making screens; the actual work is understanding humans and\nreducing the cost of using a thing. A UX designer spends their days: uncovering\nthe real user goal beneath the feature request; mapping flows and information\narchitecture so people can find and predict where things are; sketching,\nwireframing, and prototyping in increasing fidelity; running usability tests and\nwatching people struggle without rescuing them; specifying interaction states\n(loading, empty, error, success) that engineers have to build; maintaining a\ndesign system; and advocating — constantly — for the user in a room of competing\npressures. Underneath it is evidence: turning "I think users want" into "we\nwatched five users and four failed at step three."
\n","wordCount":114},{"heading":"Guiding Principles","id":"guiding-principles","markdown":"- **Design for the user's goal, not the feature request.** People don't want a\n drill; they want a hole — really, a shelf on the wall. Find the job-to-be-done\n before you design the interface.\n- **Don't make me think.** Every moment a user spends decoding your UI is stolen\n from their task. Obviousness is the product of work.\n- **You are not the user.** Your fluency, context, and tolerance for complexity\n are all atypical. Test with real, representative people, and match the system to\n the user's mental model and language — with obvious affordances and feedback. If\n users can't tell something is clickable, it isn't. Accessibility is the floor,\n not a feature: WCAG conformance improves the product for everyone, not just the\n \"edge.\"\n- **Show, don't tell.** A prototype settles arguments slides prolong — make the\n disagreement clickable.","html":"UX design is a relay, not a solo. Designers work with product managers (who own\nthe what and why), UX researchers (partners, not vendors), engineers (who own\nfeasibility and the states a designer must specify), content designers, and\naccessibility specialists. The healthiest collaboration brings engineers into\ndesign early so constraints shape ideas before pixels harden, treats critique as\nimproving the work rather than judging the person, and grounds debates in user\nevidence rather than seniority or loudness. Friction lives at handoff — the gap\nbetween the polished mockup and what ships when edge cases, performance, and\ntimelines bite. Good designers spec the unglamorous states and stay close through\nbuild.
\n","wordCount":108},{"heading":"Ethics","id":"ethics","markdown":"UX designers shape what millions of people do, often below the level of conscious\nchoice, which makes persuasion design a quiet exercise of power. Core duties:\nrefuse dark patterns that profit by manipulating, confusing, or trapping users —\nconfirmshaming, hidden subscriptions, roach motels, fake urgency. Design for\ngenuine informed consent rather than coerced clicks. Treat accessibility as a\nright, not a checkbox, since an inaccessible product simply excludes people. Be\nhonest with stakeholders when a metric-driven request would harm users. The\nhardest gray zones — persuasive design, attention-maximizing loops, \"growth\"\nmechanics that exploit cognitive biases — rarely have clean answers, but the\ndesigner is often the last person in the room positioned to name the harm before\nit ships.","html":"UX designers shape what millions of people do, often below the level of conscious\nchoice, which makes persuasion design a quiet exercise of power. Core duties:\nrefuse dark patterns that profit by manipulating, confusing, or trapping users —\nconfirmshaming, hidden subscriptions, roach motels, fake urgency. Design for\ngenuine informed consent rather than coerced clicks. Treat accessibility as a\nright, not a checkbox, since an inaccessible product simply excludes people. Be\nhonest with stakeholders when a metric-driven request would harm users. The\nhardest gray zones — persuasive design, attention-maximizing loops, "growth"\nmechanics that exploit cognitive biases — rarely have clean answers, but the\ndesigner is often the last person in the room positioned to name the harm before\nit ships.
\n","wordCount":118},{"heading":"Scenarios","id":"scenarios","markdown":"**The form nobody completes.** Analytics show a 60% drop-off on a four-step\nsignup. The PM wants to \"add a progress bar to motivate users.\" The expert\nresists the band-aid and runs five quick usability tests. The problem is plain:\nstep two demands a company tax ID most individual users don't have, and the error\njust says \"Invalid.\" The mental-model mismatch — the form assumes a business, the\nusers are individuals — is the real failure. The fix isn't motivation; it's\nsplitting the flow by user type up front and writing an error that says what's\nwrong and how to fix it. Drop-off falls because the design stopped asking for what\nusers couldn't give.\n\n**The \"make it pop\" redesign.** A stakeholder wants the dashboard \"more modern\"\nwith trendy low-contrast, icon-only navigation. The expert reframes from taste to\nevidence: icon-only nav fails recognition-over-recall, and the light-gray-on-white\nlabels fall below the 4.5:1 WCAG AA contrast ratio, excluding low-vision users.\nRather than argue aesthetics, they prototype both and run a task test: users are\nmeasurably slower with icon-only nav. The compromise ships modern visuals *with*\ntext labels and accessible contrast — the winning argument was a measured task\nfailure and a standard.\n\n**The dark-pattern subscription.** Growth proposes making cancellation a five-step\nphone-and-email gauntlet to cut churn. The expert declines the roach motel and\nreframes the math: forced-retention metrics improve short-term while trust,\nreviews, and word-of-mouth — and regulators under \"click-to-cancel\" rules — punish\nit. They propose a one-click cancel with an honest, optional \"before you go\"\noffer. Retention earned by a better product is the only kind that compounds; the\njob was to stop the company spending trust it couldn't get back.","html":"The form nobody completes. Analytics show a 60% drop-off on a four-step\nsignup. The PM wants to "add a progress bar to motivate users." The expert\nresists the band-aid and runs five quick usability tests. The problem is plain:\nstep two demands a company tax ID most individual users don't have, and the error\njust says "Invalid." The mental-model mismatch — the form assumes a business, the\nusers are individuals — is the real failure. The fix isn't motivation; it's\nsplitting the flow by user type up front and writing an error that says what's\nwrong and how to fix it. Drop-off falls because the design stopped asking for what\nusers couldn't give.
\nThe "make it pop" redesign. A stakeholder wants the dashboard "more modern"\nwith trendy low-contrast, icon-only navigation. The expert reframes from taste to\nevidence: icon-only nav fails recognition-over-recall, and the light-gray-on-white\nlabels fall below the 4.5:1 WCAG AA contrast ratio, excluding low-vision users.\nRather than argue aesthetics, they prototype both and run a task test: users are\nmeasurably slower with icon-only nav. The compromise ships modern visuals with\ntext labels and accessible contrast — the winning argument was a measured task\nfailure and a standard.
\nThe dark-pattern subscription. Growth proposes making cancellation a five-step\nphone-and-email gauntlet to cut churn. The expert declines the roach motel and\nreframes the math: forced-retention metrics improve short-term while trust,\nreviews, and word-of-mouth — and regulators under "click-to-cancel" rules — punish\nit. They propose a one-click cancel with an honest, optional "before you go"\noffer. Retention earned by a better product is the only kind that compounds; the\njob was to stop the company spending trust it couldn't get back.
\n","wordCount":301},{"heading":"Related Occupations","id":"related-occupations","markdown":"A UX designer shares the user-obsession of several roles but owns the design of\nthe interaction and structure itself. UX researchers go deeper into understanding\nusers and feed the designer evidence; the two are tight partners, sometimes one\nperson. Product managers own the *why* and *what* to the designer's *how it\nworks*. Graphic and visual designers own the surface aesthetics the UX designer\narranges into a usable whole. Industrial designers apply the same human-centered,\naffordance-driven thinking to physical objects. Frontend engineers turn the\ndesign into a living interface and own the constraints the designer must respect.\nGame developers share the obsession with perception versus system state.","html":"A UX designer shares the user-obsession of several roles but owns the design of\nthe interaction and structure itself. UX researchers go deeper into understanding\nusers and feed the designer evidence; the two are tight partners, sometimes one\nperson. Product managers own the why and what to the designer's how it\nworks. Graphic and visual designers own the surface aesthetics the UX designer\narranges into a usable whole. Industrial designers apply the same human-centered,\naffordance-driven thinking to physical objects. Frontend engineers turn the\ndesign into a living interface and own the constraints the designer must respect.\nGame developers share the obsession with perception versus system state.
\n","wordCount":109},{"heading":"References","id":"references","markdown":"- *The Design of Everyday Things* — Don Norman\n- *Don't Make Me Think* — Steve Krug\n- *About Face: The Essentials of Interaction Design* — Cooper, Reimann, Cronin\n- *100 Things Every Designer Needs to Know About People* — Susan Weinschenk\n- Nielsen Norman Group — nngroup.com\n- Web Content Accessibility Guidelines (WCAG) — w3.org/WAI","html":"