-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfinal-project.html
More file actions
75 lines (71 loc) · 10.3 KB
/
final-project.html
File metadata and controls
75 lines (71 loc) · 10.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<!DOCTYPE html>
<html>
<head>
<title>Portfolio Usability Research and Analysis | Kevin Phan</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="keywords" content="Portfolio Usability Research and Analysis">
<meta name="description" content="Kevin Phan - Software Engineering Student from UCI. I like making a difference and lending my skills.">
<meta name="author" content="Kevin Phan">
<link rel="icon" type="image/png" href="img/favicon.png">
<link rel="stylesheet" href="css/main.css">
<link href="https://fonts.googleapis.com/css?family=Roboto" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet">
<link rel="stylesheet" href="css/final-project.css">
</head>
<body>
<header class="heading col-12 col-md-12" >
<h1><a id="name-heading" href="index.html">Kevin Phan</a></h1>
<nav class="navigation-bar">
<ul id="navigation-buttons">
<li><a href="index.html#contact">Contact</a></li>
<li><a href="index.html#fun">Fun</a></li>
<li><a href="index.html#work">Work</a></li>
<li><a href="index.html#about">About</a></li>
</ul>
</nav>
</header>
<main>
<h1 >Portfolio Usability Research and Analysis</h1>
<h2>User Interviews</h2>
<img src="img/userInterviewScreenshot.PNG">
<p>The user interviews are an essential part of user research. I use the interviews to understand the mindset of potential visitors of my website. While all of my interviewees were competitive students, they provided interesting ideas on what a portfolio website should feature. They validated the importance or appropriateness of my website’s content. The types of questions are important in user interviews because certain motivations or lack of it are not always apparent and they affect the answers given in the interview. For example, the students I interviewed may not reflect an accurate portrayal of someone from the hiring industry, who has their own biases.</p>
<a href="https://drive.google.com/open?id=1oaUxlyzmYO6KUqTQ7nufINupS9MGAkGNw4G-21-kz5I">Read more</a>
<h2>Competitor Analysis</h2>
<img src="img/competitorAnalysisScreenshot.PNG">
<p>Competitor analysis complements with the user interviews. Competitor analysis is an evaluation of the strengths and weaknesses of competitors’ products and then comparing the findings to my product. My website can benefit from evaluating other people’s portfolio websites. Their websites may signal whether I need to add more content or change the aesthetics. I chose to review other students’ websites from my classroom to see how I fare in creating my website. I reviewed a professional’s website to see if there were any inspirations to be found that were relevant to a hiring manager.</p>
<a href="https://drive.google.com/open?id=1FBMArCf3AVzRZSj32xo0Gw8QRgfRJbsXkwoZnFpGf54">Read More</a>
<h2>Feature Value Matrix</h2>
<img src="img/featureValueMatrixScreenShot.PNG">
<p>Feature value matrixes provides a road-map on what features to focus on. It defines a criterion for valuing features or recommendations of a product, such as my portfolio website. Feature value matrixes are most useful when business needs are a factor in calculating values of features. The features I have chosen are based on what I think would be important to my targeted audience: hiring managers and recruiters. The most important features are about providing relevant content to the recruiting process. Few of the features were technical in design to ensure that the website is usable.</p>
<a href="https://drive.google.com/open?id=1UmfYHwO3W1JRdzGv6Dyyc-BLqx0PP5VQcKXfTSBh5QA">Read More</a>
<h2>Feature Prioritization</h2>
<img src="img/featurePrioritizationScreenShot.PNG">
<p>Feature prioritization is a graphic that shows a hierarchy of features and where each feature is positioned relative to others. Essentially, the most important features that must be finished are grouped closely together. I prioritized my features or set their positions on the graphic based on the scores given in the feature value matrix. This feature prioritization graphic is incorporated into building the interface by showing which features must be prioritized or which features can be quickly finished. I can quickly review the graphic to find if there is a pattern found in business needs.</p>
<a href="https://drive.google.com/open?id=1iLGKTImp2W2dbtczdI9o5EjbCxNYKzRTAlsuJKnYqk4">Read More</a>
<br>
<h2>User Stories</h2>
<img src="img/userStoriesScreenshot.PNG">
<p>The importance of stories is reflecting about how different types of users use my portfolio website. The benefits include discovering usability needs and understanding the strengths and weaknesses of an interface. I creatively thought about the types of stories or epics that certain users will take part in. I created the stories by first brainstorming on what types of users would visit a portfolio website. I mostly thought about why I would visit such websites as someone from HR. Afterwards, I used my feature value matrix to identify stories and epics that were yet to be created. </p>
<a href="https://drive.google.com/open?id=1rLSfiaztU2oE5HVFBByOALavKqYXA9p-A7JFQPYfO3o">Read More</a>
<h2>Cognitive Walkthrough</h2>
<img src="img/cognitiveWalkthroughScreenshot.PNG">
<p>In a cognitive walkthrough, new users perform a series of tasks and are given a set of questions to answer. An evaluator would guide the new users, asking questions and recording the interactions between the user and the product. The activity aims to discover usability issues of an interactive system, emphasizing on the interactions with a new user. Some of the challenges I faced had to do with the quality of my questions. A tester may not understand me. The questions did not provoke a deep or insightful answer about the interactions because the questions were shallow in testing.</p>
<a href="https://drive.google.com/open?id=1A2E93u1jI2e69m73H0bpZ9FGlS6YRrqdPOUzaXL-QOg">Read More</a>
<h2>Task Based Tests</h2>
<img src="img/taskBasedTestScreenshot.PNG">
<p>The types of tests conducted were the question test and the click test. I chose the click test to see whether my navigation bar was effective and understandable. I used the question test to ask questions about the aesthetics of my website. Those tests were the most effective to write. The challenges I faced was not having grammatically coherent questions, so I risked getting answers from confused testers. As for the test results, testers revealed that my website is readable, however there were a lot of white space that should be removed. The navigation was simple according to my testers.</p>
<a href="https://usabilityhub.com/tests/c9422b4c91f1/results/abb6112406c5">Results of First Test</a>
<br>
<a href="https://usabilityhub.com/tests/4cbb05c52307/results/d62a1fb32dc5">Results of Second Test</a>
<br>
<h1> Summary of Findings</h1>
<p>From my user research, I gathered information that suggested that portfolio should be an online display of a resume. A list of skills, work, and professional related details should be provided for visitors to read. The user research encouraged me to pay more attention to the quality of questions I give to testers or interviewees because sometimes I wanted insightful questions. Some users would provide brief answers. The competitor analysis revealed that aesthetics matter and that my design and type of content was similar to others. The feature prioritization showed that the business needs, such as the project content, defined the most important parts of the website. The user stories justified usable content. The cognitive walkthrough and the tests showed how my interface needs to be improved in typography, formatting, and visual experience.</p>
<p>From my findings from the user research and user testing, I can draw a conclusion that my website has the appropriate content for a portfolio website. However, the website could be improved in terms of aesthetics. The entire procedure of user research and testing helped understand how my interface can be improved. The activities involving other people to test my website, such as the cognitive walkthrough and user tests, showed information that were generally harder to obtain. For example, people revealed which parts of my website did not provide a good experience and how long it takes them to learn and test the interface (usually 30 seconds). The information gathered will guide me when improving the usability of my website.</p>
<h1>Incorporation of Findings</h1>
<p>I haven’t implemented any changes since the first prototype has been finished. I will discuss my plans for changes instead. Based on my findings, my solutions need to address the problems that my users and testers have identified. Because my testers have shown that my skills section are not aligned properly depending on the browser size, I would need to revisit and decide if it is better to change its orientation to left sided or keep it centered. I didn’t expect that centering a list of words could be unappealing. Based on other people’s research, my skills section could be improved by adding details on what I have used each skill.</p>
<p>While my layout was simple and usable, there were problems with how much white space there are on my website and the color transitions. At first, I wanted to provide an interface with clearly defined sections using contrasting colors using a color scheme. However, I found it difficult to fill up sections with content, which left a lot of white space. Another consequence was that the differing background color was jarring for few to scroll through because the colors were sometimes too dark and varying. I would fix the problem by making the text size bigger to fix the gaps and use muted colors for the background to make the interface look smoother when scrolling.</p>
</main>
</body>
</html>