case: dailyGOURMET and dailyHOTEL app service
my analysis: here
The mission of this blog is: 1. to openly talk about meaningful UX related content 2. to encourage everyone to think like UX professionals in a holistic way; so that any attempt to design, develop, and distribute can be more people-loving and personally meaningful; therefore, people's time and energy will be spent on things of true importance not being wasted on tedious UX.
Tuesday, December 1, 2015
Friday, November 6, 2015
[personal UX/UI review] the power of "Reply" button on review page (e.g. Chrome Web Store)
<case: Chrome Web Store's product detail page>
positive: the existence of "Reply" button on review page
reason: because of the button, the review page can be used as a terrific communication channel: 1. allowing users to answer questions of another user, which reduces communication cost of the app creator 2. working like a CS (customer service) channel, providing the app creator an opportunity to directly respond to eliminate frustrations of users, which may help reduce "bounce rate" of the app use 3. displaying interactions among users so that each thread can be more open and transparent
<case: iTunes App Store's product detail page>
Tuesday, November 3, 2015
[personal UX/UI review] thought on displaying product images on websites
<case: product page for Nest Cam >
<case: product page on Amazon>
<case: product page on Amazon>
reason: Putting a universally recognized size standard object such as a deck of cards, coins, silverware, etc. next to a foreign product helps viewers' understanding of the product size. Also, if the product can be placed at a context such as a hand or an arm, that would be a bonus.
Friday, October 30, 2015
[personal UX/UI review] why we need word-breaks for Korean
case: parts of Korean words along with numbers chopped off from right edge of web documents
issue: viewers need to go back and forth from line to line to make sense of chopped-off texts
recommendation: implement Korean word-break system onto Korean websites! (e.g. Hyung Woo's jQuery plugin)
Tuesday, October 20, 2015
[class: PM Camp@Fast Campus#20] 제품 유지 보수하기 #2 (my note is WIP)
7. 15 수
|
제품 유지 보수하기 #2
|
제품의 유지 보수를 위한 실제 예제 분석
|
Mr.M
|
- lesson:
- retrospection
- method: collecting positives and negatives to sharpen the positives and improve the negatives
- prep for retrospection: facilitator’s role is important
- timeline method: 1st, 2nd, 3rd, … week
- which event occurred and how negatives can be overcome
- triple nickels (aka “rolling paper” method): 3x5 minutes (first 5-minute, write everything comes to mind; switch the paper and write on top of the previous write-up and iterate the process one more time; share at the end
- iteration plan by MoSCoW, user story point, etc.
- c.f. C=M (method: e.g. email, phone) * L (length: communication quantity e.g. email quantity)
- break-down user story by task
- know what’s completed and left
- constantly update backlog
- quality means no error
- the earlier errors are fixed, the lower the cost
- quality management = risk control
- cohort (e.g. 1회 대화, 5회 대화, 등록 후 로그인하지 않음, 유료) analysis: e.g. registered members in May vs. June
- myth about accumulated metric
- AARRR metrics
- 조건부
- personal takeaway:
[class: PM Camp@Fast Campus#19] 제품 유지 보수하기 #1 (my note is WIP)
10주차
|
7. 11 토
|
제품 유지 보수하기 #1
|
제품 출시 이후 제품의 품질을 유지하기 위한 활동
|
Mr.M
|
- lesson:
- Epic: first depth category (e.g. for bookstore website, examples for epic can be search, purchase, promotion, and customer service.)
- 1조 example
- 소개팅 장소/시간 정하는 데 소요되는 시간 최소화
- 소개팅 실패시 리스크 최소화
- 상대 취향 파악
- 폐쇠된 공간에서 대화
- read
- writing
- example (needs to be descriptive and short; remove emotional context): user A가 user B를 한 두 번 밀다가, user B가 자리에 앉게 되었음
- practice
- start writing followed by reading the written text (reason: short of breath)
- start writing subject and verb and try to make your sentence shorter
- remove “있을 수 있다” and conjunction
- Markdown: e.g. iA Writer, hashify.me
- read
- acceptance test
- planning and scheduling
- triangulation
- release planning: 소멸차트, etc
- workshop:
- 5 iteration, 8 velocity
- create a doc: title | description | point | priority
- priority: MoSCoW (Must have, Should have, Could have, and Would like but won't get)
- personal takeaway:
- practice objective writing without emotions
[class: PM Camp@Fast Campus#18] 프로젝트 관리 기법 #2 (my note is WIP)
7. 6 수
|
프로젝트 관리 기법 #2
|
프로젝트를 관리하기 위한 실제 예제
|
Mr.M
|
- lesson:
- backlog: list up all features (c.f. backlog helps create burndown chart)
- daily meeting: ask members to bring write-ups for what they did, are doing, and current issues for 10-15 minute daily meeting
- mature organization: planning and result are the same (e.g. easy backup when the person in charge is not around, short integration speed)
- what’s important in project management
- purpose needs to be shared: e.g. create backlog and share with all members
- consistency between members’ responsibility and task
- break-down big tasks into small tasks
- teamwork
- communication
- outsourcing: try to avoid outsourcing in software development
- user story: 누가, 무엇을 달성하기 위해, 이런 기능이 필요하다 (i.e. As a …, I want …, so that …)
- personal takeaway:
- user story: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. <source: Wikipedia>
Subscribe to:
Posts (Atom)