Google HEART

-
How Google Improves User Experience with the HEART Framework
Click here for article
The metrics Google created for its designers to use as a guideline, HEART, is part of what makes the Google suite so powerful and pervasive.  The goal of the rubric is to build a system that is more effective at carrying out its intended purpose[Task success] thereby satisfying a user[Happiness] as well as encouraging them to want to use it more often[Engagement], become loyal to it[Adoption], and to continue to use it[Retention].  The result of this is the Google suite that has become standard for school systems, workplaces, and personal affairs.  I have not used Microsoft office since my sophomore year of highschool, mainly because using Google Drive is simply easier and more convenient; I can access whatever I'm working on from any computer or smartphone that has an internet connection.  The Google suite is simple and nearly seamless to use, and upon finding their rubric for product development, how they achieved this product makes more sense to me.

Discussion Questions:

Is there a way we could implement this model in the New Media program? How would that happen and what would it be used for?

What would MaineStreet look like if its designers had used a rubric similar to this?  Would the experience be better able to cement itself into the user's memory?

Comments

Post a Comment

Popular posts from this blog

Redesigning the FitBit app

-
Image
click here for article First off, the idea of guerrilla usability testing is extremely funny to me:  a method of  testing a website or app that involves "pouncing on lone people in cafes and public spaces, quickly filming them whilst they use a website for a couple of minutes.”  The mental image is ludicrous enough to actually seem feasible.   As for her actual prototyping and redesign process, there were again some interesting takeaways for me.  The job stories that allow you to better analyze what people want to do with an app was a practice I had not thought of, and the idea of 'pain points' seems like a useful tool that I will be able to utilize in my job.  The discovery of the pain points provides specific goals to troubleshoot, as opposed to wandering blindly, which I appreciate.   Discussion questions Would guerrilla usability testing be feasible for the snow plowing app? why/why not? What tasks would it make sense to ask of testers? What othe
Read more

Metrics Versus Experience

-
Image
Click here for article I thought that the name of the article (Metrics Versus Experience) was interesting simply because the first point of the article was "don't frame stuff as 'Metrics Versus Experience.'"  The actual content of the article was a nice insight into something I am only barely aware of:  the metrics used to analyze the success of a website or product.  I have interacted with them in terms of Instagram(there is a feature that lets you see how many people have seen a post and how many people have interacted with a post, and how those numbers stack up against your other posts) and Google analytics(which lets you see where people who access your website are from and how they are getting to the site), but I have never had to use them to better execute a product.  In Zhou's article, she talks about different ways to figure out which metrics you should actually track, and I liked the way she explained it because it's similar to the way I te
Read more

Glossary of UX terms [ongoing]

-
An ongoing glossary of UX terms that will be updated as we learn more. 5: five second test a form of usability test where the user is shown a web page for 5 seconds and then asked questions to determine the clarity of the website. A: B: C: D: E: F: G: Guerrilla User Testing According to  Martin Belam, "Guerrilla usability test is “the art of pouncing on lone people in cafes and public spaces, quickly filming them whilst they use a website for a couple of minutes.” H: I: Iterative design the process of repeatedly redesigning a product based on user feedback. J: K: L: M: N: Needfinding A process of determining what a user actually needs a product to do.  This information can be found using questionnaires (explicitly determined) or through usability testing (implicitly determined). O: P: Prototype A mock up of a product that evolves closer to the actual product over time(low fidelity,
Read more