Please enable JavaScript.
Coggle requires JavaScript to display documents.
7 Note ((adequate, pointer, agenda, generalization, avatar, relational,…
7 Note
-
-
no practicers use only single method to know their users, they mix the methos together
-
:red_cross: missing
like receipt -> follow the method -> get your result -> case study
:check: when cooking, few people follow the receipt
:check: people are not trying to use UX methods, they are trying to use a good tech
people must get involved to get it work
:check: real life case study & method review of case study -> construct model of this case study for practical generalization -> few studies
-
- when & what & how we talk about users
-
what is a user
- economics -> user is an entity that can give the tech directly benefits
- engineer & researcher -> broader -> impacted people -> people who enjoy the interfaces & suffer from the inconsistency of it & delighted by the new functions
- user shape is an emerging characteristics -> we grow into users -> we are not born users, but gradually learn how to use & appreciate the tech
phenomenon
tech emerge not as a new tech, but it has users
-
-
:check: user refers to imagined / implicated / potential / real people who are / could be using a design object
:check: identity -> from tech / design point of view, I am a user rather than Sally / patient / citizen -> only one aspect of being
:red_flag: our engagements with users mean it is a relational category with us trying to figure out these people out there
:check: how we view these people
:check: what information we seek
:check: how well these people understand them
:check: what kind of information they provide us
:check: what are our assumptions
:check: what are our backgrounds
user representation
-
-
involvment
I developed a product, I invite you to tell me your ideas about it -> what you really need
-
-
designers use themselves as proxy for users -> comments & personal UX & methodology
example -> design for themselves & buddies -> assume that users are like you -> truth is not
tags prototypes -> web page design
work well -> many moving images here -> hard to navigate
:check: developers follow the trend -> make the page simple and clean
:check: developers are using new tech -> location data -> what users should do/ should not do
:star: ATM -> rely on general cash machine -> 2 tipicaly user studies -> rely on it & not rely on it
rather than business model, the emerging for market and users -> leading to a business sensitive model -> investors demand that visualing of users
example
:check: fenlan museum
- how many people they attract
- how much money it costs
-> the money they use may fail to get by attracting more people
-> how many people may come & the minimal service & feature we develop to reduce risks
:green_cross: startup plan is to sell 2 m pieces of the dumpling -> the other way around
- how big the market we will go into
- how generality out product should get out
- study competitors
- instead of referring users' needs in the first place
-> may get a smaller market, but couldn't cover the cost either
-> may get no market
-> not acculated
- study people
- get the information
- every function of the company interprets results, someone differently
pay attention to users out there & users in there -> strategic market user insights
soft point
- it is difficult to assess
:check: what is new/old to users
:check: what is needed by developers to know
- study users -> gather information -> make things more or less work
are companies looking for small detail
- rethink the process of user research
:green_cross: commission and study users, what users in real life are doing
:check: know what the organization already think about users with methods mixes for developers / managers / marketing / stakeholders -> personas -> what they assume for users
- user representation and also compromise assumptions
:check: user research -> evidence -> video -> what they are doing -> you think they do X, but they do Y
:check: your survey about what they do is not representative
:check: hard to relate to what users are doing in fact
:check: mix hard evidence with comparable soft evidence about what you assume about users
-
persona scenario -> clarify unclear topic about users -> in team talking about users -> you assume many things -> different backgrounds & different meanings -> map different people -> who we are designing for and what are the benefits of it -> help what we are doing -> don't work -> you stuck here -> model -> multiple test
elevator -> hospital -> button & how it works -> physical mockup -> 30% engineer make the elevator wrong -> both hands with patient no hand with button -> US market -> smaller elevator -> freak
make sense -> construct the user representation you have -> keep in caring business changing -> control panel are used
understanding of users & market & business & technology solution rather than just design user managing operation -> designer can do
-
:star: not the more it is, the better
-
example
largest teenage social media platform -> merge before facebook in 2000 -> over 10 m visitors in a month
-
how do the companies know users?
:check: few users -> developers are also users -> they ask their buddy for feedback and hangout to find what work & don't work -> inform but first-hand
:check: thousands of users -> keep into what users do -> seminar meeting -> revenue based on mobile payments of furniture & chat with others -> formal way
:check: millions of users -> diverse people are doing is not possible to get from informal ways -> market service & focus group & usability evaluation & usability testing
:check: 5~8 million -> online user panel & incorporated user tagging -> market survey to know how users globally act to their promises -> automating the survey result, as it is too plentiful for people to handle more -> what they get and do -> data mining -> UX testing & personas
:check: 10 million -> formal method
-
-
-
-
-
-
stage
- the company becomes committed to UX, this is a critical feature for the company to be actively involved in developing
- UX becomes a part of company's strategy
- UX is important and formalized to keep it up and shortly find its way to the products that emerges, if you put tech in your product, users don't appreciate, it won't work
- UX is important, but it only receive a little funding & attention in company
- how users experience a product, there is no specific recognition of it, we assume that we bring this tech, it should work
UX is not important to get our tech work
- the whole company will be naturally involved and know some methods / information about users for product development
arguement
any user research & human-centered design will always be featured as one part, that is, how users are understood in the organization
wise to do about the reality
:check: we should know users who will use our product
:check: what the company knows about the users -> most companies don't know what they already know -> knowledge about users is transparent -> not used in development
