
This diagram shows the process in which to conduct a heuristic evaluation. Throughout the lecture we were told exactly what that means. I have to admit though I did think to myself ‘we are in no position to to evaluate or criticise a professional website or application’ We are still learning how to produce user friendly workflows with engaging elements to enhance the user experience. The hows and why were yet to be revealed.

This pretty much says it all & I felt like I was back in the first year contemplating my decision to entertain this notion of being a UX developer. I honestly thought OK I can use Figma, show my process and even create functional prototypes but this seemed like it was just beyond me .
Over the year I’ve learned a lot, not just about design and its history but also a lot on creating components and implementing engaging graphics with appropriate typography that suit the tone of brands. In short I do feel I’ve came a long way in a short time but pinpointing less than perfect of a digital product revealing which parts of a site or app that are causing headaches for users really did seem out of my ability level right now.
Then we were shown a break down of how the evaluation is conducted and I began to realise the value of lecture and why we were getting in only halfway through our second year. Knowing there was a rule of thumb for guiding you through the process was a huge weight of my shoulders ‘thank you Jacob Nielson’ The 10 rules to look out for are a huge help in this, Understanding these and being aware of what to look out for will make this assignment a hell of a lot easier.










Without these guidelines I honestly wouldn’t know where to start with this. Having a hard copy I think will make the process a little easier
I could comment on all 10 of these but I’ll only refer to them when I conduct the Audit on the assigned site. I will say this though, I wish Adobe products would follow the 9th rule a little more. I don't know how many times I’ve received error codes over the years and hadn't a clue what they meant. With me printing out these 10 rules to follow as a reference I’m sure the cognitive walkthrough and the first part of the procedure will be manageable. The second part of the of the procedure on the other hand where we brainstorm and try to fix the issues or problems is an an area I’m sure will test me.

Rating the problems is another area I think I will have to be careful with. Unless its an obviously poorly designed site or application I think its going to be difficult to determine the urgency of these issues.

These slides I think will be of great value. It’s not an exciting exercise but we are given all the tools to conduct it as best we can.

He was just showing off really lol. He is a great designer. With the site he conducted the audit on he showed clearly how a user interface and workflow can be improved. I was impressed how he transformed a stale flat generic site into a smoother more efficient design and with a few subtle tweaks even made the UI more pleasing on the eye.
He conducted a full audit with over 40 pages going into great detail with screenshots and clear descriptions of the issues with a table with these colour coded in order of importance I’m just glad we don’t have to go into such depth with our audits but I really do see the benefits of conducting this now. Learning It early will not only help us identify issues that commonly arise with apps and sites but it will essentially make us better designers for our future projects (I think Kyle actually said that but now I believe him) There is good reason for us doing this now and IA hope I can effectively conduct an audit to get a better grasp on user friendly designs.

This week I think I will have to check this book out before I even begin.