this was brilliant, sold me on watching the whole series now!! and i was watching a movie, swapped to his video and had a much better time too, thanks.. and now feel alert and inspired .. \0/..
Are the people in these talks specifically focused on Chrome? I have no knowledge of the organizational structure and inter-product team overlap at Google. Chrome won me over with its usability years ago, but I can't say my experience has been the same with any other Google flagship products (except maybe Google Translate, which is wonderful.)
There have been quite a few people who have appeared in the series who don't work at Google and don't focus on Chrome. It's usually more developer-designer focused; but (as with this specific program) can encompass wider roles in the product development process. I've many favored Google products (I'm perhaps biased!) but I'd particularly call out Project Fi. This has worked way more flawlessly for me than any other SIM I have used when visiting different countries. Thanks for your thoughts, appreciate them.
Sure. These are the words I heard in this interview which didn't felt were tangible: "Research, problem, product, stage, exposed, what works well, end users, biases, confidence, usability, golden rule, task, critical user journeys, content, foundation research, observation work, better understanding, complementary, converting, quantitative data, representative, sweet spot, diminishing returns, pivot, adjust, mental models" It's fine to use them if every one of them is attached to some real or fake example from everyday work. If you cannot talk about about client product details then you can come up with your own examples. The product can be Angry Bird's game and then you can describe how usability would be tested on such game. Interview is as good as the examples and personal knowledge given. Example of excellent interview (in my opinion): ruclips.net/video/gNh9r-VbSVg/видео.html
That makes sense, and it seems fair to suggest that we could have had some more examples in here, which would provide interesting illustration. Doesn't seem reasonable to expect every such word to be brought into examples and illustration in such a short video; but I get your point. Will consider that for 'part 2'! I will listen more to the interview that you linked to - which is very long! Thanks!
Not every word has to have an example but there should be some value in interview. If there isn't enough time then something should be changed. Split into small segments :). Thanks for listening!
UX researcher is so my dream job
Do IT! its such a rewarding practice
One of the best episodes to date!
Thanks for sharing!! this is really inspired me to do better! as a User Researcher!
Are you working at Google now as UX researcher?
this was brilliant, sold me on watching the whole series now!! and i was watching a movie, swapped to his video and had a much better time too, thanks.. and now feel alert and inspired .. \0/..
In 14:02, are they talking about A/B Testing vs. Usablity Testing (Completing a Task)?
Are the people in these talks specifically focused on Chrome? I have no knowledge of the organizational structure and inter-product team overlap at Google. Chrome won me over with its usability years ago, but I can't say my experience has been the same with any other Google flagship products (except maybe Google Translate, which is wonderful.)
There have been quite a few people who have appeared in the series who don't work at Google and don't focus on Chrome. It's usually more developer-designer focused; but (as with this specific program) can encompass wider roles in the product development process. I've many favored Google products (I'm perhaps biased!) but I'd particularly call out Project Fi. This has worked way more flawlessly for me than any other SIM I have used when visiting different countries. Thanks for your thoughts, appreciate them.
looking at series there are two #20 so this #21 ?
It's true! It needs fixing :)
Opps, just fixed that, should be find now :)
Interesting
So many buzz words..
Oh interesting, I apologize if there were too many ... it's hard to see that in ones own area of work I guess. What confusion can I help clean up?
Sure. These are the words I heard in this interview which didn't felt were tangible:
"Research, problem, product, stage, exposed, what works well, end users, biases, confidence, usability, golden rule, task, critical user journeys, content, foundation research, observation work, better understanding, complementary, converting, quantitative data, representative, sweet spot, diminishing returns, pivot, adjust, mental models"
It's fine to use them if every one of them is attached to some real or fake example from everyday work. If you cannot talk about about client product details then you can come up with your own examples. The product can be Angry Bird's game and then you can describe how usability would be tested on such game.
Interview is as good as the examples and personal knowledge given.
Example of excellent interview (in my opinion):
ruclips.net/video/gNh9r-VbSVg/видео.html
That makes sense, and it seems fair to suggest that we could have had some more examples in here, which would provide interesting illustration. Doesn't seem reasonable to expect every such word to be brought into examples and illustration in such a short video; but I get your point. Will consider that for 'part 2'! I will listen more to the interview that you linked to - which is very long! Thanks!
Not every word has to have an example but there should be some value in interview.
If there isn't enough time then something should be changed. Split into small segments :).
Thanks for listening!