Tuesday, 31 March 2015

Week 6 Reflection (Lo-fi Prototype)

For week 6, we were set the task of creating a lo-fi prototype of our application. This came in the form of a paper prototype, as can be seen below. The idea behind this prototype was to create wireframes of the different screens that may appear on our application, to allow us to test it on potential users. The actual prototyping itself was rather straightforward, as we simply drew up wireframes on paper. However, the testing proved to be rather more interesting.

One of the screens from my paper prototype
When I tested my prototype on fellow classmates, I wasn't sure what to expect at first. I assumed there would be a large amount of criticism and suggested changes, but this wasn't to be. In fact, the large majority of my test subjects had no suggested changes to make; they felt the prototype application was easy to navigate as it was. This was inspiring and very useful - it was enlightening to see how such a simple process could give such valuable feedback. Of course, there were some suggestions for minor changes I could make, and I took all of these on board and considered them for refining my idea. The whole process was extremely helpful and taught me the value of prototyping before attempting to implement a design. Zigmond (2011) pointed out the importance of ethical guidelines in a profession, saying that they must be kept 'alive, relevant and effective'. One of these ethical guidelines stood out to me; to 'design for all'. Testing my prototype on others helped me keep my design relevant and effective, as instead of designing it specifically for myself, I received feedback from others.

References (APA)

Zigmond, M. J. (2011). Making Ethical Guidelines Matter. American Scientist, 99(4), 296-299.

Sunday, 22 March 2015

Week 5 Reflection (Demographics, Psychographics and Personas)

This week we focused on the user. A design should center around the user (hence the term 'user-centered design'), as it ultimately requires their approval to be successful. Therefore, defining the user is instrumental to prototyping and refining a design. Defining the user is a process that requires considerable thought and research. Ultimately, it also leads to a good usable design, as explained by Claxton:

"The essence of good design is usability, which requires the study of users' behavior to accurately assess product performance." (Claxton, 2008)

As we learnt this week, this can be done through defining the age demographic of the user, the psychographic of the user, and creating personas.

In order to create my solution for the assignment, I considered who my users are. Defining demographics and psychographics were relatively straightforward. However, creating personas required more thought, but ultimately was the most useful. I created a detailed persona about a fictional university student who could be a potential user of my design. This gave me insight into exactly what type of user would be a candidate for my design.

Persona I created for this assignment
One thing I gathered from this process was that it is much easier to create a persona after defining the demographics and psychographics of potential users. This narrowed down the field considerably, and gave me context to work from when creating a persona.

References (APA)

Claxton, B. (2008). The significance of user-centered design. Mobile Radio Technology, 26(7), 16.

Sunday, 15 March 2015

Week 4 Reflection (User Expectations and Needs vs. Wants)

For this week, we focused on the users needs and expectations. Specifically, we applied this to our assignments. Before the tutorial, we were required to consider whether there is a need for our proposed idea, and the requirements of the idea.

When preparing these points, I thought in depth about needs vs. wants. My idea was for an application that would help university students study. Studying is certainly a problem among uni students, as I identified from questioning a number of students. However, to address this issue, what does the user want, and what do they need?

A list of my issues and potential solutions
Product requirements for my application
Many students may want a quick fix, something that does the work for them and that they rely upon. However, this is not what they need; this would not be helpful in the long term. Therefore, there is a tricky balance that must be achieved. Listing the requirements of my application helped. For example, one of my requirements was that the application must be encouraging, not discouraging or commanding. This process of listing the requirements helped greatly in finding the fine line between what the user wants, and what they actually need. This idea of conducting preliminary research in order to identify the problem should apply to just about every profession and even to daily life (Nagurney, 2007).

References (APA)

Nagurney, A. (2007). The Importance of Research. Chronicle Of Higher Education, 53(22), B18.

Wednesday, 4 March 2015

Week 3 Reflection - (User Centric Design and Requirement Gathering)

This week heralded the start of our first assignment - to come up with an application that would aid students in university life. In preparation for the tutorial, we were tasked with coming up with 3 problems and 3 solutions in relation to the task.

Finding three separate problems might sound easy on paper, but actually required some thought. I found myself asking 'what is the hardest thing about university?'

In the end, I came up with three problems, simply by examining my personal experience and by interviewing fellow students. Focusing on three ideas rather than a multitude was helpful, as it allowed me to make sure each idea was refined and of good quality. Briggs (2010) says that the goal of ideation is not to necessarily come up with a large quantity of ideas, but to come up with quality ideas. I also learned that this is a form of requirement gathering, and thus discovered why it is so important. Without using this step first, it would be easy to lose direction and focus - what is the problem I am attacking here? It's absolutely vital to clarify the problem first, and then go about finding a solution.

Finding an idea for a solution was also not very straightforward. Again, whenever I came up with a potential idea, I questioned myself - would I be willing to use this idea to assist in university life? This really highlighted to me just how important it is to keep the target market consistently at the forefront of your mind. A brilliant idea must be one that engages with the target market - otherwise it would be a flop. Again, this is another example of requirement gathering; one of the most important requirements for a user centric design is the engagement of the user. If this requirement is not satisfied, the end result will more than likely be a failure.

References (APA)

Briggs, R. O., & Reinig, B. A. (2010). Bounded Ideation Theory. Journal Of Management Information Systems, 27(1), 123-144.

Tuesday, 3 March 2015

Week 2 Reflection - Good and Bad UI

During this week, we examined what makes a 'good' or 'bad' user interface. I found this an interesting topic, as we have all stumbled across a clunky, terrible application or website, and often take the well designed ones for granted.

The lecture for the week finished by instructing each of us to find an example of a good user interface and a bad one, and to justify our reasons for thinking so. I thought back to what I could use as an example - I've had many experiences with good user interfaces, but I really had to rack my brains to think of a bad one.

One instance came to mind - earlier this year I was booking plane tickets for a trip to Europe, and thus had to use an online travel agency. One of the websites I intended to use was an absolute nightmare - the pages were hard to navigate, with items being laid out in an unorthodox fashion. The pages were incredibly long, requiring a large amount of scrolling to get through a whole page. This is something that should be avoided when designing a good user interface, as noted by Sethumadhavan (2013). While this was annoying, the most fundamental flaw made itself apparent when I attempted to enter my name, as displayed on my passport. The required field had a 20 character maximum, meaning that people with long names were unable to enter their full name! Unfortunately, I could not remember the specific travel agency, so I decided to go with a different option.

Eventually I decided on Windows Movie Maker - specifically, comparing the old version (good user interface) and the new version (bad user interface). Without going into too much detail, the new version was an example of a bad user interface as it had been over-engineered - the programmers had 'reinvented' the program to such an extent that it was missing important features and was a nightmare to navigate around.
The old Windows Movie Maker, who's interface is based off professional video editing software
The new Windows Movie Maker
This got me thinking - often when designing user interfaces, too much emphasis is put on the visual appeal of the interface. While aesthetics are important, ease of use and functionality should be a higher priority. This was displayed perfectly through the new version of Windows Movie Maker - while it may look more streamlined and modern than the old version, functionality has been sacrificed in favour of this.

References (APA)

Sethumadhavan, A. (2013). Principles for Designing Good User Interfaces. Ergonomics In Design: The Quarterly Of Human Factors Applications, 21(1), 33-33. doi:10.1177/1064804612471791

Intro Post

Welcome to my blog! I am Steven Rummukainen, a student at the University of Canberra, and here I will be posting about all sorts of things to do with User Interface and Experience.