Saturday, December 20, 2014

[lesson] 힐링캠프, 기쁘지 아니한가 161회 물음특집 2탄 - 김봉진 대표, 김영하 작가 편 (translation: Healing Camp #161)

video source: link
lessons I learned when watching Healing Camp #161

tips on how to approach investors
  1. clearly explain identity of your service
  2. first, know the most important metrics for your service; then, through the metrics, explain how your service gets to grow consistently while meeting your service goal
  3. view investors as people to learn from instead of people to take advantage of; interact with them to gain lessons

general tips in life
  1. begin everything (e.g. especially your work) in life by defining what it is
  2. shoot for growth not success

[lecture] “성장하고 성공하는 서비스를 만들기 위한 서비스 디자인의 이해" (translation: Understanding Service Design to Create Growing and Successful Service)

My note below is work-in-progress. Need to update to reorganize lessons. Thanks!

“성장하고 성공하는 서비스를 만들기 위한 서비스 디자인의 이해" (translation: Understanding Service Design to Create Growing and Successful Service)
D.CAMP 5th Fl.
December 18, 2014 (Thu) 19:30~21:30
고영혁 (Dylan Ko)
service design
  1. lesson:
    1. requirement for successful service
      1. growth: continuously generating revenues in upward direction from past to present
      2. growth curve: through post-mortem, identify bottlenecks suppressing growth
      3. defined success: define success/goal (e.g. solving customers challenging problems)
        1. for me, many people restore relationships with God, others, and themselves
    2. thoughts regarding service
      1. definition of service: tangible or intangible products which actualize value creation to activate business model
      2. examples of service component
        1. customer: mostly people who hire/use the service
        2. experience: people’s perception or feeling on the service; need to feel easy when using the service (<- information architecture needs to be well flowed so that people don’t need to be stressed out to find next steps)
    3. concepts to be familiar with
      1. bootstrapping: minimal profitability (c.f. profit= revenue - cost) to survive without funds
      2. service: value creation through problem solving
      3. business model= monetize value
      4. service design: everything that service providers do to bring quality service
    4. data design to make service successful
      1. need to have time concept of both static and dynamic: static as in snapshot of time and dynamic as in observing changes over time
      2. need to track causality so the learned lessons on service can be reusable
        1. when: not time but contextual case (e.g. when conducting a specific marketing)
        2. what: (e.g. the inflow of people increased)
        3. how: (e.g. )
        4. result: (e.g. )
      3. keep record of case history to learn from success and keep applying the success
    5. efficient growth (consider lean startup)
      1. meaning of lean: no unused items
      2. lean process: idea -> (make) -> product ->(measure) -> data -> (learn) -> go back to idea and iterate the process fast
    6. growth hacking- mixture of engineering and marketing
      1. meaning: maximize ROI
      2. concept: product (define and improve), marketing & sales filled with experiments at the intersection
      3. component: viral growth through landing page optimization, product management, SEO, onboarding, UX, behavioral economics, behavioral economics, email marketing, and analytics at core of all activities
    7. one of the best ways to learn service design
      1. create and launch at markets and go through one cycle
      2. watch global services (e.g. Facebook) how being transformed
    8. data design
      1. manage time appropriately:
        1. must have timestamp (need to find out users’ patterns e.g. buy at the point of checking-out, return and buy after 3 days), tables (e.g. user ID, product info, purchase method) (which users who signed-in when users sign-out), both time and time span are important; thus, keep record of both time and time span 
      2. my data should be able to tell my service’s value
        1. e.g. 땡처리 (“uber discount sale”)  (value: price difference, variety of products, coverage) => price: display history of price discount, coverage
      3. my data needs to contain key responses of users
        1. make distinctions
          1. between important and unimportant responses
          2. real and not real cases (i.e. bug)
          3. intentional and unintentional
      4. event’s group and structure
        1. independant event and continuous events need to be distinctive (e.g. credit card selection event: credit card payment selection precedes prior to credit card selection)
    9. what is metrics?
      1. static vs. dynamic
      2. void (exaggerated metrics: click, page view, visit, unique visitor, follower/friend/like) vs. actionable (results identifiable info: purchased, clicked detailed category of information: e.g. thumbnail-> number, rolling)
    10. requirements for good metrics
    11. to succeed, minimize unnecessary failures,
    12. MVP (minimum viable product): good features to test the users responses
      1. minimum (crappy products nobody wants to use) + viable (the product you want to build)
        1. include only one feature
    13. interactive prototyping
      1. mockup, wireframe
      2. prototype: service creator shouldn’t decide which one to launch MVP
        1. paper prototyping
      3. flow: repetitive use

  1. Personal takeaway
    1. read slideshare which contains images and concise texts
    2. study MVP (minimum viable product)
    3. study axure (an interactive mockup program) (c.f. 450 USD for collaborative feature and 300 USD for basic)

Friday, December 5, 2014

[Fireside Chat] Building Korea’s Startup Ecosystem by Up Global

Building Korea’s Startup Ecosystem
Maru 180 B1 Event Hall (Gangnam-gu Yeoksam-ro 180, Seoul, Korea)
December 5, 2014 (Fri) 15:30~17:00
William Fitzgerald, Google
Joon Oh, MangoPlate / Startup Grind
Mike Orgill, Airbnb
Mark Tetto, The Ventures
Up Global (consolidated org from Startup Weekend and Startup America)
listen to insights to build holistic view on how startup ecosystem works, which I believe eventually help me to provide quality QA due to understanding big pictures of startups and their community

  1. lesson:
    1. William Fitzgerald, Google
      1. attend Startup Weekend to fail fast and start new things with massive actions
        1. Talent: diverse assets (e.g. gender, nationality)
        2. Density: collection of resources physically located close to each other
        3. Culture: entrepreneurism is considered as positive
        4. Capital: multiple choices to get funds
        5. Regulatory Environment: cooperative government
      2. strategic adjustment: use suitable platforms to serve locales e.g. Park Here (changed map platform from Naver to Google Maps to serve countries other than Korea)
      3. use Google for Entrepreneurs: e.g. take advantage of Startup Grind
    2. Joon Oh, MangoPlate/Startup Grind
      1. be open about failures by sharing them with other entrepreneurs
    3. Mike Orgill, Airbnb
      1. learn how companies can comply with governments
      2. don’t mess up with culture and make the culture scalable
    4. Mark Tetto, The Ventures
      1. for any startups, each hour spent creates a big difference; thus, work hard and try new things as much as you can
      2. check business ideas with other people before quitting jobs

  1. personal takeaway
    1. take actions. massive actions. get involved with start-up events now
    2. refrain from hiring Korean anchors for moderators
    3. remove distractions: e.g. get rid of “cameramen,” check microphone before events

Friday, November 28, 2014

[personal UX/UI review] emergency door instruction at a subway train

Case: visual guide how to open doors in emergency
Positive: 1. images and color (i.e. red) to explain a how-to instruction 2. material to glow the instruction even under a blackout situation 

Especially In emergency, people would understand and respond to visual cues such as images and colors more quickly than texts only. The choice of material is good because the designer considered various circumstances to fulfill the purpose of the instruction. 

Wednesday, November 19, 2014

[lecture] DataDay@선릉 세번째 (data analysis for actions)

데이터를 접근해서 체계적으로 쌓고 이를 활용해서 인사이트를 얻는 데까지의
데이터 활용 프로세스의 전반적인 내용에 대한 다양한 주제의 발표로 이루어집니다.
D.CAMP 6th Fl.
November 18, 2014 (Tue) 19:30~21:30
[meeting: link]
고객 관리를 위한 오퍼링 효과 분석 (권정민,데이터 분석가)
Strata+HadoopWorld NY 2014 트위터로 둘러보기 (엄태욱, 데이터 프로그래머)
스타트업을 위한 지표 - 기본 개념과 활용 (서하연, 지표 전문가)
data analysis for actions
  1. Strata+HadoopWorld NY 2014 트위터로 둘러보기 (presentation slide: link) [엄태욱, Data Programmer]
    1. lesson
      1. coding in data science
        1. data scientists need to solve problems through data analysis and data coding
        2. knowing how to code prevents faking data (read Faking Big Data #strataconf)
      2. empathic data interpretation: “walk in your data’s shoes” by @jeggers
      3. prompt usage of data: data needs to be utilized on collection when they are fresh
      4. behavior over identity: “Nowadays it’s not your identity that’s being tracked, it’s your behavior.” by Rachel Kalmar (@grapealope)
      5. users over data: “Focus on your users first, then your data.” by Emil Ong (@OngEmil)
    2. personal takeaway
      1. be user-oriented
      2. coding is required for data science

  1. 세바시 429회 데이터로 세상이 다시 한번 바뀝니다 (YouTube video: link) [하용호, Data Scientist @SKT]
    1. lesson: attention is the rarest resource and being able to match with that attention is the advantage a company will have
    2. personal takeaway: provide useful action items to users as soon as users find you

  1. 지표의 개념과 활용 (presentation: link) [서하연, CEO @Alex & Company]
    1. lesson:
      1. KPI = 지표 (key performance indicator); 1~2개의 숫자로 어떤 상태를 알려줌
        1. 개념
          1. key: 핵심 (the number of KPI is handful amount)
          2. performance: 성과
          3. indicator: 상태 like litmus paper
        2. e.g. BMI
      2. 지표의 작동 메커니즘
        1. 좋은 지표는 현상을 잘 설명하고, 사람의 행동을 바꿔야 함
        2. 지표: 활동을 숫자로 나타낸 것
          1. 활동의 예: 수동 집계, 시스템 카운트, 로그 가공, 숫자 아닌 경우도 있음
            1. e.g. 직원의 성실도: 기준 (e.g. 지각 정도)
          2. 숫자로 표현되면서 일어나는 일: 객관화 (크고 작음이 명확해짐, 공통의 기준이 생김), 비교 (지표 공유가 활발해짐, 지표를 평가 도구로 사용하게 됨)
          3. 지표에 평가가 연계될 때, 지표는 행동을 변화시킨다!
            1. 활동 (업무, 전략)-> 수치화 (표현, 객관화) -> 비교 -> 평가
            2. e.g. “숫자 피드백은 인간의 행동을 바꾸는 수단"- 토마스 괴테
            3. Appendix
              1. 숫자가 우리를 원하지 않는 방향으로 이끌기도 함
                1. 숫자 (친구 수, 좋아요 수/조회 수)-> 반응 (좋아요 얼마나 받는 지 체크함)
              2. Facebook Demetricator 벤자민 그로서
                1. 효과: 핵심에 집중할 수 있었음
            4. negative case: “매출”을 지표로 잡았더니, 주문 조작과 물량 푸쉬가 일어나기 시작
            5. positive case: “해결 건수"에서 “혜택 받는 시민의 수"로 지표를 바꿨더니 시간 걸리더라도 어려운 일 처리
      3. 지표를 완전하게 하는 것들
        1. #1. 목표값:
          1. 숫자가 목표를 만날 때, indicator가 됩니다.
          2. 목표값은 무엇을 언제까지 실행할 지 결정하는 데 도움을 줍니다.
          3. 지표는 스타트업 특성 상 수시로 변경되는 비즈니스 모델과 전략의 기준이 된다. e.g. Uber의 KPI (가동률 (%)-> 언제까지? 목표값 (60%))
        2. #2. 관련지표:
          1. KPI는 장기판의 말과 같습니다. (혼자서 돌아다닐 수는 있지만 이길 수는 없어요.)
          2. 단일 업무에는 하나의 KPI를, 전략 실행을 위해서는 KPI set이 필요
          3. e.g. Uber- 다운로드 수-> 활동유저 수-> 승차 유저 수-> 추천 유저 수
        3. #3. 디멘젼 (쪼개서 보기)
          1. 지표는 대표값입니다. 활용을 위해서는 피팅이 필요합니다.
          2. 데이터를 확보할 수 있다면 대표값 활용을 피하고 쪼개서 보세요.
          3. Appendix: “평균적인 가정에 기초한 계획은 평균적으로 잘못된다" - Sam Savage
            1. meaning 지표는 현상을 설명하기 어려움
            2. 세상의 대부분은 정규분포가 아님
          4. 완전체가 된 지표의 모습
            1. before: 승차 유저 수 4,351명
            2. after: (디멘젼 분석: 지역별 승차유저 수 파악) 다운로드 수 - 활동유저 수 - 승차유저 수
              1. e.g. 지난 주 TV 광고가 효과가 있어서 다운로드 증가하고 승차 유저도 늘었구나, 광고 타켓 고객이 많은
            3. 허상 지표도 완전체가 되면, 쓸모가 있게 됨
          5. 지표와 데이터 분석의 관계는?
            1. 선행지표 분석, 이탈 분석
    2. personal takeaway: concept of KPI, importance of 완전체 KPI and connection to related and relevant KPI

  1. 고객 관리를 위한 오퍼링 효과 분석- 과연 ‘이게’ ‘제대로" 먹혔을까? [권정민, Data Analyst @SK planet]
    1. lesson
      1. offering 개념: classical strategy of CRM 즉 프로모션/이벤트 (예. 쿠폰, 찌라시)
        1. 5W 1H: 타겟 고객들에게 (who) 적절할 때 (when) 우리 서비스/매장에서 (where) 적절한 benefit을 (what) 가능한 방법으로 (how) 제공; 목적 (why)은 LTV 증가/신규 고개 유입/이탈 고객 방지/서비스 인지도 상승
        2. 적용: 고객을 분류-> offering 차별화
      2. 기본 고객 관리
        1. 고객의 전반적인 lifetime 영향을 미치는 속성 구분 (e.g. 빨리빠져나갈 사람)
        2. 관련 데이터 수집 (e.g. 어떤 dungeon에선 이탈이 심함)
        3. 지속적인 모니터링 및 현 상황에 대한 고객 관리 목표 설정
      3. targetting
        1. 목적 종류 (신제품 추천, 신규 고객 유도, 이탈 예상 고객군 관리 등)에 해당하는 고객군 생성 및 분류
        2. 기본 속성(인구통계학 정보) 및 과거의 로그 데이터를 통한 고객군 생성
          1. e.g. 서울 지역에선 먹히는 데, 타 지역에선 먹히지 않음
        3. basic selection (rule-based: e.g. DOB, 20~30 women), classification, clustering,
      4. campaign
        1. 각각의 고객군에게 적합한 혜택을 제공함으로써 해당 목적에 도달할 수 있도록 함
          1. e.g. 프로모션, 이벤트 등을 통한 특별한 혜택 제공 (e.g. 나가려는 유저에게 쉬운 monster 제공)
        2. 제공할 campaign의 효과 및 고객군과의 적합도 등의 파악 + 예측 필요
      5. multivariate testing (similar to A/B testing)
        1. 초반 피크가 이후에까지 영향을 준다고 볼 수 없으나 장기적인 관측 필요 (e.g. 쿠폰은 일회성)
        2. campaign 속성이 매번 변하므로 지속적 활용 어려움
      6. 캠페인과 서비스 변경- 지속성
        1. 일회성으로 끝나는 건 아닌가?
        2. campaign 효과를 보기 위해 오래 기다릴 수 없는데?
        3. 캠페인 안해도 상관없는 것?
        4. 대조군을 만들 수 없는가?
        5. 한꺼번에 여러 종류 campaign 진행해야 되는데?
    2. personal takeaway: study new tool for offering evaluation (multivariate test + time-series causal analysis (CausalImpact: 시계열 분석))