{"success":true,"count":7,"items":[{"videoId":"J0FOFJFtOFw","chunkIndex":0,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 1 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","agile","product-strategy","product-discovery","continuous-delivery","outcomes","transformation","software-development"],"normalizedKeywords":["프로덕트","엔지니어링","리더십·매니지먼트"],"targetAudience":[{"who":"프로덕트 매니저","why":"기능 나열이 아닌 문제 선택·발견·배포 전환의 기준을 얻을 수 있음"},{"who":"개발팀 리더","why":"지속 배포와 계측 중심의 실제 애자일 운영 방식을 점검할 수 있음"},{"who":"제품 조직 리더","why":"조직을 결과 중심으로 바꾸는 전환의 3개 축을 이해하는 데 유용함"}],"normalizedAudience":["프로덕트 매니저·기획자","엔지니어·개발자"],"summary":"마티 케이건이 좋은 제품 조직이 공통적으로 가진 핵심 원칙을 설명하며, 제품 관리를 'output'이 아니라 'outcomes'를 만드는 일로 정의한다. 이를 위해서는 세 가지가 바뀌어야 한다고 말한다: 무엇을 만들지 정하는 방식(제품 전략), 문제를 푸는 방식(제품 디스커버리), 그리고 실제로 빌드·테스트·배포하는 방식이다.\n\n특히 그는 많은 조직이 여전히 스테이크홀더가 기능과 프로젝트를 정하고 팀이 순서대로 처리하는 방식에 머문다고 비판한다. 진짜 애자일은 방법론 이름이 아니라 지속적으로 배포하고, 계측하고, 고객을 해치지 않으면서 빠르게 학습하는 능력이라고 강조한다. Scrum이나 분기별 릴리스처럼 '애자일처럼 보이는 것'은 본질이 아니며, 결과를 만드는 조직만이 진짜 변화를 만든다고 주장한다.","insights":["제품 조직의 목표는 산출물이 아니라 결과를 만드는 것이다.","좋은 제품 회사는 전략·디스커버리·배포를 함께 바꾼다.","기능 우선 로드맵은 문제 선택을 왜곡하기 쉽다.","진짜 애자일은 분기 릴리스가 아니라 지속 배포다.","계측과 모니터링 없이는 outcomes를 증명할 수 없다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c0:3-9","startSegmentIndex":3,"endSegmentIndex":9,"startTime":11.88,"endTime":44.2,"durationSeconds":32.3,"preview":"성과 중심 전환","mustSee":true},{"clipId":"J0FOFJFtOFw:c0:22-28","startSegmentIndex":22,"endSegmentIndex":28,"startTime":126.439,"endTime":175.48,"durationSeconds":49,"preview":"배워지던 제품관리","mustSee":false},{"clipId":"J0FOFJFtOFw:c0:38-42","startSegmentIndex":38,"endSegmentIndex":42,"startTime":243.799,"endTime":272.28,"durationSeconds":28.5,"preview":"전략이 먼저다","mustSee":true},{"clipId":"J0FOFJFtOFw:c0:58-62","startSegmentIndex":58,"endSegmentIndex":62,"startTime":408.88,"endTime":450.759,"durationSeconds":41.9,"preview":"문제 해결의 방식","mustSee":false},{"clipId":"J0FOFJFtOFw:c0:63-83","startSegmentIndex":63,"endSegmentIndex":83,"startTime":450.759,"endTime":607.399,"durationSeconds":156.6,"preview":"진짜 애자일 기준","mustSee":true}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:17:00.182Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":1,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 2 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","product-team","product-strategy","leadership","cross-functional","software-development","organization-design","product-culture"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","비즈니스·전략"],"targetAudience":[{"who":"프로덕트 매니저","why":"진짜 PM의 역할과 오해받는 직무 범위를 분명히 볼 수 있음"},{"who":"엔지니어 리드","why":"기술 리더가 무엇에 책임져야 하는지 정리하는 데 도움됨"},{"who":"디자인 리더","why":"디자이너와 PM 간 권한·책임 충돌의 구조를 이해할 수 있음"},{"who":"조직 리더","why":"제품 모델 전환에 필요한 역량·문화·전략을 한 번에 볼 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","디자인 리더·CXO","엔지니어·개발자"],"summary":"이 영상은 '제품 조직이 제대로 일하려면 무엇이 바뀌어야 하는가'를 설명한다. 핵심 주장은 세 가지 변화, 즉 어떤 문제를 풀지 정하는 방식, 문제를 푸는 방식, 솔루션을 배포하는 방식이 바뀌어야 하며, 이를 위해 조직에는 네 가지 새로운 역량과 다섯 가지 핵심 개념이 필요하다는 것이다.\n\n특히 많은 회사가 제품 조직을 운영한다고 생각하지만 실제로는 feature team에 머물러 있다고 비판한다. 그 결과 PM·디자이너·엔지니어 간 충돌이 생기고, 진짜 product strategy, product team, discovery/delivery, product culture, product principles가 갖춰지지 않는다. 결국 이 영상은 '역할 명칭'이 아니라 '책임 구조와 의사결정 체계'를 바꾸지 않으면 제품 전환이 실패한다고 말한다.","insights":["제품 전환은 역할 추가가 아니라 책임 구조의 재설계다.","진짜 PM은 결과 책임을 지고, 일정 전달자는 아니다.","디자이너·엔지니어 갈등은 보통 feature team의 증상이다.","전략은 팀별로 쪼개는 것이 아니라 팀을 관통해야 한다.","실험과 빠른 배포 없이는 outcome 검증도 불가능하다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c1:1-4","startSegmentIndex":1,"endSegmentIndex":4,"startTime":601.069,"endTime":637.519,"durationSeconds":36.5,"preview":"제품모델 전환의 뼈대","mustSee":false},{"clipId":"J0FOFJFtOFw:c1:7-18","startSegmentIndex":7,"endSegmentIndex":18,"startTime":650.32,"endTime":745.32,"durationSeconds":95,"preview":"네 가지 핵심 역량","mustSee":true},{"clipId":"J0FOFJFtOFw:c1:19-32","startSegmentIndex":19,"endSegmentIndex":32,"startTime":745.32,"endTime":844.88,"durationSeconds":99.6,"preview":"전략과 리더십의 역할","mustSee":false},{"clipId":"J0FOFJFtOFw:c1:33-60","startSegmentIndex":33,"endSegmentIndex":60,"startTime":844.88,"endTime":1049.44,"durationSeconds":204.6,"preview":"제품모델의 다섯 개념","mustSee":true},{"clipId":"J0FOFJFtOFw:c1:62-80","startSegmentIndex":62,"endSegmentIndex":80,"startTime":1053.32,"endTime":1206.24,"durationSeconds":152.9,"preview":"기능팀의 갈등 신호","mustSee":false}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:17:29.242Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":2,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 3 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","feature-team","product-ownership","customer-research","role-clarity","agency","career-growth","leadership","business-strategy"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","커리어·성장"],"targetAudience":[{"who":"프로덕트 매니저","why":"피처팀식 역할에서 벗어나 진짜 PM의 책임을 이해하는 데 도움됨"},{"who":"프로덕트 리더","why":"조직 구조와 역할 정의를 바꿔 영향력을 키우는 관점을 얻을 수 있음"},{"who":"커리어 전환자","why":"기술·비즈니스·고객 이해를 빠르게 넓히는 성장 전략을 배울 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","지식노동자 일반","학생·주니어"],"summary":"이 영상은 '피처팀(feature team)'에서 일하는 제품 역할이 왜 쉽게 대체 가능해 보이며, 회사가 비용을 줄일 때 특히 취약해지는지 날카롭게 지적한다. 화자는 진짜 제품 팀이라면 PM, 디자이너, 엔지니어가 각각 가치/실용성, 사용자 경험, 기술적 실현 가능성과 배송 책임을 분명히 나눠 맡기 때문에 역할이 흐려지지 않는다고 설명한다. 반대로 왜 단순히 'why를 전달하고 회의를 조율하는 일'만으로는 PM의 존재 이유를 설명할 수 없는지도 강조한다.\n\n이어 그는 개인 기여자와 리더 모두가 조직을 바꿀 수 있는 'agency'를 과소평가하지 말라고 조언한다. 특히 피처팀에 있는 PM이라도 회사를 옮기지 않고도 역할을 개선할 수 있으며, 이를 위해서는 고객 이해, 데이터, 비즈니스 구조, 산업 지식을 스스로 익히고 팀의 공감대를 얻어야 한다고 말한다. 결국 진짜 PM이 된다는 것은 프로세스 운영자가 아니라 제품 결과에 책임지는 사람으로 성장하는 일이라는 메시지다.","insights":["피처팀 PM은 가치 창출이 약해 보여 가장 먼저 흔들린다.","PM의 본질은 why 전달이 아니라 결과 책임이다.","진짜 제품팀은 역할이 겹치지 않게 책임을 분리한다.","회사 탓만 하기보다 개인의 agency를 키워야 바뀐다.","고객·데이터·비즈니스를 알아야 실질적 PM이 된다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c2:1-14","startSegmentIndex":1,"endSegmentIndex":14,"startTime":1202.029,"endTime":1306.559,"durationSeconds":104.5,"preview":"피처팀의 취약성","mustSee":false},{"clipId":"J0FOFJFtOFw:c2:15-26","startSegmentIndex":15,"endSegmentIndex":26,"startTime":1306.559,"endTime":1388.48,"durationSeconds":81.9,"preview":"진짜 팀의 분업","mustSee":false},{"clipId":"J0FOFJFtOFw:c2:27-40","startSegmentIndex":27,"endSegmentIndex":40,"startTime":1388.48,"endTime":1494.279,"durationSeconds":105.8,"preview":"변화는 가능하다","mustSee":true},{"clipId":"J0FOFJFtOFw:c2:41-61","startSegmentIndex":41,"endSegmentIndex":61,"startTime":1494.279,"endTime":1671.08,"durationSeconds":176.8,"preview":"진짜 PM이 되는 법","mustSee":false},{"clipId":"J0FOFJFtOFw:c2:62-75","startSegmentIndex":62,"endSegmentIndex":75,"startTime":1671.08,"endTime":1792.2,"durationSeconds":121.1,"preview":"팀과 함께 성장","mustSee":false}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:17:48.937Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":3,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 4 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","product-leadership","coaching","organizational-change","leadership","product-operating-model","team-transformation","pilot-teams","product-strategy","engineering-management"],"normalizedKeywords":["리더십·매니지먼트","프로덕트","비즈니스·전략"],"targetAudience":[{"who":"프로덕트 리더","why":"조직을 제품 운영 방식으로 바꾸는 리더십과 설득 전략을 배울 수 있음"},{"who":"제품 조직 관리자","why":"PM들의 역량을 키우고 회사 전체를 변화시키는 실전 접근이 담겨 있음"},{"who":"창업자","why":"작은 파일럿으로 조직 변화를 검증하는 방법을 참고할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","지식노동자 일반"],"summary":"이 영상은 제품 조직을 '통제 중심'에서 '제품 운영 모델'로 바꾸는 방법을 설명한다. 핵심은 개별 제품 리더가 먼저 PM들의 역량을 키우고, 그다음 회사의 핵심 이해관계자와 CEO를 설득해 신뢰를 쌓는 것이다. 변화는 전사 일괄 도입보다 파일럿 팀으로 시작하는 편이 훨씬 안전하며, 특히 Head of Product와 Head of Engineering의 역할이 성패를 좌우한다고 강조한다.\n\n또한 저자는 강한 명령이나 워터폴식 전환보다, 기존 리더들의 우려를 인정하고 실험을 제안하는 방식이 더 효과적이라고 말한다. Trainline 사례를 통해, 낡은 구조의 회사도 올바른 리더와 작은 실험을 통해 제품 회사처럼 재구성될 수 있음을 보여준다.","insights":["제품 조직 변화의 성패는 결국 리더 두 명에게 달려 있다.","PM을 바꾸려면 먼저 PM 리더가 코칭 역량을 가져야 한다.","전사 혁신보다 파일럿 팀이 변화 저항을 훨씬 낮춘다.","사람을 설득할 때는 통제 박탈이 아니라 더 나은 결과를 제시하라.","좋은 제품 운영 모델은 프로세스보다 신뢰를 먼저 만든다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c3:11-24","startSegmentIndex":11,"endSegmentIndex":24,"startTime":1878.76,"endTime":2012.36,"durationSeconds":133.6,"preview":"PM 코칭이 출발점","mustSee":true},{"clipId":"J0FOFJFtOFw:c3:27-42","startSegmentIndex":27,"endSegmentIndex":42,"startTime":2034.48,"endTime":2185.319,"durationSeconds":150.8,"preview":"권한보다 신뢰 설득","mustSee":false},{"clipId":"J0FOFJFtOFw:c3:46-55","startSegmentIndex":46,"endSegmentIndex":55,"startTime":2225.48,"endTime":2320.839,"durationSeconds":95.4,"preview":"파일럿이 혁신을 만든다","mustSee":true},{"clipId":"J0FOFJFtOFw:c3:56-66","startSegmentIndex":56,"endSegmentIndex":66,"startTime":2320.839,"endTime":2404.92,"durationSeconds":84.1,"preview":"Trainline 전환 사례","mustSee":false}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:18:17.389Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":4,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 5 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","product-leadership","coaching","digital-transformation","hiring","product-strategy","organizational-change","agile"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","비즈니스·전략"],"targetAudience":[{"who":"프로덕트 리더","why":"제품 조직 전환에 필요한 리더의 역할과 코칭 기준을 배울 수 있음"},{"who":"프로덕트 매니저","why":"좋은 제품 전략과 제품 코칭이 무엇인지 기준을 세우는 데 도움됨"},{"who":"조직개편 담당자","why":"기존 조직을 제품 중심으로 바꾸는 과정과 채용 원칙을 이해할 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","엔지니어·개발자"],"summary":"이 영상은 제품 조직을 제대로 바꾸기 위해 무엇이 필요한지, 특히 제품 리더와 코치의 역할을 중심으로 설명한다. 한 사례로는 중견 기업이 제품 원칙을 도입하고 사람을 채용·코칭하며 제품 비전, 전략, 팀 토폴로지, 아키텍처를 정비해 몇 년 만에 큰 성과를 낸 과정을 들려준다. 핵심 메시지는 조직 변환은 문서나 구호가 아니라, 실제 경험이 있는 리더가 사람을 키우고 전략적 맥락을 설계할 때 가능하다는 것이다.\n\n또한 '코치'라는 말만 믿고 경험 없는 사람을 쓰면 안 된다고 강하게 경고한다. 특히 제품 코칭은 심리상담식 코칭이 아니라 실제 제품 전략과 의사결정을 도와줄 수 있는 실전형 코칭이어야 하며, CSPO/PSPO 같은 교육도 실무 경험 없는 강사가 가르치는 경우가 많다고 비판한다. 마지막으로, 책에서 20개 원칙을 제시하더라도 상황에 따라 해석이 필요하다는 문제의식으로 이어진다.","insights":["조직 전환은 채용보다 먼저 원칙과 맥락을 설계해야 한다.","제품 리더의 핵심은 사람 개발과 전략적 맥락 구축이다.","경험 없는 코치는 제품 전략을 가르칠 수 없다.","좋은 코칭은 위로가 아니라 의사결정 능력을 키운다.","변화는 1~3년 걸리며, 실전형 리더가 있어야 성과가 난다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c4:3-19","startSegmentIndex":3,"endSegmentIndex":19,"startTime":2408.88,"endTime":2540.119,"durationSeconds":131.2,"preview":"조직 전환의 실제","mustSee":true},{"clipId":"J0FOFJFtOFw:c4:20-34","startSegmentIndex":20,"endSegmentIndex":34,"startTime":2540.119,"endTime":2661.48,"durationSeconds":121.4,"preview":"경험 있는 코칭","mustSee":false},{"clipId":"J0FOFJFtOFw:c4:35-51","startSegmentIndex":35,"endSegmentIndex":51,"startTime":2661.48,"endTime":2811.72,"durationSeconds":150.2,"preview":"가짜 코치의 함정","mustSee":false},{"clipId":"J0FOFJFtOFw:c4:52-72","startSegmentIndex":52,"endSegmentIndex":72,"startTime":2811.72,"endTime":2973.2,"durationSeconds":161.5,"preview":"코칭의 정의 차이","mustSee":true},{"clipId":"J0FOFJFtOFw:c4:73-76","startSegmentIndex":73,"endSegmentIndex":76,"startTime":2973.2,"endTime":2997.76,"durationSeconds":24.6,"preview":"원칙의 해석법","mustSee":false}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:18:49.034Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":5,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 6 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","product-culture","principles","experimentation","hardware","software","book-review","leadership","design"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","비즈니스·전략"],"targetAudience":[{"who":"프로덕트 매니저","why":"제품 원칙과 역할 정의를 다시 생각하게 해줌"},{"who":"창업자","why":"좋은 제품과 조직 문화를 보는 기준을 얻을 수 있음"},{"who":"기획자","why":"프로세스보다 원칙이 더 중요하다는 관점을 배울 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업","디자인 리더·CXO"],"summary":"이 영상은 프로덕트 일을 볼 때 '원칙'과 '도구/방법'을 구분해야 한다는 메시지를 중심으로 전개된다. 스피커는 진짜 제품 원칙은 오래 유지되지만, 이를 실행하는 툴과 프로세스는 빠르게 바뀐다고 말하며, 실험 문화처럼 본질은 같고 실행 수단만 진화하는 영역을 예로 든다.\n\n이어 최근 인상 깊게 읽은 책으로 Tony Fadell의 Build를 언급하며, 하드웨어와 소프트웨어를 넘나드는 실제 제품 경험의 가치를 높이 평가한다. 또 Netflix, Stripe, Amazon 같은 회사들의 문화를 비교하며, 좋은 문화는 보편적 정답이 아니라 사람과의 궁합에 따라 달라진다고 강조한다. 마지막으로 가장 불만인 개념으로 '대중적으로 오해된 product management 정의'를 꼽으며, 이를 사실상 프로젝트 관리로 축소하는 교육·인증 업계를 강하게 비판한다.","insights":["좋은 제품 원칙은 오래가고, 도구와 방법만 빠르게 바뀐다.","실험은 '어떻게'보다 '반드시 해야 한다'가 더 중요하다.","제품 문화는 보편적 우열보다 사람과의 궁합이 핵심이다.","하드웨어는 실패 비용이 커서 오히려 더 많은 실험이 필요하다.","PM을 프로젝트 관리로 축소하면 역할 불만이 구조적으로 커진다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c5:1-22","startSegmentIndex":1,"endSegmentIndex":22,"startTime":3004.549,"endTime":3180.95,"durationSeconds":176.4,"preview":"원칙은 안 바뀐다","mustSee":true},{"clipId":"J0FOFJFtOFw:c5:24-36","startSegmentIndex":24,"endSegmentIndex":36,"startTime":3185.52,"endTime":3272,"durationSeconds":86.5,"preview":"빌드와 제품 철학","mustSee":false},{"clipId":"J0FOFJFtOFw:c5:39-53","startSegmentIndex":39,"endSegmentIndex":53,"startTime":3280.04,"endTime":3404.76,"durationSeconds":124.7,"preview":"문화는 궁합이다","mustSee":false},{"clipId":"J0FOFJFtOFw:c5:56-62","startSegmentIndex":56,"endSegmentIndex":62,"startTime":3422.16,"endTime":3492.23,"durationSeconds":70.1,"preview":"디자인이 제품이다","mustSee":false},{"clipId":"J0FOFJFtOFw:c5:63-73","startSegmentIndex":63,"endSegmentIndex":73,"startTime":3492.23,"endTime":3606.559,"durationSeconds":114.3,"preview":"PM 정의를 바로잡다","mustSee":true}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:19:08.111Z","keyClipsTotalSec":1460},{"videoId":"J0FOFJFtOFw","chunkIndex":6,"totalChunks":7,"title":"Godfather of Product Management: Do THIS! — Part 7 of 7","thumbnail":"https://i.ytimg.com/vi/J0FOFJFtOFw/maxresdefault.jpg","duration":3688,"uploader":"Aakash Gupta","youtubeUrl":"https://www.youtube.com/watch?v=J0FOFJFtOFw","keywords":["product-management","product-operations","leadership","business","career","growth","startup","software","podcast"],"normalizedKeywords":["프로덕트","리더십·매니지먼트","커리어·성장"],"targetAudience":[{"who":"프로덕트 매니저","why":"제품 운영 방식과 PM의 영향력을 드러내는 원칙을 배울 수 있음"},{"who":"창업자","why":"고성과 팀의 제품 운영 모델을 조직에 적용하는 관점을 얻을 수 있음"},{"who":"커리어 탐색자","why":"프로덕트·그로스 분야에서 어떤 역량이 중요한지 감을 잡을 수 있음"}],"normalizedAudience":["프로덕트 매니저·기획자","창업자·스타트업"],"summary":"이 영상은 프로덕트 매니지먼트의 가치를 더 이상 애매하게 보이지 않게 만들고, 고성과 팀이 실제로 따르는 '제품 운영 모델'과 20가지 원칙의 필요성을 강조한다. 좋은 PM은 단순히 일을 조율하는 사람이 아니라, 조직이 그 영향과 성과를 명확히 볼 수 있게 만드는 사람이라는 메시지가 핵심이다.\n\n마지막 구간이라 전체 대화의 마무리와 감사 인사가 중심이지만, 남는 본질은 분명하다. 제품과 그로스 조직은 결과가 보이는 방식으로 일해야 하며, 개인의 경력 측면에서도 이런 원칙과 모델을 이해하는 것이 중요하다는 점을 반복해서 환기한다.","insights":["PM의 가치는 '보이는 영향'으로 증명돼야 한다.","고성과 팀은 직감보다 운영 원칙으로 일한다.","제품 운영 모델은 PM의 역할을 더 명확하게 만든다.","좋은 커리어는 무엇을 아는지보다 어떻게 일하는지에 달린다."],"keyClips":[{"clipId":"J0FOFJFtOFw:c6:7-7","startSegmentIndex":7,"endSegmentIndex":7,"startTime":3644.839,"endTime":3669.68,"durationSeconds":24.8,"preview":"제품운영의 핵심","mustSee":true},{"clipId":"J0FOFJFtOFw:c6:5-5","startSegmentIndex":5,"endSegmentIndex":5,"startTime":3619.4,"endTime":3628.48,"durationSeconds":9.1,"preview":"대화의 마무리","mustSee":false}],"curatedSegments":[{"segmentIndex":3,"text":"Starting at the highest level, the very highest level, it's really all about moving from output to outcomes. The very highest level, it's really all about moving from output to outcomes.","startTime":11.88,"endTime":20.48,"durationSeconds":9,"level":"B2","overallScore":8.6,"rationale":"핵심 원칙을 압축한 통찰 문장."},{"segmentIndex":72,"text":"I see them in feature teams. In fact, they are clear symptoms of feature teams.","startTime":1133.799,"endTime":1140,"durationSeconds":6,"level":"B2","overallScore":8.6,"rationale":"문제의 본질을 단정해 통찰 밀도가 높음."},{"segmentIndex":17,"text":"That is a hard job because fundamentally the product manager, they're responsible for the value and the viability, and that's they take ownership of the outcome.","startTime":1324.4,"endTime":1335.2,"durationSeconds":11,"level":"C1","overallScore":8.8,"rationale":"PM 핵심 책임을 압축해 정의함."},{"segmentIndex":49,"text":"We have to go talk to a lot of customers. I remember the person who was coaching me, wouldn't, as a new product manager, would not let me make a single decision until I visited in person 30 customers, 15 in the US, 15 in Europe.","startTime":1568.24,"endTime":1584.399,"durationSeconds":16,"level":"C1","overallScore":8.8,"rationale":"강한 일화로 고객 접점 중요성 전달."},{"segmentIndex":51,"text":"That was my start of my customer visits. But when you can't do the job of product manager if you don't deeply engage with your users and customers.","startTime":1590.039,"endTime":1599.84,"durationSeconds":10,"level":"B2","overallScore":8.8,"rationale":"PM 필수 조건을 분명히 단언함."},{"segmentIndex":64,"text":"So what I want to help them do is become a real product manager, defining real as how the best companies actually do this. And that means they have to do some work. They have to learn the customers. They have to learn the data. They have to learn the business dimensions.","startTime":1705.399,"endTime":1714.32,"durationSeconds":9,"level":"C1","overallScore":8.8,"rationale":"핵심 기준 제시, 학습 표현도 풍부."},{"segmentIndex":12,"text":"In fact, I tell product leaders that they will be judged by their weakest product managers, so they need to take that personally, and that needs to be their job, their responsibility.","startTime":1889.159,"endTime":1901.639,"durationSeconds":12,"level":"C1","overallScore":8.8,"rationale":"강한 기준과 책임을 제시한 문장."},{"segmentIndex":37,"text":"So the real nuance comes to these product leaders to win over the hearts and minds of the rest of the company, especially the key stakeholders and the key executives, and that takes building trust and sort of being very smart about picking your battles.","startTime":2115.4,"endTime":2134.32,"durationSeconds":19,"level":"C1","overallScore":9,"rationale":"변화 리더십 핵심을 압축해 제시."},{"segmentIndex":41,"text":"So am I. How about we do some experiments together to see if we can't do this better for you, literally for you?","startTime":2165.599,"endTime":2175.76,"durationSeconds":10,"level":"C1","overallScore":9,"rationale":"협업 제안 프레임이 매우 실용적."},{"segmentIndex":46,"text":"Well, in fact, I would argue that the real key to successful transformation... There's a lot of things that have to go right, a lot of things that are hard, but the real key are those product leaders, especially the head of product and the head of engineering.","startTime":2225.48,"endTime":2241.88,"durationSeconds":16,"level":"C1","overallScore":8.6,"rationale":"변화 성공의 핵심 요인을 명시."},{"segmentIndex":41,"text":"And what they're really teaching them is like, okay, you have to use Jira to prioritize a backlog. That's not product. That's administration.","startTime":2716.92,"endTime":2722.76,"durationSeconds":6,"level":"B2","overallScore":9,"rationale":"개념 구분이 선명한 핵심 문장."},{"segmentIndex":65,"text":"I think though the thing that bothers me more than anything else is this, you know, the prevalent definition of product management because I think not only is it not helpful, but I think it's the root reason so many people in that job are not happy. So, that's where the differences, I think, really are.","startTime":3512.119,"endTime":3532.24,"durationSeconds":20,"level":"C1","overallScore":8.8,"rationale":"핵심 문제의 원인을 짚는 통찰적 문장."},{"segmentIndex":7,"text":"We need to move to a way of working where product managers, it's obvious the impact that they're making and how positive that impact is, and we need to move to this product operating model and these 20 principles, because these 20 principles are what's shown to have really worked for high-performing product and growth teams.","startTime":3644.839,"endTime":3669.68,"durationSeconds":25,"level":"C1","overallScore":8.8,"rationale":"원칙·근거를 담은 핵심 통찰 문장."},{"segmentIndex":1,"text":"\"If the first thing they tell me is they release every quarter, I'm like, don't bother me. You're not agile in any sense at all. What are the principles that you've seen in the best companies?","startTime":1.75,"endTime":8.76,"durationSeconds":7,"level":"B2","overallScore":8,"rationale":"애자일 비판과 질문이 담긴 문장."},{"segmentIndex":31,"text":"And so, um, it's hard to, uh, it's hard to get heard above the noise. It's hard. Output is easy.","startTime":189.92,"endTime":200.239,"durationSeconds":10,"level":"B2","overallScore":8,"rationale":"잡음 속 전달 어려움과 핵심 대비."},{"segmentIndex":33,"text":"So if you had to say in one phrase what it's about, changing to delivering outcomes, which, as everybody knows who has even ever tried that, is very hard.","startTime":210.959,"endTime":222.239,"durationSeconds":11,"level":"B2","overallScore":7.8,"rationale":"핵심 개념과 난점을 함께 제시함."},{"segmentIndex":34,"text":"Uh, outcomes is hard. Output is easy.","startTime":222.239,"endTime":225.439,"durationSeconds":3,"level":"B1","overallScore":7.4,"rationale":"핵심 대비가 선명한 통찰 문장."},{"segmentIndex":39,"text":"In other words, the old, you know, one way, which is what's used still in most of the world, is the stakeholders define a bunch of features and projects that they prioritize onto road maps, and the team just knocks them out one after another. What is most important work to do?","startTime":248.64,"endTime":254.4,"durationSeconds":6,"level":"C1","overallScore":8,"rationale":"구식 운영 방식을 구체적으로 비판."},{"segmentIndex":64,"text":"And this is, um, uh, if you want to prove outcomes, you need to make sure you have the data, which means you have to have everything instrumented. You have to have everything monitored.","startTime":462.879,"endTime":471.84000000000003,"durationSeconds":9,"level":"C1","overallScore":8,"rationale":"성과 검증 조건을 명확히 말해 통찰 높음."},{"segmentIndex":66,"text":"It means if you especially if you want to take care of your customers and not hurt your customers, then, uh, which sounds obvious, but this is the difference between being agile and doing agile, right?","startTime":476.44,"endTime":491.159,"durationSeconds":15,"level":"C1","overallScore":8,"rationale":"핵심 대비 통찰과 쓸 만한 표현이 많음."}],"generatedAt":"2026-06-25T00:19:29.628Z","keyClipsTotalSec":1460}]}