Application Design: Project 2_UI/UX Document

19 May 2025 - 26 July 2025

CHONG CHENG TAO (0371072)
Application Design | Bachelor of Design in Creative Media | Taylor's University
Project 2: UI/UX Document


List


LECTURES

Week 5

User Experience Research

"It's the process of UX research that matters, not the beauty of the final artifact." For our redesign, focus on who are the new audience to the "new" app. An app is better to have a niche target audience, rather than to all the public. 

User research is to understand user behaviors, needs and feelings. 


Roles of UX
  • Understanding user emotion during interaction. 
  • Reveal how user interact with the system and pain points.
  • Understand users' behavior, goals, motivations and needs.
  • Ensure the product is grounded. 

UX Research Duties
  • Develop coherent research methodologies.
  • Selecting and recruiting targeted end'users.
  • Conduct individual interviews.
  • Utilizing data analysis tools.
  • Collaborating with product team using the research data. 

    Steps of UX Research
    • Define objectives
    • Hypotheses & assumptions
    • Conisder methods
    • Conduct the research
    • Synthesize and address the knowledge gap. 

    UIUX Documents
    • Online survey
    • Interview
    • User persona
    • Card sorting
    • Flow chart
    *Good reserach come with the new asepct we didn't think about. 

    Interview
    • Explore attitudes, beliefs and experiences related to a product. 
    • Max 20 minutes. 
    • Observe both what user says and the body language or facial expressions. 
    • Do not push interviewee to answer. 
    • Ask open-ended questions. 
    • Design interview questions in a flow that gradually guiding the interviwees, from general to specific. 
    • Avoid leading question, do not assumes user has negative feelings about the features.

    Week 6

    Firstly, we will need to synthetize research from the interview. 

    We might have bias on some of the interviewee, thus the following steps are important:
    • Even it out, scatter the sources on the same level.
    • Spread information, give each info some spaces to see the big picture. 
    • Find pattern of the information.
    • Find outliers form the information.
    By doing these steps, we are able to:
    • Funnel the data down, reduce the volume.
    • Find the high trends but also the low, subdued trends that are not evident.
    • Find the root cause, similar ideas are put together will highlight insights.
    When do we synthetize:
    • Volumen is too high. 
    • Hard to grasp. 
    • Too long to navigate. 

    Affinity Mapping
    • Affinity mapping helps in finding patterns.
    • A research method to reveal themes and insights from large sets of qualitative data.

    Splitting Notes
    • Divide and rewrite the transcript.  
    • Controlled chaos. 
      • Use 1 color to represent each user (using 1 color for ourselves).
      • Bring together post that have share similar ideas, tones and feelings.
    • Split or merge groupings.
      • 5+, 3-4, 2, 1, 0
    • Putting names on group, sort by user insights and problem, not solution.

    User Personas (Min 3)
    • To create a relationship between the development team and the users. 
    • A user presona takes the most painful problems. 
    • Make personas normal and local, give them the pressure/motivations to do a actions.  
    • A user persona should include:
      • Profile picture
      • Quote
      • Bio
      • Wants & Needs
      • Frustrations
      • Brands (What the persona likes)
      • Social anchors
      • Relevant achors

    Mr. Sylvain gives us a exmaple on how to sort and create user persona. 

    Example of Splitting Notes and User Persona

    *Keep it chaos!!!

    Week 7

    User Scenario 
    • Illustrate the persona points
      • Put goals, needs and frustration together. 
    • Give context
    • Show the stakes
    • State the problem
    Make 2 story, scnerios with the app and without the app. 


    Building a scenario
    • Who is the persona?
    • What do they want?
    • Why do they want it?

    User Journey Map
    • Provide a visual representation of the steps an individual takes to achieve a goal. 
    • Use "face" to represent user emotion.
    • How to reduce low points and keep the high points.
    • Start from a draft journey map, add points into specific actions later, to determine the required improvements.  
    • Business objectives for the journey is significant. 
    • Opportunities: What can desginers do/propose to make the product better. 
    To do user journey map:
    1. Identify who is the persona
    2. Identify the goals, task and needs
    3. Emotional journey & functional journey
    4. Visualize with sketches
    1. Setting up:
      • Define what will be mapping
      • Define scenario
      • Define goals
      • State of the process
    2. Define phase
    3. List actions



    Legal User Journey Map

    *Some purpose negative can bring expectation and excitement. 
    *Always be aware when things go bad. 


    User Flow
    • Rounded square: Entry point / End point
    • Square: Steps / Action
    • Diamond: Decision (YES or NO)

    What is the paths for the product? 
    • The Happy Path
    • The Sad, Unhappy Path
      *Can have more than 1 entry point (e.g. external link, promotion...)
      *User journey can be a long period, user flow is a sequence of actions (microinteraction) at one specific period. 
      *Yes/No decision only. 


      Minumum Vuable Product (MVP)

      MoSCoW
      • MUST: Unique
      • SHOULD: Function and usable
      • COULD: Nice to have
      • WON'T: Not going to do
      Using MUST and SHOULD, make a 2x2 metrics:


      Week 9


      Ideation
      • The process of generating ideas and solutions. 
      • Divergent and Convergent thinking. 
      • Ideation can be expressed via graphical, written or verbal method. 

      Why Ideate
      • Stretch minds and re-frame the problem.
      • Explore new directions.
      • Step back from the literal approach.
      • Find features and solutions that address the root causes. 
      • Build collaboration with stakeholders.

      *Search for FEATURES, COMPETITIONS and TRENDS.

            INSTRUCTIONS

            This is the Module Information Booklet for this module: 



            Application Design: UI/UX Document


            Requirement

            After locking down their App concept and idea, students are now ready to proceed to UX design. The students are required to produce a comprehensive UX design document which will provide better directions for them to design the app. 

            Based on the information gathered in task 1, students will:
            • Determine and verify their target audiences.
            • Outline the content element of their app, and exercise card sorting method to achieve optimum information architecture.
            • Listing the app features and identifying the application Minimum Viable Product (MVP).
            • Create wireframes for main screens. 
            • Plan the user interaction and interactivity (Flow chart)

            Interview

            We were instructed by Mr. Sylvain to conduct 5 interviews with the potential user, each with 20+ minutes. Instead of getting into the detail features of the selected app, we were encouraged to understand the user and their life/ problems/opinions. 

            Interview requirement

            Interview questions


            Interview guide

            Here is the interview response


            Affinity Map


            From the interview transcript, I did the first draft sorting. 

            Affinity mapping

            Affinity map sorting


            User Journey

            For user journey map, I did 2 maps for different type of users: artists & fans (normal user). 

            User journey map 1

            User journey map 2


            MoSCoW, 2x2

            MoSCoW, 2x2


            User Flowchart 

            After reveiving feedback from Mr. Sylvain, I start with the user flow chart for the artist persona. 

            User flow (version 1) for artist persona: 


            For the refinement, sending clients the artwork would be the priority before posting it. Thus, the order of the flow on sending artwork to clients and posting it online should be changed.

            User flow (version 2) for artist persona: 




            Final Submission



            FEEDBACK

            Week 5

            General Feedback: 
            • Instead of getting into the detail features of the selected app, understanding the user and their life/ problems/opinions. 
            • Besides the app's weaknesses, try to analyze the strengths. 
            Specific Feedback: 
            • Considering a South-East Asia/Malaysia version of Pixiv app, try localizing the app. 

            Week 6

            General Feedback: 
            • Keep the process chaos. 
            Specific Feedback: 
            • -

            Week 7

            General Feedback: 
            • Use user journey map for non-technical people.
            • Normally, technical people (engineer etc... ) like user flow too.
            Specific Feedback: 
            • Try make journey map and user flow for both type of personas (artist and normal user). 
            • Make the user persona's quote stronger and more straight to the point. 
            • Combine persona 1 and persona 3, make another persona as the normal user. 

            Week 8

            General Feedback: 
            • 2x2 metrics table is important for creating MVP.
            Specific Feedback: 
            • Reconsidering the ads display problem, how to make user think "I WANT TO PAY FOR PREMIUM".

            Week 9

            General Feedback: 
            • -
            Specific Feedback: 
            • Combine the user flows for different actions into one flow for one persona.  


            <back to top>

            REFLECTIONS

            I thought receiving and organizing user responses would not be a hard thing. Hmmmm I think I wrong now. 

            Despite its hard and time consuming, I'm quite enjoying the process of interview and analyzing the user feedback. It offers insights from some angles you wouldn't think of. I really had some "WOW" moment during the interview I had never would think in this way if I never get in touch with the real user.

            Comments