3.1 Research Goal
Research Goal is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
Step by step
- Define the user problem connected to Research Goal.
- Collect evidence before jumping to a polished solution.
- Create the smallest flow, sketch, wireframe, prototype, or test needed to answer the question.
- Test the design with realistic content, states, and device constraints.
- Record what you learned and change the design based on evidence rather than preference.
10 practical examples
- Apply Research Goal to a course website and explain the decision you made.
- Apply Research Goal to a online store and explain the decision you made.
- Apply Research Goal to a banking app and explain the decision you made.
- Apply Research Goal to a school portal and explain the decision you made.
- Apply Research Goal to a clinic booking system and explain the decision you made.
- Apply Research Goal to a dashboard and explain the decision you made.
- Apply Research Goal to a restaurant site and explain the decision you made.
- Apply Research Goal to a mobile app and explain the decision you made.
- Apply Research Goal to a creator site and explain the decision you made.
- Apply Research Goal to a business landing page and explain the decision you made.
Hands-on example
UI/UX PRACTICE
Problem: A user struggles with Research Goal.
Evidence to collect: interview, observation, analytics, or usability result.
Artifact: flow, sketch, wireframe, prototype, or test plan.
Success measure: task completion, clarity, error reduction, or satisfaction.
Next step: test one assumption.Expected output
A user-centered design artifact for Research Goal plus a clear statement of what evidence would confirm or reject the design decision.
Practice exercise
Create a fresh example for Research Goal using a different product, screen, component, or content set. Explain what changed and why.
3.2 Research Questions
Research Questions is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
Step by step
- Define the user problem connected to Research Questions.
- Collect evidence before jumping to a polished solution.
- Create the smallest flow, sketch, wireframe, prototype, or test needed to answer the question.
- Test the design with realistic content, states, and device constraints.
- Record what you learned and change the design based on evidence rather than preference.
10 practical examples
- Apply Research Questions to a course website and explain the decision you made.
- Apply Research Questions to a online store and explain the decision you made.
- Apply Research Questions to a banking app and explain the decision you made.
- Apply Research Questions to a school portal and explain the decision you made.
- Apply Research Questions to a clinic booking system and explain the decision you made.
- Apply Research Questions to a dashboard and explain the decision you made.
- Apply Research Questions to a restaurant site and explain the decision you made.
- Apply Research Questions to a mobile app and explain the decision you made.
- Apply Research Questions to a creator site and explain the decision you made.
- Apply Research Questions to a business landing page and explain the decision you made.
Hands-on example
UI/UX PRACTICE
Problem: A user struggles with Research Questions.
Evidence to collect: interview, observation, analytics, or usability result.
Artifact: flow, sketch, wireframe, prototype, or test plan.
Success measure: task completion, clarity, error reduction, or satisfaction.
Next step: test one assumption.Expected output
A user-centered design artifact for Research Questions plus a clear statement of what evidence would confirm or reject the design decision.
Practice exercise
Create a fresh example for Research Questions using a different product, screen, component, or content set. Explain what changed and why.
3.3 Methods
Methods is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
Step by step
- Define the user problem connected to Methods.
- Collect evidence before jumping to a polished solution.
- Create the smallest flow, sketch, wireframe, prototype, or test needed to answer the question.
- Test the design with realistic content, states, and device constraints.
- Record what you learned and change the design based on evidence rather than preference.
10 practical examples
- Apply Methods to a course website and explain the decision you made.
- Apply Methods to a online store and explain the decision you made.
- Apply Methods to a banking app and explain the decision you made.
- Apply Methods to a school portal and explain the decision you made.
- Apply Methods to a clinic booking system and explain the decision you made.
- Apply Methods to a dashboard and explain the decision you made.
- Apply Methods to a restaurant site and explain the decision you made.
- Apply Methods to a mobile app and explain the decision you made.
- Apply Methods to a creator site and explain the decision you made.
- Apply Methods to a business landing page and explain the decision you made.
Hands-on example
UI/UX PRACTICE
Problem: A user struggles with Methods.
Evidence to collect: interview, observation, analytics, or usability result.
Artifact: flow, sketch, wireframe, prototype, or test plan.
Success measure: task completion, clarity, error reduction, or satisfaction.
Next step: test one assumption.Expected output
A user-centered design artifact for Methods plus a clear statement of what evidence would confirm or reject the design decision.
Practice exercise
Create a fresh example for Methods using a different product, screen, component, or content set. Explain what changed and why.
3.4 Participants
Participants is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
Step by step
- Define the user problem connected to Participants.
- Collect evidence before jumping to a polished solution.
- Create the smallest flow, sketch, wireframe, prototype, or test needed to answer the question.
- Test the design with realistic content, states, and device constraints.
- Record what you learned and change the design based on evidence rather than preference.
10 practical examples
- Apply Participants to a course website and explain the decision you made.
- Apply Participants to a online store and explain the decision you made.
- Apply Participants to a banking app and explain the decision you made.
- Apply Participants to a school portal and explain the decision you made.
- Apply Participants to a clinic booking system and explain the decision you made.
- Apply Participants to a dashboard and explain the decision you made.
- Apply Participants to a restaurant site and explain the decision you made.
- Apply Participants to a mobile app and explain the decision you made.
- Apply Participants to a creator site and explain the decision you made.
- Apply Participants to a business landing page and explain the decision you made.
Hands-on example
UI/UX PRACTICE
Problem: A user struggles with Participants.
Evidence to collect: interview, observation, analytics, or usability result.
Artifact: flow, sketch, wireframe, prototype, or test plan.
Success measure: task completion, clarity, error reduction, or satisfaction.
Next step: test one assumption.Expected output
A user-centered design artifact for Participants plus a clear statement of what evidence would confirm or reject the design decision.
Practice exercise
Create a fresh example for Participants using a different product, screen, component, or content set. Explain what changed and why.
3.5 Ethics
Ethics is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
Step by step
- Define the user problem connected to Ethics.
- Collect evidence before jumping to a polished solution.
- Create the smallest flow, sketch, wireframe, prototype, or test needed to answer the question.
- Test the design with realistic content, states, and device constraints.
- Record what you learned and change the design based on evidence rather than preference.
10 practical examples
- Apply Ethics to a course website and explain the decision you made.
- Apply Ethics to a online store and explain the decision you made.
- Apply Ethics to a banking app and explain the decision you made.
- Apply Ethics to a school portal and explain the decision you made.
- Apply Ethics to a clinic booking system and explain the decision you made.
- Apply Ethics to a dashboard and explain the decision you made.
- Apply Ethics to a restaurant site and explain the decision you made.
- Apply Ethics to a mobile app and explain the decision you made.
- Apply Ethics to a creator site and explain the decision you made.
- Apply Ethics to a business landing page and explain the decision you made.
Hands-on example
UI/UX PRACTICE
Problem: A user struggles with Ethics.
Evidence to collect: interview, observation, analytics, or usability result.
Artifact: flow, sketch, wireframe, prototype, or test plan.
Success measure: task completion, clarity, error reduction, or satisfaction.
Next step: test one assumption.Expected output
A user-centered design artifact for Ethics plus a clear statement of what evidence would confirm or reject the design decision.
Practice exercise
Create a fresh example for Ethics using a different product, screen, component, or content set. Explain what changed and why.
Chapter 3 review — 10 questions and answers
1. What is the main purpose of Research Goal?
Answer: Research Goal is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
2. What is a common mistake with Research Goal?
Answer: Treating Research Goal as a visual preference instead of connecting it to a user need, constraint, or testable outcome.
3. What is the main purpose of Research Questions?
Answer: Research Questions is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
4. What is a common mistake with Research Questions?
Answer: Treating Research Questions as a visual preference instead of connecting it to a user need, constraint, or testable outcome.
5. What is the main purpose of Methods?
Answer: Methods is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
6. What is a common mistake with Methods?
Answer: Treating Methods as a visual preference instead of connecting it to a user need, constraint, or testable outcome.
7. What is the main purpose of Participants?
Answer: Participants is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
8. What is a common mistake with Participants?
Answer: Treating Participants as a visual preference instead of connecting it to a user need, constraint, or testable outcome.
9. What is the main purpose of Ethics?
Answer: Ethics is a UI/UX design skill that helps make products easier to understand, use, test, and improve. The method should be tied to a real user problem instead of decoration alone.
10. What is a common mistake with Ethics?
Answer: Treating Ethics as a visual preference instead of connecting it to a user need, constraint, or testable outcome.