Showing posts with label lesson. Show all posts
Showing posts with label lesson. Show all posts

Friday, February 2, 2018

[my takeaway] "Steve Jobs - The Lost Interview"

"I always ask why you do things... nobody knows why they... "

Q. How to run business?
1. be a curious person
“In business, … if you are willing to ask a lot of questions and think about things and work really hard, you can learn businesses pretty fast not the hardest thing in the world.”

2. learn how to program
“I think everybody in this country should learn how to program a computer. Should learn a computer language because it teaches you how to think.”

3. help people have vested interest in your product
“... a lot of other people had a very strong vested interest in helping IBM make it better so if it’s just been up to IBM they would have been crashed and burned but IBM did have I think a genius in their approach which was to have a lot of other people have a vested interest in their success and that’s what saved them in the end.”

4. manage content people well
“People get confused that the process is the content that’s the ultimate downfall of IBM. IBM had the best processed people in the world. They just forgot about the content. And that’s what happened a little bit at Apple, too. We had a lot of people who were great at management process. They just didn’t have a clue as to the content. And in my career, I found that the best people you know are the ones that really understand the content and they are pain in the butt to manage but you put up with it because they are so great at the content and that’s what makes great products. It’s not process it’s content.”

5. don’t care about being wrong just get it right
“I don’t care about being right. I just care about success. So you will find a lot of people that will tell you that I had a very strong opinion and they presented evidence to the contrary and five minutes later and I completely changed my mind because I’m like that I don’t mind being wrong. I’ll admit that I’m wrong a lot. It doesn’t matter to me that much. What matters to me is that we do the right thing.”

Sunday, July 26, 2015

[lesson] what I learned after watching "Stephen Key: 'One Simple Idea for Startups', Talks at Google"

1. idea to market process: find a pain point and have a solution -> file for provisional patent -> call companies -> sale sheet with rough prototype -> meet with them

2. for one year perceived ownership of my idea, consider filing for USPTO's provisional patent under 125 USD

3. play game for idea generation
(1) material change
(2) put it upside down
(3) mix and match 
(4) ask what if
(5) solve it
(6) go to inspiration spot (shower, movie, mall, nature)

4. When to license or start a company?
(1) Can my product be made at a price?
(2) Does it have a wow factor?
(3) Can I describe it in one sentence?
(4) What is the market size?

[lesson] what I learned from watching "7 Things I Learned At Google And Every Startup Should Copy"

1. ask "why not"? ... not "why!"
- e.g. why not break the rules? why not all of Europe instead of 10

2. No opinions, just data! 
- e.g. A/B testing

3. There's no such thing as over-communication
- e.g. make most information open -> people will trust you

4. Ask for forgiveness, not for permission
- e.g. Uber; ask why not?

5. Hire for the company, not for the job
- e.g. build culture that lasts; technology changes; hire people for solving problems

6. Give a license to dream
- e.g. 20% 

7. Think money last and users first
- e.g. if users are satisfied, they will come back; build cash register early; think how you will be making money from day one

Wednesday, May 20, 2015

[lesson: PM] after reading "Memories Reloaded: 프로덕트 매니저 (PM) 의 자질 - 1"

Memories Reloaded: 프로덕트 매니저 (PM) 의 자질 - 1: 가끔 커리어 패스로 프로덕트 매니저 (PM) 쪽을 하고 싶다는 분들로부터 프로덕트 매니저는 어떤 일을 하는지에 대한 질문을 받는다. 나보다 프로덕트 매니저로써 훨씬 뛰어난 분들이 많이 계시지만, 구글에서 얼마전까지 3년반동안 개인적으로 경험했던 것을...

Lesson learned from PM 자질 1편 (translation: characteristics of PM):

1. fan: "프로덕트 매니저는 자신이 맡은 서비스의 가장 열렬한 사용자 중 한명이어야 한다."

2. planner: "가장 기본적인 역할은 시장과 경쟁자 동향, 사용자 요구에 맞추어 제품이나 서비스의 피쳐를 기획하는 '기획자'의 역할이다."

3. bug reporter: "만약 버그가 발생했을 경우 그것을 가장 먼저 알아내고 개발팀에 이야기 해주는 사람이어야 하며,"

4. proactive problem solver: "사용자들이 불편을 겪고 있다면 어떤 불편인지를 알아내서 고치는 동시에 그 사용자들과 직접 대화도 하는 사람이어야 한다."

5. PR: "이와 관련된 PR 문제가 발생했다면 그것 역시 프로덕트 매니저가 일차적으로 책임을 져야 한다."

6. communication facilitator: "이와 관련된 모든 커뮤니케이션을 책임지는 과정에서 미팅 노트를 쓰는 등 사소한 잡일도 당연히 해야 한다.

7. integrator: "모든 것을 혼자서 다 해야 한다는 이야기가 아니라, 모든 것을 총괄하고 관리하고 이슈의 오너십을 가져야 한다는 것이다."

[lesson: PM] after reading "Memories Reloaded: 프로덕트 매니저 (PM) 의 자질 - 2"

Memories Reloaded: 프로덕트 매니저 (PM) 의 자질 - 2: (링크: 프로덕트 매니저 (PM) 의 자질 - 1 ) 방 안에서 가장 많이 알고있는 사람  프로덕트 매니저는 해당 제품이나 서비스를 둘러싼 모든 것들 -- 시장, 경쟁환경, 트렌드, 기술적인 부분들 -- 에 대해서 가장 잘 알고 있는 사람이어...

Lesson learned from PM 자질 2편 (translation: characteristics of PM):

1. study and think: "비전은 자다가 또는 샤워하다가 갑자기 나오는게 아니라, 많이 알고 많이 생각하는 사람에게 어느날 갑자기 찾아오는 것이다."

2. communicate with data: "정확한 팩트와 데이터에 기반해서 주장할 수 있어야 한다. 이런 면에서 가끔 프로덕트 매니저는 법정에 서는 변호사와 같기도 하다고 느껴진다.
나도 개인적으로 내가 생각할 때는 너무도 당연한 기능인데 그걸 넣는 것에 대해서 반대하는 팀을 설득해야 할 때가 종종 있었다. 그럴때 그냥 “아니 이건 당연한 건데 왜 그걸 모르냐”는 등의 주관적인 설득을 펼치면 거의 성과가 없었던 것 같다. 하지만 누구나 납득 가능한 데이터를 제시하면 다른 반응을 얻을 수 있었다. 이를테면 한번은 유저들을 대상으로 내가 제안했던 기능에 대한 설문 조사를 했고, 그 결과 80% 이상이 그 기능을 필요로 한다고 답변을 했었다. 그 데이터를 제시하자 어렵지 않게 그 기능을 추가하는 것으로 결론이 났었다. 전에는 반대했던 사람도 흔쾌히 결과를 수용했었다."

3. respond within one day: "이를테면 자신에게 온 이메일이 어떤 방식으로든 응답되는데 최대 24시간이 걸리지 않도록 하는 것이라든지,"

4. follow-up: "단순히 이메일을 포워딩만 하고 잊어버리는게 아니라 그 이메일이 잘 처리되고 있는지를 끝까지 팔로우업 하는 것, 이런 것들도 크게보면 모두 커뮤니케이션 능력에 해당하는 것이다."

5. sync-up all stakeholders: "목표는 자기가 커뮤니케이션 잘 하는 사람임을 증명하는게 아니라, 일을 이루어가기 위해서 모든 이익 대변자 (stakeholder) 들이 다 똑같은 정보를 가지고 있는지를 확인하는 일이다."

Sunday, April 19, 2015

[lesson] Peter Thiel's visit to Korea regarding his book Zero to One

lesson: build something no one has ever started

Friday, April 3, 2015

[lesson] 미국무부 경제부문 차관보 Charles Rivkin

At Startup Alliance, just attended a talk by Charles Rivkin, an Assistant Secretary of the State. So many good lessons relearned. 
1. Don't take no for an answer. 
2. Failure reveals character. 
3. Read and comprehend Korean/English faster on spot to address issues. 
4. Cultivate a manner of respect.

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

Wednesday, November 5, 2014

[lesson] "The Data on Diversity: It’s not just about being fair" by Beryl Nelson


  1. create heterogeneous work environment or at least acknowledge benefits of diversity: 
    • "Social scientists have shown that teams and organizations whose members are heterogeneous in meaningful ways, for example, in skill set, education, work experiences, perspectives on a problem, cultural orientation, and so forth, have a higher potential for innovation than teams whose members are homogeneous." 
    • "Diversity is important to organizations that innovate, but the culture of an organization determines whether minority members of the community can thrive." 
  2. be aware of my bias and unlearn them: "Know your own biases. Read some of the literature about unconscious bias and about the IAT, and then take the Implicit Attitude test5 at"
    • after taking this IAT (Implicit Aptitude Test), learned that I'm a little bit biased towards the relationship between weight and positivity. [link