Skip to content

User Experience Design

← All revisions

b11554c0 · PointSav Digital Systems ·

Heading heal (documentation): insert 216 section headings on 33 heading-sparse articles (EN+ES, insertion-only, no prose change, ~90-150 w/h band)

View the full record as of this revision →

@@ -26,6 +26,8 @@ keynote: false

User experience design (UXD, UED, or XD) is the process of defining the experience a user would have when interacting with a company, its services, and its products. UX design is characterized by a user-centered approach in which research data, user testing results, and observed behavior drive decisions rather than aesthetic preferences or feature assumptions. The discipline encompasses all aspects of a user's perceived experience — usability, usefulness, desirability, brand perception, and overall performance — and extends to the full scope of customer experience (CX) beyond the immediate product interaction.

## Distinction from user interface design

The breadth of UX design sets it apart from [[user-interface-design|user interface design]]. UI design is concerned with the visual and interactive surface — what an interface looks like and how it physically responds. UX design is concerned with the total experience a person has: the cognitive model they form of the system, the emotional response they have to using it, the ease with which they accomplish their goals, the error recovery they experience when things go wrong, and the satisfaction or frustration they feel after completing a task. A well-designed UI can be embedded within a poor UX (a beautiful interface for a product that doesn't solve the user's actual problem); conversely, a high-quality UX can be delivered through an interface that is visually undistinguished.

## History
@@ -38,18 +40,26 @@ The proliferation of personal computers in workplace environments through the 19

## Elements

### User research and personas

**User research.** UX design begins with research: understanding who the users are, what goals they have, what tasks they need to accomplish, and what context they work in. Research methods include ethnographic field observation, contextual inquiry, interviews, surveys, and analytics analysis. User research seeks to discover users' actual behaviors and motivations — which often differ substantially from what users report in surveys or what product teams assume.

**User modeling and personas.** Research findings are synthesized into persona documents — composite archetypes based on observed behavior patterns across a user research sample. Personas are not real people but representative profiles: a persona document describes a user type's goals, frustrations, technical sophistication, and context of use. Personas help design teams maintain focus on user needs when making design decisions.

### Visual design and information architecture

**Visual design.** The visual layer of UX design draws on graphic design, communication design, and the principles of Gestalt psychology (the study of how humans perceive visual information as organized patterns rather than collections of individual elements). Visual design establishes the aesthetic qualities that make an interface attractive, trustworthy, and coherent.

**Information architecture.** Information architecture is the art and science of organizing and labeling information to support usability and findability. It encompasses the navigation model, the hierarchy of content, the labeling system, and the search functionality that enable users to locate what they need within a system. Information architecture sits between knowledge management and data management — it is concerned with how information is structured for human retrieval, not merely machine processing.

### Interaction design and usability

**Interaction design (IxD).** Interaction design is concerned with creating products that produce efficient and satisfying end-user experiences. Interaction designers specify the behavior of the system — how it responds to user input, what feedback it provides, how it handles errors, and how it guides users through sequences of actions. Interaction design overlaps with visual design in the design of controls and feedback indicators, and with industrial design in the design of physical interfaces.

**Usability.** Usability is the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use. Usability is a component of UX but not wholly contained within it — a product can be usable (users can accomplish their goals) while still delivering a poor experience (the process is frustrating, the feedback is confusing, or the outcome fails to satisfy). Usability testing is the most common formal method of assessing usability: users are given tasks to complete while a researcher observes and records their process, paying attention to where they hesitate, err, or abandon the task.

### Accessibility and HCI foundations

**Accessibility.** Accessibility addresses the ease with which products can be used by people with disabilities — visual, auditory, motor, or cognitive. The Web Content Accessibility Guidelines (WCAG) 2.0, published by the World Wide Web Consortium, define accessibility requirements through four principles: Perceivable (information is presentable to users in ways they can perceive), Operable (interface components and navigation are operable), Understandable (information and operation of the interface is understandable), and Robust (content can be interpreted by a wide variety of user agents, including assistive technologies). These principles are known by the acronym POUR.

**Human-computer interaction (HCI).** HCI is the discipline that studies the design, evaluation, and implementation of interactive computing systems for human use and the major phenomena surrounding them. HCI provides the research base from which UX design draws its methods: experimental psychology, cognitive science, social science, and computer science contribute to an evidence base for design decisions.
Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. See TRADEMARK.md in this repository for the full trademark notice.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →