{"success":true,"count":6,"items":[{"videoId":"T3VRz18ntjQ","chunkIndex":0,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 1 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","startup","product-teams","user-research","product-strategy","innovation","business","ux"],"normalizedKeywords":["프로덕트","비즈니스·전략","리더십·매니지먼트"],"targetAudience":[{"who":"초기 창업자","why":"새 문제를 만들기보다 기존 문제를 더 잘 푸는 관점을 얻을 수 있음"},{"who":"프로덕트 매니저","why":"성공하는 제품팀의 공통 원리와 잘못된 착각을 점검할 수 있음"},{"who":"실무 리더","why":"고객 이해와 제품 의사결정에 대한 팀의 시간 배분을 재고하게 됨"}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"마티 케이건은 최고의 제품팀과 그렇지 못한 팀의 차이를 설명하며, 많은 팀이 제품을 잘못 이해하는 10가지 오해를 짚겠다고 말한다. 이 도입부에서 그는 특히 '새로운 문제를 풀어야 한다'는 착각을 비판하고, 대부분의 위대한 제품은 완전히 새로운 문제보다 기존의 오래된 문제를 훨씬 더 잘 해결한 사례라고 주장한다. 애플과 구글의 예를 들어, 시장은 이미 존재했지만 솔루션의 질이 압도적으로 좋아졌기 때문에 성공했다고 설명한다.\n\n이어 그는 두 번째 오해로, 팀이 문제 공간을 이해한다는 이유로 너무 오래 고객 인터뷰와 리서치에만 머무는 경향을 지적한다. 사용자 연구 자체는 중요하지만, 현실에서는 스타트업은 자금이, 대기업은 인내심이 먼저 바닥나므로 '충분히 오래 탐색하는 이상적인 상황'이 아니라 '제한된 시간 안에 올바른 결정을 내리는 방식'이 필요하다고 강조한다.","insights":["위대한 제품은 새 문제보다 기존 문제를 더 잘 푼다.","카테고리 창출은 희귀하고, 비용도 매우 크다.","시장에 이미 불만족한 해답이 있을 때 개선이 가장 강력하다.","리서치는 중요하지만 시간 제한 안에서 써야 한다.","문제 이해는 길게, 의사결정은 늦지 않게 해야 한다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c0:29-50","startSegmentIndex":29,"endSegmentIndex":50,"startTime":277.199,"endTime":514.979,"durationSeconds":237.8,"preview":"새 문제 집착의 오류","mustSee":false},{"clipId":"T3VRz18ntjQ:c0:51-60","startSegmentIndex":51,"endSegmentIndex":60,"startTime":514.979,"endTime":607.54,"durationSeconds":92.6,"preview":"리서치의 함정","mustSee":false}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:02:54.909Z","keyClipsTotalSec":1255},{"videoId":"T3VRz18ntjQ","chunkIndex":1,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 2 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","product-discovery","b2b","domain-expertise","customer-interviews","solution-design","saas","product-strategy"],"normalizedKeywords":["프로덕트","비즈니스·전략","리더십·매니지먼트"],"targetAudience":[{"who":"프로덕트 매니저","why":"문제 탐색보다 해법 탐색에 시간을 써야 한다는 핵심 원칙을 얻을 수 있음"},{"who":"초기 창업자","why":"고객 요구를 그대로 받기보다 더 나은 해법을 설계하는 관점을 배울 수 있음"},{"who":"B2B 팀","why":"도메인 출신 채용과 레거시 관성의 함정을 이해하는 데 유용함"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업"],"summary":"이 영상은 제품에서 가장 어려운 일은 문제를 이해하는 것이 아니라, 고객이 실제로 선택할 만큼 압도적으로 좋은 해법을 만드는 것이라고 주장한다. Marty Cagan은 문제 발견에만 오래 머무르면 정작 팔릴 만한 솔루션을 만들 시간이 사라진다고 말하며, discovery의 초점은 거의 전적으로 solution discovery에 있어야 한다고 강조한다.\n\n또한 B2B 제품이 대체로 형편없는 이유로 '도메인 출신'만 뽑는 관행을 비판한다. 진짜 도메인 전문성은 지식에서 독단을 뺀 것이며, 많은 경우 빠르게 배우는 사람과 도메인 전문가 접근권이 더 중요하다고 본다. 마지막으로 고객은 가능한 해법을 스스로 알지 못하므로, 요구사항을 받아 적는 역할에 머물면 안 되고 제품팀이 해법을 설계해야 한다는 메시지로 마무리된다.","insights":["제품의 핵심 난제는 문제 이해가 아니라 해법 우월성이다.","문제 탐색에만 치우치면 팔릴 제품을 만들 시간이 줄어든다.","B2B가 나쁜 이유 중 하나는 도메인 출신 집착이다.","진짜 도메인 전문성은 지식에 관성을 더하지 않는 것이다.","고객은 문제를 말할 수 있어도 가능한 해법은 모른다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c1:1-18","startSegmentIndex":1,"endSegmentIndex":18,"startTime":600.59,"endTime":746.3389999999999,"durationSeconds":145.7,"preview":"해법이 본질이다","mustSee":true},{"clipId":"T3VRz18ntjQ:c1:19-27","startSegmentIndex":19,"endSegmentIndex":27,"startTime":746.3389999999999,"endTime":833.76,"durationSeconds":87.4,"preview":"발견의 초점 이동","mustSee":false},{"clipId":"T3VRz18ntjQ:c1:28-36","startSegmentIndex":28,"endSegmentIndex":36,"startTime":833.76,"endTime":939.8389999999999,"durationSeconds":106.1,"preview":"도메인 집착의 함정","mustSee":false},{"clipId":"T3VRz18ntjQ:c1:44-58","startSegmentIndex":44,"endSegmentIndex":58,"startTime":986.639,"endTime":1131.89,"durationSeconds":145.3,"preview":"독단 없는 전문성","mustSee":false},{"clipId":"T3VRz18ntjQ:c1:59-66","startSegmentIndex":59,"endSegmentIndex":66,"startTime":1131.89,"endTime":1205.62,"durationSeconds":73.7,"preview":"고객요구의 한계","mustSee":false}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:03:26.194Z","keyClipsTotalSec":1255},{"videoId":"T3VRz18ntjQ","chunkIndex":2,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 3 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","startup","customer-development","product-discovery","agile","product-strategy","entrepreneurship","business"],"normalizedKeywords":["프로덕트","비즈니스·전략","리더십·매니지먼트"],"targetAudience":[{"who":"초기 단계 창업자","why":"해결책 집착보다 문제 집착이 왜 중요한지 배울 수 있음"},{"who":"프로덕트 매니저","why":"고객이 아니라 팀이 솔루션을 발명해야 한다는 관점을 얻을 수 있음"},{"who":"애자일 실무자","why":"애자일을 절차가 아닌 빠른 학습과 배포로 다시 정의하게 됨"}],"normalizedAudience":["창업자·스타트업","프로덕트 매니저·기획자","지식노동자 일반"],"summary":"이 영상은 제품의 본질을 '고객 문제'와 '새롭게 가능한 해법'의 결합으로 설명하면서, 고객이나 스테이크홀더가 제품 해법을 직접 알려줄 수 있다는 생각을 강하게 비판한다. Marty Cagan은 Jeff Bezos와 Steve Jobs의 사례를 들어, 좋은 제품 솔루션은 인터뷰 답변에서 나오는 것이 아니라 팀이 고객을 대신해 발명해야 한다고 강조한다.\n\n이어 그는 창업자가 자신의 해결책에 집착해 같은 MVP를 수년간 반복한 사례를 통해, 문제에 집착하지 않으면 discovery가 멈추고 시간만 낭비된다고 말한다. 또한 유럽의 많은 팀이 product owner를 애자일 역할로 오해하며 실제로는 분기별 릴리스에 머무는 현실을 비판하고, 애자일의 문제는 원칙이 아니라 프로세스 중심 인력이 제품보다 절차를 앞세운 데 있다고 주장한다.","insights":["고객은 문제를 말할 수 있어도 해법은 대신 설계하지 못한다.","좋은 제품은 인터뷰의 평균값이 아니라 팀의 발명으로 나온다.","해결책에 집착하면 검증보다 변명만 반복하게 된다.","문제에 집착하는 팀만 다양한 접근을 빠르게 실험한다.","애자일의 핵심은 의식이 아니라 배포 속도와 학습 속도다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c2:1-12","startSegmentIndex":1,"endSegmentIndex":12,"startTime":1201.25,"endTime":1337.88,"durationSeconds":136.6,"preview":"고객은 해법을 못 준다","mustSee":false},{"clipId":"T3VRz18ntjQ:c2:13-30","startSegmentIndex":13,"endSegmentIndex":30,"startTime":1337.88,"endTime":1576.01,"durationSeconds":238.1,"preview":"문제보다 해법에 집착","mustSee":false},{"clipId":"T3VRz18ntjQ:c2:34-46","startSegmentIndex":34,"endSegmentIndex":46,"startTime":1612.86,"endTime":1726.86,"durationSeconds":114,"preview":"애자일의 진짜 기준","mustSee":true},{"clipId":"T3VRz18ntjQ:c2:47-56","startSegmentIndex":47,"endSegmentIndex":56,"startTime":1726.86,"endTime":1804.059,"durationSeconds":77.2,"preview":"프로세스가 제품을 잡는다","mustSee":false}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:03:46.939Z","keyClipsTotalSec":1255},{"videoId":"T3VRz18ntjQ","chunkIndex":3,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 4 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","product-owner","product-design","engineering","product-discovery","decision-making","leadership","agile","startup","business-strategy"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","비즈니스·전략"],"targetAudience":[{"who":"프로덕트 매니저","why":"PM의 본질이 가치·실현가능성 판단과 팀 정렬임을 다시 세울 수 있음"},{"who":"창업자","why":"프로세스보다 제품 판단과 엔지니어 역량을 어떻게 써야 하는지 배울 수 있음"},{"who":"엔지니어","why":"단순 구현자가 아니라 제품 방향을 함께 만드는 역할을 이해할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"마티 케이건은 프로덕트 오너와 프로덕트 매니저를 강하게 구분하며, PM의 핵심 책임은 프로세스 관리가 아니라 제품의 가치와 사업적 실현가능성(viability)을 판단하는 일이라고 강조한다. 디자이너는 사용성, 엔지니어는 기술적 실현가능성을 주로 보지만, PM은 수익화·시장성·규제·윤리·비용까지 포함해 전체 해법이 성립하는지 책임져야 한다고 말한다. 이 역할이 비면 의사결정은 위로 올라가고, 결국 디자인 바이 커밋티로 흐르기 쉽다고 경고한다.\n\n또한 그는 ‘혁신적 아이디어를 먼저 내야 한다’거나 ‘엔지니어는 코딩만 하면 된다’는 생각을 비판한다. 좋은 제품은 아이디어에서 끝나는 것이 아니라, 엔지니어와 디자이너가 함께 프로토타입을 반복 검증하며 다듬는 discovery 과정에서 나온다고 설명한다. 특히 강한 제품 회사에서는 엔지니어가 단순 실행자가 아니라 무엇이 가능한지 제시하고, 동의한 뒤에만 만들며, 그 자체가 자가교정 장치라고 주장한다.","insights":["PM의 본질은 프로세스가 아니라 가치와 사업성 판단이다.","좋은 제품은 아이디어가 아니라 반복 검증으로 만들어진다.","엔지니어는 실행자가 아니라 가능성을 제시하는 공동 창조자다.","팀이 이유를 이해하지 못하면 실행은 형식만 남는다.","의사결정을 위로 올릴수록 디자인 바이 커밋티가 된다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c3:1-19","startSegmentIndex":1,"endSegmentIndex":19,"startTime":1800.95,"endTime":1967.039,"durationSeconds":166.1,"preview":"PM의 진짜 책임","mustSee":true},{"clipId":"T3VRz18ntjQ:c3:20-34","startSegmentIndex":20,"endSegmentIndex":34,"startTime":1967.039,"endTime":2072.879,"durationSeconds":105.8,"preview":"프로세스 집착의 함정","mustSee":false},{"clipId":"T3VRz18ntjQ:c3:35-48","startSegmentIndex":35,"endSegmentIndex":48,"startTime":2072.879,"endTime":2198.22,"durationSeconds":125.3,"preview":"아이디어는 시작일뿐","mustSee":false},{"clipId":"T3VRz18ntjQ:c3:49-73","startSegmentIndex":49,"endSegmentIndex":73,"startTime":2198.22,"endTime":2401.72,"durationSeconds":203.5,"preview":"엔지니어를 활용하라","mustSee":true}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:04:22.616Z","keyClipsTotalSec":1255},{"videoId":"T3VRz18ntjQ","chunkIndex":4,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 5 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","product-market-fit","startup","go-to-market","engineering","agile","process","leadership","product-strategy"],"normalizedKeywords":["프로덕트","비즈니스·전략","리더십·매니지먼트"],"targetAudience":[{"who":"프로덕트 매니저","why":"제품만이 아니라 시장·유통까지 함께 봐야 함을 배울 수 있음"},{"who":"초기 단계 창업자","why":"PMF 전에 마케팅·세일즈를 키우면 돈을 낭비하기 쉬움을 알 수 있음"},{"who":"엔지니어","why":"좋은 엔지니어와 프로세스에 잠식되지 않는 팀 문화의 기준을 얻을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"이 영상은 좋은 제품을 만드는 것만으로는 부족하며, 진짜 product-market fit은 제품과 시장의 양쪽이 함께 맞아야 성립한다고 강조한다. 특히 많은 회사가 제품이 조금 보이기 시작하면 너무 일찍 세일즈와 마케팅을 키워 돈을 낭비하고, 고객이 제품을 찾고 이해하고 구매할 수 있는 go-to-market 경로를 설계하지 못한다고 비판한다.\n\n또한 대기업과 성장한 조직이 'process people'에게 잠식되면 혁신이 사라진다고 경고하며, 아마존의 day one/day two, 스티브 잡스의 'process의 병' 같은 사례를 들어 설명한다. 마지막으로 회사를 최고의 제품 회사처럼 바꾸려면 빌드·테스트·배포 방식, 특히 최소 2주마다 고객에게 릴리스하는 체계를 갖춰야 한다고 주장한다.","insights":["PMF는 제품만이 아니라 시장 접근까지 포함한다.","제품이 좋아도 고객이 못 찾으면 시장에서 사라진다.","PMF 이전의 무리한 세일즈·마케팅은 돈만 태운다.","큰 회사의 최대 적은 프로세스가 생각을 대신하는 것이다.","지속적 릴리스가 좋은 팀 문화를 강제로 만든다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c4:3-18","startSegmentIndex":3,"endSegmentIndex":18,"startTime":2431.31,"endTime":2601.66,"durationSeconds":170.3,"preview":"PMF는 시장까지다","mustSee":true},{"clipId":"T3VRz18ntjQ:c4:19-31","startSegmentIndex":19,"endSegmentIndex":31,"startTime":2601.66,"endTime":2688.54,"durationSeconds":86.9,"preview":"프로세스의 함정","mustSee":false},{"clipId":"T3VRz18ntjQ:c4:32-51","startSegmentIndex":32,"endSegmentIndex":51,"startTime":2688.54,"endTime":2888.88,"durationSeconds":200.3,"preview":"혁신을 잃는 이유","mustSee":false},{"clipId":"T3VRz18ntjQ:c4:52-64","startSegmentIndex":52,"endSegmentIndex":64,"startTime":2888.88,"endTime":3009.599,"durationSeconds":120.7,"preview":"릴리스가 문화를 만든다","mustSee":true}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:04:43.032Z","keyClipsTotalSec":1255},{"videoId":"T3VRz18ntjQ","chunkIndex":5,"totalChunks":6,"title":"Marty Cagan - The Nature of Product — Part 6 of 6","thumbnail":"https://i.ytimg.com/vi/T3VRz18ntjQ/hqdefault.jpg?sqp=-oaymwEmCOADEOgC8quKqQMa8AEB-AH-CYAC0AWKAgwIABABGH8gMSgTMA8=&rs=AOn4CLCzeGRmIOg1v7mrqjcDPUw9MSo0kQ","duration":3539,"uploader":"School of Product","youtubeUrl":"https://www.youtube.com/watch?v=T3VRz18ntjQ","keywords":["product-management","product-strategy","continuous-delivery","agile","product-discovery","software-development","team-organization","technology"],"normalizedKeywords":["프로덕트","비즈니스·전략","엔지니어링"],"targetAudience":[{"who":"프로덕트 매니저","why":"문제 정의, 제품 발견, 전략 우선순위의 역할을 직접 다룸"},{"who":"개발 조직 리더","why":"배포 방식과 팀 운영을 제품 조직 관점에서 재정의함"},{"who":"창업자","why":"제한된 자원에서 어떤 문제를 풀지 정하는 전략이 중요함"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"마티 케이건은 강한 제품 회사가 되기 위해서는 세 가지를 바꿔야 한다고 말한다. 첫째는 작은 단위로 자주 배포하는 방식으로 바꾸는 것이고, 둘째는 기능을 찍어내는 방식이 아니라 문제를 발견하고 해결하는 방식으로 바꾸는 것이다. 셋째는 모든 문제를 다 하지 말고, 데이터와 리서치, 기술·산업 트렌드를 바탕으로 어떤 문제를 우선할지 정하는 제품 전략을 갖추는 일이다.\n\n그는 SAFe 같은 형식적 프로세스를 강하게 비판하면서, 진짜 애자일은 빠른 배포와 문제 해결 능력, 그리고 전략적 선택에서 나온다고 주장한다. 또한 product manager의 존재 이유도 단순 기능 전달이 아니라 가치와 실행 가능성을 함께 다루는 데 있다고 강조한다. Stripe와 같은 사례를 들어, 작은 팀이 큰 조직보다 성과를 낼 수 있는 이유가 바로 제품 전략의 힘이라고 설명한다.","insights":["자주 작은 배포가 품질과 속도를 동시에 높인다.","기능 전달이 아니라 문제 해결이 제품팀의 본업이다.","제품 발견의 핵심은 가치·사용성·실행가능성·수익성 검증이다.","좋은 제품 회사는 무엇을 안 할지 정하는 데 강하다.","제품 전략은 적은 인원으로도 경쟁사를 압도하게 만드는 힘이다."],"keyClips":[{"clipId":"T3VRz18ntjQ:c5:1-12","startSegmentIndex":1,"endSegmentIndex":12,"startTime":3003.55,"endTime":3112.319,"durationSeconds":108.8,"preview":"작은 배포가 정답","mustSee":false},{"clipId":"T3VRz18ntjQ:c5:13-29","startSegmentIndex":13,"endSegmentIndex":29,"startTime":3112.319,"endTime":3270.54,"durationSeconds":158.2,"preview":"기능이 아닌 문제","mustSee":true},{"clipId":"T3VRz18ntjQ:c5:30-49","startSegmentIndex":30,"endSegmentIndex":49,"startTime":3270.54,"endTime":3446.64,"durationSeconds":176.1,"preview":"전략이 힘을 만든다","mustSee":true},{"clipId":"T3VRz18ntjQ:c5:50-53","startSegmentIndex":50,"endSegmentIndex":53,"startTime":3446.64,"endTime":3476.28,"durationSeconds":29.6,"preview":"강한 회사의 조건","mustSee":false}],"curatedSegments":[{"segmentIndex":8,"text":"But this point is so true, and this is what I try to emphasize to product teams: what's hard about product is not understanding the problem space; it's coming up with a solution that's so much better than the alternatives that your customers choose you.","startTime":638.88,"endTime":666.48,"durationSeconds":28,"level":"C1","overallScore":9.8,"rationale":"핵심 통찰과 구조 표현이 매우 풍부."},{"segmentIndex":18,"text":"There's nothing you can do after that. And what he didn't realize is that what you want to do as a founder is not fall in love with your solution, but fall in love with the problem.","startTime":1411.919,"endTime":1427.94,"durationSeconds":16,"level":"B2","overallScore":9.8,"rationale":"창업자 태도의 핵심 교훈을 제시함."},{"segmentIndex":39,"text":"But in every one of these cases, there were many products before it solving that problem, and the difference was they were able to find a solution that was dramatically better.","startTime":389.22,"endTime":409.02,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"차별화의 본질을 명확히 설명하는 핵심 문장."},{"segmentIndex":24,"text":"And if they spend too much time on what's called problem discovery instead of solution discovery, they won't have time to come up with a product that people will buy.","startTime":780.899,"endTime":807.779,"durationSeconds":27,"level":"C1","overallScore":8.8,"rationale":"문제·해결 탐색의 우선순위를 날카롭게 설명."},{"segmentIndex":44,"text":"So he's right: true domain expertise is knowledge of the domain minus dogma.","startTime":986.639,"endTime":995.76,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"개념을 날카롭게 정의한 통찰 문장."},{"segmentIndex":55,"text":"So you need access, but it is much better to come with that open learning mind than it is to have to try to figure out what are the things you know that are really important and what are the things that are just legacy. So, the only big thing I want you to take away from this is that it's critical that you spend your time on coming up with a solution.","startTime":1088.22,"endTime":1105.919,"durationSeconds":18,"level":"C1","overallScore":9,"rationale":"핵심 교훈과 표현 가치가 모두 높음."},{"segmentIndex":7,"text":"Your customers can't tell you what to build. Your job is to invent great solutions on our customers' behalf.'","startTime":1256.039,"endTime":1266.419,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"제품팀 역할 원칙을 직접 제시함."},{"segmentIndex":27,"text":"If that startup team had done a solution tree, what it really makes you do is realize right at the beginning that there are many different ways we could approach this problem, and if the first one doesn't work after a few weeks, let's try another one.","startTime":1524.96,"endTime":1540.38,"durationSeconds":15,"level":"C1","overallScore":8.8,"rationale":"기법의 실제 효과를 명확히 설명함."},{"segmentIndex":45,"text":"To me, it's obvious. And let me just be brutally clear here: if you're not releasing at least once every two weeks, you can call yourself agile if you want, you're not fooling anybody.","startTime":1705.919,"endTime":1721.94,"durationSeconds":16,"level":"B2","overallScore":9,"rationale":"애자일 기준을 단호하게 제시함."},{"segmentIndex":19,"text":"So then what happens? You have to escalate everything up to your leaders, or you have to make any kind of decision, you have to get all the stakeholders in a room, which leads to something called design by committee, which is never a good result.","startTime":1946.88,"endTime":1967.039,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"의사결정 실패 메커니즘을 잘 설명함."},{"segmentIndex":41,"text":"A product comes out of this discovery process where you're iterating, and every iteration you do, you learn some things that you need to change, other things that are working, and you keep iterating on it until you've crafted a great solution.","startTime":2117.78,"endTime":2135.88,"durationSeconds":18,"level":"C1","overallScore":8.8,"rationale":"제품 발견의 반복 원리를 잘 설명함."},{"segmentIndex":59,"text":"And the funny thing is, the way most companies, the rest, work, the engineers are not... In fact, I'll make this very specific for you: if the first time your engineers are seeing your product ideas is at sprint planning, you have totally failed.","startTime":2280.119,"endTime":2301.359,"durationSeconds":21,"level":"C1","overallScore":9,"rationale":"강한 기준 제시와 표현 다양성이 뛰어남."},{"segmentIndex":18,"text":"And if you're trying to manage your money well, you don't want to ramp up sales and marketing until after you have demonstrated product-market fit, because before that you're going to waste a lot of money.","startTime":2582.72,"endTime":2601.66,"durationSeconds":19,"level":"C1","overallScore":8.8,"rationale":"타이밍 조언이 분명하고 실용적."},{"segmentIndex":40,"text":"But he's right: the problem is that big companies, process becomes a substitute for thinking.","startTime":2759.48,"endTime":2768.4,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"프로세스 비판의 핵심 통찰 문장."},{"segmentIndex":8,"text":"And if they are, if I can find, my rule is normally, if I can find six teams at six different companies using a method or a technique that's working for them, then I'll talk about it here. I talk about it in books.","startTime":83.4,"endTime":100.74000000000001,"durationSeconds":17,"level":"C1","overallScore":8,"rationale":"자신의 검증 기준을 구체적으로 제시함."},{"segmentIndex":13,"text":"But until then, I'm just going to focus on what they're using consistently to succeed. Now, the surprise is not so much how good companies work.","startTime":122.52,"endTime":130.38,"durationSeconds":8,"level":"B2","overallScore":7.8,"rationale":"성공 요인에 집중하자는 핵심 메시지."},{"segmentIndex":14,"text":"The surprise is how different that is from how most companies work.","startTime":130.38,"endTime":140.099,"durationSeconds":10,"level":"B2","overallScore":7.4,"rationale":"좋은 회사와 보통 회사의 차이를 날카롭게 짚음."},{"segmentIndex":35,"text":"But the truth is, almost every great product out there is not solving a new problem.","startTime":351.6,"endTime":360.36,"durationSeconds":9,"level":"B2","overallScore":7.4,"rationale":"주장의 핵심을 직설적으로 압축함."},{"segmentIndex":37,"text":"This is really important to understand because, and I mean literally, 99% of the great product teams I find, they are all working on old problems.","startTime":364.139,"endTime":379.919,"durationSeconds":16,"level":"B2","overallScore":7.8,"rationale":"핵심 주장에 근거와 강도를 더함."},{"segmentIndex":41,"text":"That's called category development, when you're... and it's very expensive, by the way, because you have to educate the market that this is a problem they should care about.","startTime":420.36,"endTime":430.62,"durationSeconds":10,"level":"C1","overallScore":8,"rationale":"개념 정의와 시장 교육 비용 통찰이 좋음."}],"generatedAt":"2026-06-25T00:05:12.592Z","keyClipsTotalSec":1255}]}