Interaction Design: Understanding objective-oriented design

I. Goal-oriented design

1. understand users' expectations, needs, motivations, and usage situations, better understand users' goals, and how these goals help design appropriate interactions.

2. Identify user goals-focus on user goals rather than the tasks to be completed by users.

3. Design Process Overview:

Research -------> modeling ------> definition requirement ------> definition framework ------> Design refinement ------> Design Support

1) Research: defines the project scope, objectives, and calendar; interviews with stakeholders to understand product prospects and restrictions;

2) Modeling: character roles, users, and customer models;

3) requirement definition: A scenario script (a story about the ideal user experience) describes the product requirements (the capabilities required by the product ), such as functional requirements, data requirements, user psychological models, design requirements, product prospects, business needs, and technologies;

4) design framework: defines how information and functions are presented, designs the overall architecture of user experience, and describes the interaction between character roles and products;

5) design refinement: detailed and specific (appearance, interface, behavior, information, and visualization );

6) Design Support: design corrections maintain the integrity of design concepts when technical constraints change.

Note: The Key to product success is the goal, not the feature.

 

II. Implementation Model and Psychological Model

Implementation Model --------------------> Presentation Model -----------------> Psychological Model

(Reflection technology) <---- poor ------- performance model -------- better ----> reflects users' imagination

 

Design principle: the user interface should be based on the user's psychological model rather than the implementation model. The target-oriented interaction reflects the user's psychological model.

 

3. New users, experts, and intermediate users

Most users are neither new users nor experts.Intermediate user.

Design Principle: no one is willing to stay at the beginner level.

Designed for different experience levels: optimized for intermediate users.

Converting a novice user into an intermediate user requires special help from the program. Once an intermediate user becomes an intermediate user, this help will in turn impede the user. This means that no matter what kind of help you provide, it should not be fixed in the interface. This help should disappear when you no longer need this service.

The features you provide for expert users must also be supported by new users. But more importantly, you must design a majority of your talents, time, and resources for a majority of representative users-permanent intermediate users to provide them with the best interaction.

4. Understanding users: Qualitative Research

Types of qualitative research:

1) Interview with stakeholders

2) interview subject expert

3) Interview with users and customers

4) user observation/race science field research (aims to understand the behavior and habits of people interacting with personal products)

5) Literature Research

6) Product/prototype and competitive review

 

V. Modeling for users: roles and objectives

When you expand the features of any product, it will increase the cognitive burden and navigation costs for all users. The ability to enjoy features of some users may reduce the satisfaction of other users.

1) determine who the product is designed, and sort the product priorities. (If you do not know the user well, the product features are not clearly positioned)

2) for designers,EmpathyCritical. (Actors in the movie will useExperience school performancesIt is very effective to understand and shape the actual characters.) ---- designers need to transform roles thoroughly and assume they are typical users;

3) The role must have motivation: understanding the reason the user executes the task enables the design to improve or even eliminate some tasks, while still achieving the goal.

4) Goal: One of the most critical tasks for modeling a person's role is to confirm the goal and express it concisely. Each goal should be expressed in a simple sentence.

5) design the [experience goal] For the instinct response and the behavior hierarchy (improve the user's own behavior, the implied assumptions and the Product Behavior of the Psychological Model) [ultimate goal], reflecting on design [goal of life]

6) experience goals are related to instinctive processing, that is, what the user wants to feel;

7) the final goal is related to the behavior processing process, that is, what the user wants to do;

8) the goal of life is related to the process of reflection, that is, what the user wants to be.

9) construct a role:

Step 1: Discover and determine behavior variables (such as activities, attitudes, abilities, motivations, and skills)

Step 2: map the access object and the behavior variable (those access objects have the behavior variables and gradually correspond to them)

Step N: specify the role type (priority): primary role, secondary role, and supplementary role;

Design Principle: each interface is designed to focus on a single primary role.

 

Vi. Design Basics: Scenario scripts and requirements

Use Case: describes how users interact with the system

Before designing the "how" behavior of a product, you must define what the product performs ".

In the early stages of design, we assume that the interface has a magic effect. ---- Personal understanding: do not be subject to technical constraints in the early stages of design, and assume that technology is omnipotent.

Determine the need: determine the need from the context script. For example, "call a number (Action) directly from the appointment record (Situation) to a person (object )". The requirement description should include data requirements, functional requirements, and other requirements (business requirements, technical requirements, brand and experience requirements, customer and partner needs ).

 

VII. From demand to design: Framework and refinement

1) define the interaction framework: shape, input, function groups and layers, and outline the interaction framework;

2) define the visual design framework:

3) refine the shape and behavior:

4) design verification and availability testing: