Application Design 1 - Task 2: UI, UX, IXD Design Document

21.10.2025 - 18.11.2025 / Week 5 - Week 9

Brenda Wynn / 0372128

Application Design 1 / Bachelors of Design (Hons) in Creative Media / Taylor's University

Task 2

JUMP LINKS

LECTURES

Week 5 - Week 6

User Interviews

= A process to understand the users behavior, needs, and attitude by observing and collecting feedback.

Why UX Research?

1. Provides insights from targeted users;

2. Makes designing process more efficient;

3. Creates connection and understanding with the users.

UX Design Roles and UX Researcher Duties

Figure 1.1 UX design roles and UX researcher duties

How to do UX research properly=
1. Involve the targeted users;
2. Gain and listen to users feedback;
3. Consider all of the different user perspectives;

4. Engage with the users.

Figure 1.2 UX research steps

UX Research Methods=

1. Qualitative

- Provides descriptive data which is analyzed to identify patterns and used to explore user needs.

Exp= Interviews & observation, User groups, Guided card sorting, and Usability testing.

2. Quantitative

- Provides numerical data which is analyzed to validate design decisions and used to measure usability & gather feedback.

Exp= Online surveys, Unguided card sorting, Web/App analytics, and Eye-tracking test.

Concept to Launch Process=

1. Aligning the design directions with the users' needs;

2. Early research to validate concepts;

3. Testing prototypes;

4. Gathering Feedback;

5. Revise/adjust product;

6. Final adjustments based on feedback;

7. User feedback/satisfaction towards the product.

Week 7

UI/UX Design Document Content:

1. Survey and Interview;

2. User Persona;

3. Card Sorting;

4. Information Architecture Map;

5. User Journey Map;

6. User Flow Chart.

User Persona(to represent a group of users) Purpose:

1. To understand users' needs for problem statement creation;

2. To guide design decisions.

User Personas' Influence Towards Product Decisions:

1. Allows the design of the product to be align with the users' needs;

2. Understanding the users' pain points keeps them engaged;

3. Controls the prioritization of the features.

User Persona Qualities and Effectiveness:

1. Utilize interview and survey data;

2. Avoid creating personas based of assumptions;

3. Prioritize relevance;

4. Focus on the users principles and reasonings.

Figure 1.3 Design thinking(empathy) key components

What to include in User Persona?

1. Demographic information;

2. Personality traits;

3. Goals and objectives;

4. Behavioral information;

5. Needs and Pain Points;

6. Scenarios and use cases;

7. User quotes.

Week 8

User Journey Map:

1. Provides visual representation on how a user achieve a goal;

2. Encourages designers and developers to consider the users' experience;

3. Creates empathy to understand the users' more;

4. Identifies pain points users' face when using the product.

User Journey Map Values:

1. Define what the users' might feel;

2. Understand the users' behavior;

3. Identify the steps users' do to achieve a goal;

4. Define the order of the steps;

5. Identify the functionality needs to achieve the goal;

6. Define what needs to be mindful of on the steps;

7. Create a visualization of the product.

User Journey Map Examples

Figure 1.4 User journey map example 1

Figure 1.5 User journey map example. 2

User Journey Maps Creation Criteria:

1. Identify the personas;

2. Identify the tasks to do the journey;

3. Identify the role;

4. Sketch the visualization;

5. Sketch/ write the steps;

6. Create it digitally.

Week 9

Site Map

= A footprint that shows how each page relates to the web/app's hierarchy and how it will guide the users' attention & organize it's content.

Figure 1.6 Site map examples

How to create a Site Map?

1. Visualization of the web/app's content organization;

2. Boxes represents the content;

3. Arrows or lines are used to show the relationship between pages;

4. Card sorting is used to create a logical organization.

User Flow

= A user's step by step journey from start to finish to achieve a goal.

What is a User Flow?

1. Visual representations of how interactions will work in the web/app;

2. To help reach a goal more efficiently;

3. Focuses on specific actions users do to complete a task;

4. Different paths are provided depending on the users' choices;

5. It helps designers understand how users interact with the product and identify the issues faced.

Why User Flow?

1. Shows the sequence of how the users' navigate through the web/app, which can help designers improve the flow;

2. Identifies potential pain points the users' might face;

3. Acts like a visual language for the developers to understand;

4. Can be utilized to create certain scenarios for testing;

5. To identify areas that needs refinement.

How to create a User Flow?

1. Research on targeted users;

2. Identify the purpose and goals;

3. Create the possible steps for an efficient design process;

4. Create the user flow;

5. Review and revise.

Shapes Representations in User Flows

Figure 1.7 Shapes representation in user flows

BACK TO TITLE

INSTRUCTIONS

BACK TO TITLE

TASK

TASK 2 - APPLICATION DESIGN 1

WORK SPACE

FigJam Board

BACK TO TITLE

FEEDBACK

Week 6

Mr. Sylvain told me to not mention the application directly at the start of the interview and guided me on how I should create the interview questions.

Week 7

Mr. Sylvain suggested me to revise some of the survey questions to gain more valuable insights.

BACK TO TITLE

REFLECTION

During the period of finishing task 2, I have learnt how to properly do research before developing or creating an app. I realized how important it is to do research before creating an app for designers. Through this task, I noticed that I tend to understand quite slowly, it takes one point and another point for me to realize the correlation between the content of the research. However, I don't think that it is that big of a problem since I end up figuring it out step by step. The time taken to finish this task made me learn much more about the importance of research and how it takes part for the future steps of application creation or development.

BACK TO TITLE